Here you find the vSRX 3.0 custom template for your EVE-NG.
Add this file (named vsrx30.yml) to your /opt/unetlab/html/templates/intel/ folder:
<code>
# Copyright (c) 2016, Andrea Dainese
# Copyright (c) 2016, Alain Degreffe
# Copyright (c) 2017, Alain Degreffe
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
# * Neither the name of the UNetLab Ltd nor the name of EVE-NG Ltd nor the
# names of its contributors may be used to endorse or promote products
# derived from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
# DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
# LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---
type: qemu
name: vSRX3-0
cpulimit: 1
icon: JuniperSRX.png
cpu: 2
ram: 4096
eth_name:
- fxp0/mgmt
eth_format: ge-0/0/{0}
ethernet: 6
qemu_nic: virtio-net-pci
console: telnet
qemu_arch: x86_64
qemu_options: -machine type=pc-1.0,accel=kvm -cpu qemu64,+ssse3,+sse4.1,+sse4.2,+x2apic,+aes,pclmulqdq -serial
mon:stdio -nographic -nodefconfig -nodefaults -rtc base=utc
</code>Don’t forget to include it in your custom_templates file at /opt/unetlab/html/includes/custom_templates.yml:
custom_templates:
- name: JATP
listname: 'Juniper JATP Appliance (SkyATP on Premise)'
- name: PACKETFENCE
listname: 'PacketFence OpenSource NAC'
- name: CSRX
listname: 'Juniper cSRX'
- name: vsrx30
listname: 'Juniper vSRX3.0'
- name: jspacelogcollector
listname: 'JunOS Space Log Collector'Compared to the vSRX-NG Template, which took the vSRX 3.0 6-7min to fully boot, this “new” template (which is basically a linux based template) takes roughly 2-3min to fully boot with 19.4 and 20.1 😉
Enjoy your unleashed vSRX3.0 🙂
Feel free to ask questions / suggestions in the comments here 🙂
I followed your tutorial and vSRX3.0 appeared in Node list but it’s greyed out. Is there any naming convention for vSRX3.0 folder and file?
Hi pablo,
yes – it’s looking for vsrx30-.
vsrx30-20.1R1 fpr example.
BR
Christian
thanks a lot!
how do i load this custom template file? i dont see juniper vsrx 3.0 in my list of nodes. sorry, new to eve
No worries. You need to create the file as mentioned in the Article.
There are templates for a lot of Devices present on your eve server already – the vSRX 3.0 is just a copy of the Linux Template with some CPU instructions added 🙂
I will also make a video about that soon
Hello Christian,
I’ve followed the steps described above but after i add new node and pick up vSRX30 i got message:
Template does not exists or is not available (60031).
I am using eve-ng 3.0.1-16-PRO Can you try this template on new eve-ng?
Thank you.
Hi Jan,
I will test this and let you know the outcome.
Should work on any EVE Pro – I did not change any settings regarding the path of the templates. But since my eve was upgraded from an eralier version I will check if the brand new install will behave differently.
Hello, if anyone else encounters this error this may help. I have an AMD processor and reading through the Eve-ng Cookbook I found the following:
“Starting from EVE-PRO Version 2.0.6-42, EVE installation is autodetecting what kind of CPU manufacturer has your server: Intel or AMD, to choose proper templates set. You can check it manually on EVE cli: example below, showing that EVE has Intel CPU.
If you have Intel CPU, then your template files are in “/opt/unetlab/html/templates/intel/”•If you have AMD CPU, then your template files are in “/opt/unetlab/html/templates/amd/””
I was having the same 60031 error and once i moved the vsrx30.yaml to the amd folder it worked right away.
Hope that helps anyone else that encounters this error
Christian
Can you do a quick post on where/how to import the files needed for the vSRX3.0?
Version 20.1 would be great, if you can do that.
Thanks
Hi Shayne,
I actually made a Video about that 😀
https://www.youtube.com/watch?v=zFTewtbnYk4
Let me know if you need any more help 🙂
Christian
Hi there,
I’m wondering if this could be adapted to allow for export of configs, or if you have a different workflow that means you don’t have to use that.
And you did add the export script in an other post! Cheers!
Hi , I need change nic type to e1000 or virtio-pci-net in template.
Is there any way to do this in the template? like first_nic, secondary_nic and so on?
1 nic=virtio-pci-net
2 nic=virtio-pci-net
3 nic=virtio-pci-net
4 nic =e1000
5 nic=e1000
.
.