With SSL VPN-Plus, you can connect to private networks behind a NSX edge gateway. A user can then access applications and servers on the private network. Since this is a SSL VPN, a user can access the private networks by use of a web browser or a client that is installed on the local machine. Below is a diagram taken from the NSX Admin Guide of the clients connect to the private network and also the support operating systems for the SSL VPN client:
NSX edge supports site to site IPSec VPN to remote sites. You can configure multiple internal networks to connect to through the VPN tunnel. Subnets and internal networks behind the NSX edge must not have overlapping addresses. The size of the edge device determines the number of tunnels that are supported. The number of tunnels needed can be found out by using a simple equation of : “local subnets x peer subnets = number of tunnels needed”. Below is a chart taken from the NSX Administrator’s Guide outlining the number of IPSec tunnels that a edge device can handle depending on the size and also the supported algorithms.
In this blog post I will cover section 1 objective 1.3 of the VCAP6-NV Deploy exam.
In this blog post, I will cover section 1 objective 1.2 of the VCAP6-NV Deploy exam.
In this blog post, I will cover section 1 objective 1.1 of the VCAP6-NV Deploy exam.
Well….here goes nothing! I’ve decided that the next certification that I will pursue will be the VCAP6-NV Deploy. (I sure hope I don’t regret this! 😳) With all the hype surrounding NSX and SDDC, what better time than now to really focus on the software defined network. More and more companies are starting to adopt NSX to harden their security, help them get into network automation with products like vRealize Automation, or even to help protect and migrate workloads to public cloud. So to stay relevant….I better jump on the bandwagon sooner than later.
Let's v4Real 