Nore: For vMX is available family bridge but not family ethernet-swithing. And I need very very very much to configuring using family ethernet-swithing.
Now I am preparing for a Juniper lab based on Switching configuration.
I have tried to install and use Juniper vQFX which is a Juniper Virtual Switch. I this moment it can be read into my blog that I can not make it work. If I will find a solution I will upgrade the article about vQFX.
Read moreInformation from internet: https://forums.juniper.net/t5/vMX/vMX-max-interface/td-p/293775
ESXi has the limitation of 10 Virtual NICs per VM, which limits the number of revenue interface to 8. (1 is used for management and 1 is used for vfp-vcp inter-connection)
https://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdf, Page 2: Virtual NICs per virtual machine 10
I try to add more but it seems this is maximum, 8 interfaces. Other 2 are for internal communications. One is connected between RE and PFE and an other is for technical communication of engineers devices.
Read moreNote in date 2020.03.25:
For information about configuring transparent mode for vSRX, see Layer 2 Bridging and Transparent Mode.
This document info
I wanted to make a lab about Layer 2 Ethernet Switching. The details of the lab was based on Juniper EX devices.
Searching Juniper Virtual EX (vEX) devices, I have found out that it does’n exist. If I want to make lab about Layer 2 Ethernet Switching I can use Juniper SRX, Juniper EX or Juniper QFX products or I was thinking at virtual applications.
Read moreIdea: 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.
Useful Photos are here: https://photos.app.goo.gl/J8Gph2tcsyDj9EDh7
Introduction
To start Juniper series off, I’ll take you through the steps of beginning your first virtual Junos lab using Junos Firefly and VMware Fusion. By the end of this series, you should be able to setup your own virtual topology that enables you to practice for that JNCIA, S, P, or E exams you’re cramming for. The concepts you learn throughout this series should be applicable to other hypervisors.
Read moreIn this article, I will build an Interprovider L3VPN Option C setup on a single vMX. Each individual router will be configured as a logical router. The vMX router has a back-to-back connection between ge-0/0/0 and ge-0/0/1 ports. For each different link, a different VLAN number will be configured to separate the traffic generated based on router ID number.
Note: This option is the most scalable solution comparing with option A and option B.
In this article, I will build an Interprovider L3VPN Option B setup on a single vMX. Each individual router will be configured as a logical router. The vMX router has a back-to-back connection between ge-0/0/0 and ge-0/0/1 ports. For each different link, a different VLAN number will be configured to separate the traffic generated based on router ID number.
In this article, I will build an Interprovider L3VPN Option A setup on a single vMX. Each individual router will be configured as a logical router. The vMX router has a back-to-back connection between ge-0/0/0 and ge-0/0/1 ports. For each different link, a different VLAN number will be configured to separate the traffic generated based on router ID number.
In this article, I will build a Carrier-of-Carriers with Internet Service Provider as the customer setup on a single vMX. Each individual router will be configured as a logical router. The vMX router has a back-to-back connection between ge-0/0/0 and ge-0/0/1 ports. For each different link, a different VLAN number will be configured to separate the traffic generated based on router ID number.
In this article, I will build a Carrier-of-Carriers with VPN Service Provider as the customer setup on a single vMX. Each individual router will be configured as a logical router. The vMX router has a back-to-back connection between ge-0/0/0 and ge-0/0/1 ports. For each different link, a different VLAN number will be configured to separate the traffic generated based on router ID number.