Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

AP-105 Warm Starting

This thread has been viewed 0 times
  • 1.  AP-105 Warm Starting

    Posted Jan 30, 2015 04:40 PM

    The following message is being listed consistently  

     

    05:30:09Access point 00:24:6c:c9:1a:d9 with name 00:24:6c:c9:1a:d9 and IP address 192.168.1.17 warm-started 326 time(s)

     

    I assume the AP needs to be replaced?



  • 2.  RE: AP-105 Warm Starting

    Posted Jan 31, 2015 04:29 AM

    is the Instant or Controller based?

     

    i assume a warm boot is a proces restart, there might be a valid reason for that which is not hardware related. how often does it actually happen? have you reset that AP back to factory default and get it up again? is there anything else in the logs indicating a reason?

     

    i think the fastest way to go is try to RMA it, probably TAC will ask you some questions and determine is this is hardware related or just another type of issue.

     

    please do report back if you try to RMA and what the resultat was.



  • 3.  RE: AP-105 Warm Starting

    EMPLOYEE
    Posted Jan 31, 2015 07:08 AM

    @tmattson57 wrote:

    The following message is being listed consistently  

     

    05:30:09 Access point 00:24:6c:c9:1a:d9 with name 00:24:6c:c9:1a:d9 and IP address 192.168.1.17 warm-started 326 time(s)

     

    I assume the AP needs to be replaced?


    You can type:

    show ap debug counters ap-name 00:24:6c:c9:1a:d9

     ..and see what the nature of the warm starts are, to get an idea of what is happening.

     

    You can also type "show log system 50" to see if the access points says why it is restarting, in addition.  The reason why an AP is restarting now and the reason why it restarted before is not always the same.  If you mounted and powered an AP before the controller was in place, it would restart quite a few times.  If the reason for it restarting is different, lately, you need to determine that to see if it is a configuration, network or a hardware issue.

     



  • 4.  RE: AP-105 Warm Starting

    Posted Feb 02, 2015 02:03 PM

    Looks like it isn't talking to the controller. What might cause that?

     

    AP Counters
    -----------
    Name               Group    IP Address    Configs Sent  Configs Acked  AP Boots Sent  AP Boots Acked  Bootstraps (Total)  Reboots  Crash
    ----               -----    ----------    ------------  -------------  -------------  --------------  ------------------  -------  -----
    00:24:6c:c9:1a:d9  default  192.168.1.17  0             0              0              0               1          (1357 )  1357     N

     

    Feb 2 02:44:16 :303022:  <WARN> |AP 00:24:6c:c9:1a:d9@192.168.1.17 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:05:38 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1152 dest=192.168.1.12 tries=10 seq=0



  • 5.  RE: AP-105 Warm Starting

    EMPLOYEE
    Posted Feb 02, 2015 02:07 PM

    Is there a firewall or a WAN between the controller and that access point?

     



  • 6.  RE: AP-105 Warm Starting

    Posted Feb 02, 2015 02:46 PM

    I don't believe there is.



  • 7.  RE: AP-105 Warm Starting

    Posted Feb 02, 2015 03:06 PM

    I rebooted the controller to adjust the date/time and now I see these messages...doesn't look good.

     

    2015-02-0303:58:33Access point 00:24:6c:cb:0b:2e with Name 00:24:6c:cb:0b:2e and IP address 192.168.1.17 cold-started 17 time(s)


  • 8.  RE: AP-105 Warm Starting
    Best Answer

    Posted Feb 02, 2015 03:11 PM

    Well I believe I found the issue. We have two AP's with the same static IP address...crap



  • 9.  RE: AP-105 Warm Starting

    Posted Feb 03, 2015 04:26 AM

    @tmattson57 wrote:

    Well I believe I found the issue. We have two AP's with the same static IP address...crap


    and that is one of the reasons why you should use DHCP to provide IP addresses for your APs and try to stay away from static settings as much as possible. (if you can of course)