2020.05.13 – Install Juniper vMX into ESXi 6.7.0

Software for this installation:

  • MacBook PRO with 16GB hardware of RAM 
  • VMware Fusion 11.5.1
  • VMware vSphere Hypervisor (a.k.a. ESXi 6.7.0 ISO) Installed and configure with 4 CPUs and 8 GB RAM.

Reference tutorial: https://www.juniper.net/documentation/en_US/vmx/topics/topic-map/vmx-installing-on-vmware.html

Tony helped me a lot at the begging. He is the one that also publish a lot of useful article in his blog GRASPINGTECH

Maximum Minimum Hardware Requirements for VMware

A. Number of cores

  • Note: Performance mode is the default mode and the minimum value is based on one port.
    • For lite mode: Minimum of 4
      • 1 for VCP
      • 3 for VFP
    • Note: If you want to use lite mode when you are running with more than 3 vCPUs for the VFP, you must explicitly configure lite mode.

B. Memory

  • Note: Performance mode is the default mode.
    • For lite mode: Minimum of 3 GB
      • 1 GB for VCP
      • 2 GB for VFP

C. Storage

  • Local or NAS
  • Each vMX instance requires 44 GB of disk storage
  • Minimum storage requirements:
    • 40 GB for VCP
    • 4 GB for VFP

vMX Package Contents

  • Software image file for VCP: ova/vcp_20.1R1.11.ova
  • Software image file for VFP: ova/vfpc_20.1R1.11.ova

Configuration

Step 1. Download the vMX software package for VMware: vmx-bundle-esxi-20.1R1.11.tar

  • From the vMX page 
  • 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

2020.05.6 – Start Juniper JSE lab into VMware ESXi

Juniper Space Essentials (JSE) lab is a laboratory for JSE cours. I will configure this lab on:

  • MacBook PRO with macOS Catalina 10.15.4 and 16 GB memory
  • VMware Fusion 11.5.3
  • VMware ESXi 6.7.0

Step 1. Lab Network Diagram: Network Application Platform

Content inside a single ESXi:

  • Juniper vMX router including
    • vFPC and vVCP
    • Maximum 15 logical-systems
  • CentOS 8 VM
  • Juniper jSpace 19.4R1.3

Step 1.1. Configure the network in MacBook PRO and VMware Fusion

Add this in MacBook PRO in networking file

sudo vim /Library/Preferences/VMware\ Fusion/networking


answer VNET_90_DHCP no
answer VNET_90_DHCP_CFG_HASH FE0C96BF7336905CC5CBAEE1429075B44B7967CE
answer VNET_90_DISPLAY_NAME vSphere
answer VNET_90_HOSTONLY_NETMASK 255.255.255.0
answer VNET_90_HOSTONLY_SUBNET 10.1.1.0
answer VNET_90_NAT yes
answer VNET_90_NAT_PARAM_UDP_TIMEOUT 30
answer VNET_90_VIRTUAL_ADAPTER yes
answer VNET_91_DHCP no
answer VNET_91_DHCP_CFG_HASH A1C76BDC5757C2D1C1AB73A7542E3550A9C88BA1
answer VNET_91_DISPLAY_NAME JunOS-fxp0
answer VNET_91_HOSTONLY_NETMASK 255.255.255.0
answer VNET_91_HOSTONLY_SUBNET 172.25.11.0
answer VNET_91_NAT yes
answer VNET_91_NAT_PARAM_UDP_TIMEOUT 30
answer VNET_91_VIRTUAL_ADAPTER yes
answer VNET_92_DHCP no
answer VNET_92_DHCP_CFG_HASH EAD55CCD2F57318B68F4A60E8E63B8F090516844
answer VNET_92_DISPLAY_NAME JunOS-ge
answer VNET_92_HOSTONLY_NETMASK 255.255.0.0
answer VNET_92_HOSTONLY_SUBNET 172.17.0.0
answer VNET_92_NAT yes
answer VNET_92_NAT_PARAM_UDP_TIMEOUT 30
answer VNET_92_VIRTUAL_ADAPTER yes

Step 1.2. Configure the network in VMware ESXi

Add maximum networks in VMware ESXi

Note: This lab needed three Network Adapter.

Step 2. Power ON all then read all apply the lab inside JSE guide.

Observation: I have problem installing this lab in EVE-PRO. I successfully install in ESXi. The MacBook PRO makes noice if all application for lab are power on, do I will power on all when is absolutely necessary for the lab.

2020.05.6 – Install CentOS 8 Server on VMware ESXi

This page inspire me: https://linuxhint.com/install_centos8_vmware_esxi_server/

Note: This version is without GUI. If needed chose Server with GUI.

The inspiration is very good. I have some differences and I will put here.

Difference:

  • Install into MacBook Pro > VMware Fusion > VMware ESXi
  • Click ESXi web client > Datastore browser > Create directory with name CentOS
  • Different Hard Disk and Network Adapter
  • Host Name: CentOS
  • Tipe and Data: for Romania
  • Username: silvia and mine password
  • Include also Root password

All other are exactly as in the helping blog.

2020.05.3 – Install Junos Space on VMware Fusion in VMware ESXi

Device and Applications:

  • MacBook PRO 15-inch, 16 GB Memory, 2.9 GHz Processor
  • macOS Catalina 10.15.4
  • VMware Fusion 11.5.3
  • VMware ESXi 6.7

Details from reading and learning installation here:

Download Junos Space files

I this moment the last versions:

  • The ova image: space-19.4R1.3.ova
  • The security director: Security-Director-19.4R1.53.img

Overview

You can deploy the Junos Space Virtual Appliance *.ova file on a VMware ESXi server version 5.5, 6.0, or 6.5. Basic I have ESXi 6.7 but into installation step maybe I can modify to 6.0.

After the Junos Space Virtual Appliance is deployed, you can use the VMware vSphere client or Virtual Machine Manager (VMM) to connect to the VMware ESXi server and configure the Junos Space Virtual Appliance.

The minimum hardware requirements for deploying a Junos Space Virtual Appliance are as follows: 

Installing a Junos Space Virtual Appliance on a VMware ESXi Server

Login ESXi, mine name is esxi00. Go to Virtual Machine > Create/Register VM and click Deploy a virtual machine from an OVF or OVA file. Then Next

Enter a name as jSpace-1-20.1R1.2. I needed an other version to install and I use the name jSpace-2-19.4R1.3. Find in MacBook and chose space-19.4R1.3.ova file. Click Next

Chose the datastore where jSpace will be installed

  • Note: I have install a new ESXi VM into VMware Fusion with
    • Datastore name: datastre1
    • Capacity: 532 GB
    • Free: 504 GB (as I install CentOS firs)
    • Type: VMFS6

Please untag the Power on Automatically and you will si way … Click Next

Verify that all is correctly and click Finish

Failed to Power On. I mine case some modification have to be done before powering on.

Down in Recent Tasks you will see and wot to finish to complete. After finished go further.

Go to Virtual Machine > jSpace-1-20.1R1.2. This si default

Virtual Machine > jSpace-2-19.4T1.3

Click Edit

CPU 2, Memory 8 GB meaning 8192 MB, Default Hard Disk is minimal accepted of 500 GB.

To be able to finish type 500 GB

Power on is working now. Go here to get help: https://rtodto.net/how-to-install-junos-space-and-security-director/

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
Configuring Eth0:

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
172.25.11.109
Please enter new IPv4 subnet mask for interface eth0
255.255.255.0

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

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

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:
172.25.11.100

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

Add NTP Server? [y/N] y

Please type the new NTP server: 82.197.221.30

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

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.

  • Get inside CentOS using the password
  • Open Firefox application
  • Use https://172.25.11.100 to open Junos Space
    • Username: super
    • Password: juniper123
  • Change Temporary Password

Now going to install Security-Director-19.4R1.53.img file.

Security Director

Testing ping in MacBook Pro Terminal

murgescusilvia@Murgescus-MacBook-Pro ~ % ping centos
PING centos.silvique.ro (10.1.1.50): 56 data bytes
64 bytes from 10.1.1.50: icmp_seq=0 ttl=64 time=0.832 ms
64 bytes from 10.1.1.50: icmp_seq=1 ttl=64 time=1.320 ms
64 bytes from 10.1.1.50: icmp_seq=2 ttl=64 time=0.684 ms
c64 bytes from 10.1.1.50: icmp_seq=3 ttl=64 time=0.705 ms
64 bytes from 10.1.1.50: icmp_seq=4 ttl=64 time=0.461 ms
^C
--- centos.silvique.ro ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.461/0.800/1.320/0.286 ms
murgescusilvia@Murgescus-MacBook-Pro ~ %
  • -> Copy the file Security-Director-19.4R1.53.img from MacBook Pro to CentOS using Terminal from MacBook PRO

Not possible to use user name Silvia to update Security-Director-19.4R1.53.img file to CentOS:

murgescusilvia@Murgescus-MacBook-Pro ~ % scp -r /Users/murgescusilvia/Downloads/Security-Director-19.4R1.53.img Silvia@10.1.1.50:~/
Silvia@10.1.1.50's password: 
Permission denied, please try again.
Silvia@10.1.1.50's password: 
Permission denied, please try again.
Silvia@10.1.1.50's password: 
Silvia@10.1.1.50: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
lost connection
murgescusilvia@Murgescus-MacBook-Pro ~ % 

Observation: Maybe it was a mistake using Silvia when I should use silvia.

But is possible to do the same and replace Silvia with root:

murgescusilvia@Murgescus-MacBook-Pro ~ % scp /Users/murgescusilvia/Downloads/Security-Director-19.4R1.53.img root@10.1.1.50:/
root@10.1.1.50's password: 
Security-Director-19.4R1.53.img                                   37%  523MB  24.5MB/s   00:35 ETA
  • -> Enter in CentOS
  • -> Open Terminal application and use cd .. command many times which goes to the top folder
  • -> From user silvia go to root with command su root
[silvia@CentOS /]$ su root
Password:

[root@CenrOS /]#

-> Copy the Security-Director-19.4R1.53.img file to /home/silvia/Download directory

[root@CenrOS /]# sudo cp Security-Director-19.4R1.53.img /home/silvia/Downloads/Security-Director-19.4R1.53.img

-> Remove file from root

[root@CenrOS /]# sudo rm Security-Director-19.4R1.53.img
[root@CenrOS /]# ls

Ready to use jSpace to deploy the security director.

  • Inside CentOS open Firefox than jSpace using the web IP like https://172.25.11.100
  • Web user is super and the configured password
  • Go to Adminitration -> Applications -> + button meaning Add Application
  • Select Upload via HTTP and upload the Security-Director-19.4R1.53.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. I exit and I will not enter again. Now I take a break to be sure it will be installed after mine break.
  • When it is finished you will see other new applications
    • Application Visibility – new
      • Version 19.4,
      • Release R1,
      • Build 53,
      • Server Group Platform
    • Log Director – new
      • Version 19.4,
      • Release R1,
      • Build 53,
      • Server Group Platform
    • Network Management Platform – exited already
      • Version 19.4,
      • Release R1,
      • Build 3,
      • Server Group Platform
    • NSM Migration
      • Version 19.4,
      • Release R1,
      • Build 53,
      • Server Group Platform
    • Security Director – new
      • Version 19.4,
      • Release R1,
      • Build 53,
      • Server Group Platform
    • Security Director Login and Reporting – new
      • Version 19.4,
      • Release R1,
      • Build 53,
      • Server Group Platform
  • In Administation > Licenses
    • License Type Tryal
    • Sku Mode Trial-license
    • Total License Days 60
    • Remaining Days 60

And here we are! We have installed both space platform and security director. Last but not least I need to recap usernames we have configured so far to avoid any confusion. 

1) admin user: We set this for the Linux shell and default password during the installation is abc123
2) maintenance user: we also set password for this but it is used for special operations. No default password for this. It must be set.
3) super user: this user is used for WEB UI and initial default password is juniper123

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.05.1 – Configuring a Junos Space Virtual Appliance in EVE-PRO

Note: Not Working for me! I install Junos Space into ESXi and try to make it work.

What I need to read and apply are here: Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node

After you deploy a Junos Space Virtual Appliance on a EVE-PRO server, you must enter basic network and machine information to make your Junos Space Virtual Appliance accessible on the network. You must also add disk space to the partitions of the Junos Space Virtual Appliance.

Before you begin, ensure that you have the following information available:

  • IPv4 address and subnet mask for the node management (eth0) Ethernet interface
  • IPv4 address of the default gateway for the eth0 Ethernet interface
  • IPv4 address of the name server
  • Virtual IP (VIP) address in IPv4 and IPv6 formats
    • The IPv4 format of the VIP address is used for accessing the Junos Space Network Management Platform GUI through a Web browser. This IP address must be in the same subnet as the IP address assigned to the eth0 Ethernet interface
  • IPv4 address or URI of the NTP source to synchronize time

To configure a Junos Space Virtual Appliance:

  • At the Junos Space login prompt, type admin as your default login name and press Enter.
space-node login:admin 
Password:
  • Type abc123 as the default administrator password and press Enter. Junos Space prompts you to change your default password.
  • To change the default password, do the following: 
    • Type the default password and press Enter.
    • Type your new password and press Enter.
    • Retype your new password and press Enter.
  • Enter the new password to log in to Junos Space.
  • Type S to install the virtual appliance as a Junos Space node.
  • Configure the IP address for the eth0 interface.
    • Type 1.
    • Type the IPv4 address for eth0 interface in dotted-decimal notation and press Enter.
Please enter new IPv4 address for interface eth0:
172.25.11.99
  • Type the subnet mask for the IPv4 address and press Enter.
Please enter new IPv4 subnet mask for interface eth0:
255.255.255.0
  • Type the IPv4 address of the default gateway for the eth0 Ethernet interface in dotted-decimal notation and press Enter.
Enter the default IPv4 gateway as a dotted-decimal IP Address:
172.25.11.254

2020.05.1 – Start Juniper JSE lab into EVE-PRO

Juniper Space Essentials (JSE) lab is a laboratory for JSE cours. I will configure this lab on:

  • MacBook PRO
  • VMware Fusion
  • EVE-PRO

Step 1. Create tha lab in EVE-PRO

Step 2. Power-on all

To be sure it works Ok I power-on one at a time in this order:

  • JuniperSpace1
  • CentOS
  • vMX-VCP1
  • vMX-VFP1
  • vMX-VCP2
  • vMX-VFP2

Powered-on all but I have difficulty to continue to work on installation of JuniperSpace.

I will try to install all these lab in ESXi and see if it is working.

SSH commands

Move in a directory

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

View all existing file

root@eve-ng:/opt/unetlab/addons/qemu# ls
root@eve-ng:/opt/unetlab/addons/qemu# ls nextExisting_File_Name

Create a new directory

root@eve-ng:/opt/unetlab/addons/qemu# mkdir newDirName

Rename Directory

root@eve-ng:/opt/unetlab/addons/qemu# mv oldDirName NewDirName

Rename Files:

root@eve-ng:/opt/unetlab/addons/qemu# mv oldFileName newFileName

Create qcow2 file

root@eve-ng:/opt/unetlab/addons/qemu/NeededFolder# /opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 30G (use what needed)

Delete files

root@eve-ng:/opt/unetlab/addons/qemu# rm myFile.txt myFile1.txt myFile2.txt

Delete a whole folder and its content

root@eve-ng:/opt/unetlab/addons/qemu# rm -rf foldername/

Problem and solution

Problem when using ssh

murgescusilvia@Murgescus-MacBook-Pro ~ % ssh silvia@ip-address  

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 

The ECDSA host key for us01 has changed, and the key for the corresponding IP address ip-address is unchanged. 
This could either mean that DNS SPOOFING is happening or the IP address for the host and its host key have changed at the same time. 
Offending key for IP in /Users/murgescusilvia/.ssh/known_hosts:20 

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 

IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. 

The fingerprint for the ECDSA key sent by the remote host is SHA256:5b11LsICh7VVaHkfY/HiLh6IThcZYjkkDD7Pt6dixJw. 

Please contact your system administrator. Add correct host key in /Users/murgescusilvia/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/murgescusilvia/.ssh/known_hosts:19 ECDSA host key for ip-address has changed and you have requested strict checking. 

Host key verification failed.

Solution to solve this problem:

murgescusilvia@Murgescus-MacBook-Pro ~ % ssh-keygen -R ip-address 

# Host ip-address found: line 19 /Users/murgescusilvia/.ssh/known_hosts updated. 
Original contents retained as /Users/murgescusilvia/.ssh/known_hosts.old

I will add a command every time I search and use something.

Posted in NFV

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/

Note: I have installed 2 versions and I do not find a solution to make it work.

>>>>>>>> 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