WAP 551 errors on cluster (cluster.NodeStatusMonitor.getStatus)

[Xavier RICOL]

I have errors on a 16 WAP cluster :

error occured for query on path cluster.NodeStatusMonitor.getStatus (function: data_service, file: /projects/ccxsw_scratch/builds/uap/5328264_RELEASE_CUST_CISCO_UMR2_1.2.0.2/dni3420smp/uap/ap/broadcom/src/web-ui-framework/data_service.c, line: 481)

activator_execute: connect to /var/clusterd.socket failed: Connection refused (function: activator_execute_buffer, file: /projects/ccxsw_scratch/builds/uap/5328264_RELEASE_CUST_CISCO_UMR2_1.2.0.2/dni3420smp/uap/ap/broadcom/src/web-ui-services/activator_query.c, line: 67)

I reset all the WAP 551 and 561 in the cluster and setup again the cluter with a different name. Everything was OK yesturday, but this error came back this morning.

I have this problem with the old and the last firmware avalaible on Cisco support.

PID VID:	WAP551-E-K9 V01
Active Firmware Version:	1.2.0.2
Inactive Firmware Version:	1.0.3.4

Thanks for your help !

Regards,

Benoît

[Eric Moyers]

My name Eric Moyers. I am an Engineer in the Small Business Support Center.

I am sorry to hear that you are experiencing this issue. A couple of questions, is there any impact to the access Points or Cluster when this error is showing in the logs? Are you seeing this on all of the access points, just some (only 561's or only 551's) or only one specific access point? On the 561's are you including both radios in the cluster setup?

From what I have understood from your post, you have 16 WAP 551 and 5561 Access Points all in one cluster.

While I have not seen that specific error before, if you have both 551 and 561 in the same cluster it could cause that issue.

551 and 561 should only be clustered as 551 with 551 and 561 with 561. The reason being the 561 has two radio, when it tries to pass its configuration over to another WAP that does not have 2 radios, issues could occur.

As a test I would suggest either removing one group from the cluster (either 551 or 561) and see if the errors go away or create two separate clusters one for 551 and one for 561. Then monitor for a day or two.

If this does not improve your issue, please call our support center and open a case so that one of our engineers can work directly with you.
http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

Eric Moyers
.:|:.:|:. CISCO | Cisco Presales Technical Support | Wireless Subject Matter Expert

Please rate helpful Posts and Let others know when your Question has been answered.

[Xavier RICOL]

Hello Eric,

I put two separate cluster with 12 WAP 551 and 4 WAP 561. I have the same problem...

I can see this message on the "Single Point Setup -> Access Point" page. It's in red on the bottom of the page.

If you need an external access on this IP, no problem, just let me known.

Regards,

Benoît

[Eric Moyers]

At this point it would be best to call in and open a case with one of our Engineers. That way someone can work directly with you to resolve this issue.

http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

Once you get a case number, let me know and I can also check in on it.

Eric Moyers
.:|:.:|:. CISCO | Cisco Presales Technical Support | Wireless Subject Matter Expert

Please rate helpful Posts and Let others know when your Question has been answered.

[Chris33]

Hi Eric
I have the exact same problem on WAP 361.
How can i solve the problem ?

thanks

[Chris33]

Hi Xavier

Did you resolve your problem ?
I have the exact same probleme now with WAP 361. It worked at the beginning but have the red error msg at the bottom too.

Thanks