Upgrading Virtual Controllers
Virtual controllers can be upgraded the same way as the hardware controllers. See sections Upgrading via CLI, Upgrading via GUI, and Upgrading an NPlus1 Site.
Download the appropriate virtual controller image from Fortinet Customer Support website.
For more information on managing the virtual controllers, see the Virtual Wireless Controller Deployment Guide.
Upgrading the controller can be done in the following ways:
- Using the FTP, TFTP, SCP, and SFTP protocols.
- Navigate to Maintenance < File Management in the FortiWLC GUI to import the downloaded package.
The following are sample commands for upgrading the virtual controllers using any of these protocols.
- upgrade-image tftp://10.xx.xx.xx:forti-x.x-xbuild-x-x86_64-rpm.tar.fwlc both reboot
- upgrade-image sftp://build@10.xx.xxx.xxx:/home/forti-x.x-xGAbuild-88-FWC1KD-rpm.tar. fwlc both reboot
- upgrade-image scp://build@10.xx.xxx.xxx:/home /forti-x.x-xGAbuild-88-FWC1KD-rpm.tar. fwlc both reboot
- upgrade-image ftp://anonymous@10.xx.xx.xx:forti-x.x-xbuild-x-x86_64-rpm.tar.fwlc both reboot
The both option upgrades the Fortinet binaries (rpm) as well as the Kernel (iso), the apps option upgrades only the Fortinet binaries (rpm).
After upgrade, the virtual controller should maintain the System-id of the system, unless there were some changes in the fields that are used to generate the system-id.
The international virtual controller can be installed, configured, licensed and upgraded the same way.