10.8 Build a Large Scale Remote Access VPN Service

Version from 19:11, 3 Mar 2013

If you expect a large number of simultaneous connections to your VPN Server based remote access VPN system like the one described in section #10.4#, you can use the clustering capability of SoftEther VPN Server Enterprise Edition to perform load balancing across multiple VPN Servers. This allows you to decrease the load on each VPN Server and increase overall throughput. It also allows you to automatically introduce fault-tolerance into your network design.

...

This section will give an example layout of this type of remote access VPN service and inform you of important points to keep in mind when designing a cluster network. Please refer to section #3.9# for more detailed information about the clustering capability.

...

The best one to use for a remote access VPN is the static Virtual Hub. (See section #3.9.7#.)

...

10.8.5 Calculating the Number of Required Licenses

Let's calculate how many licenses will be needed for this network layout. You will need three VPN Server product licenses to receive incoming connections from VPN Clients. This time you are using clustering so you will need the Enterprise Edition.

Finally, you have 300 VPN Clients connecting to the VPN Server at the same time, so you will need connection licenses for 300 clients. Connection licenses will be managed by the entire cluster, therefore you only need to register them to the cluster controller.

The bridge connection required to connect each VPN Server's Virtual Hub to the existing LAN will be handled by the VPN Servers so a bridge connection license is not required.

Thus, the required product licenses and connection licenses are as shown below.

• VPN Server Enterprise Edition License x 3
• VPN Server Client Connect License (100 Clients) x 3

Please refer to section #1.3# for more information about the licensing system.

...

10.8.6 Installing and Configuring the Cluster Controller

...

Please refer to section #3.9.2# for more information on setting up a VPN Server as a cluster controller.

...

10.8.7 Installing and Configuring the Cluster Member Servers

Each VPN Server installed after the first will connect to the cluster controller as a cluster member server. Please refer to section #3.9.3# for more information on setting up a VPN Server as a cluster member server.

...

10.8.8 Creating Static Virtual Hubs

...

10.8.9 Making a Local Bridge between the Existing LAN and the Virtual Hubs

When a static Virtual Hub is created on the cluster controller an instance of that static Virtual Hub will automatically be made on all VPN Servers in the cluster. (See section #3.9.7#.)

Next, make a direct administrative connection to each VPN Server and set up a local bridge connection between that Virtual Hub and the physical LAN you wish to connect to remotely. (For more information on creating local bridge connections, see section #3.6#.) As explained previously, if the network you wish to connect to remotely has multiple segments, you must make local bridge connections between each static Virtual Hub and their respective physical LAN. (You will need multiple network adapters for this.)

Refer to section #10.4.7# for things to note when making local bridge connections.

...

10.8.10 Managing VPN Sessions on a Clustered VPN

...

Version as of 18:03, 4 Mar 2013

If you expect a large number of simultaneous connections to your VPN Server based remote access VPN system like the one described in section 10.4Build a Generic Remote Access VPN, you can use the clustering capability of SoftEther VPN Server Enterprise Edition to perform load balancing across multiple VPN Servers. This allows you to decrease the load on each VPN Server and increase overall throughput. It also allows you to automatically introduce fault-tolerance into your network design.

...

This section will give an example layout of this type of remote access VPN service and inform you of important points to keep in mind when designing a cluster network. Please refer to section 3.9 Clustering for more detailed information about the clustering capability.

...

The best one to use for a remote access VPN is the static Virtual Hub. (See section 3.9 Clustering.)

...

Please refer to section 3.9 Clustering for more information on setting up a VPN Server as a cluster controller.

...

10.8.6 Installing and Configuring the Cluster Member Servers

Each VPN Server installed after the first will connect to the cluster controller as a cluster member server. Please refer to section 3.9 Clustering for more information on setting up a VPN Server as a cluster member server.

...

10.8.7 Creating Static Virtual Hubs

...

10.8.8 Making a Local Bridge between the Existing LAN and the Virtual Hubs

When a static Virtual Hub is created on the cluster controller an instance of that static Virtual Hub will automatically be made on all VPN Servers in the cluster. (See section 3.9 Clustering.)

Next, make a direct administrative connection to each VPN Server and set up a local bridge connection between that Virtual Hub and the physical LAN you wish to connect to remotely. (For more information on creating local bridge connections, see section 3.6Local Bridges.) As explained previously, if the network you wish to connect to remotely has multiple segments, you must make local bridge connections between each static Virtual Hub and their respective physical LAN. (You will need multiple network adapters for this.)

Refer to section 10.4 Build a Generic Remote Access VPN for things to note when making local bridge connections.

...

10.8.9 Managing VPN Sessions on a Clustered VPN

...