Idea: I had installed vSRX for about 1-2 weeks ago. I tried to setup something on all at the same time. The new setup made it impossible to power-on vSRXs, therefore, I deleted all and reinstalled all.
- Network Ideas
I do not know how to connect different vSRX applications. However, based on configuration I know that different interfaces are connected with each other. The picture below shows the lab I am doing now.
I do not know for sure, if ge-0/0/3 from vSRX-1 can communicate with ge-0/0/2 from vSRX-2. However, I want to make sure that only ge-0/0/3 from vSRX-1 can communicate with ge-0/0/3 from vSRX-2.
Note on 16.03.2020: I am sure that interfaces can not communicate. For example ge-0/0/3 from vSRX-1 can not communicate with ge-0/0/2 from vSRX-2.
2. Networks on VMware Fusion (added on 16.03.2020)
- Guides I used:
The idea is to create custom virtual switches with the standard version of VMware Fusion.It’s easier to create virtual switches with the Pro version of VMware Fusion because there’s a user interface for editing the networks. It’s possible with the standard version by editing config files.
The directory containing the network config files is:
We’re going to add more new virtual switches (vmnet12 to vmnet31) by opening the
networkingconfig file. On Terminal application taste then use MacBook PRO password:
sudo vim /Library/Preferences/VMware\ Fusion/networking
- Configure networking file into vim application using:
:i[enter]to start editing the file content. Botton [enter] means to press the return or enter key on your keyboard. The a command inserts to the right of the current cursor location. The I command inserts to the front of the line, while A inserts to the end of the line.
- When you are finished with editing, press the [esc] key to go back to the command mode.
:x[return]to save the file and exit the editor.
:q![return]to quit vim without saving the file.
- save: :w
- save and exit: :wq
- exit: :q
Adding the following to the networking file will create the new virtual switches named vnet10 to vnet31.
answer VNET_10_DHCP no
answer VNET_10_HOSTONLY_NETMASK 255.255.255.0
answer VNET_10_HOSTONLY_SUBNET 10.1.1.0
answer VNET_10_NAT no
answer VNET_10_VIRTUAL_ADAPTER yes
answer VNET_11_DHCP no
answer VNET_11_HOSTONLY_NETMASK 255.255.255.0
answer VNET_11_HOSTONLY_SUBNET 184.108.40.206
answer VNET_11_NAT no
answer VNET_11_VIRTUAL_ADAPTER yes
................. up to ................
answer VNET_31_DHCP no
answer VNET_31_HOSTONLY_NETMASK 255.255.255.0
answer VNET_31_HOSTONLY_SUBNET 220.127.116.11
answer VNET_31_NAT no
answer VNET_31_VIRTUAL_ADAPTER yes
- Restart VMware Fusion and then check the networks have been added by modifying the network adapter of a virtual machine.
3. Create networks on external ESXi 6.7 Virtual Machine (added on 16.03.2020)
- Go to the external ESXi virtual machine.
- Click Add Device… and create an other adapter that’s connected to the corresponding network.
It seems 10 Network Adapters is the maximum!!!
4. Networks on ESXi powered on
Lets include Physical Adapters on each network to make it as it was and working!
- The picture below shows how vmnic2 looks
- Open Edit settings and click Add Uplink. Choose the correct vmnic, in this case vmnic2. Then click Save.
- The Physical Adapters was included
Now ge-0/0/x from vSRX-1 can communicate with all ge-0/0/x interfaces from vSRX-n
ge-0/0/0 to all ge-0/0/0
ge-0/0/1 to all ge-0/0/1
ge-0/0/2 to all ge-0/0/2
ge-0/0/3 to all ge-0/0/3
ge-0/0/4 to all ge-0/0/4
ge-0/0/5 to all ge-0/0/5
ge-0/0/6 to all ge-0/0/6
ge-0/0/7 to all ge-0/0/7