Wireless Access

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?

When I see these 'module busy' messages, it's in general something in the software version and upgrading to the latest resolves this. The 10.7.0.0 is not a version that I would recommend, and it probably is best to check the recommended firmware version as shown in Central.

If you don't get a proper response from TAC Support, escalate the case as explained in the TAC Support Guide. For the troubleshooting, it's probably good that you are already on a recent version now.

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?

I've already attempted escalation and have gotten nowhere. I have upgraded to the recommended 10.7.1.1_92045 and am still seeing "Association request rejected temporarily; try again later". Currently the APs are carrying a client load, but I'm not convinced the APs are stable or the issue is actually resolved. 

When I see these 'module busy' messages, it's in general something in the software version and upgrading to the latest resolves this. The 10.7.0.0 is not a version that I would recommend, and it probably is best to check the recommended firmware version as shown in Central.

If you don't get a proper response from TAC Support, escalate the case as explained in the TAC Support Guide. For the troubleshooting, it's probably good that you are already on a recent version now.

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?

Afte Upgrading all APs I'm still seeing authentication rejects (Association request rejected temporarily; try again later). Although the APs are still taking clients this continues to be an issue.

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?

what firmware version did you upgrade to?

Afte Upgrading all APs I'm still seeing authentication rejects (Association request rejected temporarily; try again later). Although the APs are still taking clients this continues to be an issue.

I have an issue where clients are getting intermittently rejected on APs. The issue seems to be happening across the board and is affecting all of our SSIDs & APs. Recently two of our APs stopped accepting clients all together. To give some background we are utilizing Aruba Central Cloud with AP 535's mostly running 10.7.0.0_90579.  Both APs are showing Amber alarms, but PoE & resource utilization have been ruled out. The APs are being powered by two separate Aruba switches and PoE reservation and allocation have both been confirmed. CPU is at 3% with no spikes identified. 802.11r has been disabled for other reasons but I see that is a known issue causing hung processes.  I'm seeing a number of processes that are in an uninterruptable state waiting for IO :

5551 root     D <    14856  5417  0.0  0.8 stm

5530 root     D N    14412  5417  0.0  0.8 sapd

                                                                 4900 root            DW  [iapt]

                                                                 5530 root            14412 D N /aruba/bin/sapd

                                                                 5551 root            14856 D < /aruba/bin/stm

                                                                 5666 root             5280 D   /aruba/bin/dpp_daemon

When I attempt to run additional commands, I'm getting numerous busy errors/warning:

                                                               Module SAPM Client is busy.  Please try later.

                                                               Module AM is busy.  Please try later.

                                                                Module AP STM Low Priority is busy.  Please try later.

One of the Aps were rebooted last week for refusing client association and the issue seemed to gradually reappear until all clients are being denied. I've also upgraded the other AP to AOS-10.7.1.1 this morning but am again beginning to see intermittent refusals. I've engaged Aruba support but honestly obtained more useful information in a two-minute Google search.

Anyone have any ideas as to why this is happening and/or how to stabilize this?