Wireless Access

 View Only
  • 1.  MSM760 not detecting MSM460 AP's - status of "death"

    Posted Oct 16, 2013 08:39 AM

    Hello,

     

    We have a problem whereby if we plug in a new MSM460 AP the MSM760 Controller team is not detecting it properly and the status of the AP's appears as "death". See below for the Event Log

     

     

    2013-10-16 13:29:55 Controlled AP Discovery Death

    2013-10-16 13:29:55 Controlled AP Discovery Detected

    2013-10-16 13:29:55 Controlled AP Discovery Undetected

    2013-10-16 13:29:54 Controlled AP Discovery Death

    2013-10-16 13:29:54 Controlled AP Discovery Detected

    2013-10-16 13:29:54 Controlled AP Discovery Undetected

    2013-10-16 13:29:53 Controlled AP Discovery Death

    2013-10-16 13:29:53 Controlled AP Discovery Detected

    2013-10-16 13:29:53 Controlled AP Discovery Undetected

    2013-10-16 13:29:52 Controlled AP Discovery Death

     

    The firmware on the MSM760 is 5.7.2.0-12736

     

    All of our AP's which have already been provisioned are working fine. Last week we had to reboot the controllers as the proxy service had crashed and was taking up 100% CPU resources. This is the only change that has occured since it was working last.

     

    Thanks



  • 2.  RE: MSM760 not detecting MSM460 AP's - status of "death"

    Posted Oct 16, 2013 11:35 AM
    The only time I've seen the Death issue is when we ended up having an improperly tagged WAN link on the network and as a result APs at site-A were able to connect to the controller's on both site-A and site-B. This resulted in the APs showing on the controller in site-A as Death. Removing the incorrect VLAN tagging across the WAN link fixed that issue. Probably not related to your issue but....


  • 3.  RE: MSM760 not detecting MSM460 AP's - status of "death"

    Posted Nov 30, 2013 08:47 AM

    5.7.2 is quite an old firmware. You may want to investigate getting an upgrade whatever the outcome of this issue.

     

    If it is just one AP, you may want to try a manual reset, and maybe even convert to autonomous and upgrade to the current firmware manually, and then change it back to controlled mode.