Controllerless Networks

last person joined: 23 hours ago 

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

IAP - Cluster communications fail and master ip set to 169.254.x.x

This thread has been viewed 4 times

  • 1.  IAP - Cluster communications fail and master ip set to 169.254.x.x

    Posted Jan 18, 2016 06:22 PM

    Hi All, I've got an installation that keeps failing at random times for no apparent reason. 

     

    The install consists of 5 x IAP-225 running 6.4.2.6-4.1.1.7 code. All AP's are statically addressed with a VC address defined as well. 

     

    Everything generally works fine but once in a while, the AP's will reboot with no log entry and when they come back up, the master is operational but all the slaves are disconnected. When you login to the slave CLI you can see that the master IP they are trying to contact is a 169.254 address. There is no DHCP involved anywhere here. 

     

    Anybody experienced this?

     

    If i reboot the master VC it seems to all come back up fine. 

     

    None of the devices are using Eth1.

     

    This is from the active master (show summary)

     

    Master IP Address *:192.168.1.251
    IP Address :192.168.1.251
    Netmask :255.255.255.0
    Gateway :192.168.1.1

     

    This is from a slave:

     

    Master IP Address :169.254.107.171
    IP Address :192.168.1.250
    Netmask :255.255.255.0
    Gateway :192.168.1.1

     

     

     

    When the slaves reboot i see this in the logs:

     

    Jan 18 07:15:54 cli[5287]: <341135> <WARN> |AP APNAME1@192.168.1.250 cli| Master Changed - new 169.254.107.171 old 0.0.0.0 current swarm state 0.
    Jan 18 07:15:55 cli[5287]: <341135> <WARN> |AP APNAME1@192.168.1.250 cli| Master Changed - new 169.254.107.171 old 0.0.0.0 current swarm state 1.

     

     

    And on the master I see:

     

    Jan 18 10:12:52 stm[5302]: <304067> <ERRS> |AP APNAME1@192.168.1.250 stm| PAPI_Send failed: papi_send_status_callback, 2877: Connection timed out; from 8451 to 169.254.107.171:15200 len 27 type 115

     

    For some reason it seems the Master forgets who it is?

     

    Scott



  • 2.  RE: IAP - Cluster communications fail and master ip set to 169.254.x.x

    Posted Jan 18, 2016 06:57 PM
    Are you sharing that segment with any other devices ?

    Duplicate IP address ?

    Sent from Outlook Mobile


  • 3.  RE: IAP - Cluster communications fail and master ip set to 169.254.x.x

    Posted Jan 18, 2016 07:51 PM

    Hi Victor, yes its shared segment, i had considered the possibility of a duplicate but have not been able to detect one yet. Will try and lab test this and see if i can reproduce.

     

     



  • 4.  RE: IAP - Cluster communications fail and master ip set to 169.254.x.x

    Posted Jan 23, 2016 10:09 AM

    169.254. is the range for dhcp failures (not officially but still). so perhaps some "rogue" IAP that messes things up? sometimes it is suggested to use fixed IPs so rule out such issues.