I have read and applied what is here: Running VMware vCenter 6.7 on VMware Fusion
The link is here: https://graspingtech.com/vcenter-vmware-fusion/
Good lock!
I have read and applied what is here: Running VMware vCenter 6.7 on VMware Fusion
The link is here: https://graspingtech.com/vcenter-vmware-fusion/
Good lock!
Read and learn from here: How to run Nested Virtualization on a Mac
Link is this: https://graspingtech.com/nested-virtualization-mac/
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.
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:
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:
Info in YouTube:
Note: Modified and updated on 2020.09.1.
This page is about basic configuration of jSpace installed in EVE-PRO or VMware Fusion. I will go further to include configuration in EVE-PRO.
Note: jSpace need to be connected to a network which has access to Internet.
MacBook Pro is external, connected to internet and used for configuration inside terminal and Firefox. Appears in picture just just for understanding the configuration and use of jSpace.
1 – Click jSpace. It will be opened in EVE-PRO.
2 – You will be asked to enter user and password respectively also for UNIX password.
3 – After this you will be asked to change the password. Choose your new password according to the local instructions. Otherwise you may fail to set a proper password.
[sudo] password for admin: Juniper123Juniper123 (- the_configured_password)
4 – Press enter and continue. Configuration Eth0 will start.
Choose the type of node to be installed [S/F] S
Configuring Eth0: 1) Configure UPv4 2) Configure Both IPv4 and IPv6 R) Redraw Menu
5 – Click 1 and continue
Choice [1-2,R]: 1
Please enter new IPv4 address for interface eth0 192.168.100.199 Please enter new IPv4 subnet mask for interface eth0 255.255.255.0 Enter the default IPv4 gateway as a dotted-decimal IP address: 192.168.100.1 Please type the IPv4 nameservicer address in dotted decimal notation: 8.8.8.8 Configure a separate interface for device management? [y/N] n Will this Junos Space system be added to an existing cluster? [y/N] n
6 – Web GUI configuration
Configuring IP address for web GUI: 1) Configure IPv4 R) Redraw Menu Chose [1,R]: 1 Please enter IPv4 Address for web GUI: 192.168.100.200 Do you want to enable NAT service? [y/N] n Add NTP Server? [y/N] y Please type the new NTP server: 192.168.100.1 Please enter display name for this node: jSpace Enter password for cluster maintenance mode: Juniper123Juniper123 (- mine_password) Re-enter password: Juniper123Juniper123 (- mine_password) ----- A> Apply settings ----- Chose [ACQR]: A
Note: For Please type the new NTP server: 192.168.100.1 which is default IPv4 gateway you can use also something external like 82.197.221.30
Here is an image but all to do list is up
7 – Now you can connect to the box via SSH at its ip 192.168.100.199
% ssh admin@192.168.100.199 admin@192.168.100.199's password: Juniper123Juniper123 (- the-password) ... 7) (Debug) run shell ... Chose [1-7,AQR]: 7 [sudo] password for admin: Juniper123Juniper123
[root@space-000c29cb6706 ~]# ip -4 addr 1: lo: <LOOPBACK,UP,LOWER_UP> meu 655536 disc no queue state UNKNOWN inet 127.0.0.1/8 scope host lo 2: eth0: <BROUDCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 inet 192.168.100.199/24 brd 192.168.100.255 scope global eth0 <---Primary IP inet 192.168.100.200/24 brd 192.168.100.255 scope global secondary eth0:0 <---Secondary GUI IP Address
8 – Now it is time to login to the web UI.
Note: If connect to correct internet and configure with current ip, jSpace can be open also with Firefox from MacBook Pro.
You have to configure a new password. I insert mine new password jSpace321jSpac.
9 – Ready to use jSpace to deploy the Network Director.
Enjoy!!
How to copy a file from MacBook Pro to EVE-PRO?
Using FileZilla:
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.
I am happy!
Importamt information:
Note: This article does not contain all information for different situations. It contains the information for mine use only. I will update this article till I finish all installation.
1.. EVE System Requirements
1.1. EVE-NG requires:
1.2. NOT Officially supported or have issues:
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
2.2. Hardware I bought to use
-> Monitor LED Sell from eMAG: www.emag.ro
-> Keyboard Kit + Mouse A + K1 Kandaon, Black from eMAG: www.emag.ro
-> DELL Precision T7910 Workstation from Server Config: www.server-config.ro
Content:
3.. Static IP on ONT/Router HG8247U
Note: This is what I have in my house in this moment of creating this page. HG8247U is an old version that I use but on internet I found specification for HG8247H version and seems the same and helped me.
Informations here: https://hg8245h.wordpress.com/2015/12/14/how-to-assign-static-ip-address-on-hg8245h/
Many people prefer to have static internal IP address rather than some random numbers allocated by the DHCP server. Two ways to accomplish that, either assign a static IP directly in your computer network settings or use IP reservation which is the preferred way of doing it.
Testing: I have configured an Manual IP Address for iMac. From iMac I ping all Its from devices I have in house like iPad or BOSE SoundLinks and it is OK.
It si required and I decide to configure Static IP directly into
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 :
Create installation 2 separate DVDs:
4.1. Invalid partition table! error
4.2. Ubuntu Server Installation
Note: Internet is reachable from mine Dell Precision. EVE ISO installation requires internet access to get updates and install the latest EVE-PRO version from the EVE-NG repository. DNS must work as well. To check it, do a named ping, for example ping www.google.com.
4.2.1. Ubuntu Server Installation Phase 1
All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/
Sume help here: https://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html
4.2.2 EVE Professional Installation Phase 2
All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/
4.2.3 EVE Professional Installation Phase 3
All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/
4.3. EVE Management IP Address setup
All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/
5. Login to the EVE WEB GUI
Note: In MacBook Pro I use Firefox application as it is impossible to use Safari
Login to the EVE management UI: https://192.168.100.51/
Default user access:
User: admin Password: eve
6. EVE-NG Professional Licensing
You can move the having license from existing EVE-PRO (I have one in MacBook Pro > VMware Fusion) to a new installed EVE-PRO.
All details step by step is in EVE-PRO Book: https://www.eve-ng.net/index.php/documentation/professional-cookbook/
This was all about installation!
Installation Note:
!!! Appears a new version EVE-PRO to use to install.
Software for this installation:
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
B. Memory
C. Storage
vMX Package Contents
Configuration
Step 1. Download the vMX software package for VMware: vmx-bundle-esxi-20.1R1.11.tar
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
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:
4.1. Virtual Switch Configuration
4.2. Port groups Configuration
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:
Step 6. Deploying the FPC VM
To deploy the FPC VM using .ova
files:
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
Step 8. Settings for the vFPC VM
Not mandatory but you can add more networks:
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
Info details of the problem
VM with allowed network NAT
[root@esxi00:~] ping yahoo.com getaddrinfo() for "yahoo.com" failed (-3: Temporary failure in name resolution)
VM with Share with my MAC
WAN -> em0 -> DHCP: 192.168.100.128 LAN -> em1 -> 10.1.1.251
murgescusilvia@Murgescus-MacBook-Pro ~ % ssh root@192.168.100.128 ssh: connect to host 192.168.100.128 port 22: Host is down
murgescusilvia@Murgescus-MacBook-Pro ~ % ssh root@192.168.100.128 ssh: connect to host 192.168.100.128 port 22: Operation timed out
[2.4.5-RELEASE][root@pfSense.silvique.ro]/root: ping yahoo.com PING yahoo.com (98.138.219.232): 56 data bytes ping: sendto: No route to host ...
Sometime work sometime does not work ….
Step 1. Reading VMware documentation to trying to solve the problem:
From here https://kb.vmware.com/s/article/2009642?lang=en_US I’ve dome this and restart the MacBook PRO :
sudo rm -f "Library/Preferences/VMware Fusion/networking" sudo rm -f "Library/Preferences/VMware Fusion/locations" sudo "/Applications/VMware Fusion.app/Contents/Library/vmnet-cli" -c
The problem is still there. Not solve it!
Step 2 . Ideas receive from a fried and apply it => Solved the problem! OK!!
Change network from 10.1..1.251 to 10.1.1.2 and very and test Internet connection
2.0. Make sure pfSense is powered pff
2.1. Inside ESXi terminal
[root@esxi00:~] esxcfg-route VMkernel default gateway is 10.1.1.2 [root@esxi00:~] esxcli network ip dns server list DNSServers: 10.1.1.2 [root@esxi00:~] ping google.com PING google.com (216.58.212.142): 56 data bytes 64 bytes from 216.58.212.142: icmp_seq=0 ttl=128 time=52.287 ms 64 bytes from 216.58.212.142: icmp_seq=1 ttl=128 time=53.458 ms 64 bytes from 216.58.212.142: icmp_seq=2 ttl=128 time=53.811 ms --- google.com ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 52.287/53.185/53.811 ms [root@esxi00:~]
2.2. For internal CentOS VM inside ESXi_00 I change external ip to 10.1.1.50/25 and 10.1.1.2 and it works OK.
2.3. For pfSense in Vmware Fusion I do not modify anything, but ping works ok.
All are connected to Network > Custom > Allow using NAT
Problem: Increase the size of a ESXi Virtual Disk
I wasn’t able to find a solution and mad it work!
Thing an other solution:
Step 1. Migrate a Virtual Machine to New Storage in the vSphere Web Client
Step 2. Remove a Virtual Hard Disk from a Virtual Machine
Now imposible to power on!
The solution is to install a new ESXi and all VM that I’ve lost!