Table of contents
Combined revision comparison
...
A VPN Server Enterprise Edition License or Carrier Edition License is required for each VPN Server when creating a cluster between multiple VPN Servers.
It is also recommended to connect the all of VPN Servers to a network with minimal delays and high throughput. Typically when joining a cluster, each server is set up in the same location. In this case, it is probably most desirable for all cluster member servers to be directly connected to the cluster controller on the same segment without traveling via a router. Although performance declines, it is technically possible to set up the cluster controller and cluster member servers in separate locations via a router. In either case, the cluster controller must be set up in a location which allows TCP/IP protocol communication from all other cluster member servers.
...
Fig. 3-9-1 Connecting the cluster controller & cluster member servers
.
...
Fig. 3-9-2 Configure Clustering settings window.
...
Fig. 3-9-3 Cluster controller connection status display window.
...
Fig. 3-9-4 Intra-cluster VPN Server list administration window.
...
Fig. 3-9-5 Intra-cluster member server status display window.
...
Points = (4096 - Number of Concurrent VPN Sessions * |
* SoftEther VPN Server Carrier Edition substitutes 4096 with 100000.
The above formula enables a definition of the performance standard ratio of each VPN Server by setting "weighting" parameters for each server. By setting the values of the [Function Standard Ratio in Cluster] settings entry in the VPN Server's [Configure Clustering], it is possible to change the weight parameter freely. The default setting of the weight parameter is 100.
...
Fig. 3-9-6 Realizing fault tolerance with the SoftEther VPN Cluster
.
...
3.9.11 Cluster Configuration Licenses
Clustering Product Licenses
When using the clustering function, either the VPN Server Enterprise Edition License or the VPN Server Carrier Edition License is required for each SoftEther VPN computer to be run as a cluster controller or cluster member server. Without these product licenses the clustering function can not be enabled.
Inserting a single license key into multiple cluster controllers or cluster member servers causes a licensing error to occur while using clustering, so be careful not to inadvertently enter the same license key into more than one cluster controller or cluster member server.
Administering Clustering Connection Licenses
When using the clustering function, a connection license only needs to be registered for the cluster controller. Connection licenses do not have to be registered for each cluster member server (doing so is meaningless).
Therefore, when purchasing a VPN Server Enterprise Edition License and intending to use the clustering function, it is necessary to purchase more than one of said license, and of these, one is designated as the Server ID and client licenses and bridge connection licenses are then purchased based on the number required for this Server ID. Also, that Server ID's product license key and connection license keys are to be registered on the VPN Server to become the cluster controller.
The number of client connection licenses required is the total number of client connection sessions capable of connecting to the entire cluster simultaneously. Similarly, the number of bridge connection licenses required is the total number of bridge connection sessions capable of connecting to the entire cluster simultaneously.
SoftEther VPN Server's internal SecureNAT sessions, local bridge sessions, cascade sessions and administration sessions connected from the VPN Server Manager and vpncmd utility to administer SoftEther VPN Server are not subject to the above-mentioned number of client connections or bridge connections and do not consume a connection license.
Please refer to #1.3# for details on product licenses and connection licenses.
3.9.12 Functions not Available Simultaneously with Clustering
...
Other changes:
- /body/p[9]/a/@class:
" external"⇒ nothing - /body/p[9]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-1.gif"⇒ "https://www.softether.org/@api/deki/files/230/=3-9-1.png" - /body/p[9]/a/@title: nothing ⇒ "3-9-1.png"
- /body/p[9]/a/img/@alt:
"Click to enlarge."⇒ "3-9-1.png" - /body/p[9]/a/img/@border:
"2"⇒ nothing - /body/p[9]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-9-1_small.jpg"⇒ "/@api/deki/files/230/=3-9-1.png?size=webview" - /body/p[9]/a/img/@class: nothing ⇒ "internal default"
- /body/p[9]/a/img/@style: nothing ⇒ "width: 350px; height: 240px;"
- /body/p[10]/@style: nothing ⇒ "text-align: center; "
- /body/p[16]/a/@class:
" external"⇒ nothing - /body/p[16]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-2.gif"⇒ "https://www.softether.org/@api/deki/files/231/=3-9-2.png" - /body/p[16]/a/@title: nothing ⇒ "3-9-2.png"
- /body/p[16]/a/img/@alt:
"Click to enlarge."⇒ "3-9-2.png" - /body/p[16]/a/img/@border:
"2"⇒ nothing - /body/p[16]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-9-2_small.jpg"⇒ "/@api/deki/files/231/=3-9-2.png?size=webview" - /body/p[16]/a/img/@class: nothing ⇒ "internal default"
- /body/p[16]/a/img/@style: nothing ⇒ "width: 415px; height: 550px;"
- /body/p[17]/@style: nothing ⇒ "text-align: center; "
- /body/p[28]/a/@class:
" external"⇒ nothing - /body/p[28]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-3.gif"⇒ "https://www.softether.org/@api/deki/files/232/=3-9-3.png" - /body/p[28]/a/@title: nothing ⇒ "3-9-3.png"
- /body/p[28]/a/img/@alt:
"Click to enlarge."⇒ "3-9-3.png" - /body/p[28]/a/img/@border:
"2"⇒ nothing - /body/p[28]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-9-3_small.jpg"⇒ "/@api/deki/files/232/=3-9-3.png?size=webview" - /body/p[28]/a/img/@class: nothing ⇒ "internal default"
- /body/p[28]/a/img/@style: nothing ⇒ "width: 550px; height: 435px;"
- /body/p[29]/@style: nothing ⇒ "text-align: center; "
- /body/p[31]/a/@class:
" external"⇒ nothing - /body/p[31]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-4.gif"⇒ "https://www.softether.org/@api/deki/files/233/=3-9-4.png" - /body/p[31]/a/@title: nothing ⇒ "3-9-4.png"
- /body/p[31]/a/img/@alt:
"Click to enlarge."⇒ "3-9-4.png" - /body/p[31]/a/img/@border:
"2"⇒ nothing - /body/p[31]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-9-4_small.jpg"⇒ "/@api/deki/files/233/=3-9-4.png?size=webview" - /body/p[31]/a/img/@class: nothing ⇒ "internal default"
- /body/p[31]/a/img/@style: nothing ⇒ "width: 550px; height: 323px;"
- /body/p[32]/@style: nothing ⇒ "text-align: center; "
- /body/p[36]/a/@class:
" external"⇒ nothing - /body/p[36]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-5.gif"⇒ "https://www.softether.org/@api/deki/files/234/=3-9-5.png" - /body/p[36]/a/@title: nothing ⇒ "3-9-5.png"
- /body/p[36]/a/img/@alt:
"Click to enlarge."⇒ "3-9-5.png" - /body/p[36]/a/img/@border:
"2"⇒ nothing - /body/p[36]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-9-5_small.jpg"⇒ "/@api/deki/files/234/=3-9-5.png?size=webview" - /body/p[36]/a/img/@class: nothing ⇒ "internal default"
- /body/p[36]/a/img/@style: nothing ⇒ "width: 550px; height: 435px;"
- /body/p[37]/@style: nothing ⇒ "text-align: center; "
- /body/p[55]/a/img/@alt:
"File:C:/TMP/130301vpn4man/VPN4_Manual_(English)/html/images/3-9-6.gif"⇒ "3-9-6.png" - /body/p[55]/a/img/@border:
"0"⇒ nothing - /body/p[55]/a/img/@height:
"365"⇒ nothing - /body/p[55]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-9-6.gif"⇒ "/@api/deki/files/235/=3-9-6.png?size=webview" - /body/p[55]/a/img/@width:
"331"⇒ nothing - /body/p[55]/a/img/@class: nothing ⇒ "internal default"
- /body/p[55]/a/img/@style: nothing ⇒ "width: 300px; height: 350px;"
- /body/p[56]/@style: nothing ⇒ "text-align: center; "
Version from 16:53, 2 Mar 2013
...
A VPN Server Enterprise Edition License or Carrier Edition License is required for each VPN Server when creating a cluster between multiple VPN Servers.
It is also recommended to connect the VPN Servers to a network with minimal delays and high throughput. Typically when joining a cluster, each server is set up in the same location. In this case, it is probably most desirable for all cluster member servers to be directly connected to the cluster controller on the same segment without traveling via a router. Although performance declines, it is technically possible to set up the cluster controller and cluster member servers in separate locations via a router. In either case, the cluster controller must be set up in a location which allows TCP/IP protocol communication from all other cluster member servers.
...
...
...
...
...
Points = (4096 - |
* SoftEther VPN Server Carrier Edition substitutes 4096 with 100000.
...
![]()
|
...
3.9.11 Cluster Configuration Licenses
Clustering Product Licenses
When using the clustering function, either the VPN Server Enterprise Edition License or the VPN Server Carrier Edition License is required for each SoftEther VPN computer to be run as a cluster controller or cluster member server. Without these product licenses the clustering function can not be enabled.
Inserting a single license key into multiple cluster controllers or cluster member servers causes a licensing error to occur while using clustering, so be careful not to inadvertently enter the same license key into more than one cluster controller or cluster member server.
Administering Clustering Connection Licenses
When using the clustering function, a connection license only needs to be registered for the cluster controller. Connection licenses do not have to be registered for each cluster member server (doing so is meaningless).
Therefore, when purchasing a VPN Server Enterprise Edition License and intending to use the clustering function, it is necessary to purchase more than one of said license, and of these, one is designated as the Server ID and client licenses and bridge connection licenses are then purchased based on the number required for this Server ID. Also, that Server ID's product license key and connection license keys are to be registered on the VPN Server to become the cluster controller.
The number of client connection licenses required is the total number of client connection sessions capable of connecting to the entire cluster simultaneously. Similarly, the number of bridge connection licenses required is the total number of bridge connection sessions capable of connecting to the entire cluster simultaneously.
Please refer to #1.3# for details on product licenses and connection licenses.
...
3.9.12 Functions not Available Simultaneously with Clustering
...
Current version
...
It is recommended to connect the all of VPN Servers to a network with minimal delays and high throughput. Typically when joining a cluster, each server is set up in the same location. In this case, it is probably most desirable for all cluster member servers to be directly connected to the cluster controller on the same segment without traveling via a router. Although performance declines, it is technically possible to set up the cluster controller and cluster member servers in separate locations via a router. In either case, the cluster controller must be set up in a location which allows TCP/IP protocol communication from all other cluster member servers.
...
Connecting the cluster controller & cluster member servers.
...
Configure Clustering settings window.
...
Cluster controller connection status display window.
...
Intra-cluster VPN Server list administration window.
...
Intra-cluster member server status display window.
...
Points = (4096 - Number of Concurrent VPN Sessions * 100 / weight) * 100000 / 4096 |
The above formula enables a definition of the performance standard ratio of each VPN Server by setting "weighting" parameters for each server. By setting the values of the [Function Standard Ratio in Cluster] settings entry in the VPN Server's [Configure Clustering], it is possible to change the weight parameter freely. The default setting of the weight parameter is 100.
...
Realizing fault tolerance with the SoftEther VPN Cluster.
...