Versafvnf cannot be found ??

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
dragonfly
Posts: 9
Joined: Tue Oct 16, 2018 7:50 pm

Versafvnf cannot be found ??

Post by dragonfly » Wed Mar 24, 2021 5:16 pm

* Eve Platform - 2.0.3-92

* virtioa.qcow2 {File arrived in that format}

* https://www.eve-ng.net/index.php/docume ... ks-sd-wan/


I have followed the guide above ( URL) & all seemed well, but when it came to searching for the VNF Edge device, it failed to appear within the drop downlist.

Meanwhile I upgraded the platform to 2.0.3-92, with no problems, I believe.

So my question is why is it that I cannot see the device in question ? Is the file corrupted is there any way to test this notion ?

The file virtioa.qcow2 sits here:
/opt/unetlab/addons/qemu/versafvnf-16.1
Admittedly I do not know what version virtioa.qcow2 is..


HELP!!

Uldis (UD)
Posts: 5180
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Versafvnf cannot be found ??

Post by Uldis (UD) » Thu Mar 25, 2021 8:28 am

Upgrade EVE
Versa is supported on latest EVE

dragonfly
Posts: 9
Joined: Tue Oct 16, 2018 7:50 pm

Re: Versafvnf cannot be found ??

Post by dragonfly » Tue Mar 30, 2021 12:28 pm

Thanks Uldis

## Side Note;

https://www.eve-ng.net/index.php/1845-2 ... x-to-v3-x/

If you have v2-x & expereience this whilst performing

apt upgrade

Use this link; https://askubuntu.com/questions/163200/ ... onfigure-a


E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

This error is actually telling you exactly what is wrong: dpkg was interrupted as a result the package was not configured correctly.

Run the command it tells you to sudo dpkg --configure -a and it should be able to correct itself.

If it doesn't try running sudo apt-get install -f (to fix broken packages) and then try running sudo dpkg --configure -a again.

Post Reply