Support and News Forum

Hi all,

I tried to implement fortimanager (fortinet) to my eve-ng community edition and can't figure out why the node isn't started.

I followed this :
2. Obtain FortiManager KVM image and prepare for EVE.
2.1. Using our image table, create correct image folder, this example is for image 1. in the table above. It is Fortinet Manager(FMG) image. Per our image naming table we have to create image folder starting with fortinet-, lets do it.
mkdir /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/
2.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/ folder using for example FileZilla or WinSCP.
2.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/
2.4. Unzip original filename
unzip FMG_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
2.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv fmg.qcow2 virtioa.qcow2
rm FMG_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
2.6. Create second HDD 100Gb drive virtiob.qcow2
/opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 100G
2.7. Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

I add a node, choose my fortinet-FMG_VM64_KVM-v7.4.6.M-build2588 node, modify cpu to 2 and memory to 2048 or 4096. No way to make it work, it doesn't start at all.

If someone can help me.

Thanks a lot

Hi,

I tried to launch the fortimanager from CLI :
/opt/qemu-4.1.0/bin/qemu-system-x86_64 -m 4096 -smp 2 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -drive file=virtiob.qcow2,if=virtio,bus=0,unit=1,cache=none -nographic

This command worked. I tried again from eve-ng, no boot, no start, nothing.
Can't find logs or errors.

ok i found my error (maybe it is written somewhere but it should be interested to put it inside fortinet howto).
My folder was too long !
So simply... I went to fortinet-FMG-7.4.6 and it started after fix permissions