Juniper SD-WAN Virtual Lab - 3 - vSRX SD-WAN Gateway Deployment скачать в хорошем качестве

Juniper SD-WAN Virtual Lab - 3 - vSRX SD-WAN Gateway Deployment

This is the third video in a series that demonstrates to the viewer how to install, configure, and operate a Juniper Cloud CSO SD-WAN spoke test-environment on their own laptop or desktop computer. In my previous video, we setup our hypervisor interfaces and deployed our WAN emulation virtual machine. In this video, we will be doing initial setup on our virtual SRX secure SD-WAN gateway. We’ll start by importing the vSRX ova file and deploying it in Fusion. We’ll then boot our vSRX guest and perform some initial configuration tasks to ensure we are ready for provisioning. Before we get started, I’d like to take a moment to explain one of the more complex components of this video. Our SD-WAN test environment requires the addition of an interface to the default configuration that every vSRX guest deploys with. By default, the vSRX will include 3 interfaces. The first interface is mapped to the out-of-band management port, configured as FXP0 in Junos. The second and third interfaces map to ge-0/0/0 and ge-0/0/1, respectively. We’ll be using these interfaces for our simulated WAN links, which means we’ll need ge-0/0/2 for our LAN client. vSRX requires that all interfaces use the virtual adaptor type “vmxnet3”. For most hypervisors, defining the virtual adaptor type is done when creating a new interface. In Fusion, and maybe some other hypervisors I don’t know about, this option to define the virtual adaptor type isn’t present. This means that if you add a new network adaptor to your vSRX guest in Fusion and attempt to boot, you will receive an error message and this interface will not be connected. The solution is to create and boot your guest in a very specific manner, then edit the guest’s .vmx configuration file, adding required lines of configuration for your new interface. If you’re not proficient in a linux CLI, this can seem a bit daunting, and yes, a bit ridiculous, but once you’ve done it a few times, it becomes straightforward enough. NOTE: Great catch by a viewer (thank you, Rinky!) to point out that the interfaces I connect Net2 and Net3 to in the video are WAN-0 and WAN-1, but in my documentation, I defined the bridge interfaces. Thank goodness the VIDEO IS CORRECT! I'm updating the documentation right now! Companion Documentation: https://drive.google.com/file/d/178GD...