Description | This article describes how to resolve scenarios where clients are unable to connect via the MPSK SSID. |
Scope | FortiLAN Cloud, FortiAP. |
Solution |
Configure the MPSK + FortiLAN Cloud according to the documentation.
Troubleshooting tip from FortiAP:
Log in to the CLI of FortiAP and check whether MPSK settings are being pushed to FortiAP.
h_diag mpsk-info
SSID config (004/004): SSID(MPSK-FLAN) VAP(wlan00) refcnt(1) Password name (001/003): , test7368 mac-binding: 00:00:00:00:00:00 sta cnt(0) type (0) max sta cnt(65536) vlan_type(0) vlan_id(0) schedule_cnt(1) schedules :SMTWTFS 00:00->00:00, PMK: 40c0adbb6ae8d112f1fe32715ff81b57c6647e571abf7752ce0e7b5b18a7cae0 Password name (002/003): , etest123 mac-binding: 00:00:00:00:00:00 sta cnt(0) type (0) max sta cnt(65536) vlan_type(0) vlan_id(0) schedule_cnt(1) schedules :SMTWTFS 00:00->00:00, PMK: 310f4c77edc8951a60f6bc436a35af16ca79d27c634e427245da38c6258634de Password name (003/003): , test234 mac-binding: 00:00:00:00:00:00 sta cnt(0) type (0) max sta cnt(65536) vlan_type(0) vlan_id(0) schedule_cnt(1) schedules :SMTWTFS 00:00->00:00, PMK: a0d44c9cfb14da6cb1043d73100fd71c91a83b1e78248a1d3348da1d331b02a2
acconf | grep "key_params" key_params[0][1]_1_1=1-0-00:00:00:00:00:00-0-7951c1e68081e14333ce789a66 key_params[0][1]_1_1_1=e7449ab029379c0d91b6158bb7e8eef05b3f98 key_params[0][2]_1_1=1-0-00:00:00:00:00:00-0-f339871004db9c3429aeace588 key_params[0][2]_1_1_1=a0118e7b1e9773f1edc4d9f188f237cff56ad1 key_params[0][3]_1_1=1-0-00:00:00:00:00:00-0-6d9e51c49d8a15ee641a154fd0 key_params[0][3]_1_1_1=49263f1729ce150ad16214b02cf11892b2b673
If the above commands give no outputs, reboot the AP once and check if the settings are pushed to FortiAP afterwards. If not, contact TAC for further assistance. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.