<?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>ebernard Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>ebernard Tracker</description>
    <pubDate>Wed, 15 Nov 2023 15:04:00 GMT</pubDate>
    <dc:date>2023-11-15T15:04:00Z</dc:date>
    <item>
      <title>What's New on VMware Cloud on AWS: April 5, 2022 (SDDC v1.18 Release)</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-New-on-VMware-Cloud-on-AWS-April-5-2022-SDDC-v1-18/m-p/2903250#M184</link>
      <description>&lt;P&gt;Another major release with this latest update that includes a lot of improvements and new features especially at the network level!&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;VMware Cloud on AWS Multi CGW&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;​&lt;/STRONG&gt;This feature enables customers to create additional CGWs (Compute Gateways or Tier-1 Gateways) and manage the life cycle for those CGWs. Customer managed CGWs can be created as Routed, NAT'ed or Isolated CGWs. This feature will support addition of static routes, route aggregation, filtering, local DHCP server or DNS forwarding, and Traceflow. This feature will enable the following use cases:&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;Multi-tenancy within an SDDC&lt;/LI&gt;
&lt;LI&gt;Overlapping IPv4 address space across CGWs&lt;/LI&gt;
&lt;LI&gt;Gateway Firewall/ NAT scoped to individual CGWs&lt;/LI&gt;
&lt;LI&gt;Support for static routes on customer managed CGW&lt;/LI&gt;
&lt;LI&gt;Access to the Connected VPC from&amp;nbsp;customer managed CGW&lt;/LI&gt;
&lt;LI&gt;Deployment of Isolated test 'segments’ for Disaster Recovery (DR) testing or “sandbox” environments.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;For more information, please see&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://blogs.vmware.com/cloud/2022/04/06/vmware-cloud-on-aws-advanced-networking-and-routing-features/" target="_blank" rel="noopener noreferrer" name="&amp;amp;lpos=Release Notes_content link : 220" aria-describedby="sk-tooltip-182" data-sk="tooltip_parent" data-stringify-link="https://blogs.vmware.com/cloud/2022/04/06/vmware-cloud-on-aws-advanced-networking-and-routing-features/"&gt;https://blogs.vmware.com/cloud/2022/04/06/vmware-cloud-on-aws-advanced-networking-and-routing-features/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Route Aggregation for&amp;nbsp;Advertisement over&amp;nbsp;Direct Connect &amp;amp; Transit Connect&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;VMware Cloud on AWS support for AD/LDAP&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Tanzu Kubernetes Grid (TKG) Services&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Customers can now enable Tanzu Kubernetes Grid (TKG) Services on existing SDDCs and clusters on VMware Cloud on AWS and VMware Cloud on Dell EMC. There is no longer a need to create new SDDCs or new Clusters, allowing customers to leverage their existing environments.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For more details please read the release notes here:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 12:54:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-New-on-VMware-Cloud-on-AWS-April-5-2022-SDDC-v1-18/m-p/2903250#M184</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2022-04-08T12:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: VMC / DHCP server on segment not working with DFW. I need correct rule</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-DHCP-server-on-segment-not-working-with-DFW-I-need-correct/m-p/2899929#M334</link>
      <description>&lt;P&gt;Hello Sebastian&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please explain what are you looking to achieve?&amp;nbsp;&lt;BR /&gt;You have an on-premises DHCP server that will be leveraged by many segments on VMC with Relay DHCP, right?&lt;/P&gt;
&lt;P&gt;thank you&lt;BR /&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2022 15:07:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-DHCP-server-on-segment-not-working-with-DFW-I-need-correct/m-p/2899929#M334</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2022-03-22T15:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: TKG 1.4 Management cluster deployment on AWS fails</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/TKG-1-4-Management-cluster-deployment-on-AWS-fails/m-p/2899922#M333</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;I do recommend you to open a ticket within the Cloud console or ask to a Customer success team member from the console (on the top right with question mark) that'd be more convenient for you.&lt;BR /&gt;Do not hesitate to keep us updated&lt;/P&gt;
&lt;P&gt;Cheers&lt;BR /&gt;Emmanuel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2022 14:54:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/TKG-1-4-Management-cluster-deployment-on-AWS-fails/m-p/2899922#M333</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2022-03-22T14:54:10Z</dc:date>
    </item>
    <item>
      <title>VMware Cloud on AWS What's new at AWS re:Invent</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMware-Cloud-on-AWS-What-s-new-at-AWS-re-Invent/m-p/2882190#M160</link>
      <description>&lt;P&gt;After VMworld on October, VMware Cloud made a lot of announcements during re:Invent, AWS' annual conference.&lt;/P&gt;
&lt;P&gt;We have released more than 300 features since this Cloud service is GA, we've released 17 major versions and service is now available on 19 AWS regions to satisfy our customer needs while they want to accelerate their Cloud journey.&lt;/P&gt;
&lt;P&gt;You can find all details about these announcements here:&amp;nbsp;&lt;A href="https://blogs.vmware.com/cloud/2021/12/01/vmware-cloud-on-aws-going-big-reinvent2021/" target="_blank"&gt;https://blogs.vmware.com/cloud/2021/12/01/vmware-cloud-on-aws-going-big-reinvent2021/&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;Briefly, we've added external storage capabilities, discount for 3 nodes purchasing, etc....&lt;/P&gt;
&lt;P&gt;Enjoy this reading and do not hesitate to contact your local VMware contact.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 14:56:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMware-Cloud-on-AWS-What-s-new-at-AWS-re-Invent/m-p/2882190#M160</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-12-08T14:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: aws eks cluster</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/aws-eks-cluster/m-p/2880526#M319</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please elaborate more about your issue?&lt;/P&gt;
&lt;P&gt;You're talking about AWS EKS cluster right? What are you looking to achieve?&lt;BR /&gt;If you can give us more details, I'd be more than happy to help you&lt;/P&gt;
&lt;P&gt;thank you&lt;/P&gt;
&lt;P&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 17:45:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/aws-eks-cluster/m-p/2880526#M319</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-11-29T17:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: VMC on AWS ADD-ON</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMC-on-AWS-ADD-ON/m-p/2861964#M147</link>
      <description>&lt;P&gt;Hi PK&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As the screen shows, vRli is included in a “light” version that offers 1 Gb of log traffic per day and a 7 days of logs retention.&lt;/P&gt;
&lt;P&gt;if you want to go beyond these limits you can subscribe to this add-on that provides all capabilities.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;cheers&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Emmanuel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 08:31:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMC-on-AWS-ADD-ON/m-p/2861964#M147</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-08-13T08:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: HCX on prem to VMC issue</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/HCX-on-prem-to-VMC-issue/m-p/2861475#M143</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;First of all, can I Ask you if you strictly followed pre requisites regarding ports by having a look here:&amp;nbsp;&lt;A href="https://ports.vmware.com/home/VMware-HCX" target="_blank"&gt;https://ports.vmware.com/home/VMware-HCX&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have also the ability to chat with Support and eventually open a ticket through the chat window from the Cloud Console by clicking on "?"&lt;BR /&gt;Is this a POC or a project with a customer? &lt;BR /&gt;Are you already in contact with a VMware Cloud on AWS team member in your country?&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Tue, 10 Aug 2021 14:31:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/HCX-on-prem-to-VMC-issue/m-p/2861475#M143</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-08-10T14:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: question about hosting on AWS</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/question-about-hosting-on-AWS/m-p/2861473#M142</link>
      <description>&lt;P&gt;Hi RadarG&lt;/P&gt;
&lt;P&gt;Your question generates questions! &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;
&lt;P&gt;First, when you mean AWS, do you mean native AWS (EC2, EBS..) or our VMware Cloud on AWS Service?&lt;/P&gt;
&lt;P&gt;Just to say that, 1st option can run only workloads in native AWS mode, you don't have the ability to run our VMware hypervisor (vSphere) on top of AWS servers, on your own. Either you choose to transform your current VMware workloads to run on AWS native services OR you choose to adopt VMware Cloud on AWS (aka VMC).&lt;/P&gt;
&lt;P&gt;In this case, you have access to a VMware environment (VMware Cloud Foundation), fully automated and deployed by VMware running on AWS infrastructure (servers) and datacenters among 18 Regions.&lt;BR /&gt;Pricing is per host and you can purchase this service in On demand model (pay per hour) for a couple of hours, days or weeks... or if you plan to run it longer you can purchase it in "Reserved instances" mode, with a commitment on your side in term of duration but you will save you money compared to "On demand" mode.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;So, about your statement about higher price, it's quite tricky to answer because as explained above we are providing an entire host that can run many VMs and you are totally free to choose consolidation ratio (10 VMs, 20, 40, 50 VMs per host...) while with AWS native services to pay at VM and resources level which is totally different.&amp;nbsp;&lt;BR /&gt;You can start to deploy VMC with 2 nodes to build a cluster and get something ready for production. You have also the ability to start with a single node but as this is not for production, it will be stopped after 30 days.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;That's a topic which requires a lot of discussions and that deserves to work on.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Hope that helped you to understand differences &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;BR /&gt;&lt;BR /&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Tue, 10 Aug 2021 14:33:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/question-about-hosting-on-AWS/m-p/2861473#M142</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-08-10T14:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: Radware Alteon LB on VMC</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Radware-Alteon-LB-on-VMC/tac-p/2855225#M31</link>
      <description>&lt;P&gt;+1 on Pablo.&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit; color: #000000;"&gt;Just to add on this, in the future if you have any question about 3rd party solutions and VMware Cloud on AWS (or any other product/service) go to Marketplace:&amp;nbsp;&lt;A href="https://marketplace.cloud.vmware.com/services/?certifications=Partner%20Ready%20VMware%20Cloud%20on%20AWS" target="_blank"&gt;https://marketplace.cloud.vmware.com/services/?certifications=Partner%20Ready%20VMware%20Cloud%20on%20AWS&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit; color: #000000;"&gt;Hope that helps&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit; color: #000000;"&gt;Emmanuel&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2021 15:17:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Radware-Alteon-LB-on-VMC/tac-p/2855225#M31</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-30T15:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: Hybrid Cloud Readiness Assessment Service</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Hybrid-Cloud-Readiness-Assessment-Service/m-p/2853515#M136</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I think you are talking about an exam which is part of the Master Service Competency for VMware Cloud on AWS. This is part of a certification for our partner.&lt;/P&gt;
&lt;P&gt;If you're a partner, please see with your local VMware contact from the Partner team.&lt;/P&gt;
&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jun 2021 17:39:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Hybrid-Cloud-Readiness-Assessment-Service/m-p/2853515#M136</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-18T17:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: VMC (NSX-T) and "service insertion"</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMC-NSX-T-and-quot-service-insertion-quot/m-p/2853477#M134</link>
      <description>&lt;P&gt;Hi Sebastian,&lt;BR /&gt;&lt;BR /&gt;Thank you for your question, indeed this is an important topic.&lt;BR /&gt;&lt;BR /&gt;Lei asked to our Product Management team but since this is holiday time in US, let me just give you some inputs regarding your question:&lt;BR /&gt;&lt;BR /&gt;Service insertion was initially planned to embed 3rd party security features within VMC, it was 2 or 3 years ago as the AWS article is showing. But in the meanwhile some events appeared: we switched from NSX-V to NSX-T and we acquired companies and enhance NSX features.&lt;/P&gt;
&lt;P&gt;So, based on these events, VMware has decided to choose another option, at least for the mid-term:&lt;/P&gt;
&lt;P&gt;- Enhance NSX features into VMC (like in the latest release with L7, IDS-IPS, identity firewall)&lt;/P&gt;
&lt;P&gt;- let our customer choose another security vendor by leveraging AWS services (ALB, ELB, 3rd party firewall in marketplace)&amp;nbsp;&lt;A href="https://cloud.vmware.com/community/2020/06/08/integrating-aws-application-load-balancing-vmware-cloud-aws/" target="_blank"&gt;https://cloud.vmware.com/community/2020/06/08/integrating-aws-application-load-balancing-vmware-cloud-aws/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;- or for larger environment including many VPC's or SDDC's, leverage in 1st case a Transit Gateway:&amp;nbsp;&lt;A href="https://blogs.vmware.com/networkvirtualization/2020/06/vmware-cloud-on-aws-with-transit-gateway-demo.html/" target="_blank"&gt;https://blogs.vmware.com/networkvirtualization/2020/06/vmware-cloud-on-aws-with-transit-gateway-demo.html/&lt;/A&gt; or build a Transit Connect in 2nd case:&amp;nbsp;&lt;A href="https://blogs.vmware.com/networkvirtualization/2020/09/vmware-transit-connect-simplifying-networking-for-vmc.html/" target="_blank"&gt;https://blogs.vmware.com/networkvirtualization/2020/09/vmware-transit-connect-simplifying-networking-for-vmc.html/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope these details are clear and are fully addressing your question!&lt;BR /&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jun 2021 13:47:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/VMC-NSX-T-and-quot-service-insertion-quot/m-p/2853477#M134</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-18T13:47:23Z</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>
    <item>
      <title>What's new on VMware Cloud on AWS: June 15th (SDDC v1.15): MAJOR release</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-new-on-VMware-Cloud-on-AWS-June-15th-SDDC-v1-15-MAJOR/m-p/2853195#M128</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Just before summer time our VMware Cloud BU delivered a major SDDC release (v1.15) with huge improvements and new features to enhance networking performance, enable cross regions connectivity, add security features like IDS/IPS, identity based firewall,....&lt;/P&gt;&lt;P&gt;Kudos to the developer team!&lt;/P&gt;&lt;P&gt;Here's the complete list below and to be regularly updated, don't forget to read our release notes page here: &lt;A title="VMC Release Notes" href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html" target="_blank" rel="noopener"&gt;link&lt;/A&gt;&lt;/P&gt;&lt;P&gt;New Features for VMware Cloud on AWS: SDDC v1.15&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;VMware Transit Connect/&amp;nbsp;SDDC Group connectivity to Transit VPC&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;VMware&amp;nbsp;Transit Connect enhancement to enable Transit VPC connectivity. VMware Transit Connect customers can configure a static route for a VPC attachment in the same AWS region. This capability becomes immediately available to all SDDC Group deployments (compatible with SDDC version 1.12 and above).&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;VMware Transit Connect/&amp;nbsp;SDDC Group connectivity&amp;nbsp;across regions&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;SDDC Groups can now be expanded across regions. Customers can select SDDCs in more than one region for an SDDC Group. VMware Transit Connect provides automatic provisioning and connectivity for SDDCs Group members across multiple regions. This provides high bandwidth connectivity for SDDC to SDDC communication across regions.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;VMware NSX®&amp;nbsp;Advanced Firewall for VMware Cloud on AWS&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;VMware Cloud on AWS introduces major security capabilities. NSX Advanced Firewall includes NSX Distributed IDS/ IPS, NSX Identity Firewall and&amp;nbsp;Distributed Firewall Layer7 with Application Identification and&amp;nbsp;FQDN Filtering.&amp;nbsp;Available as an Add-on for SDDC version 1.15.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;NSX Distributed IDS/ IPS&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;VMware NSX Distributed IDS/IPS is an intrusion detection and prevention system for SDDC network traffic.&amp;nbsp;Customers can detect and prevent lateral threats to workloads using curated threat signatures and apply rules at the relevant VM level. Distributed IDS/IPS&amp;nbsp;utilizes threat signatures updated by the VMware NSX Threat Intelligence Service.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;NSX Distributed Firewall Layer7 with Application Identification and&amp;nbsp;FQDN Filtering&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Customers can apply stateful layer 7 access controls and filtering.&amp;nbsp;The Distributed Firewall is built with L7 application profiles (L7 Application IDs) for common enterprise applications.&amp;nbsp;Customers can also define specific FQDNs that are allowed or denied access to applications in the SDDC.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;NSX Identity Firewall&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Distributed Firewall integrates with Active Directory to provide User Identification rules. Customers can utilize Active Directory Groups to define distributed firewall rules to control access to workloads and applications such as virtual desktops (VDI) in SDDCs.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;vSphere Distributed Switch (VDS)&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;VMware Cloud on AWS ESXi hosts will use the vSphere Distributed switch (VDS) for networking, replacing the current NSX-T Virtual distributed Switch (NVDS). The VDS switch will be introduced in SDDC version&amp;nbsp;1.15.&amp;nbsp;Customers can opt-in to use VDS in 1.15.&amp;nbsp;Please chat with the Support team or open an SR to get access to this feature.&lt;/LI&gt;&lt;LI&gt;Future deployments&amp;nbsp;starting with version 1.16 will use VDS. Existing&amp;nbsp;deployments&amp;nbsp;will be converted to VDS prior to 1.18 upgrade.&lt;/LI&gt;&lt;LI&gt;The vSphere Web Services API Opaque Network objects will be converted to NSX DistributedVirtualPortGroup (DVPG) objects. The corresponding API parameters/ return values are changing, therefore customers need to update applications that are using these API calls.&amp;nbsp;vSphere Opaque Network objects will not be supported beyond 1.16.&lt;/LI&gt;&lt;LI&gt;For more details, please refer to the KB&amp;nbsp;&lt;A title="https://kb.vmware.com/s/article/82487" href="https://kb.vmware.com/s/article/82487" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/82487&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Local User Management in PCI&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;It provides the ability to add local users to NSX Manager in order to allow users to operate the SDDC in environments that don't use CSP to authenticate users.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Networking performance improvement for i3EN hosts&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;This release incorporates improvements for i3EN.metal (approximately 50% higher packet processing compared to the previous release). Customers can realize higher throughput for their workloads, depending upon the specific application network profile.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;VMC Networking UI in standalone mode with CSP Authentication&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Using CSP credentials, VMC users would be able to authenticate to Networking UI in standalone mode. This will enable private access to Networking UI from on-prem over Direct Connect, Transit Connect or VPN.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;VMware Cloud on AWS Networking enhancements.&amp;nbsp;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Enhancements to minimize data plane impact due to planned edge failover events.&lt;/STRONG&gt;&amp;nbsp;Communication over Transit Connect/ Connect VPC is affected for sub-second duration.&amp;nbsp;Communication over Direct&amp;nbsp;Connect/ VPN is affected for less than 10 seconds due to&amp;nbsp;planned edge failover event.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Enable RPF on a per interface Basis.&lt;/STRONG&gt;&amp;nbsp;This will allow the customer to enable/disable/change Reverse Path Forwarding (RPF) on the Intranet and Services Interface.&amp;nbsp; This will enable customers who have asymmetric routing in their environment to control the RPF behavior on these interfaces.&lt;/LI&gt;&lt;LI&gt;This release also optimizes communication from VM to Edge on the same host, which benefits VDI workloads.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 10:33:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-new-on-VMware-Cloud-on-AWS-June-15th-SDDC-v1-15-MAJOR/m-p/2853195#M128</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-17T10:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: Create SDDC Old Release</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Create-SDDC-Old-Release/m-p/2851479#M127</link>
      <description>&lt;P&gt;Hi Terry,&lt;/P&gt;&lt;P&gt;Release are automatically pushed and rolled out in phases among regions, so you don't have the ability to choose an older version of SDDC.&lt;/P&gt;&lt;P&gt;If I may ask, why do you need to test and older SDDC version as we do offer full compatibility and we take care of patching/upgrading the SDDC layer?&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Emmanuel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jun 2021 07:55:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Create-SDDC-Old-Release/m-p/2851479#M127</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-08T07:55:17Z</dc:date>
    </item>
    <item>
      <title>Re: VMC High Availability</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-High-Availability/m-p/2851030#M306</link>
      <description>&lt;P&gt;Hi PK,&lt;/P&gt;
&lt;P&gt;Glad to see you again here!&lt;/P&gt;
&lt;P&gt;Please find my answers below:&lt;/P&gt;
&lt;P&gt;1) Clusters start at 2 nodes and max is 16 hosts&lt;/P&gt;
&lt;P&gt;2) If you plan to deploy 17 nodes based on your requirements, I do recommend to split into 2 clusters (ie: 9 and 8 that will let you enough room to add hosts in the future if needed, in each cluster.&lt;/P&gt;
&lt;P&gt;3) When you deploy your cluster, a storage policy (VSAN protection level, FTT)&amp;nbsp; is applied based on number of nodes, please see:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;4) If 2 hosts in a cluster in FTT=2, yes we will support and guarantee SLA if this applies to. Basically you look at the table and knowing which FTT you do want, you choose number of hosts.&lt;/P&gt;
&lt;P&gt;5) If you split into many clusters (like for example 2), of course, SLA are at cluster level.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;if you want to change storage policy you can read this:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-F52F0AE9-FB31-4236-B566-D9610B14C670.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-F52F0AE9-FB31-4236-B566-D9610B14C670.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;6) vSphere HA is of course available in VMC and if an hosts fails we will replace it automatically and evacuate VMs from failed hosts. This is what we call "Host remediation". This is provided by default, with no additional fees.&lt;/P&gt;
&lt;P&gt;Hope that answered to your questions and I can warmly recommend to contact your local VMware team to address all your questions in&amp;nbsp; the future as it will bring you an easier way to understand the service and all his mechanisms.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jun 2021 13:35:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-High-Availability/m-p/2851030#M306</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-04T13:35:56Z</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>What's new on VMware Cloud on AWS: April 30th release</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-new-on-VMware-Cloud-on-AWS-April-30th-release/m-p/2845373#M116</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Here's a new release with some nice features:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Tanzu Application Service 2.11 Support&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Tanzu Application Service v2.11 is now supported on VMware Cloud on AWS.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Tanzu Kubernetes Grid (TKG) Management Cluster Registration with Tanzu Mission Control&lt;/STRONG&gt;&lt;STRONG&gt;​&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Tanzu Mission Control now supports the ability to&amp;nbsp;register Tanzu Kubernetes Grid (1.2 &amp;amp; later) management clusters running on&amp;nbsp;&lt;EM&gt;VMware Cloud on AWS&lt;/EM&gt;.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Automatic Partition Placement Group Retrofit&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;A fully automated background process to retrofit existing clusters with&amp;nbsp;&lt;A title="https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html#wn07132020" href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html#wn07132020" target="_blank" rel="noopener"&gt;Partition Placement Groups&lt;/A&gt;&amp;nbsp;(PPG).&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;VMware Cloud Sizer Launchpad Integration&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;The VMware Cloud Sizer has been added to the VMware Cloud Launchpad to make it easier for customers to find and size VMware Cloud deployments.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Single host to 2-host scale-up&amp;nbsp;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Single host SDDC's can now be non-disruptively scaled up to a 2-host SDDC. This process adds resiliency and full SLA support allowing the SDDC to exist beyond 30-days.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;More details here &lt;A href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html#wn09430020" target="_blank"&gt;https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html#wn09430020&lt;/A&gt; and do not hesitate to visit this page on a regular basis.&lt;/P&gt;&lt;P&gt;Enjoy!&lt;/P&gt;</description>
      <pubDate>Tue, 04 May 2021 13:56:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/What-s-new-on-VMware-Cloud-on-AWS-April-30th-release/m-p/2845373#M116</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-05-04T13:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Fault Tolerance| Monitoring | Addressing</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2842276#M114</link>
      <description>&lt;P&gt;Hi PK,&lt;/P&gt;&lt;P&gt;Yes, you're right:&lt;BR /&gt;- L3 VPN means routing, so different subnets&lt;BR /&gt;- L2 means switching, so similar subnets on both side&lt;BR /&gt;&lt;BR /&gt;Both are available with VMC:&lt;BR /&gt;- L3 VPN with your usual endpoint on premise (from any vendor)&lt;BR /&gt;- L2 based on a NSX Edge standalone client available for download from VMC console.&lt;BR /&gt;And don't forget that HCX, provided with VMC has also the ability to do L2 Extension by extending your distributed virtual switch (aka dVS)&lt;/P&gt;&lt;P&gt;hope that helped&lt;/P&gt;&lt;P&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 16:56:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2842276#M114</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-04-16T16:56:12Z</dc:date>
    </item>
    <item>
      <title>New VMC on AWS Feature: Elastic DRS Rapid Scale-Out policy</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/New-VMC-on-AWS-Feature-Elastic-DRS-Rapid-Scale-Out-policy/m-p/2841414#M113</link>
      <description>&lt;P&gt;Imagine you need to add many hosts in a very short time to handle a Disaster Recovery with VCDR for example or to receive hundreds of Virtual Desktops with Horizon : you have now the ability to add up to 12 hosts in parallel with this Elastic DRS enhancement called Rapid Scale out!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;With Elastic DRS Rapid Scale out you can deploy up to 12 hosts only in 40 minutes!!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;More details in this VMware blog post:&amp;nbsp;&lt;A href="https://cloud.vmware.com/community/2021/04/05/enhancement-elastic-drs-rapid-scale-policy-vmware-cloud-aws/" target="_blank" rel="noopener"&gt;https://cloud.vmware.com/community/2021/04/05/enhancement-elastic-drs-rapid-scale-policy-vmware-cloud-aws/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Official doc here:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-961C4B32-6093-4C2E-AFE5-5B1F56BF4EEE.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-961C4B32-6093-4C2E-AFE5-5B1F56BF4EEE.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enjoy!&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 22:51:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/New-VMC-on-AWS-Feature-Elastic-DRS-Rapid-Scale-Out-policy/m-p/2841414#M113</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-04-12T22:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: Fault Tolerance| Monitoring | Addressing</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2839093#M110</link>
      <description>&lt;P&gt;Hi PK,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find my answers below, I hope that will help you :&lt;/P&gt;&lt;P&gt;1) You can use whatever network CIDR you want, you have a full freedom to choose anyone. Of course, if you want to interconnect with your on premise environment thru a VPN you have to choose accordingly to avoid IP overlap.&lt;/P&gt;&lt;P&gt;To be more precise, you have 2 different parts into VMC: First is the management part that VMware is responsible for and where vCenter, ESXi hosts and NSX appliances will be deployed: you choose any RFC1918 CIDR.&lt;BR /&gt;And on the other side you have your Compute environment where you will deploy your workloads and you can create any private IP network/subnets as described above.&lt;/P&gt;&lt;P&gt;2) For BFD I don't know if we do support it on our VPN. So, in this case, let me ask you if it's about L3 or L2 VPN?&lt;BR /&gt;We do support resilience on our VPN: both L3 and L2. Maybe someone else can answer to your switching speed?&lt;/P&gt;&lt;P&gt;3) you can use Netflow or IPFIX and can do port mirroring if needed, see:&amp;nbsp;&lt;A href="https://cloud.vmware.com/community/2019/04/25/port-mirroring-vmware-cloud-aws/" target="_blank"&gt;https://cloud.vmware.com/community/2019/04/25/port-mirroring-vmware-cloud-aws/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Emmanuel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 23:20:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2839093#M110</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-03-30T23:20:40Z</dc:date>
    </item>
  </channel>
</rss>

