2.2. https://dave.dev/blog/2018/06/juniper-vqfx10k-esxi-6-5/ – here are not many-many details and steps as I need to understand and use but I in this article discovered a solution to understand and use what I need: Existing hard drive in New virtual machine – 4 Customise settings – Add hard disk – Existing hard drive. Also I use Compatibility – ESXi 5.5 virtual machine. because ESXi 6.5 does not work for me …
Idea 3. Use 2.1. article to learn how to Searc and discover what you need for your version of vQFX switch:
Nested virtualization lets you run a virtual machine inside a virtual machine, and it’s very useful for testing apps. This guide will show you how to do it on a Mac.
The Juniper vMX images are based on dual nodes setup, where Routing Engine (VCP) is connected to Forwarding Plane (VFP) and act like single node. All cli configurations will be done on the VCP, but porting and connections will be on VFP.
Step 1. Create temporary working directory for image:
root@eve-ng:/opt/unetlab/addons/qemu# mkdir vMX
Step 2. Upload the downloaded images to the EVE using for example FileZilla (or WinSCP).
root@eve-ng:/opt/unetlab/addons/qemu/vMX# ls
vmx-bundle-20.2R1.10.tar
Add VCP and VFP nodes on the topology and connect them with int interfaces. int interface is communication port between VCP and VFP. This setup will be one vMX node (set of 2). Use VFP to connect your lab element to the ports.
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 alsosomething 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
[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…
Open MacBook Pro. Open FileZilla application and connect to EVE-PRO using the EVE-PRO IP address.
You do have permission to list this directory
Solution
1.. Go to Edit > Directory access permissions…
2.. Click Add directory… and chose the directory from you MacBook Pro
3.. The directory you have chose is available to chose the applications from MacBook Pro and copy to EVE-PRO.
A new discovery
In FileZilla is possible some nice things. For example right click in open location and see that new directory can be created or renames…. for example.
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: 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
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.
Uncompress the package in a location accessible in MacBook Pro
Step 2. Launch the VMware ESXi server, esxi00.silvique.ro, and log in to the server with your credentials.
Step 3. If using Dropbox make sure the files needed are totally active
Right – click on the ova folder inside vm-esxi/ova
Click Smart Sync > Local
Step 4. Setting Up the Network
In VMware ESXi, to set up the different networks for management (br-ext), internal connection of the VMs (br-int), and WAN ports for data:
Enter VMware ESXi using Firefox
4.1. Virtual Switch Configuration
Click Networking > Virtual Switch > Add Standard virtual switch
1. Configure vSwitch Name: vmnic1
MTU 1500
Uplink 1: vmnic1
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
2. Configure vSwitch Name: vmnic2
MTU 1500
Uplink 1: vmnic2
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
3. Configure vSwitch Name: Internal.vMX
MTU 1500
Uplink 1: delete
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
4.2. Port groups Configuration
Click Networking > Port groups > Add Standard port group
1. Configure Name: br-ext.vMX
VLAN ID: 0
Virtual Switch: vmnic1
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
2. Configure Name: br-int.vMX
VLAN ID: 0
Virtual Switch: Internal.vMX
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
3. Configure Name: p2p1-ge.vMX
VLAN ID: 0
Virtual Switch: vmnic2
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
4. Configure Name: p2p2-ge.vMX
VLAN ID: 0
Virtual Switch: vmnic2
Security Accept to all:
Promiscuous mode: Accept
Mac address changes: Accept
Forged transmits: Accept
4.3. Note: I made a discovery opening vMX in SSH using ssh root@172.25.11.3 command
murgescusilvia@Murgescus-MacBook-Pro ~ % ssh root@172.25.11.3
Password:
Last login: Fri May 15 00:30:49 2020
--- JUNOS 20.1R1.11 Kernel 64-bit JNPR-11.0-20200219.fb120e7_buil
root@vMX:~ # cli
root@vMX> show interfaces terse | match ge-
ge-0/0/0 up up
ge-0/0/0.16386 up up
ge-0/0/1 up up
ge-0/0/1.16386 up up
ge-0/0/2 up down
ge-0/0/2.16386 up down
ge-0/0/3 up down
ge-0/0/3.16386 up down
ge-0/0/4 up down
ge-0/0/4.16386 up down
ge-0/0/5 up down
ge-0/0/5.16386 up down
ge-0/0/6 up down
ge-0/0/6.16386 up down
ge-0/0/7 up down
ge-0/0/7.16386 up down
ge-0/0/8 up down
ge-0/0/8.16386 up down
ge-0/0/9 up down
ge-0/0/9.16386 up down
Only ge-0/0/0 and ge-0/0/1 are up up. All other networks are up down. You have to create other Port group networks to put more in up up. For example, the total number o network creation in VM is p2p3-ge.vMX to maximum p2p8-ge.vMX
root@vMX> show interfaces terse | match ge-
ge-0/0/0 up up
ge-0/0/0.16386 up up
ge-0/0/1 up up
ge-0/0/1.16386 up up
ge-0/0/2 up up
ge-0/0/2.16386 up up
ge-0/0/3 up up
ge-0/0/3.16386 up up
ge-0/0/4 up up
ge-0/0/4.16386 up up
ge-0/0/5 up up
ge-0/0/5.16386 up up
ge-0/0/6 up up
ge-0/0/6.16386 up up
ge-0/0/7 up up
ge-0/0/7.16386 up up
ge-0/0/8 up down
ge-0/0/8.16386 up down
ge-0/0/9 up down
ge-0/0/9.16386 up down
! At the moment I do not know how to make all ge interfaces, including ge-0/0/8 and ge-0/0/9, up up. I will search a solution when I will needed.
Step 5. Deploying the VCP VM
To deploy the VCP VM using .ova files:
Enter VMware ESXi using Firefox
Click Virtual Machine > Create/ Register VM
Select create type: click Deploy a virtual Machine for an OVF to OVA file and Next
Select OVF and VMDK files:
Name: vMX-vVCP_20.1R1.1
File: vcp_20.1R1.11.ova
Click Next
Select storage: ESXi00.datastore1 and Next
Untag Power on automatically end Next
Click Finish
Step 6. Deploying the FPC VM
To deploy the FPC VM using .ova files:
Enter VMware ESXi using Firefox
Click Virtual Machine > Create/ Register VM
Select create type: click Deploy a virtual Machine for an OVF to OVA file and Next
Select OVF and VMDK files:
Name: vMX-vFPC_20.1R1.1
File: vfpc_20.1R1.11.ova
Click Next
Select storage: ESXi00.datastore1 and Next
Untag Power on automatically end Next
Click Finish
After you have deployed the vVCP and vFPC VMs, you can modify the amount of memory, the number of vCPUs, and the number of WAN (here vmnic2) ports.
Step 7.Settings for the vVCP VM
CPU: 1
Memory: 1024 MB
Network Adapter 1: br-ext.vMX
Adapter Type: E1000
Network Adapter 2: br-int.vMX
Adapter Type: E1000
Step 8.Settings for the vFPC VM
CPU: 3
Memory: 2048 MB
Network Adapter 1: p2p1-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 2: p2p2-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 3: br-ext.vMX
Adapter Type: E1000
Network Adapter 4: br-int.vMX
Adapter Type: E1000
Not mandatory but you can add more networks:
Network Adapter 5: p2p3-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 6: p2p4-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 7: p2p5-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 8: p2p6-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 9: p2p7-ge.vMX
Adapter Type: VMXNET 3
Network Adapter 10: p2p8-ge.vMX
Adapter Type: VMXNET 3
Step 9.Launching vMX on VMware
Now you are ready to launching vMX on VMware. The firs basic configuration is the following:
[edit]
root@silvia# show
## Last changed: 2020-01-17 04:53:09 UTC
version 20.1R1.11;
system {
host-name vMX;
root-authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
login {
class c1only {
logical-system C1;
permissions all;
}
class c2only {
logical-system C2;
permissions all;
}
class c3only {
logical-system C3;
permissions all;
}
class c4only {
logical-system C4;
permissions all;
}
class r1only {
logical-system R1;
permissions all;
}
class r2only {
logical-system R2;
permissions all;
}
class r3only {
logical-system R3;
permissions all;
}
class r4only {
logical-system R4;
permissions all;
}
class r5only {
logical-system R5;
permissions all;
}
class r6only {
logical-system R6;
permissions all;
}
class r7only {
logical-system R7;
permissions all;
}
user class01 {
uid 2001;
class c1only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user class02 {
uid 2002;
class c2only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user class03 {
uid 2003;
class c3only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user class04 {
uid 2004;
class c4only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos01 {
uid 2023;
class r1only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos02 {
uid 2024;
class r2only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos03 {
uid 2223;
class r3only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos04 {
uid 2224;
class r4only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos05 {
uid 2225;
class r5only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos06 {
uid 2226;
class r6only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user junos07 {
uid 2227;
class r7only;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
user vMX {
full-name "Silvia Murgescu";
uid 2000;
class super-user;
authentication {
encrypted-password "your_passord"; ## SECRET-DATA
}
}
}
services {
ssh {
root-login allow;
protocol-version v2;
}
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
processes {
dhcp-service {
traceoptions {
file dhcp_logfile size 10m;
level all;
flag all;
}
}
}
}
logical-systems {
C1;
C2;
C3;
C4;
R1;
R2;
R3;
R4;
R5;
R6;
R7;
Source;
Receiver;
}
chassis {
fpc 0 {
pic 0 {
tunnel-services {
bandwidth 10g;
}
interface-type ge;
number-of-ports 8;
}
lite-mode;
}
network-services enhanced-ip;
}
interfaces {
ge-0/0/0 {
vlan-tagging;
}
ge-0/0/1 {
vlan-tagging;
}
ge-0/0/2 {
vlan-tagging;
}
ge-0/0/3 {
vlan-tagging;
}
ge-0/0/4 {
vlan-tagging;
}
ge-0/0/5 {
vlan-tagging;
}
ge-0/0/6 {
vlan-tagging;
}
ge-0/0/7 {
vlan-tagging;
}
fxp0 {
unit 0 {
description For_SSH_Connection;
family inet {
address 172.25.11.3/24;
}
}
}
}
Note: The 172.25.11.1 IP or 172.25.11.2 IP not working to open/run vMX in MacBook Pro Terminal application. I have tried and works if configure IP 172.25.11.3/24.
To copy and paste a config from a text file. Use the CTRL-D or ^D option to exit the terminal mode and return to the firewall prompt.
[edit]
root@vMX# load replace terminal
-> Copy and Paste here
CTRL-D
[edit]
root@SRX# commit
NOTE: If interfaces connectivity and communication is needed, into Port Groups include VLAN ID 6095.
Below is an example: two logical-systems with 2 difference interfaces, ge-0/0/1.12 and ge-0/0/5.12 and the ping command for testing works