2020.06.28 – Junos Space Basic Configuration

Note: Modified and updated on 2020.09.1.

This page is about basic configuration of jSpace installed in EVE-PRO or VMware Fusion. I will go further to include configuration in EVE-PRO.

Note: jSpace need to be connected to a network which has access to Internet.


MacBook Pro is external, connected to internet and used for configuration inside terminal and Firefox. Appears in picture just just for understanding the configuration and use of jSpace.

1 – Click jSpace. It will be opened in EVE-PRO.

2 – You will be asked to enter user and password respectively also for UNIX password.

  • Username: admin
  • Password abc123

3 – After this you will be asked to change the password. Choose your new password according to the local instructions. Otherwise you may fail to set a proper password.

[sudo] password for admin: Juniper123Juniper123 (- the_configured_password)

4 – Press enter and continue. Configuration Eth0 will start.

Choose the type of node to be installed [S/F] S
Configuring Eth0:

1) Configure UPv4
2) Configure Both IPv4 and IPv6

R) Redraw Menu 

5 – Click 1 and continue

Choice [1-2,R]: 1
Please enter new IPv4 address for interface eth0
192.168.100.199
Please enter new IPv4 subnet mask for interface eth0
255.255.255.0

Enter the default IPv4 gateway as a dotted-decimal IP address:
192.168.100.1

Please type the IPv4 nameservicer address in dotted decimal notation:
8.8.8.8

Configure a separate interface for device management? [y/N] n

Will this Junos Space system be added to an existing cluster? [y/N] n

6 – Web GUI configuration

Configuring IP address for web GUI:

1) Configure IPv4

R) Redraw Menu

Chose [1,R]: 1

Please enter IPv4 Address for web GUI:
192.168.100.200

Do you want to enable NAT service? [y/N] n

Add NTP Server? [y/N] y

Please type the new NTP server: 192.168.100.1

Please enter display name for this node: jSpace

Enter password for cluster maintenance mode: Juniper123Juniper123 (-   mine_password) 
Re-enter password: Juniper123Juniper123 (- mine_password)

-----

A> Apply settings

-----

Chose [ACQR]: A

Note: For Please type the new NTP server: 192.168.100.1 which is default IPv4 gateway you can use also something external like 82.197.221.30

Here is an image but all to do list is up

7 – Now you can connect to the box via SSH at its ip 192.168.100.199

% ssh admin@192.168.100.199 

admin@192.168.100.199's password: Juniper123Juniper123 (- the-password)
...
7) (Debug) run shell
...

Chose [1-7,AQR]: 7

[sudo] password for admin: Juniper123Juniper123
[root@space-000c29cb6706 ~]# ip -4 addr 
1: lo: <LOOPBACK,UP,LOWER_UP> meu 655536 disc no queue state UNKNOWN
  inet 127.0.0.1/8 scope host lo 
2: eth0: <BROUDCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 
  inet 192.168.100.199/24 brd 192.168.100.255 scope global eth0 <---Primary IP 
  inet 192.168.100.200/24 brd 192.168.100.255 scope global secondary eth0:0 <---Secondary GUI IP Address

8 – Now it is time to login to the web UI.

  • https://192.168.100.200
  • Impossible use Safari from MacBook Pro. Install and use Firefox.

Note: If connect to correct internet and configure with current ip, jSpace can be open also with Firefox from MacBook Pro.

  • Username: super
  • Password juniper123

You have to configure a new password. I insert mine new password jSpace321jSpac.

9 – Ready to use jSpace to deploy the Network Director.

  • Download and use Network-Director.4.0R1.36.img in Download folder or … It is difficult to use an .img situated in Dropbox. Make a copy of the Network-Director.4.0R1.36.img and put it in Downloads folder in MacBook Pro.
  • Inside MacBook Pro open Firefox than jSpace using the web IP like https://192.168.100.200
  • Web user is super and the configured password jSpace321jSpace
  • Go to Adminitration -> Applications -> + button meaning Add Application
  • Select Upload via HTTP and upload the Network-Director.4.0R1.36.img
  • Please click on Job ID to new details > OK
  • Once it appears, click install then OK
  • Application Management Job Information: Please logout and log in again after the installation of new application completed successfully. Click on Job ID to new details > OK
  • It will take a while for the application to be installed…

Enjoy!!

2020.06.13 – Install EVE-NG as Bare Hardware Server

Importamt information:

Note: This article does not contain all information for different situations. It contains the information for mine use only. I will update this article till I finish all installation.

1.. EVE System Requirements

1.1. EVE-NG requires:

  • Intel CPU VT-x/EPT
  • Ubuntu Xenial Xerus 16.04.X LTS 64bit (suggested with any processors). (Ubuntu 18 and 19 are not supported due it still not have all necessary libs for EVE)

1.2. NOT Officially supported or have issues:

  • VIRTUAL BOX DOESN’T SUPPORT HW ACCELERATION !!! AVOID USING IT !!!! 
  • Hyper-V, Promox and XEN Citrix are not officially supported.
  • Azure cloud is not officially supported, because Azure overwrite kernel for EVE VM, and do not accept custom Kernels for VM Machines.
  • AWS cloud is not officially supported due issues with sub-virtualization. It has issues to run Qemu nodes.

Note: As EVE-NG is installed directly on physical hardware, without a hypervisor, using the provided ISO image, this is referred to as a “bare metal” install and is the most recommended method of installing EVE-NG.

2.. Hardware Requirements and Use for EVE

2.1. Dedicated Server (bare) System Requirements

CPU: Intel Xeon CPU supporting Intel® VT-x with Extended Page Tables (EPT) Operation System: Ubuntu Server 16.04.4 LTS x64

  • CPU: Recommended CPU Intel E5-2650v3 (40 Logical processors) or better supporting Intel® VT-x with Extended Page Tables (EPT) Minimum CPU is any Intel Xeon CPU supporting Intel® VT-x with Extended Page Tables (EPT)
  • RAM: 128 Gb
  • HDD: 2 Tb
  • Space Network: LAN Ethernet

2.2. Hardware I bought to use

-> Monitor LED Sell from eMAG: www.emag.ro

-> Keyboard Kit + Mouse A + K1 Kandaon, Black from eMAG: www.emag.ro

-> DELL Precision T7910 Workstation from Server Config: www.server-config.ro

Content:

3.. Static IP on ONT/Router HG8247U

Note: This is what I have in my house in this moment of creating this page. HG8247U is an old version that I use but on internet I found specification for HG8247H version and seems the same and helped me.

Informations here: https://hg8245h.wordpress.com/2015/12/14/how-to-assign-static-ip-address-on-hg8245h/

Many people prefer to have static internal IP address rather than some random numbers allocated by the DHCP server. Two ways to accomplish that, either assign a static IP directly in your computer network settings or use IP reservation which is the preferred way of doing it.

Testing: I have configured an Manual IP Address for iMac. From iMac I ping all Its from devices I have in house like iPad or BOSE SoundLinks and it is OK.

It si required and I decide to configure Static IP directly into

  • DELL / Ubuntu: 192.160.100.50/24
  • EVE-PRO 192.168.100.51/24

4.. Bare Hardware Server Ubuntu and EVE Installation

4.1. Download and prepare for installation

Note: I use iMac, USB SuperDrive and totally new DVDs..

Download the Ubuntu and EVE-PRO :

  • Download Ubuntu Server 16.04.6 LTS ISO image: ubuntu-16.04.6-server-amd64.iso
  • Download EVE-PRO: EVE-PRO.iso
  • Not mandatory Copy paste from Downloads to Dropbox

Create installation 2 separate DVDs:

  • Insert DVD to USB SuportDrive
  • Find ubuntu-16.04.6-server-amd64.iso, > right click > Burn Disk Image
  • Burn Disk in: Apple SupertDrice > click Burn
  • Wait few minutes to finish and automatically Eject Disk

4.1. Invalid partition table! error

  • PowerOn Dell Precision without Operation System possible to get a message like Invalid partition table!
  • Install Ubuntu Server as in the next step, 4.2. Ubuntu Server Installation
  • PowerOn Dell Precision will using a tutorial: https://www.youtube.com/watch?v=BdLLjohm7_8
    • Press F2
    • Go to Settings > General > Boot Sequence
    • Select UEFI > click Apply > Exit
  • Noe Dell Precision PowerOn normally in Ubuntu

4.2. Ubuntu Server Installation

Note: Internet is reachable from mine Dell Precision. EVE ISO installation requires internet access to get updates and install the latest EVE-PRO version from the EVE-NG repository. DNS must work as well. To check it, do a named ping, for example ping www.google.com.

4.2.1. Ubuntu Server Installation Phase 1

All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/

Sume help here: https://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html

4.2.2 EVE Professional Installation Phase 2

All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/

4.2.3 EVE Professional Installation Phase 3

All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/

4.3. EVE Management IP Address setup

All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/

5. Login to the EVE WEB GUI

Note: In MacBook Pro I use Firefox application as it is impossible to use Safari

Login to the EVE management UI: https://192.168.100.51/
Default user access:
User: admin Password: eve

6. EVE-NG Professional Licensing

You can move the having license from existing EVE-PRO (I have one in MacBook Pro > VMware Fusion) to a new installed EVE-PRO.

All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/

This was all about installation!

Installation Note:

!!! Appears a new version EVE-PRO to use to install.

  • Till now you can install EVE-PRO
    • Starting to install Ubuntu 16.04 using a DVD.
    • After this installation it was mandatory to make sure to have active internet connection
    • Internet connectivity helps to install and upgrade EVE-PRO.iso
  • In 26.06.2020, appears a new version of EVE-PRO, 3.1.
    • Now you have to download EVE-Bionic-Pro.iso that contains both Ubuntu 18.04.4 and EVE-Pro 3.1
      • Till 26.06.2020 was impossible to use Ubuntu 18.04.4. Version 16.04 was mandatory to be used
    • Create a DVD
    • And install both, Ubuntu and EVE-PRO, more easier
    • The document with all details about installation and usage of EVE-PRO is updated to version EVE-COOK-BOOK-3.1-2020.pdf.

2020.05.2 – Connecting EVE Lab to a physical device

Some help ideas are in EVE professional Cookbook.

A virtual lab that include CentOS is configured in EVE-PRO. The EVE-PRO is configure in VMWare Fusion. VMware Fusion is in MacBook PRO. The idea is to connect virtual CentOS to internet.

Open VMware Fusion > Click on EVE-PRO virtual machine > Click on Settings…

Create, or select if already created, 3 Network Adapter:

  • Network Adapter > Connect to vSphere network
  • Network Adapter 2 > Connect to vSphere network
  • Network Adapter 3 > Connect to vSphere network

Into EVE-PRO lab create a new Network type Cloud1 and connect to CentOS. Do not forget to configure the correct IP in CentOS. Details of how I done it are here: 2020.04.30 – CentOS installation into EVE-NG.

The Internet is working now

I am happy!!!

2020.04.30 – CentOS installation into EVE-NG

All used information to install I found here:

Using things:

  • EVE-PRO meaning with license
  • CentOS CentOS-8.1.1911-x86_64-dvd1.iso

Step 1. Download CentOS – donloaded from Download CentOS version Linux DVD ISO

See 2. Go into EVE-PRO and move into qemu directory

root@eve-ng:~# cd /opt/unetlab/addons/qemu

Step 3. Create a new directory and move inside it

root@eve-ng:/opt/unetlab/addons/qemu# mkdir linux-centeros-8
root@eve-ng:/opt/unetlab/addons/qemu# cd linux-centeros-8
root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8#

Step 4. Upload CentOS-8.1.1911-x86_64-dvd1.iso in EVE-PRO using FilaFilla application

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# ls
CentOS-8.1.1911-x86_64-dvd1.iso

Step 6. Create qcow2 file

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# /opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 40G
Formatting 'hda.qcow2', fmt=qcow2 size=42949672960 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# 

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# ls
CentOS-8.1.1911-x86_64-dvd1.iso  hda.qcow2
root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# 

Step 6. Rename CentOS-8.1.1911-x86_64-dvd1.iso file

oot@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# mv CentOS-8.1.1911-x86_64-dvd1.iso cdrom.iso

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# ls
cdrom.iso  hda.qcow2

Step 7. Login to EVE-PRO then Add new lab end add CentOS node

CentOS need to have

  • Name: CentOS
  • CPU: 2
  • RAM (MB): 4096
  • Ethernets: 2
  • QEMU Version : 2.4
  • QEMU arch: tpl (x86_64)
  • QEMU Nic: e1000-

Click SAVE

Add a switch and configure it as Type: Management (Cloud0) and click Save

Connect

Step 8. Now ready to start CentOS

Do not click anything, just wait …

Step 9. Go throw installation process

English and Continue

Verify and configure different things…

Keuboard: English

Software: Server with GUI

Installation Destination: ATA QENU HARDDISK

After finishing click Begin Installation

During installation you need to insert toot password and user name and password

Root Pasword

User Name and Password. Also select Make this user admin

Wait to finish installation

Step 10. Restating CentOS

Before restarting CentOS you need to modify the name if application needed to install

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# mv cdrom.iso centos-install.iso

I do not like restart. I click restart, then power-off and them power-on or Start

Step 11. Go throw internal installation process.

Click License Information

I accept the license agreement.

Click Finish configuration

English and Next

English (US) and Next

Privacy OFF and Next

Connect Your Online: Skip

Finish to install internal

Step 12. Networks

Select Wired Settings

I don’t have Automatic Ethernet on these network, si I have to configure it manually

Open Terminal

Use ifconfig command

I will do not this now ….

Step 13. Save the configured CentOS for all new EVE-PRO lab

Into EVE-PRO open Lab Details

Use SSH

root@eve-ng:/opt/unetlab/tmp/0/085884f1-7807-492d-814f-7b588fd1892c/1# ls
cdrom.iso  hda.qcow2  l1down_1  l1up_0  mon-sock  mon2-sock  qmp-sock  wrapper.txt

root@eve-ng:/opt/unetlab/tmp/0/085884f1-7807-492d-814f-7b588fd1892c/1# /opt/qemu/bin/qemu-img commit hda.qcow2


Image committed.

Here is tha same

root@eve-ng:/opt/unetlab/tmp/0/085884f1-7807-492d-814f-7b588fd1892c/1# ls
cdrom.iso  hda.qcow2  l1down_1  l1up_0  mon-sock  mon2-sock  qmp-sock  wrapper.txt

A needed command to make it work as configured

root@eve-ng:/opt/unetlab/addons/qemu/linux-centeros-8# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions


May 01 07:09:28 May 01 07:09:28 Online Check state: Valid

All done. CentOS is ready to go. We will now add a couple of nodes to confirm that CentOS is working.

Step 14. Verify that CentOS is working

Add a total of three CentOS

Power-on all

All 3 can power-on …

Step 14. Configure and Mange Network Connection using nmcli

The needed information I find here: How to configure and Manage Network Connections using nmcli. I use The nmcli connection sub-command chapter.

  • View connection profiles
# nmcli connection show 
NAME UUID TYPE DEVICE 
virbr0 bbe539aa-7042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet virbr0
virbr0-nic bbe539aa-8042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet virbr0-nic
ens3 bbe539aa-5042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet --
ens4 bbe539aa-6042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet --
  • The nmcli connection add Command
$ nmcli connection add con-name new-ens3 ifname ens3 type ethernet ip4 192.168.1.25/24 gw4 192.168.2.1 
Connection 'new-ens3' (f0c23472-1aec-4e84-8f1b-be8a2ecbeade) successfully added.

$ nmcli connection add con-name new-ens4 ifname ens4 type ethernet ip4 172.25.11.254/24 gw4 172.25.11.254
Connection 'new-ens4' (f0c23472-1aec-5e84-8f1b-be8a2ecbeade) successfully added.
# nmcli connection show
NAME UUID TYPE DEVICE
new-ens3 bbe539aa-9042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet ens3
new-ens4 bbe539aa-1042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet ebs4
virbr0 bbe539aa-7042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet virbr0
virbr0-nic bbe539aa-8042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet virbr0-nic
ens3 bbe539aa-5042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet --
ens4 bbe539aa-6042-4d28-a0e6-2a4d4f5dd744 802-3-ethernet --
# ls /etc/sysconfig/network-scripts/ifcfg* 
/etc/sysconfig/network-scripts/ifcfg-ens3 /etc/sysconfig/network-scripts/ifcfg-new-ens3
/etc/sysconfig/network-scripts/ifcfg-ens4 /etc/sysconfig/network-scripts/ifcfg-new-ens4

I can see this but I modify using nmcli command

I hope all detail help me and you in future use.

2020.04.26 – Juniper Junos Space Network Management installation into EVE-PRO

The information for installation is from here : https://www.eve-ng.net/index.php/documentation/howtos/juniper-j-space/

>>>>>>>> Chapter 1:

  • EVE Image Name: jspace-19.3R1.3
  • Downloaded Original Filename: space-19.3R1.3.qcow2
  • Version: 19.3R1.3
  • vCPUs: 2
  • vRAM: 8192
  • HDD Format: virtioa
  • Console: vnc/https
  • Interfaces: x2 virtio

Chapter 1 topic:

Step 1. Download KVM qcow2 image from Juniper.

Step 2. Using our image table, create correct image folder, this example is for image jspace- in the table above.

mkdir /opt/unetlab/addons/qemu/jspace-19.3R1.3/

Step 3. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/jspace-19.3R1.3 folder using for example FileZilla or WinSCP.

Step 4. From the EVE cli, go to newly created image folder.

cd /opt/unetlab/addons/qemu/jspace-19.3R1.3/

Step 5. Rename original filename to virtioa.qcow2

mv space-19.3R1.3.qcow2 virtioa.qcow2 

Step 6.  Fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions


Step 7. Open a lab, add Junos Space and power-on

Step 8. Default logins:

CLI: admin/abc123
https: super/juniper123

>>>>>>>> Chapter 2:

  • EVE Image Name: jspace-20.1R1.2
  • Downloaded Original Filename: space-20.1R1.2.qcow2
  • Version: 20.1R1.2
  • vCPUs: 2
  • vRAM: 8192
  • HDD Format: virtioa
  • Console: vnc/https
  • Interfaces: x2 virtio

Chapter 2 topic:

Note: I have installed and it does’n work for me. Maybe it work for you … just try it!

Step 1. Download KVM qcow2 image from Juniper.

Step 2. Using our image table, create correct image folder, this example is for image jspace- in the table above.

mkdir /opt/unetlab/addons/qemu/jspace-20.1R1.2/

Step 3. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/jspace-20.1R1.2 folder using for example FileZilla or WinSCP.

Step 4. From the EVE cli, go to newly created image folder.

cd /opt/unetlab/addons/qemu/jspace-20.1R1.2/

Step 5. Rename original filename to virtioa.qcow2

mv space-20.1R1.2.qcow2 virtioa.qcow2 

Step 6.  Fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions


Step 7. Open a lab, add Junos Space and power-on

Step 8. Default logins:

CLI: admin/abc123
https: super/juniper123

Getting Start Guid: https://www.juniper.net/documentation/en_US/junos-space20.1/platform/topics/concept/junos-space-getting-started-fabric-architecture-overview.html

2020.04.25 – Juniper vSRX-NG installation into EVE-PRO

I used this guid for my installation:: https://www.eve-ng.net/index.php/documentation/howtos/howto-add-juniper-vsrx-ng-15-x-and-later/

Versions this guide is based on:

  • Name: vsrxng-20.1R1.11
  • Download original filename: junos-vsrx3-x86-64-20.1R1.11.qcow2
  • Version: 20.1R1.11
  • VCPUS: 2
  • VRAM: 4096

Step 1. Create correct image folder

root@eve-ng:/opt/unetlab/addons/qemu# mkdir vsrxng-20.1R1.11

Step 2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/vsrxng-17.3R1.10/  folder using for example FileZilla or WinSCP.

Step 3. From the EVE cli, go to newly created image folder.

root@eve-ng:/opt/unetlab/addons/qemu# cd vsrxng-20.1R1.11

root@eve-ng:/opt/unetlab/addons/qemu/vsrxng-20.1R1.11# ls
junos-vsrx3-x86-64-20.1R1.11.qcow2

Step 4. Rename original filename to virtioa.qcow2

root@eve-ng:/opt/unetlab/addons/qemu/vsrxng-20.1R1.11# mv junos-vsrx3-x86-64-20.1R1.11.qcow2 virtioa.qcow2

Step 5. Fix permissions:

root@eve-ng:/opt/unetlab/addons/qemu/vsrxng-20.1R1.11# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions


Apr 25 06:51:19 Apr 25 06:51:19 Online Check state: Valid

Step 6. Create a testing lab and open:

Step 7. By default the number of interfaces are 4: fxp0 and ge-0/0/0 – ge-0/0/2.

To increase the number of interfaces change the default Ethernets configuration of 4 to 10. The picture below shows maximum to ge-0/0/6 but it is maximum to ge-0/0/8.

Note: To open vSRX with Terminal in MacBool Pro make sure you configured/changed QEMU Nic to vmxnet3

Information about vSRX and vSRX-NG:

Junos release 18.4R1 has introduced a new model of virtual SRX (referred to as “vSRX 3.0”), which will be available in addition to the existing virtual SRX model (referred to as “vSRX”), which has been available since Junos 15.1X49-D15 release.

The vSRX 3.0 has a new architecture, which has benefits for operating in virtual environments. Some enhancements are a faster boot time, smaller install image size and better agility due to no nested routing-engine VM being used anymore.

However, the original vSRX model will still be available as long as not all features which are available on vSRX have been ported to vSRX 3.0 yet.

With respect to the security features, the both virtual SRX models are in feature parity. However, some platform related features may not be in parity yet.

The below table specifies differences and similarities in features between vSRX and vSRX 3.0, so that you can decide when to best use which type of virtual SRX, based on your needs and environment.

Platform feature differences overview between vSRX and vSRX 3.0

 vSRXvSRX 3.0
Resources supported  
2 vCPU / 4 GB RAMyesyes
5 vCPU / 8 GB RAMyesyes
9 vCPU / 16 GB RAMyesyes (*2)
17 vCPU / 32 GB RAMyesyes (*2)
Flexible flow session capacity scaling by adding additional vRAMyesyes (*3)
Multi-core scaling support (Software RSS)noyes (*4)
Add one additional vCPU to give the nested RE two vCPU’syesN/A
VMXNET3yesyes
Virtio (virtio-net, vhost-net)yesyes
SR-IOV over Intel 82599 seriesyesyes
SR-IOV over Intel X710/XL710 seriesyesyes
SR-IOV over Mellanox ConnectX-3 and ConnectX-4yesno
   
Hypervisors supported  
VMware ESXi 5.5, 6.0, 6.5yesyes
VMware ESXi 6.7noyes (*4)
KVM on Ubuntu 16.04, Centos 7.1, Redhat 7.2yesyes
Hyper-Vyesyes (*2)
Nutanixnoyes (*2)
Contrail Networking 3.xyesyes
Contrail Networking 5.xnoyes (*4)
AWSyesyes (*6)
Azureyesyes (*7)
Google Cloud Platform (GCP)noyes (*4)
   
Other features  
Cloud-inityesyes
Powermode IPSecyesno
vMotion / live migrationnoyes
AWS ELB and ENA using C5 instancesnoyes (*1)
Chassis Clusteryesyes
GTP TEID based session distribution using Software RSSnoyes (*4)
On-Device Antivirus Scan Engine (Avira)noyes (*5)
   
Requirements  
Requires Hardware Acceleration / VMX CPU flag enabled in the hypervisoryesno
Disk space16 GB18 GB

Notes:

  1. Supported in Junos 18.4R1 and higher
  2. Supported in Junos 19.1R1 and higher
  3. Supported in Junos 19.2R1 and higher
  4. Supported in Junos 19.3R1 and higher
  5. Supported in Junos 19.4R1 and higher
  6. vSRX model available on AWS is vSRX 3.0 from Junos 18.3 onwards (before vSRX 3.0 was generally available, it was already available on AWS).
  7. vSRX model available on Azure is vSRX 3.0 from Junos 19.1 onwards

2020.04.23 – Juniper vRR installation into EVE-PRO

Inspiration in EVE guid: https://www.eve-ng.net/index.php/documentation/howtos/howto-add-juniper-vrr/ where it is made with version 17.4R1.16.

  • Note: I have installed three times.
    • Firs time with vRR 19.2R1.8 (vrr-bundle-kvm-19.2R1.8.tar) – workilg OK!
    • second time with vRR 20.1R1.11 (vrr-bundle-kvm-20.1R1.11.tar) – not work!
    • third time with vRR 19.4R1.10 (vrr-bundle-kvm-19.4R1.10.tar) – working OK!

The blog is about third installation exactly as the first installation.

Read more

2020.04.18 – Install EVE-NG: THE Network Emulator!

What I found and I use as help to download and install EVE-NG is from here: https://thenetworkberg.com/eve-ng-first-time-configuration/

Note: I had problems and I’be installed 2 times in 2 different version: -NG and -PRO. I will update here as Note into each Step to remember if I need to installed again.

Need to have something similar:

  • MacBook Pro (15-inch, 2016):
    • macOS Catalina version 10.15.3
    • Processor 2,9 GHs Quad-Core Intel
    • Memory 16 GB 2133 MHsLPDDR3 (of RAM)
  • VMWare Fusion 11.5.3 installed

EVE-NG Community Cookbook: https://www.eve-ng.net/index.php/documentation/community-cookbook/

Read more