UC1-R5: Users should be able to access only the company Management Network (192.168.1.0) and the Load-Balancer-Tier-01 VXLAN (172.16.50.0) logical network.Only users within a given Organizational Unit (OU name: NSX VPN Users) should be given access connect through the VPN. UC1-R4: Windows Active Directory will be used to authenticate identities (users) accessing the VPN.The VPN will be published on the external network with IP 128.1.1.10. UC1-R3: External (public) accessing the VPN are located on the 128.1.1.0 subnet.UC1-R2: External (public) users should be able to access the VPN under the URL:.UC1-R1: SSL VPN solution should utilize a certificate issued by the company’s private internal Certificate Authority.The company has identified the following requirements for their VPN implementation: To accomplish this the company will be utilizing the already existing VMware NSX virtual network infrastructure platform to create a Virtual Private Network (VPN). The company has made design decision and is planning to extend it’s existing network infrastructure to allow external (public) access to some segments of it’s internal network. The logical design of this lab can be seen HERE. Remote users can access servers and applications in the private networks. With SSL VPN-Plus, remote users can connect securely to private networks behind a NSX Edge gateway. In this article we will take a look on how to configure SSL VPN-Plus functionality in VMware NSX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |