Table of contents
Combined revision comparison
...
- Creating a large-scale remote access VPN Service where it would be difficult for a single VPN Server to process all simultaneous connections (please refer to
#10.8 Build a Large Scale Remote Access VPN Service#for details). - Creating a large-scale Virtual Hub hosting service where it would be difficult for a single VPN Server to process all Virtual Hubs and simultaneous connections (please refer to
#10.9Build a Large Scale Virtual Hub Hosting Service#for details).
...
The load sharing discussed here is an overview, and more detailed control is performed depending on the type of Virtual Hub to which the actual VPN connection is made. For details, please refer to 3.9.7 and 3.9.8.#3.9.7# and #3.9.8#.
...
| Using the SoftEther VPN Server in cluster mode makes some functions unavailable. Of the functions used in stand alone server mode, please note that the configuration data relating to functions described in 3.9.12 |
...
Virtual Hubs are created for the cluster controller in the VPN Server clustering environment. Where necessary, the cluster member servers create temporary Virtual Hub instances upon instructions from the cluster controller, but it is not necessary to directly create Virtual Hubs for the cluster member servers. As explained in 3.9.10,#3.9.10#, Virtual Hub creation and the setting & administration of all Virtual Hubs can only be carried out for the cluster controller in a clustering environment.
...
Please refer to 3.9.7#3.9.7# for details on static Virtual Hubs.
...
Please refer to 3.9.8#3.9.8# for details on dynamic Virtual Hubs.
...
The cluster controller may select itself as the VPN Server to process a VPN connection from a VPN source. When the cluster controller decides the VPN Server to which to allocate a new VPN session, the decision is based on the cluster's VPN Server point values determined by the algorithms described in 3.9.4,#3.9.4#, so both the cluster controller and the cluster members are judged according to an equal standard.
...
This mechanism enables the creation of a large-scale remote access VPN service required to process a large volume of simultaneous connections. Please refer to # 10.8Build a Large Scale Remote Access VPN Service# for specific configurations.
...
This system makes it possible to create a large-scale Virtual Hub hosting service capable of hosting a large number of Virtual Hubs. Please refer to # 10.9Build a Large Scale Virtual Hub Hosting Service# for specific configurations.
...
Virtual Hub Administrators may, however, need to connect to the static Virtual Hub instance of an arbitrary VPN Server in a cluster for administration purposes. In this event, when creating the connection settings in the VPN Client or the like, designate the address of the VPN Server and the name of the Virtual Hub to which direct connection is sought instead of designating the cluster controller as the connection destination VPN Server. In addition, designate the password required to connect as an Administrator user (see 3.4 Virtual Hub Functions#3.4.14# for details). This exception makes it possible for a VPN connection to be made directly to the desired VPN Server's static Virtual Hub without going via the cluster controller router.
...
Local bridge and virtual layer 3 switch settings are carried out for each VPN Server. However, entire VPN Server Administrator authority is required for these settings. Please refer to 3.9.12#3.9.12# for further details.
...
Version from 18:59, 3 Mar 2013
...
- Creating a large-scale remote access VPN Service where it would be difficult for a single VPN Server to process all simultaneous connections (please refer to
#10.8#for details). - Creating a large-scale Virtual Hub hosting service where it would be difficult for a single VPN Server to process all Virtual Hubs and simultaneous connections (please refer to
#10.9#for details).
...
The load sharing discussed here is an overview, and more detailed control is performed depending on the type of Virtual Hub to which the actual VPN connection is made. For details, please refer to #3.9.7# and #3.9.8#.
...
| Using the SoftEther VPN Server in cluster mode makes some functions unavailable. Of the functions used in stand alone server mode, please note that the configuration data relating to functions described in |
...
Virtual Hubs are created for the cluster controller in the VPN Server clustering environment. Where necessary, the cluster member servers create temporary Virtual Hub instances upon instructions from the cluster controller, but it is not necessary to directly create Virtual Hubs for the cluster member servers. As explained in #3.9.10#, Virtual Hub creation and the setting & administration of all Virtual Hubs can only be carried out for the cluster controller in a clustering environment.
...
Please refer to #3.9.7# for details on static Virtual Hubs.
...
Please refer to #3.9.8# for details on dynamic Virtual Hubs.
...
The cluster controller may select itself as the VPN Server to process a VPN connection from a VPN source. When the cluster controller decides the VPN Server to which to allocate a new VPN session, the decision is based on the cluster's VPN Server point values determined by the algorithms described in #3.9.4#, so both the cluster controller and the cluster members are judged according to an equal standard.
...
This mechanism enables the creation of a large-scale remote access VPN service required to process a large volume of simultaneous connections. Please refer to #10.8# for specific configurations.
...
This system makes it possible to create a large-scale Virtual Hub hosting service capable of hosting a large number of Virtual Hubs. Please refer to #10.9# for specific configurations.
...
Virtual Hub Administrators may, however, need to connect to the static Virtual Hub instance of an arbitrary VPN Server in a cluster for administration purposes. In this event, when creating the connection settings in the VPN Client or the like, designate the address of the VPN Server and the name of the Virtual Hub to which direct connection is sought instead of designating the cluster controller as the connection destination VPN Server. In addition, designate the password required to connect as an Administrator user (see #3.4.14# for details). This exception makes it possible for a VPN connection to be made directly to the desired VPN Server's static Virtual Hub without going via the cluster controller router.
...
Local bridge and virtual layer 3 switch settings are carried out for each VPN Server. However, entire VPN Server Administrator authority is required for these settings. Please refer to #3.9.12# for further details.
...
Version as of 17:01, 4 Mar 2013
...
- Creating a large-scale remote access VPN Service where it would be difficult for a single VPN Server to process all simultaneous connections (please refer to 10.8 Build a Large Scale Remote Access VPN Service for details).
- Creating a large-scale Virtual Hub hosting service where it would be difficult for a single VPN Server to process all Virtual Hubs and simultaneous connections (please refer to 10.9Build a Large Scale Virtual Hub Hosting Service for details).
...
The load sharing discussed here is an overview, and more detailed control is performed depending on the type of Virtual Hub to which the actual VPN connection is made. For details, please refer to 3.9.7 and 3.9.8.
...
Virtual Hubs are created for the cluster controller in the VPN Server clustering environment. Where necessary, the cluster member servers create temporary Virtual Hub instances upon instructions from the cluster controller, but it is not necessary to directly create Virtual Hubs for the cluster member servers. As explained in 3.9.10, Virtual Hub creation and the setting & administration of all Virtual Hubs can only be carried out for the cluster controller in a clustering environment.
...
The cluster controller may select itself as the VPN Server to process a VPN connection from a VPN source. When the cluster controller decides the VPN Server to which to allocate a new VPN session, the decision is based on the cluster's VPN Server point values determined by the algorithms described in 3.9.4, so both the cluster controller and the cluster members are judged according to an equal standard.
...
This mechanism enables the creation of a large-scale remote access VPN service required to process a large volume of simultaneous connections. Please refer to 10.8Build a Large Scale Remote Access VPN Service for specific configurations.
...
This system makes it possible to create a large-scale Virtual Hub hosting service capable of hosting a large number of Virtual Hubs. Please refer to 10.9Build a Large Scale Virtual Hub Hosting Service for specific configurations.
...
Virtual Hub Administrators may, however, need to connect to the static Virtual Hub instance of an arbitrary VPN Server in a cluster for administration purposes. In this event, when creating the connection settings in the VPN Client or the like, designate the address of the VPN Server and the name of the Virtual Hub to which direct connection is sought instead of designating the cluster controller as the connection destination VPN Server. In addition, designate the password required to connect as an Administrator user (see 3.4 Virtual Hub Functions for details). This exception makes it possible for a VPN connection to be made directly to the desired VPN Server's static Virtual Hub without going via the cluster controller router.
...
