The Table 5-1 contains a list of upgrade scenarios available for SSL VPN along with the procedure to upgrade the server.
Table 5-1 Upgrade Scenarios
Serial Number |
Installation Scenario |
Upgrade Procedure |
---|---|---|
1 |
Traditional SSL VPN, Identity Server, and the Administration Console on the same machine; Linux Access Gateway on a separate machine |
The SSL VPN 3.0 version cannot coexist with other Novell Access Manager components that are running the 3.1 version. When SSL VPN is installed along with the other Novell Access Manager component on the same machine, the SSL VPN server is automatically upgraded to 3.1. For more information, see |
2 |
Traditional SSL VPN, Identity Server, Linux Access Gateway, and Administration Console on separate machines |
To upgrade the SSL VPN server that is installed on a separate machine, see Section 5.3, Upgrading SSL VPN Installed on a Separate Machine. |
3 |
Traditional SSL VPN and the Identity server on the same machine; Administration Console and Linux Access Gateway on separate machines |
When SSL VPN is installed along with the Identity Server on the same machine, the SSL VPN server is automatically upgraded to 3.1. For more information, see |
4 |
Traditional SSL VPN and the Administration Console on same machine, Identity Server, Linux Access Gateway on a separate machine |
When SSL VPN is installed along with the Administration Console, on the same machine, the SSL VPN server is automatically upgraded to 3.1. For more information, see |
5 |
Traditional SSL VPN and the Linux Access Gateway on the same machine, Administration Console and Identity Server on separate machines |
When SSL VPN is installed along with the Linux Access Gateway, on the same machine, the SSL VPN server is automatically upgraded to 3.1. For more information, see |
6 |
Move from Traditional Novell SSL VPN 3.0 to ESP-enabled SSL VPN 3.1 |
If you have installed the Traditional Novell SSL VPN server and want to move to the ESP-enabled SSL VPN, you cannot upgrade the server directly. You need to install the ESP-enabled SSL VPN on a separate machine and then import the traffic policies from the 3.0 Traditional SSL VPN into the 3.1 ESP-enabled SSL VPN. For more information, see Section 5.4, Migrating a Traditional SSL VPN Server to the ESP-Enabled Version. |
7 |
Upgrade traditional SSL VPN servers clustered in the 3.0 version by using config.txt or the server persistent method through Linux Access Gateway. |
If you have configured a cluster of SSL VPN servers in 3.0 by using the config.txt file or though the Linux Access Gateway do one of the following:
|