2021.04.30 – Install CentOS.ova in VMware Fusion

This example is for:

  • MacBook Pro
  • Vmware Fusion Profesional 12.1.1
  • CentOS.ove
  1. Install CentOS.ove in VMware Fusion 

1.1. Download CentOS.7z.001 – CentOS.7z.004 

Note: Can be more or less files but here is an example of 4 files

1.2. Install and use Keka app to connect CentOS.7z.001 – CentOS.7z.004 and create CentOS.ova file

1.3. Import CentOS.ova in Vmware Fusion:

Select File > Import.

  • Click Choose file and browse to the .ovf or .ova file and click Open.
  • Type the name for the imported virtual machine in the Save As text box and indicate where to save it. The default destination is the Virtual Machines folder created by Fusion. 
  • Click Save. Fusion performs OVF or OVA specification conformance and virtual hardware compliance checks. A status bar indicates the progress of the import process. 

Note: The example is from Vmware docs –  https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-275EF202-CF74-43BF-

  • Click VMware Fusion > Virtual Machine > Settings > Advanced: activate Disable Side Channel Mitigations
  • Click VMware Fusion > Virtual Machine > Start Up
  • CentOS content: User: _visible_ and Password: _necesary_to_know_
  • Verify networks in CentOS > Terminal: 
$ ip add show 
=> Example: eth0 down, eth1 172.25.11.254/24, eth2 10.0.11.2/24 and 10.0.11.3/24
  • Take notes to be sure you will not forget for next steps
  • VMware Fusion > Virtual Machine > Shows Down
  1. Create/modify VMware Fusion Networks:
  • Open Terminal in MacBook Pro 
  • Open VMware network file: 
% sudo vim /Library/Preferences/VMware\ Fusion/networking
  • Modify! You can also use V in view mode to launch “VISUAL LINE” mode. Select your lines and type d to delete them.
  • Exemple of what I use
VERSION=1,0
 answer VNET_1_DHCP yes
 answer VNET_1_DHCP_CFG_HASH BC1AB29239D0B41CB64A4C11F3DE544B36D778A2
 answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
 answer VNET_1_HOSTONLY_SUBNET 192.168.120.0
 answer VNET_1_VIRTUAL_ADAPTER yes
 answer VNET_8_DHCP yes
 answer VNET_8_DHCP_CFG_HASH 96CB1EC54E103210F4A187D6355843A795323CCC
 answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
 answer VNET_8_HOSTONLY_SUBNET 192.168.100.0
 answer VNET_8_NAT yes
 answer VNET_8_VIRTUAL_ADAPTER yes
 …
 answer VNET_93_DHCP no
 answer VNET_93_DISPLAY_NAME eth1
 answer VNET_93_HOSTONLY_NETMASK 255.255.255.0
 answer VNET_93_HOSTONLY_SUBNET 172.25.11.0
 answer VNET_93_NAT yes
 answer VNET_93_NAT_PARAM_UDP_TIMEOUT 30
 answer VNET_93_VIRTUAL_ADAPTER yes
 answer VNET_94_DHCP no
 answer VNET_94_DISPLAY_NAME eth2
 answer VNET_94_HOSTONLY_NETMASK 255.255.255.0
 answer VNET_94_HOSTONLY_SUBNET 10.0.11.0
 answer VNET_94_NAT yes
 answer VNET_94_NAT_PARAM_UDP_TIMEOUT 30
 answer VNET_94_VIRTUAL_ADAPTER yes
 …
  • Quit VMware Fusion networking file
  • Open VMware Fusion app
  • Click VMware Fusion > Preferences > Network
  • Untagged Request authentication to enter promiscuous mode 
  • Click the lock to make changes
  • Activate Allow virtual machine on the network to connect to external networks (using NAT)
  • Quit VMware Fusion app
  • Open VMware Fusion app again
  1. Configure CentOS VM network in VMware Fusion app
  • Open VMware Fusion app
  • Click Virtual Machine > CentOS
  • Click Virtual Machine > Settings… 
  • — Network Adapter > Autodetect (is for eth0)
  • — Network Adapter 2 > eth1
  • — Network Adapter 3 > eth2 _to_ge-0/0/0

Note: To create and use Networks: http://tech.silvique.ro/2021/04/29/2021-04-29-create-vmware-fusion-networks/

  • Click Virtual Machine > Start Up
  1. Verify CentOS VM network inside CentOS
  • Open Terminal in CentOS and use different commands to verify
 $ ifconfig
 — eth1 172.25.11.254
 — eth2:8012 10.0.11.2/24 
 — eth2:8013 10.0.11.3/24
$ ping 10.0.11.1
$ ping 10.0.11.2
$ ping 10.0.11.3
$ ping 172.25.11.254
$ ping 172.25.11.1 

If necessary, modify network connectivity in Vmware Fusion.

Good Luck!!

2020.10.24 – Juniper vMX 20.2 installation in EVE-PRO

Very useful: https://www.eve-ng.net/index.php/documentation/howtos/howto-add-juniper-vmx-16-x-17-x/

This guide is based on version:

  • EVE images name, vCPUs and vRAM
    • vmxvcp-20.2R1.10-domestic-VCP, 1 vCPU, 2 Gb vRAM
    • vmxvfp-20.2R1.10-domestic-VFP, 3 vCPUs, 4 Gb vRAM
  • Downloaded Filename
    • vmx-bundle-20.2R1.10.tar
  • Version
    • Junos: 20.2R1.10

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

Step 3. Uncompress images:

root@eve-ng:/opt/unetlab/addons/qemu/vMX# tar xvf vmx-bundle-20.2R1.10.tar

root@eve-ng:/opt/unetlab/addons/qemu/vMX# cd vmx-limited/images/

root@eve-ng:/opt/unetlab/addons/qemu/vMX2/vmx/images# ls
junos-vmx-x86-64-20.2R1.10.qcow2  metadata-usb-fpc4.img  metadata-usb-re1.img
junos-vmx-x86-64-20.2R1.10.tgz    metadata-usb-fpc5.img  metadata-usb-service-pic-10g.img
metadata-usb-fpc0.img                     metadata-usb-fpc6.img  metadata-usb-service-pic-2g.img
metadata-usb-fpc1.img                     metadata-usb-fpc7.img  metadata-usb-service-pic-4g.img
metadata-usb-fpc10.img                    metadata-usb-fpc8.img  vFPC-20200213.img
metadata-usb-fpc11.img                    metadata-usb-fpc9.img  vmxhdd.img
metadata-usb-fpc2.img                     metadata-usb-re.img
metadata-usb-fpc3.img                     metadata-usb-re0.img

Step 4. Create VCP image folder:

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# mkdir /opt/unetlab/addons/qemu/vmxvcp-20.2R1.10-domestic-VCP

Step 5. Copy images to VCP image folder:

 Step 5.1. virtioa.qcow2

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# cp junos-vmx-x86-64-20.2R1.10.qcow2 /opt/unetlab/addons/qemu/vmxvcp-limited-20.2R1.10-domestic-VCP/virtioa.qcow2

 Step 5.2. virtiob.qcow2

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# cp vmxhdd.img /opt/unetlab/addons/qemu/vmxvcp-20.2R1.10-domestic-VCP/virtiob.qcow2

 Step 5.3. virtioc.qcow2

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# cp metadata-usb-re.img /opt/unetlab/addons/qemu/vmxvcp-20.2R1.10-domestic-VCP/virtioc.qcow2

Check all

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# ls /opt/unetlab/addons/qemu/vmxvcp-20.2R1.10-domestic-VCP
virtioa.qcow2  virtiob.qcow2  virtioc.qcow2

Step 6. Create VFP image folder:

root@eve-ng:/opt/unetlab/addons/qemu# mkdir /opt/unetlab/addons/qemu/vmxvfp-20.2R1.10-domestic-VFP

Step 7. Copy images to VFP image folder:

 Step 7.1. virtioa.qcow2

root@eve-ng:/opt/unetlab/addons/qemu/vMX/vmx/images# cp vFPC-20200819.img /opt/unetlab/addons/qemu/vmxvfp-20.2R1.10-domestic-VFP/virtioa.qcow2

Step 8. Fix permissions:

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


Apr 24 15:05:36 Apr 24 15:05:36 Online Check state: Valid

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.

Topology testing:

2020.06.28 – Junos Space Basic Configuration

Note:

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.

Photo 1

Photos are here: https://photos.app.goo.gl/UaRErMr4qRj33HgY7

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

Photo 2

Photos are here: https://photos.app.goo.gl/UaRErMr4qRj33HgY7

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

Photo 3

Photos are here: https://photos.app.goo.gl/UaRErMr4qRj33HgY7

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.18 – FileZilla Pro – Solution: You do have permission to list this directory

Note: All Photos are here: https://photos.app.goo.gl/6CJiMu74nPUXfdRy8

How to copy a file from MacBook Pro to EVE-PRO?

Using FileZilla:

  • meaning FileZilla Pro
  • in MacBook Pro
  • to insert files in EVE-PRO

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

Photo 1

Solution

1.. Go to Edit > Directory access permissions…

Photo 2

2.. Click Add directory… and chose the directory from you MacBook Pro

Photo 3

3.. The directory you have chose is available to chose the applications from MacBook Pro and copy to EVE-PRO.

Photo 4

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.

Photo 5

I am happy!

Note: All Photos are here: https://photos.app.goo.gl/6CJiMu74nPUXfdRy8

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

Click for Photo here: https://photos.app.goo.gl/p8gu1wznpspUi4EU9

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.5 – Problem and Solution with Adding ESXi host in vSphere Client

Note: All photo are here: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

I have a problem with Adding ESXi host into vSphere Client. 

Cannot contact the specified host (esxi00.silvique.ro). The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding.
  • I need to put ESXi into vSpare to install a new VM as I do not find solution of installation into ESXi. But if I insert esxi00 into vSphere using the IP, I can not install VM. So I want to insert esxi00.silvique.ro base on its name to try to install Junos Spare.
    • I thought it is fw problem, so I install it into esxi00 and powered on.

Proto 1: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

Proto 2: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

Proto 3: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

  • What can I do to insert esxi00.silvique.ro into vShere?

Ideas and solution

1. Check to see if you can ping the hostname from the vCenter appliance.

vCenter and ESXi from MacBook

murgescusilvia@Murgescus-MacBook-Pro ~ % ping 10.1.1.101
PING 10.1.1.101 (10.1.1.101): 56 data bytes
64 bytes from 10.1.1.101: icmp_seq=0 ttl=64 time=0.336 ms
64 bytes from 10.1.1.101: icmp_seq=1 ttl=64 time=0.598 ms
64 bytes from 10.1.1.101: icmp_seq=2 ttl=64 time=0.496 ms
64 bytes from 10.1.1.101: icmp_seq=3 ttl=64 time=0.217 ms
^C
--- 10.1.1.101 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.217/0.412/0.598/0.146 ms

murgescusilvia@Murgescus-MacBook-Pro ~ % ping vc01      
PING vc01.silvique.ro (10.1.1.101): 56 data bytes
64 bytes from 10.1.1.101: icmp_seq=0 ttl=64 time=0.403 ms
64 bytes from 10.1.1.101: icmp_seq=1 ttl=64 time=0.623 ms
64 bytes from 10.1.1.101: icmp_seq=2 ttl=64 time=0.456 ms
^C
--- vc01.silvique.ro ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.403/0.494/0.623/0.094 ms

murgescusilvia@Murgescus-MacBook-Pro ~ % ping vc01.silvique.ro
PING vc01.silvique.ro (10.1.1.101): 56 data bytes
64 bytes from 10.1.1.101: icmp_seq=0 ttl=64 time=0.355 ms
64 bytes from 10.1.1.101: icmp_seq=1 ttl=64 time=0.881 ms
^C
--- vc01.silvique.ro ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.355/0.618/0.881/0.263 ms

murgescusilvia@Murgescus-MacBook-Pro ~ % ping 10.1.1.10       
PING 10.1.1.10 (10.1.1.10): 56 data bytes
64 bytes from 10.1.1.10: icmp_seq=0 ttl=64 time=0.517 ms
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.389 ms
^C
--- 10.1.1.10 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.389/0.453/0.517/0.064 m
s
murgescusilvia@Murgescus-MacBook-Pro ~ % ping esxi00   
PING esxi00.silvique.ro (10.1.1.10): 56 data bytes
64 bytes from 10.1.1.10: icmp_seq=0 ttl=64 time=0.315 ms
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.513 ms
64 bytes from 10.1.1.10: icmp_seq=2 ttl=64 time=0.325 ms
^C
--- esxi00.silvique.ro ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.315/0.384/0.513/0.091 ms

murgescusilvia@Murgescus-MacBook-Pro ~ % ping esxi00.silvique.ro
PING esxi00.silvique.ro (10.1.1.10): 56 data bytes
64 bytes from 10.1.1.10: icmp_seq=0 ttl=64 time=0.385 ms
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.709 ms
^C
--- esxi00.silvique.ro ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.385/0.547/0.709/0.162 ms

ESXi00 from vCenter

murgescusilvia@Murgescus-MacBook-Pro ~ % ssh root@vc01.silvique.ro
…..

Command> ping 10.1.1.10
PING 10.1.1.10 (10.1.1.10) 56(84) bytes of data.
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=1.01 ms
64 bytes from 10.1.1.10: icmp_seq=2 ttl=64 time=1.11 ms
64 bytes from 10.1.1.10: icmp_seq=3 ttl=64 time=1.29 ms
64 bytes from 10.1.1.10: icmp_seq=4 ttl=64 time=0.978 ms
^C
--- 10.1.1.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 0.978/1.101/1.299/0.124 ms
 
Command> ping esxi00
ping: unknown host esxi00


Command> ping esxi00.silvique.ro
ping: unknown host esxi00.silvique.ro

2. If you cant you can either edit the host file on the vcenter machine

2.1. SSH’d into the vCenter using Terminal

Last login: Tue May  5 07:19:26 on ttys006
murgescusilvia@Murgescus-MacBook-Pro ~ % ssh root@vc01.silvique.ro

Command> ls /etc/
Unknown command: `ls'
Command> cd etc
Unknown command: `cd'

Command> shell
Shell access is granted to root

root@10 [ ~ ]# 

2.2. Navigated to the host files directory

  • cd /
  • cd etc
  • ls (this list everything in the directory)
root@10 [ ~ ]# cd ..
root@10 [ ~ ]# cd /etc

2.3. Used vim to edit the file:

  • vim hosts
root@10 [ /etc ]# vim hosts

2.4. Added the name and the IP that I wanted to be tied together.

  • xxx.xxx.xxx.xxx name.domain name
# Begin /etc/hosts (network card version)


127.0.0.1   localhost.localdomain
127.0.0.1       localhost
10.1.1.101 10.1.1.101 10
10.1.1.10  esxi00.silvique.ro  esxi00
# End /etc/hosts (network card version)

2.5. Exited vi (vi automatically saves the file when you leave unless specified to not save when you leave.)

  • To exit and save type                ESC + : x or ESC + : wq
  • To exit without saving type        Esc + : q!
Esc 
:wq

2.6. Now test it using the Ping command.

  • ping name
Command> ping 10.1.1.10
PING 10.1.1.10 (10.1.1.10) 56(84) bytes of data.
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.687 ms
64 bytes from 10.1.1.10: icmp_seq=2 ttl=64 time=0.512 ms
64 bytes from 10.1.1.10: icmp_seq=3 ttl=64 time=1.03 ms
64 bytes from 10.1.1.10: icmp_seq=4 ttl=64 time=0.883 ms
^C
--- 10.1.1.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 0.512/0.780/1.039/0.199 ms

Command> ping esxi00.silvique.ro
ping: unknown host esxi00.silvique.ro
Command> ping 10.1.1.10
PING 10.1.1.10 (10.1.1.10) 56(84) bytes of data.
64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.663 ms
64 bytes from 10.1.1.10: icmp_seq=2 ttl=64 time=1.03 ms
64 bytes from 10.1.1.10: icmp_seq=3 ttl=64 time=0.790 ms
64 bytes from 10.1.1.10: icmp_seq=4 ttl=64 time=0.719 ms
^C
--- 10.1.1.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.663/0.802/1.038/0.145 ms
Command> ping esxi00.silvique.ro
PING esxi00.silvique.ro (10.1.1.10) 56(84) bytes of data.
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=1 ttl=64 time=0.385 ms
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=2 ttl=64 time=0.539 ms
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=3 ttl=64 time=0.668 ms
^C
--- esxi00.silvique.ro ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.385/0.530/0.668/0.118 ms

Command> ping esxi00
PING esxi00.silvique.ro (10.1.1.10) 56(84) bytes of data.
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=1 ttl=64 time=0.388 ms
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=2 ttl=64 time=0.581 ms
64 bytes from esxi00.silvique.ro (10.1.1.10): icmp_seq=3 ttl=64 time=0.599 ms
^C
--- esxi00.silvique.ro ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.388/0.522/0.599/0.099 ms

Solution photos

Proto 4: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

Proto 5: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

An other idea: Or add the host to the dnsresolver on the pfsense firewall. When using the firewall, the vcenter machine needs to have the IP of the firewall as it’s gateway and dns server. 

It seems I don’t this idea now …

All proto: https://photos.app.goo.gl/hjpy75LpmuJVA8Ed7

2020.05.3 – Install Junos Space on VMware Fusion in VMware ESXi

Notes:

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

Verify that all is correctly and click Finish

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

Click Edit

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

To be able to finish type 500 GB

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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.

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

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

Note: In NTP server you can use also the default IPv4, here meaning 172.25.11.254.

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

Photo here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

Now you can connect to the box via SSH at its ip 172.25.11.109:

% ssh admin@172.25.11.109

admin@172.25.11.109's password: the-password

Junos Space Settings Menu
...
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

All photoare here: https://photos.app.goo.gl/ByoFKzyqe3yLMqHv9

2020.05.2 – Connecting EVE Lab to a physical device

Note: All photo are here: https://photos.app.goo.gl/GVJME61MFbZ6UeRE9

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.

Photo: https://photos.app.goo.gl/GVJME61MFbZ6UeRE9

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

Photo: https://photos.app.goo.gl/GVJME61MFbZ6UeRE9

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

Photo: https://photos.app.goo.gl/GVJME61MFbZ6UeRE9

I am happy!!!