Embed Size (px)
Citation preview
copyright 2015 1
CenturyLink Cloud ConfigurationCenturyLink Setup for VNS3:vpn, VNS3:net and VNS3:turret 2015
copyright 2015
Table of Contents
2
Introduction 3CenturyLink Cloud Deployment Setup 9VNS3 Configuration Document Links 14
copyright 2015
Introduction
3
copyright 2015
Requirements
4
• You have an CenturyLink Cloud account. (The Free CenturyLink Cloud trial of VNS3 is located in your Blueprints Library)
• You agree to the following VNS3 Terms and Conditions (Free Edition | BYOL)
• Ability to configure a client (whether desktop based or cloud based) to use OpenVPN client software.
• You have a compliant IPsec firewall/router networking device:
Preferred Most models from Cisco Systems*, Juniper, Watchguard, Dell SONICWALL, Netgear, Fortinet, Barracuda Networks, Check Point*, Zyxel USA, McAfee Retail, Citrix Systems, Hewlett Packard, D-Link, WatchGuard, Palo Alto Networks, OpenSwan, pfSense, and Vyatta.
Best Effort Any IPsec device that supports: IKE1 or IKE2, AES256 or AES128 or 3DES, SHA1 or MD5.
*Known Exclusions Checkpoint R65+ requires native IPSec connections as Checkpoint does not conform to NAT-Traversal Standards and Cisco ASA 8.4(2)-8.4(4) bugs prevent a stable connection from being maintained.
copyright 2015
Getting Help with VNS3
5
This guide covers a very generic VNS3 setup in an CenturyLink Cloud cloud computing facility. If you are interested in more custom use cases and would like Cohesive to advise and help setup the topology contact [email protected] for services pricing.Please review the VNS3 Support Plans and Contacts before sending support inquiries.
copyright 2015
Firewall Considerations
6
VNS3 Controller instances use the following TCP and UDP ports. • UDP port 1194
For client VPN connections; network cal or hypervisor access rule for the VNS3 Controller must allow UDP port 1194 from all servers that will join VNS3 topology as clients.
• UDP 1195-1197 For peering between VNS3 Controller peers; must be accessible from all peers in a given topology. Free Edition and Lite Edition will not require UDP ports 1195-1197 access as it is not licensed for Controller Peering (Single Controller Topologies).
• TCP port 8000 HTTPS admin interface; must be accessible from hosts where you will want to obtain runtime status or configure your VNS3 topology, also needs to be open to and from the Controllers at least for the peering process, and needs to be accessible when downloading credentials for installation on overlay network clients.
• UDP port 500, ESP Protocol and possibly UDP port 4500 IPsec connections to CenturyLink Cloud support both native IPsec (UDP 500 and ESP Protocol 50) and NAT-Traversal encapsulation (UDP 500 and UDP 4500).
• Free Edition: TCP port 8081For access to the Cohesive License Controller service to register the Free Edition instance and receive a Free Edition License.
copyright 2015
Remote Support
7
Note that TCP 22 (ssh) is not required for normal operations.
Each VNS3 Controller is running a restricted SSH daemon, with access limited only to Cohesive for debugging purposes controlled by the user via the Remote Support toggle and key exchange generation.
In the event Cohesive needs to observe runtime state of a VNS3 Controller in response to a tech support request, we will ask you to open Security Group access to SSH from our support IP range and Enable Remote Support via the Web UI.
Cohesive will send you an encrypted passphrase to generate a private key used by Cohesive Support staff to access your Controller. Access to the restricted SSH daemon is completely controlled by the user. Once the support ticket has been closed you can disable remote support access and invalidate the access key.
copyright 2015
Sizing Considerations
8
Image Size and Architecture VNS3 Edition Controller Images (Free Edition and BYOL-UL) are available as 64bit images to allow the greatest flexibility for your use-case. We recommend Controller instances be launched with at least 512MB of RAM. Smaller sizes are supported but the performance will depend on the use-case.
!
Clientpack Key Size VNS3 Controllers currently generate 1024 bit keys for connecting the clients to the overlay network via the “clientpacks”. Smaller or larger encryption keys can be provided upon request (from 64 bit to 2048 bit). Future releases of VNS3 will provide the user control over key size and cipher during initialization and configuration.
!
copyright 2015
CenturyLink Cloud Deployment Setup
9
copyright 2015
CLC: Select VNS3 Blueprint & and Build
10
Login to your CenturyLink Cloud (CLC) account and go to the Blueprints Library listed in the top green menu bar.
In the Blueprint Library select the edition of VNS3 you wish to use.
On the next page click on deploy blueprint.
On the Deploy page enter a password, and select DNS names for the server. NOTE: Here you can select HYPERSCALE under Server Type to allow CLC to scale your VNS3 server up and down as demands change.
Give your targeted VNS3 instance a name.
Click on next step.
Look for 8/8 steps to finish.
copyright 2015
CLC Configuration: Public IP Access
11
Once your VNS3 image has been built, go to the Dashboard. Locate the server name you just built and select that server.
Then click on the add public IP button.
Click custom Port, to add the following required inbound hypervisor firewall access rules:
• TCP port 8000
• UDP port 1194
• UDP 1195-1197
• UDP port 500, and possibly UDP port 4500
When finished, you will find the Public IP is now listed on the on the server page.
copyright 2015
VNS3 Controller Log in
12
Login to the VNS3 Web UI - https://<Controller IP>:8000
Default username: vnscubed. Default password: vnscubed
Reset your passwords: • Reset the Web UI Password - Even though the instance id is unlikely to be
“guessed”, please change it for security purposes. • NOTE: Your VNS3 Controller answers to API calls on the same port 8000 as the
web interface runs on. Ideally make a separate password for the API usage against the Controller.
• Reset the API Password - Even though the instance id is unlikely to be “guessed”, please change it for security purposes, again making it a different password than the web interface is probably best.
• NOTE: Cohesive does not have any key access or remote access to your VNS3 Controllers unless provided by you. If you forget these passwords we cannot recover them for you.
copyright 2015
VNS3 Configuration Document Links
13
copyright 2015
VNS3 Configuration Document Links
14
VNS3 Product Resources - Documentation | Add-ons !
VNS3 Configuration InstructionsInstructions and screenshots for configuring a VNS3 Controller in a single or multiple Controller topology. Specific steps include, initializing a new Controller, generating clientpack keys, setting up peering, building IPsec tunnels, and connecting client servers to the Overlay Network.
VNS3 Administration DocumentCovers the administration and operation of a configured VNS3 Controller. Additional detail is provided around the VNS3 Firewall, all administration menu items, upgrade licenses, other routes and SNMP traps.
VNS3 Docker InstructionsExplains the value of the VNS3 3.5 Docker integration and covers uploading, allocating and exporting application containers. !
VNS3 TroubleshootingTroubleshooting document that provides explanation issues that are more commonly experienced with VNS3.
