Description
This article describes how to troubleshoot if the following message in station-log 'Rejecting assignment on nonassignable' appears.
Related link.
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ac584b4a-dfb1-11e9-8977-005056...
Solution
Solution.
While troubleshooting issues with wireless clients unable to connect or clients getting prompt to enter WPA2 PSK key, despite clients already have the PSK key set, station logs show the following error:
- In 'Global Quality-of-Service Parameters' check if 'load-balance-overflow' is turnt on and if 'Maximum Stations Per BSSID' is set to non-zero value as shown below:
By default, this is set to 0.
A maximum of 1023 stations can be set.
This command is used to configure client load balancing across BSSIDs, ensuring a level of QoS for client call sessions.
This command sets the maximum number of stations that can be assigned to a BSSID.
When the maximum number of stations per BSSID is reached, new call associations can be distributed among BSSIDs in a round-robin fashion, evening out the distribution if the qosvars load‐balance overflow command is set to on.
For commands usage details refer Page #779: https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/059a67fc-dfb2-11e9-8977-005056...
Steps.
1) Set max-stations-per-bssid is set to "zero" - Go to Configuration -> Policies -> QoS -> Global Quality-of-Service Parameters as shown below.
2) Disable 'load-balance-overflow' - Go to Configuration -> Policies -> QoS -> Global Quality-of-Service Parameters as shown below.
3) Thereafter, save the config using GUI method (by hitting 'Save' button on top-right-corner of the GUI) or CLI method using command (copy running-config startup-config).
This article describes how to troubleshoot if the following message in station-log 'Rejecting assignment on nonassignable' appears.
Related link.
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ac584b4a-dfb1-11e9-8977-005056...
Solution
Solution.
While troubleshooting issues with wireless clients unable to connect or clients getting prompt to enter WPA2 PSK key, despite clients already have the PSK key set, station logs show the following error:
2019-06-07 12:58:23.713038 | f4:f9:51:6b:ac:0c | Station Assign | Rejecting assignment on nonassignable (LB) B-BSSID[06:00:41:1a:6a:9f] num_associated(3) num_assigned(3)Possible cause of the issue.
- In 'Global Quality-of-Service Parameters' check if 'load-balance-overflow' is turnt on and if 'Maximum Stations Per BSSID' is set to non-zero value as shown below:
# show qosvars'qosvars max‐stations‐per‐bssid' - Specifies the maximum number of clients (stations) that can associate with a BSSID.
Global Quality-of-Service Parameters
On/Off : on
Admission Control : admitall
Drop Policy : head
Default Time-to-live (seconds) : 0
UDP Time-to-live (seconds) : 0
TCP Time-to-live (seconds) : 0
Bandwidth Scaling (percent) : 100
Maximum Calls Per AP : 0
Maximum Calls Per Interference Region : 0
Maximum Stations Per Radio : 256
Maximum Stations Per BSSID : 50
Native Load Balance Overflow : off
Maximum Calls Per BSSID : 0
CAC Deauth : off
Station Assignment Aging Time (seconds) : 30
SIP Idle Timeout (seconds) : 120
By default, this is set to 0.
A maximum of 1023 stations can be set.
This command is used to configure client load balancing across BSSIDs, ensuring a level of QoS for client call sessions.
This command sets the maximum number of stations that can be assigned to a BSSID.
When the maximum number of stations per BSSID is reached, new call associations can be distributed among BSSIDs in a round-robin fashion, evening out the distribution if the qosvars load‐balance overflow command is set to on.
For commands usage details refer Page #779: https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/059a67fc-dfb2-11e9-8977-005056...
Steps.
1) Set max-stations-per-bssid is set to "zero" - Go to Configuration -> Policies -> QoS -> Global Quality-of-Service Parameters as shown below.
2) Disable 'load-balance-overflow' - Go to Configuration -> Policies -> QoS -> Global Quality-of-Service Parameters as shown below.
3) Thereafter, save the config using GUI method (by hitting 'Save' button on top-right-corner of the GUI) or CLI method using command (copy running-config startup-config).
Related Articles
Meru Technical Note - Viewing Station Log for a Client Device on a Meru Controller
Technical Note: Collecting buffered station log from controller
