Step by Step Process1. You can check how to install Eve-ng in windows2. Download Fortinet firewall Images.3. Creating folder in Eve-ng4. Uploading Cisco Fortinet firewall images to Eve-ng.5. Unzip Fortinet Image6. Rename Fortinate image and removing old image7. Testing Fortinet firewall Images.8. How to add Fortinet Manager in Eve-ng.
This is used primarily for IOS versions 12.X. For later versions, it is recommended to use those from Cisco VIRL, specifically the IOSv, IOSvL2, IOS-XRv, and ASAv images, which support current releases of Cisco IOS version 15.X and provide the best user experience.
Like GNS3, EVE-NG requires the use of Cisco IOS images or Cisco VIRL images to operate. Unlike GNS3 however, EVE-NG has a free community-supported edition and a pro edition that can be purchased for a reasonable price. Additional benefits of the pro version include lab timers, Wireshark integration, and other valuable tools.
I'm not 100% sure how I got to trying EVE out but I think what drew me in was the fact that it does the same thing GNS3 does but without a need for a desktop client. Just deploy the EVE-NG OVA, assign it an IP address & voila - you can use a browser to create really nice network topologies really, really fast. However, just like with GNS3, you will need to source your own IOS,vIOS, .iso, .vmdk etc images. If you're a Cisco partner, then should do the trick; if not then some google-fu is your best bet.
The .iso images you get from Cisco's website are not bootable so you'll have to use a couple of tricks to get them to run. The process is very simple and can be found all over YouTube (here or here) or by googling around (ex. like here). These tutorials are very well put together and hit the nail on the head.
For the same Cisco .iso images, you WILL need to follow this process to edit / bypass the product's hardware validation check otherwise, even though they'll boot up, the install fails when it sees OpenStack as the hardware platform.
Follow the above steps for UCCX, IM&Presence and CUCM/Unity and you should end up with 3 bootable images. Up until this point, I don't think there's anything new for somebody who's built a Cisco UC home lab.
This one's simpler than Expressway. Just use 7-ZIP to open the "Cisco_Meeting_Server_2_3_2.ova" and extract the "acano-server-disk1.vmdk" somewhere next to all the other images; we will need to upload it to EVE-NG via SFTP soon.
3.3 Download these .png icons and load them in EVE-NG: much like in steps 3.1 and 3.2, drag & drop these to EVE-NG via FileZilla to the /opt/unetlab/html/images/icons/ folder in EVE-NG.
All the images need to be stored in the /opt/unetlab/addons/qemu/ folder and *special* naming convetions have to be followed here. Every type of server/appliance needs to have its own FOLDER on EVE-NG otherwise the web GUI won't pick them up.
Each time you upload a new image to EVE-NG, the "/opt/unetlab/wrappers/unl_wrapper -a fixpermissions" command has to run in the CLI (SSH or in the ESXi CLI). Without this, the images won't boot / work! 2b1af7f3a8