<?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 The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdown/Po in VeloCloud Discussions</title>
    <link>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2910886#M9</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I have successfully initiated the Virtual VeloCloud Edge on KVM (EVE-NG). The vEdge is provisioned to the VCO. But the edge lost configuration or is unable to communicate with VCO after Turning off or shutting down the vEdge. Power ON the vEdge, the vEdge boot is in the factory default setting.&amp;nbsp;The issue is that when I turn Off the vEdge and turn On again, the vEdge boot in the default configuration needs to activate again.&amp;nbsp;&amp;nbsp;I am working on a test lab on EVE-NG/PNETLAB and as we know that EVE-NG/PNETLAB are suing the KVM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----Cloud.init.iso or cdrom.iso---------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;meta-data:&lt;BR /&gt;instance-id: vEdge&lt;BR /&gt;local-hostname: vEdge&lt;BR /&gt;network-interfaces:&lt;BR /&gt;GE3:&lt;BR /&gt;type: static&lt;BR /&gt;ipaddr: 192.168.100.111&lt;BR /&gt;netmask: 255.255.255.0&lt;BR /&gt;gateway: 192.168.100.240&lt;/P&gt;&lt;P&gt;user-data:&lt;BR /&gt;#cloud-config&lt;BR /&gt;password: velocloud&lt;BR /&gt;chpasswd: { expire: False }&lt;BR /&gt;ssh_pwauth: True&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;/P&gt;</description>
    <pubDate>Tue, 24 May 2022 16:09:43 GMT</pubDate>
    <dc:creator>like2_143</dc:creator>
    <dc:date>2022-05-24T16:09:43Z</dc:date>
    <item>
      <title>The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdown/Po</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2910886#M9</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I have successfully initiated the Virtual VeloCloud Edge on KVM (EVE-NG). The vEdge is provisioned to the VCO. But the edge lost configuration or is unable to communicate with VCO after Turning off or shutting down the vEdge. Power ON the vEdge, the vEdge boot is in the factory default setting.&amp;nbsp;The issue is that when I turn Off the vEdge and turn On again, the vEdge boot in the default configuration needs to activate again.&amp;nbsp;&amp;nbsp;I am working on a test lab on EVE-NG/PNETLAB and as we know that EVE-NG/PNETLAB are suing the KVM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----Cloud.init.iso or cdrom.iso---------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;meta-data:&lt;BR /&gt;instance-id: vEdge&lt;BR /&gt;local-hostname: vEdge&lt;BR /&gt;network-interfaces:&lt;BR /&gt;GE3:&lt;BR /&gt;type: static&lt;BR /&gt;ipaddr: 192.168.100.111&lt;BR /&gt;netmask: 255.255.255.0&lt;BR /&gt;gateway: 192.168.100.240&lt;/P&gt;&lt;P&gt;user-data:&lt;BR /&gt;#cloud-config&lt;BR /&gt;password: velocloud&lt;BR /&gt;chpasswd: { expire: False }&lt;BR /&gt;ssh_pwauth: True&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 16:09:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2910886#M9</guid>
      <dc:creator>like2_143</dc:creator>
      <dc:date>2022-05-24T16:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdow</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2914319#M12</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2059995"&gt;@like2_143&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please confirm that after the vEdge is powered on, the vEdge has internet connectivity? (try to ping 8.8.8.8 or 8.8.4.4, depending on your environment) and if so, could you please confirm if the Edge is being activated?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have console/SSH access to the vEdge, please execute the following command:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&amp;nbsp;activate.py -s &amp;lt;VCO URL&amp;gt; -i &amp;lt;Activation Key&amp;gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;MarcoHB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 15:47:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2914319#M12</guid>
      <dc:creator>marcoh2019</dc:creator>
      <dc:date>2022-06-15T15:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdow</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2916325#M19</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/4172079"&gt;@marcoh2019&lt;/a&gt;Thanks for your response. Yes, the Edge has internet access and is also reachable to VCO and VCF after being powered on. As I mentioned, needed to reactivate the vEdge after powered on.&lt;/P&gt;&lt;P&gt;Someone suggested me to disable the Cloud-init once the edge is activated but i don't know to disable it and also i am not sure this will resolve my issue.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 12:02:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/The-vEdge-on-KVM-EVE-NG-lost-configuration-or-unable-to/m-p/2916325#M19</guid>
      <dc:creator>like2_143</dc:creator>
      <dc:date>2022-06-28T12:02:07Z</dc:date>
    </item>
  </channel>
</rss>

