This section describes upgrading from the Novell VPN software contained in BorderManager version 3.5 or 3.6 to the current BorderManager version (version 3.7). This section contains the following procedure:
Two approaches are available for upgrading from version 3.5 or 3.6 to version 3.7:
The advantage of the first approach is that no new equipment or ISP connections are required to run a master server in parallel with the existing version 3.5 or 3.6 master server. However, sufficient down time is required to convert all version 3.5 or 3.6 servers without interruption to service. The amount of time needed to transfer the encryption information to and from each slave server must be considered.
The second approach requires an additional machine that can be used as the new VPN master server to be run in parallel with the existing version 3.5 or 3.6 master server. The advantage of this approach is that the upgrade can take place over a period of time without causing complete loss of service. VPN slave servers that remain on the existing VPN can still communicate with each other, but they cannot communicate with any VPN members on the new VPN until the upgrade occurs.
Use the second approach if:
This procedure is described in Upgrading VPN from a Previous Version. Use the same procedure if you want to replace the existing master server instead of adding a new master server in parallel.
There are two options in this case: This option requires an additional machine to be used as the new version 3.7 master server. However, this scenario is preferable in terms of performance. This procedure is described in Upgrading VPN from a Previous Version.
This option does not require an additional machine for the new version 3.7 master server. The disadvantage is that after the version 3.5 or 3.6 master server is removed, the remaining version 3.5 or 3.6 slave servers cannot be managed using the master server until they are upgraded to the new VPN. This procedure is described in Upgrading VPN from a Previous Version.
To upgrade version 3.5 or 3.6 sites to version 3.7 during a complete VPN shutdown, complete the following steps:
Install and configure the new VPN software on the master server.
Refer to Setting Up Your VPN for detailed instructions.
Configure the slave servers and regenerate the key for each new slave server using the master encryption information that was generated by the new master server.
Refer to Setting Up Your VPN for detailed instructions.
Add each slave server to the VPN.
Refer to Setting Up Your VPN for detailed instructions.
To upgrade version 3.5 or 3.6 sites to version 3.7 with the master server behind a router, complete the following steps:
Designate a machine that will be used as the new VPN master server.
While keeping the original VPN master and slave servers running, install and configure the new master server on the same LAN.
Refer to Setting Up Your VPN for detailed instructions.
IMPORTANT: Continue to run the original VPN master server until you are instructed later in this procedure to bring it down.
Select a slave server to upgrade to the new network, remove the slave server from the original network, and add it to the new network.
Refer to the VPN online documentation and Setting Up Your VPN for detailed instructions.
Regenerate the key for the new slave server using the master encryption information that was generated by the new master server.
Refer to Setting Up Your VPN for detailed instructions.
Repeat the steps for each slave server until all slave servers are removed from the original network and added to the new network.
After all slave servers have been upgraded to the new VPN, bring down and disconnect the original master server.
Complete the procedures described in Setting Up Your VPN, as required.
To upgrade version 3.5 or 3.6 sites to version 3.7 with a second master server behind a router, complete the following steps:
Designate a machine that will be used as the new VPN master server.
While keeping the original VPN master and slave servers running, install and configure the new master server on the LAN behind the original VPN master.
Refer to Setting Up Your VPN for detailed instructions.
IMPORTANT: Continue to run the original VPN master server until you are instructed later in this procedure to bring it down.
Select a slave server to upgrade to the new network, remove the slave server from the original network, and add it to the new network.
Refer to the VPN online documentation and Setting Up Your VPN for detailed instructions.
Regenerate the key for the new slave server using the master encryption information that was generated by the new master server.
Refer to Setting Up Your VPN for detailed instructions.
Repeat the steps for each slave server until all slave servers are removed from the original network and added to the new network.
After all slave servers have been upgraded to the new VPN, bring down and disconnect the original master server.
Complete the procedures described in Setting Up Your VPN, as required.
To upgrade version 3.5 or 3.6 sites to version 3.7 using a replacement for an existing master server, complete the following steps:
While keeping the version 3.5 or 3.6 slave servers running, install and configure the version 3.7 software on the original version 3.5 or 3.6 master server and use the same ISP connection.
Refer to Setting Up Your VPN for detailed instructions.
Select a slave server to upgrade to the new network, remove the slave server from the original network, and add it to the new network.
Refer to the VPN online documentation and Setting Up Your VPN for detailed instructions.
Regenerate the key for the new slave server using the master encryption information that was generated by the new master server.
Refer to Setting Up Your VPN for detailed instructions.
Repeat the steps for each slave server until all slave servers are removed from the original network and added to the new network.
Complete the procedures described in Setting Up Your VPN, as required.