Initializing and configuring are the very first steps for setting up VNS3 Controller instances.


Once you launch VNS3 in your cloud, log in to the VNS3 web UI. After you log in, you have 3 options to initialize:


  • Free Edition come "pre-loaded" with a default license.
  • Upload runtime snapshots from an existing VNS3 Controller
  • Fetch a remote configuration from a VNS3 multi-Controller topology (VNS3 SME and Enterprise editions only)


Option 1: Launch a new Controller using the default subnet or use a custom subnet.


  1. Paste the full license from ---BEGIN PGP MESSAGE --- through to ---END PGP MESSAGE --- and click Submit
       > For a VNS3:vpn (free edition), request a Free Edition License by clicking the Free Edition License button, enter your email and click Submit.
  2. On next screen choose between the subnet range that comes preconfigured with the license or a custom subnet defined by your specific topology needs.
    We recommend defining a custom Overlay Network Subnet that does not conflict or overlap with any subnet you plan on connecting to your VNS3 topology via IPsec VPC.
  3. Your Controller instance will reboot and will come up with your specified topology enabled and running.
    Next: Generate Keys on VNS3 Controller.



Option 2: Launch a copy of an old Controller using a locally stored snapshot of the running configuration from another Controller instance.


If this Controller is a replacement for another Controller in an
existing topology and you have a recent runtime snapshot from
the old Controller, you can instantiate the Controller by uploading the snapshot.


  1. Under Initialization, click Upload Snapshot
  2. Select a locally stored snapshot
  3. Click Submit
  4. Your Controller instance will reboot and will come up with your specified topology enabled and running.
    Next: Generate Keys on VNS3 Controller.



*Option 3: Launch a copy of an existing Controller by grabbing a configuration from a running Controller.  Fetching remote configurations can speed the configuration of Controllers you wish to Peer to an existing topology.


  1. Specify the IP address of the Controller from where you would like to fetch configuration. The security token is used for negotiation between Controller peers and must be the same for all Controllers you intend to Peer with one another.
  2. Your Controller instance will reboot and will come up with your specified topology enabled and running.
    Next: Generate Keys on VNS3 Controller.


* Multi-Controller Topologies are available in the SME and Enterprise Editions. Controllers can be peered with one another to create a highly available VNS3 Overlay Network. VNS3:vpn (free edition) and VNS3:net Lite editions must be configured to activate, but cannot be peered. 



Next steps:


After you initialize, you must generate keys to create your VNS3 clientpacks and set up Controller peering to finish configurations.


 NOTE: All VNS3 editions must complete the peering step, even for single Controller topologies.


 


Watch the step by step guide to initialize and configure VNS3 Controllers: https://youtu.be/yg59sO3xbWY