<?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 Fault Tolerance| Monitoring | Addressing in Cloud Activation, Architecture &amp; Billing Discussions</title>
    <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2838887#M109</link>
    <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;Please help to my queries below as I didn't find specific in VMC on AWS doc:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; What addressing is allowed inside VMware on cloud? What addressing is used for VMware on cloud hypervisor management interface networks?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Answer:&lt;/STRONG&gt; I believe we can use whatever private network addressing we want on VMware Cloud on AWS to align with my internal existing on-premise networks. Is there any CIDR I have to taken care of?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.&amp;nbsp;&lt;/STRONG&gt;Do we have Bidirectional Forwarding Detection support inside VPN? If yes, then is it under the full control of AWS? What is the switching speed between VPN in case of failure? I didn't find anything specific in VMC doc but I believe it is not less than 30 sec?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3.&amp;nbsp;&lt;/STRONG&gt;Do we have availability of network traffic monitoring (Netflow) for any individual virtual machine, as well as between any several virtual machines within the segment I have allocated?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;</description>
    <pubDate>Tue, 30 Mar 2021 07:06:50 GMT</pubDate>
    <dc:creator>9990374530</dc:creator>
    <dc:date>2021-03-30T07:06:50Z</dc:date>
    <item>
      <title>Fault Tolerance| Monitoring | Addressing</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2838887#M109</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;Please help to my queries below as I didn't find specific in VMC on AWS doc:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; What addressing is allowed inside VMware on cloud? What addressing is used for VMware on cloud hypervisor management interface networks?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Answer:&lt;/STRONG&gt; I believe we can use whatever private network addressing we want on VMware Cloud on AWS to align with my internal existing on-premise networks. Is there any CIDR I have to taken care of?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.&amp;nbsp;&lt;/STRONG&gt;Do we have Bidirectional Forwarding Detection support inside VPN? If yes, then is it under the full control of AWS? What is the switching speed between VPN in case of failure? I didn't find anything specific in VMC doc but I believe it is not less than 30 sec?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3.&amp;nbsp;&lt;/STRONG&gt;Do we have availability of network traffic monitoring (Netflow) for any individual virtual machine, as well as between any several virtual machines within the segment I have allocated?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 07:06:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2838887#M109</guid>
      <dc:creator>9990374530</dc:creator>
      <dc:date>2021-03-30T07:06:50Z</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>
    <item>
      <title>Re: Fault Tolerance| Monitoring | Addressing</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2839145#M111</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Emmanuel,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks for the response. Much appreciated!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I believe in layer 3 VPN, each side of the connection is on a different subnet but in L2 VPN it has to be on same subnet?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PK&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 10:58:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/Fault-Tolerance-Monitoring-Addressing/m-p/2839145#M111</guid>
      <dc:creator>9990374530</dc:creator>
      <dc:date>2021-03-31T10:58:48Z</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>
  </channel>
</rss>

