11-19-2014 09:29 PM
We are seeing one RAP3 goes down and the following message in the log.
WB-JOHN-ROGOVIN-RAP3 WB-SOHO-RAP5-WIRED-EMPLOYEE RAP-3WN 184.108.40.206 Down Rc2 10.140.xxx.xxx 0.0.0.0 00:0b:86:9f:81:ad BF0063365 N/A 220.127.116.11
Nov 19 03:23:33 nanny: <303022> <WARN> |AP WB-JOHN-ROGOVIN-RAP3@18.104.22.168 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:31:37 PST 1999; Unable to set up IPSec tunnel after 85 tries
Can they be related? Any better way to troubleshoot? Interesting enough that it's not an AP so that "show ap ....." commands are not avaiable.Please advise. Thanks,
Re: RAP reboot
Re: RAP reboot
11-23-2014 01:28 AM - edited 11-23-2014 01:29 AM
We would need more information about your infrastructure:
- Do you have a single controller or multiple controllers?
- You would see this message from a device where it finds the first controller, but the LMS-IP in the access point's ap system profile in ap-group points it to another controller that does not exist. When the access point finally reboots because it cannot find that second controller, it comes up and reports that it did not find the second controller, to the first controller. Without knowing your setup, we cannot determine if that is your issue.
- The "show ap" commands do not work for devices that are not currently up and running on a controller, so that might explain why those commands fail...
Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.