Avaya 3.7 Manuel D’Utilisation

Page de 326
Upgrading firmware and licenses
290 Avaya VPNmanager Configuration Guide Release 3.7
6. Double-click the firmware zip file to begin extracting the VPNos image. The Password 
screen appears. 
7. Enter the password from technical support.
8. Go to the VPNmanager Console, then move to the Configuration Console window.
9. Click View>Device to list all the security gateway in the Contents column.
10. From the Contents column, select the security gateway to upgrade.
11. Click the Upgrade tab, to bring it to the front.
12. Click Upgrade Firmware; the Open dialog box appears.
13. Navigate to the directory where the VPNos firmware image was saved.
14. Select the update.bin file.
15. Click Open to install the update.bin file.
16. When installation is complete, a message box appears asking if you want to reboot the 
security gateway.
If the subdirectory has an upstage2.bin file, click NO. Do not reboot the security 
gateway. You need to install the upstage2.bin file. Follow the instructions, starting from 
Step 9; in step 14, select the upstage2.bin file.
If the security gateway subdirectory does not have an upstage2.bin file, click YES. If you 
answered YES to rebooting the security gateway, your upgrade is complete.
17. Click OK to return to the VPNmanager Console.
18. The task summary is displayed.
19. Close the task summary window and check the security gateway status. The security 
gateway status should be success.
20. If you have not communicated with the target security gateway, the security gateway 
logon screen appears: enter your login credentials to complete the download.
21. When the download is finished, click Reboot Device to reboot the security gateway.
Note:
Note:
A security gateway takes at least two minutes to reboot.
License 
Beginning with VPNos 4.2, you can obtain additional licenses to increase the number of remote 
users and site-to-site VPN connections that are allowed during a secure session. 
When you purchase additional licenses, you receive a file with the encrypted information. This 
file is created based on the serial number of the security gateway and the number of licenses 
that are available on that security gateway. This file cannot be applied to another security 
gateway.