Controllerless Networks

Hi,

I'm seeing this error on our virtual controllers, they are ArubaOS (MODEL: 135), Version 6.2.1.0-3.3.0.3
Look's seriously and its happens everytime a config save is done. It sounds like the master and other APs configurations are out of sync

Has anyone seen this before? Is this expected behaviour? How do I fix it?

Aug 14 21:07:03  cli[1395]: <341273> <WARN> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Config file length is 12118, allowed length is 61440.
Aug 14 21:07:05  cli[1395]: <341233> <WARN> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Saveing AP config, reason config changed.
Aug 14 21:07:05  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.232, slave 54390 vs master 63930.
Aug 14 21:07:07  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.239, slave 54390 vs master 63930.
Aug 14 21:07:07  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.234, slave 54390 vs master 63930.
Aug 14 21:07:11  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.238, slave 54390 vs master 63930.
Aug 14 21:07:11  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.237, slave 54390 vs master 63930.
Aug 14 21:07:11  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.233, slave 54390 vs master 63930.
Aug 14 21:07:12  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.230, slave 54390 vs master 63930.
Aug 14 21:07:12  cli[1395]: <341132> <ERRS> |AP WPXXX-AP-CRM1X@192.168.5.235 cli|  Check sum error for AP-192.168.5.236, slave 54390 vs master 63930.

Hi,

This error is in the release notes for your IAP code version:

Error ID

341132

Check sum error for AP-[ip:%s], slave [s_sum:%u] vs master [m_sum:%u].
Description: AP is checking configuration.

This is certainly not expected behaviour in a fully working environment.

Might be worth backing up the configuration on the virtual controller, then reboot it. 

That way another AP will take over as the master. 

You could then make a change to the config and saved it, then check again for the error.

This will take the current master IAP out of the equation and help you narrow down what's causing the issue,

Cheers

James

Yeah, I've tried that.

So far the thing that has worked best was to downgrade to 6.2.1.0-3.3.0.2_38733. Problem seems to have gone away. I'm slowly working my way through bouncing the VC to each AP.

Hopefully the problem is gone... TAC case is open with Aruba as well.

Hi Nicholaswh,

Could you share if you managed to solve the problem?

What was TAC update on this?

Thanks