[TUTORIAL] Fortinet FortiWLM install in Proxmox
- Thread starter Disco
- Start date
In Fortinet terminology:
virtual WLAN Controller - a virtual wlan controller, that can handle WLAN access points. This is not anymore sold?
virtual WLAN Manager - a virtual manager, that cannot handle WLAN access points directly. You can use Wireless Manager (FortiWLM) to monitor, operate, and administer wireless networks on FortiGates that are managed by FortiManager.
Both are being installed on a virtualisation platform. Both need a license to run, they are commercial software.
This is one way to install a Fortinet's virtual Wlan Manager (FortiWLM) in Proxmox as a VM.
0) download controller image for KVM, eg forti-8.6-4build-2-x86_64.img.KVM.zip to your machine, copy that eg with winscp or tftp to Proxmox
1) open Proxmox terminal, unzip it there, forti-wlm-8.6-4build-6-x86_64.img should be now in directory
2) create a VM without any disks or CD's in Proxmox (settings below), ID for example not used number 212 (needed in importdisk command)
3) go to Proxmox terminal and directory where image is downloaded
qm importdisk 212 forti-wlm-8.6-4build-6-x86_64.img your-storage-name-that-supports-images --format qcow2
4) go to Proxmox GUI, and see if disk is showing up as "unused" under VM 212, double click it and make it ide0
5) in Proxmox GUI again, under VM 212, add --> hard disk --> and add SCSI disk, size 200Gb or such
6) check from Proxmox GUI --> VM 212 --> Options that in the boot order the first is IDE0
7) under VM 212, top right select "Console" and power on, see what happens
8) rest is configuring FortiWLM VM
1) VM settings as below, as there is a VLAN tag 12 on the last line. Tagging or untagging VLAN works, if untagged here, also at the switch must be untagged naturally.
2) this is how it looks at the node level, eno2 is connected to HP switch physically, and a linux brigde vmbr12 is created on it, VLAN aware enabled.
3) HP switch looks like this, port number 8 is connected to VLAN 12
virtual WLAN Controller - a virtual wlan controller, that can handle WLAN access points. This is not anymore sold?
virtual WLAN Manager - a virtual manager, that cannot handle WLAN access points directly. You can use Wireless Manager (FortiWLM) to monitor, operate, and administer wireless networks on FortiGates that are managed by FortiManager.
Both are being installed on a virtualisation platform. Both need a license to run, they are commercial software.
This is one way to install a Fortinet's virtual Wlan Manager (FortiWLM) in Proxmox as a VM.
0) download controller image for KVM, eg forti-8.6-4build-2-x86_64.img.KVM.zip to your machine, copy that eg with winscp or tftp to Proxmox
1) open Proxmox terminal, unzip it there, forti-wlm-8.6-4build-6-x86_64.img should be now in directory
2) create a VM without any disks or CD's in Proxmox (settings below), ID for example not used number 212 (needed in importdisk command)
3) go to Proxmox terminal and directory where image is downloaded
qm importdisk 212 forti-wlm-8.6-4build-6-x86_64.img your-storage-name-that-supports-images --format qcow2
4) go to Proxmox GUI, and see if disk is showing up as "unused" under VM 212, double click it and make it ide0
5) in Proxmox GUI again, under VM 212, add --> hard disk --> and add SCSI disk, size 200Gb or such
6) check from Proxmox GUI --> VM 212 --> Options that in the boot order the first is IDE0
7) under VM 212, top right select "Console" and power on, see what happens
8) rest is configuring FortiWLM VM
1) VM settings as below, as there is a VLAN tag 12 on the last line. Tagging or untagging VLAN works, if untagged here, also at the switch must be untagged naturally.
2) this is how it looks at the node level, eno2 is connected to HP switch physically, and a linux brigde vmbr12 is created on it, VLAN aware enabled.
3) HP switch looks like this, port number 8 is connected to VLAN 12
Last edited: