Versions this guide is based on:
| EVE Image Foldername | Downloaded Original Filename | Version | vCPUs | vRAM | Console | HDD format | Interfaces | |
|---|---|---|---|---|---|---|---|---|
| 1. | fortinet-FGT-v6-build1010 | FGT_VM64_KVM-v6-build1010-FORTINET.out.kvm.zip | 6.0.buildX | 1 | 1024 | telnet, http | virtioa | x4 virtio |
| 2. | fortinet-FMG-v6-build1183 | FMG_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip | 6.0.buildX | 2 | 4096 | telnet, https | virtioa, virtiob | x1 virtio |
| 3. | fortinet-FAZ-v6-build1183 | FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip | 6.0.buildX | 4 | 8192 | telnet, https | virtioa | x1 virtio |
| Instructions |
|---|
| Other versions should also be supported following bellow’s procedure.
Naming of image folder and image name please follow naming table: http://www.eve-ng.net/index.php/documentation/images-table 1. Obtain FortiGate KVM image and prepare for EVE
1.1. Using our image table, create correct image folder, this example is for image 1. in the table above. It is Fortinet FGT image. Per our image naming table we have to create image folder starting with fortinet-, lets do it.
mkdir /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
1.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/ folder using for example FileZilla or WinSCP.
1.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
1.4. Unzip original filename
unzip FGT_VM64_KVM-v6-build1010-FORTINET.out.kvm.zip
1.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv fortios.qcow2 virtioa.qcow2
rm FGT_VM64_KVM-v6-build1010-FORTINET.out.kvm.zip
1.6. Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
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
3. Obtain FortiAnalyzer KVM image and prepare for EVE.
3.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-FAZ-v6-build1183/
3.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FAZ-v6-build1183/ folder using for example FileZilla or WinSCP.
3.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FAZ-v6-build1183/
3.4. Unzip original filename
unzip FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
3.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv faz.qcow2 virtioa.qcow2
rm FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
3.6. Create second HDD 100Gb drive virtiob.qcow2
/opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 100G
3.7. Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
|