Cisco Prime Infra

Versions this guide is based on:

EVE Image Name Downloaded Filename Version vCPUs vRAM Virtual hdd name
prime-PI-APL- PI-APL- 4 12288 virtioa
prime-PI-APL- PI-APL- 4 12288 virtioa


Other versions should also be supported following bellow’s procedure.

How to is based on version Prime Infra 3.3. For version 3.2 please change image and folder names respectively.

1. Create Prime Infra image folder in the EVE-NG. Use cli:

mkdir /opt/unetlab/addons/qemu/prime-PI-APL-

2. Upload the downloaded PI-APL- image to the /opt/unetlab/addons/qemu/prime-PI-APL- using for example FileZilla or WinSCP. Then login as root using SSH protocol

3. Go to created folder and rename uploaded PI-APL- image to cdrom.iso:

mv PI-APL- cdrom.iso

4. Create HDD for Prime image install:

/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 300G

5. Fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

Start Node and follow setup

WARNING, Cisco Prime 3.3 is very heavy node, after install it will reach 40Gb HDD space !!!

Version 3.2 is very heavy node as well, after install it will reach 30Gb HDD space !!!

Advanced Prime image preparing, not mandatory but recommended. Continue after step 4.

5. Open new lab and add single new Prime Infra node on topology. Start it. When console will prompt you enter “setup”, don’t enter it, but stop node.

6. Check lab ID number on EVE side bar “Lab details”, Example:

7. EVE Cli: Convert image from lab tmp folder to defaults image location. In the command below is used lab ID (above) and as we added on lab single node, node ID is 1. Prime image foldername match what we created before. Number 0 in the line below is user POD number. Admin pod is 0.

qemu-img convert -c -O qcow2 /opt/unetlab/tmp/0/72b1903b-4885-4a1c-b9e2-aed46032583a/1/virtioa.qcow2  /opt/unetlab/addons/qemu/prime-PI-APL-

8. Remove install CD ISO from image folder:

rm -f /opt/unetlab/addons/qemu/prime-PI-APL-

9. Fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions