like2_143's Posts

Re: The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdow

by Contributor in VeloCloud Discussions
‎06-28-2022 05:02 AM
‎06-28-2022 05:02 AM
@marcoh2019Thanks 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. S... See more...
@marcoh2019Thanks 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. 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.

The vEdge on KVM (EVE-NG) lost configuration or unable to communicate with VCO after the Shutdown/Po

by Contributor in VeloCloud Discussions
‎05-24-2022 09:09 AM
‎05-24-2022 09:09 AM
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 o... See more...
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. 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.  I am working on a test lab on EVE-NG/PNETLAB and as we know that EVE-NG/PNETLAB are suing the KVM. -----Cloud.init.iso or cdrom.iso--------- meta-data: instance-id: vEdge local-hostname: vEdge network-interfaces: GE3: type: static ipaddr: 192.168.100.111 netmask: 255.255.255.0 gateway: 192.168.100.240 user-data: #cloud-config password: velocloud chpasswd: { expire: False } ssh_pwauth: True Thanks and Regards