03-07-2017 05:17 AM
My setup comprises of a Master and Local controlle
The APs in the setup are operates as:
1) Normal Campus APs
2) Mesh node APs(Mesh portals and Mesh points).
The APs are configured in fast failover mode with
The problem is for over months together, I was seeing all the AP statuses of both normal and Mesh node APs on the Master controller's Network Summary tab(Monitoring -->Network Summary).
However today, the network summary page shows the Mesh node APs as down on Network summary page of Master, even though they are up on the local controller. From services standpoint, I am not running into issues.
Has anyone ran into similar issues with code: 18.104.22.168?
What is the expected behaviour?
Solved! Go to Solution.
03-07-2017 08:18 PM
Please run the following command & check if those AP's are listed as down on master's CLI as well
show ap database
03-08-2017 05:13 AM
Interestingly I see the Mesh portals and Mesh points reflected as up in "show ap database summary" and "show ap database".
This however is not getting reflected in the "Monitoring -->Network Summary" on the Master controller.
03-09-2017 05:30 AM
Please try restarting the following processes during non-production hours & see if it fixes the issue.
(Aruba) #process restart httpd
WARNING: Do you really want to restart process: httpd (y/n): y
(Aruba) #process restart arci-cli-helper
WARNING: Do you really want to restart process: arci-cli-helper (y/n): y
It will take couple of minutes for the process to restart. We can monitor the same using the following command:
show process monitor statisitics | include httpd
show process monitor statistics | include arci-cli-helper
When both the process shows up in running state post the restart, please veirfy the status on the Web UI.
03-09-2017 10:27 AM
Thanks Nitesh for all your prompt responses.
The issue had disappeared on its own. Now the Network summary page on the master is seen reflecting all the Mesh node APs as well.
Is there a way around to know the reason of this intermittent issue?
03-09-2017 07:21 PM
It is difficult to get to the root cause of this issue without debugging.
In case I come across this issue or firmware in which similar issue might have reported/fixed, I will update the thread with the required information.