This page is about basic configuration of jSpace installed in ENE-PRO or VMware Fusion.
You will be asked to enter user and password which are admin and abc123 respectively also for UNIX password.
Once you entered these, 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: the_configured_password
Press enter and continue
Choose the type of node to be installed [S/F] S
1) Configure UPv4
2) Configure Both IPv4 and IPv6
R) Redraw Menu
Click 1 and continue
Choice [1-2,R]: 1
Please enter new IPv4 address for interface eth0
Please enter new IPv4 subnet mask for interface eth0
Enter the default IPv4 gateway as a dotted-decimal IP address:
Please type the IPv4 nameservicer address in dotted decimal notation:
Configure a separate interface for device management? [y/N] n
Will this Junos Space system be added to an existing cluster? [y/N] n
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:
Do you want to enable NAT service? [y/N] n
Add NTP Server? [y/N] y
Please type the new NTP server: 188.8.131.52
Please enter display name for this node: space2
Enter password for cluster maintenance mode: mine_password
Re-enter password: mine_password
A> Apply settings
Chose [ACQR]: A
Note: For Please type the new NTP server: 184.108.40.206 you can use also default IPv4 gateway: 172.25.11.254.
Here is an image but all to do list is up
Now you can connect to the box via SSH at its ip 172.25.11.109
7) (Debug) run shell
Chose [1-7,AQR]: 7
[sudo] password for admin:
[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 172.25.11.109/24 brd 172.25.11.255 scope global eth0 <---Primary IP
inet 172.25.11.100/24 brd 172.25.11.255 scope global secondary eth0:0 <---Secondary GUI IP Address
Now it is time to login to the web UI using Firefox from inside CentOS or Docker. Docker is inside EVE-PRO lab.
Note: If connect to correct internet and configure with current ip, jSpace can be open also with Firefox from MacBook Pro.
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)
Place Video: nVidia Quadro NVS 295 – 256MB GDDR/64bit
Needed for Monitor connection
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.
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: 220.127.116.11/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
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.
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 QEMUNic 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
2 vCPU / 4 GB RAM
5 vCPU / 8 GB RAM
9 vCPU / 16 GB RAM
17 vCPU / 32 GB RAM
Flexible flow session capacity scaling by adding additional vRAM
Multi-core scaling support (Software RSS)
Add one additional vCPU to give the nested RE two vCPU’s
Virtio (virtio-net, vhost-net)
SR-IOV over Intel 82599 series
SR-IOV over Intel X710/XL710 series
SR-IOV over Mellanox ConnectX-3 and ConnectX-4
VMware ESXi 5.5, 6.0, 6.5
VMware ESXi 6.7
KVM on Ubuntu 16.04, Centos 7.1, Redhat 7.2
Contrail Networking 3.x
Contrail Networking 5.x
Google Cloud Platform (GCP)
vMotion / live migration
AWS ELB and ENA using C5 instances
GTP TEID based session distribution using Software RSS
On-Device Antivirus Scan Engine (Avira)
Requires Hardware Acceleration / VMX CPU flag enabled in the hypervisor
Supported in Junos 18.4R1 and higher
Supported in Junos 19.1R1 and higher
Supported in Junos 19.2R1 and higher
Supported in Junos 19.3R1 and higher
Supported in Junos 19.4R1 and higher
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).
vSRX model available on Azure is vSRX 3.0 from Junos 19.1 onwards