Troubleshooting Tips
APs not connecting to the controller & seeing duplicate responses for pings from the controller to an outside system.
The same vSwitch is being used for both vNICs, define separate vSwitches for each vNIC. Alternatively, you could disable one of the vNICs in the virtual machine. You can disable the 2nd vNIC, by un-checking the Connected and Connect at Power On options.
Clients not able to connect to the network
If you look at the station log and see “Client moved to wired side”. This is an indication that your vSwitches are not configured properly. Potentially vSwitch is not mapped to one physical vNIC or the physical resources is not bonded properly or multiple hosts are sharing the same vSwitch.
How To Capture Events leading to a Crash on Virtual Controller
- Unlike physical controllers, virtual controllers may not generate a kernel-gather file if they crash.
- It should generate a file Fortinet-kernel-diag similar to Physical controller unless you encounter silent reboot which can happen to both VM and Physical controller.
- The output for a virtual controller crash may well look like a fault on VMWare.
- To confirm, connect a PC to the serial port of the physical host (virtual blade).
- Map the serial port resource on the host to the VMware image.
- Try to connect via PuTTY (same serial settings as those set for a physical host) to virtual controller.
- You will be able to catch the reboot reason / crash log, the next time the event occurs.
Does Fortinet Support Mesh on Virtual Controllers?
Yes, Fortinet supports Mesh on Virtual controllers as well.