Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Check sum mismatch

This thread has been viewed 15 times

  • 1.  Check sum mismatch

    Posted Apr 18, 2017 05:22 PM

    Our VC went offline the other day and wouldn’t respond to pings, so we simply cycled the power and all appears well again.  However, in reviewing its logs to try to ascertain what happened (if someone could provide some insight into the best way to investigate this that would be great), we noticed the following (there are many of these and they occur every few seconds or so): 

     

    Apr 18 14:54:14  cli[4096]: <341132> <WARN> |AP <redacted>@192.0.2.1 cli|  Check sum mismatch for AP-192.0.2.10, slave 34334 vs master 14192, error_cnt 6, recover_sent 6.
Apr 18 14:54:17  cli[4096]: <341132> <WARN> |AP <redacted>@192.0.2.1 cli|  Check sum mismatch for AP-192.0.2.11, slave 34334 vs master 14192, error_cnt 5, recover_sent 6.

    All our APs run Instant Orion and Centaurus version 6.4.4.6-4.2.4.0.  While I imagine a firmware upgrade might magically fix this, firmware upgrades often cause other issues too so I’m reluctant to do this unless it’ll likely address this issue.

     

    Thank you.



  • 2.  RE: Check sum mismatch

    Posted May 12, 2017 01:43 PM

    Anyone?



  • 3.  RE: Check sum mismatch

    EMPLOYEE
    Posted May 14, 2017 09:53 PM

    Is the cluster managed via Airwave?



  • 4.  RE: Check sum mismatch

    Posted May 16, 2017 04:20 PM
    @cjoseph wrote:

    Is the cluster managed via Airwave?

    No.



  • 5.  RE: Check sum mismatch

    EMPLOYEE
    Posted May 15, 2017 01:31 AM

    Hi,

     

    Are you seeing any configuraiton mismatch between master & slave?
    Generally config check happens every 10 seconds,slave will send a heartbeat msg to master and the heartbeat message have configuration checksum.

    error_cnt contains the number is the number of times the mismatch has been seen.

    recover_sent is the number of times the VC has sent the config correction to the slave

    If the recover_sent is > 6, VC will send the full config.

     

    I see their is a Bug 145050 for VC and slave mismatch configuratin issue and it is fixed in IAP4.2.4.3, IAP4.2.4.4, IAP4.3.0.3.

     

    If you are OK to go for new version, upgrade and check the status else I would recommand to open TAC ticket to confirm whether you are falling in to similar issue.

     

    Regards,

    Pavan



  • 6.  RE: Check sum mismatch

    Posted May 16, 2017 04:22 PM
    @PAVAN wrote:

     

     I see their is a Bug 145050 for VC and slave mismatch configuratin issue and it is fixed in IAP4.2.4.3, IAP4.2.4.4, IAP4.3.0.3.

     

    If you are OK to go for new version, upgrade and check the status else I would recommand to open TAC ticket to confirm whether you are falling in to similar issue.

    Thanks Pavan.  We are running an older version and will evaluate the newer ones.



  • 7.  RE: Check sum mismatch

    Posted Jul 18, 2017 05:02 AM

    Hi

     

    I am also seeing this on our IAP setup (IAP335RW), i have approx 85k messages from our VC master AP. We are running 4.3.1.4

    Ill try rebooting the VC master AP and see if it helps (or cycle the VC master to another AP)

     

    Best,

    Thomas



  • 8.  RE: Check sum mismatch

    EMPLOYEE
    Posted Oct 26, 2018 01:00 PM

    I'm currently also experiencing those check sum mismatch messages in my logs. Can someone explain me what it means? Is there something wrong? I'm on instant OS 8.3.

     

    Oct 26 16:22:52  cli[2579]: <341004> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  The DRT version is not newer than current DRT table
Oct 26 16:23:39  cli[2579]: <341101> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Execute command-configure terminal.
Oct 26 16:23:39  cli[2579]: <341101> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Execute command-airgroupservice allowall.
Oct 26 16:23:39  cli[2579]: <341101> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Execute command-enable.
Oct 26 16:23:39  cli[2579]: <341101> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Execute command-exit.
Oct 26 16:23:39  cli[2579]: <341101> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Execute command-end.
Oct 26 16:23:39  cli[2579]: <341254> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  VC add delta configuration id 16 to msg CLI_EXECUTE_CONFIG_COMMAND.
Oct 26 16:23:39  cli[2579]: <341251> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  VC record new delta configuration entry. cfg_id 16 current 16 top 15 len 55 port 15200 flags 1 seq 0

Oct 26 16:23:39  cli[2579]: <341004> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  The DRT version is not newer than current DRT table
Oct 26 16:23:41  cli[2579]: <341132> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Check sum mismatch for AP-192.168.1.37, slave 1729 vs master 34134, error_cnt 1, recover_sent 0.
Oct 26 16:23:43  cli[2579]: <341132> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  Check sum mismatch for AP-192.168.1.38, slave 1729 vs master 34134, error_cnt 1, recover_sent 0.
Oct 26 16:24:09  cli[2579]: <341004> <WARN> |AP 80:8d:b7:c0:ed:32@192.168.1.35 cli|  The DRT version is not newer than current DRT table

     



  • 9.  RE: Check sum mismatch

    Posted May 27, 2019 03:52 AM

    Hi all,

        same problem with AP 335 and Version 8.4.0.2

     

     



  • 10.  RE: Check sum mismatch

    EMPLOYEE
    Posted May 27, 2019 04:42 AM

    Are you start seeing this issue after IAP firmware upgrade or make any changes in the network?

     

    Are you managing IAPs using Airwave, do you see any issue related to device status?



  • 11.  RE: Check sum mismatch

    Posted May 27, 2019 05:07 AM

    Hi Pavan,

    it seems that issue is started after upgrading to 8.4.0.2, these ap are monitored by Airwave, but they are only in monitor mode, anyway currently I'am not seeing any issue.

    from the CLI I see that:

     

    from some ap:

    AP-PE-014# sh delta

    IAP delta configuration current_config_id:28
    IAP delta configuration top_config_id:0
    AP-PE-014#

     

    from the virtual controller

    AP-PE-009# show delta

    IAP delta configuration current_config_id:28
    IAP delta configuration top_config_id:28
    AP-PE-009#

     

    but they are on the same network