Versions this guide are based on:
| EVE Image Foldername | Downloaded Filename | Version | vCPUs | vRAM | Interfaces |
|---|---|---|---|---|---|
| vtbond-19.2.3 | viptela-edge-19.2.3-genericx86-64.qcow2 | 19.2.3 | 1 | 1024 | 2 |
| vtedge-19.2.3 | viptela-edge-19.2.3-genericx86-64.qcow2 | 19.2.3 | 1 | 1024 | 5-8 |
| vtsmart-19.2.3 | viptela-smart-19.2.3-genericx86-64.qcow2 | 19.2.3 | 2 | 2048 | 2 |
| vtmgmt-19.2.3 | viptela-vmanage-19.2.3-genericx86-64.qcow2 | 19.2.3 | 4 | 16384 | 2 |
Note: For Viptela version 20.x use same steps as below, just use for image foldernames version number respectively.
Example: vtmgmt-20.3.2, vtsmart-20.3.2, vbond-20.3.2, vtedge-20.3.2
vManage node version 20.x and later require 24Gb of RAM.
vManage node Catalyst bases version 20.12 and later require 32Gb of RAM.
| Instructions |
|---|
| Steps below are based on Viptela 19.2.3 deployment, for other image deployment, use proper names respectively. You Have to use your own cisco CCO to download images and obtain demo licences.
Note: Viptela vBond and vEdge are using same image: viptela-edge-19.2.3-genericx86-64.qcow2 1. Deployment of Cisco Viptela vBond 19.2.3 image Step 1. SSH to EVE and login as root, from cli and create temporary working directory on the EVE’s root: mkdir /opt/unetlab/addons/qemu/vtbond-19.2.3
Step 2. Upload the downloaded viptela-edge-19.2.3-genericx86-64.qcow2 image to the /opt/unetlab/addons/qemu/vtbond-19.2.3 using FileZilla or WinSCP. Step 3. Go to image location and rename uploaded image to virtioa.qcow2: cd /opt/unetlab/addons/qemu/vtbond-19.2.3
mv viptela-edge-19.2.3-genericx86-64.qcow2 virtioa.qcow2
cd
2. Deployment of Cisco Viptela vEdge 19.2.3 image Step 1. SSH to EVE and login as root, from cli and create temporary working directory on the EVE’s root: mkdir /opt/unetlab/addons/qemu/vtedge-19.2.3
Step 2. Upload the downloaded viptela-edge-19.2.3-genericx86-64.qcow2 image to the /opt/unetlab/addons/qemu/vtedge-19.2.3 using FileZilla or WinSCP. Step 3. Go to image location and rename uploaded image to virtioa.qcow2: cd /opt/unetlab/addons/qemu/vtedge-19.2.3
mv viptela-edge-19.2.3-genericx86-64.qcow2 virtioa.qcow2
cd
3. Deployment of Cisco Viptela vSmart 19.2.3 image Step 1. SSH to EVE and login as root, from cli and create temporary working directory on the EVE’s root: mkdir /opt/unetlab/addons/qemu/vtsmart-19.2.3
Step 2. Upload the downloaded viptela-smart-19.2.3-genericx86-64.qcow2 image to the /opt/unetlab/addons/qemu/vtsmart-19.2.3 using FileZilla or WinSCP. Step 3. Go to image location and rename uploaded image to virtioa.qcow2: cd /opt/unetlab/addons/qemu/vtsmart-19.2.3
mv viptela-smart-19.2.3-genericx86-64.qcow2 virtioa.qcow2
cd
4. Deployment of Cisco Viptela vManage 19.2.3 image Step 1. SSH to EVE and login as root, from cli and create image directory on the EVE: mkdir /opt/unetlab/addons/qemu/vtmgmt-19.2.3
Step 2. Upload the downloaded viptela-vmanage-19.2.3-genericx86-64.qcow2 image to the /opt/unetlab/addons/qemu/vtmgmt-19.2.3 using FileZilla or WinSCP. Step 3. Go to image location and rename uploaded image to virtioa.qcow2: cd /opt/unetlab/addons/qemu/vtmgmt-19.2.3
mv viptela-vmanage-19.2.3-genericx86-64.qcow2 virtioa.qcow2
Step 4. IMPORTANT: Create addittional (Second!) storage 100Gb HDD virtiob.qcow2: /opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 100G
Step 5. Fix permissions: cd
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Note: all images default login passwords is: admin/admin |