Versions this guide is based on:
EVE Image Foldename | Downloaded Filename | Version | vCPUs | vRAM | Console | NIC Type | QEMU version |
---|---|---|---|---|---|---|---|
nd-9.2.3.1c | nd-dk9.2.3.1c.qcow2 | 2.3.1c | 16 | 49152M | vnc | 2x e1000 | 5.2.0 |
Instructions |
---|
NOTE: If you have the EVE Professional v5.0.20 or Community v5.0.19 or earlier, you have to update your EVE templates, and icons.Obtain Nexus Dashboad template and icon. Please follow the link before you start deploy Nexus dashboard! GIT Update for templates, icons and config scripts Other versions also are supported following bellow’s procedure. Successfuly tested, 2.1 and 2.2. Steps below are based on Nexus Dashboard 2.3.1c version deployment, for other image versions, use proper names respectively.1. SSH to EVE and login as root, from cli and create image directory on the EVE’s /opt/unetlab/addons/qemu: mkdir /opt/unetlab/addons/qemu/nd-2.3.1c
cd /opt/unetlab/addons/qemu/nd-2.3.1c
2. Upload the downloaded KVM nd-dk9.2.3.1c.qcow2 image to the EVE using for example FileZilla or WinSCP. 3. Rename it to: virtioa.qcow2 cd /opt/unetlab/addons/qemu/nd-2.3.1c mv nd-dk9.2.3.1c.qcow2 virtioa.qcow2 4. Create second HDD virtiob.qcow2 for ND image : /opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 500G root@eve-ng:/opt/unetlab/addons/qemu/nd-2.3.1c# ls virtioa.qcow2 virtiob.qcow2 5. Fix permissions: /opt/unetlab/wrappers/unl_wrapper -a fixpermissions ND Image is created and ready to use. Refresh your browser and now you can open lab and your image will be visible under nodes Cisco Nexus Dashboard (ND) |