Controllerless Networks

last person joined: 2 days 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

RAP-109 rebooting problem... It reboots over and over again.

This thread has been viewed 0 times

  • 1.  RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 09, 2014 03:44 PM

    One of my remote users got a RAP-109, and we configured it and shipped it out to her. It worked for a few days then lost its configuration. She shipped it back and we reconfigured it. It worked for a couple of weeks now it is continuously rebooting. Is this a known problem with this model? It is the only RAP-109 I have in my network. Logs in airwave look like this:

     

     

           
    Thu Jan 9 14:29:38 2014  System  Status changed to 'AP is no longer associated with controller'
    Thu Jan 9 14:29:38 2014  System  Down
    Thu Jan 9 14:24:35 2014  System  Status changed to 'OK'
    Thu Jan 9 14:24:35 2014  System  Up
    Thu Jan 9 14:24:35 2014  System  Device rebooted while marked as down: Change in number of reboots detected (got 10992, expected 10987)
    Thu Jan 9 14:09:36 2014  System  Status changed to 'AP is no longer associated with controller'
    Thu Jan 9 14:09:36 2014  System  Down
    Thu Jan 9 14:04:32 2014  System  Up
    Thu Jan 9 14:04:32 2014  System  Down
    Thu Jan 9 14:04:32 2014  System  Device has rebooted: Change in number of reboots detected (got 10987, expected 10986)                                                                                                            
    Thu Jan  9 14:29:38 2014SystemStatus changed to 'AP is no longer associated with controller'
    Thu Jan  9 14:29:38 2014SystemDown
    Thu Jan  9 14:24:35 2014SystemStatus changed to 'OK'
    Thu Jan  9 14:24:35 2014SystemUp
    Thu Jan  9 14:24:35 2014SystemDevice rebooted while marked as down: Change in number of reboots detected (got 10992, expected 10987)
    Thu Jan  9 14:09:36 2014SystemStatus changed to 'AP is no longer associated with controller'
    Thu Jan  9 14:09:36 2014SystemDown
    Thu Jan  9 14:04:32 2014SystemUp
    Thu Jan  9 14:04:32 2014SystemDown
    Thu Jan  9 14:04:32 2014SystemDevice has rebooted: Change in number of reboots detected (got 10987, expected 10986)


  • 2.  RE: RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 09, 2014 03:46 PM

     

    What AOS do you have installed on your controller ?

     

    Do you have other RAPs working non-rap-109 ?



  • 3.  RE: RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 09, 2014 04:09 PM

    I have RAP-3's and RAP-5's that are working fine (most of the time).

     

    Name:    Aruba Operating System Software.
    Model:    Aruba3200-US
    Version:    6.2.1.2

     

      
      
      


  • 4.  RE: RAP-109 rebooting problem... It reboots over and over again.

    EMPLOYEE
    Posted Jan 09, 2014 04:46 PM
    @dpoppleton wrote:

    I have RAP-3's and RAP-5's that are working fine (most of the time).

     

    Name:    Aruba Operating System Software.
    Model:    Aruba3200-US
    Version:    6.2.1.2

     

       
       
       

    You need to type "show log system 50" on the commandline of your controller to see why these access points say they are rebooting.

     



  • 5.  RE: RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 09, 2014 04:53 PM

    A teammate has some debugs running on this, so there is a lot of logs. The AP name is B06731

     

    Jan 9 15:41:58 :313029:  <INFO> |fpapps|  Removing Tunnel 0x10032 from Vlan 64
    Jan 9 15:41:58 :313029:  <INFO> |fpapps|  Removing Tunnel 0x10051 from Vlan 64
    Jan 9 15:41:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:42:44 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:42:49 :316095:  <INFO> |wms|  Ageing STA 68:7f:74:4e:2e:fb
    Jan 9 15:42:49 :316095:  <INFO> |wms|  Ageing STA 74:9d:dc:79:4b:c1
    Jan 9 15:42:49 :316095:  <INFO> |wms|  Ageing STA 00:18:0a:04:16:fe
    Jan 9 15:42:49 :316095:  <INFO> |wms|  Ageing STA cc:6d:a0:84:91:0f
    Jan 9 15:42:49 :316096:  <INFO> |wms|  Ageing STA tree node  MAC cc:6d:a0:84:91:0f Monitor 24:de:c6:cd:e9:cc
    Jan 9 15:42:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:43:37 :316025:  <INFO> |wms| Sending EXPORT_IMPORT_STATUS to dbsync
    Jan 9 15:43:44 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:43:49 :316069:  <INFO> |wms|  Ageing AP 68:7f:74:4e:2e:fb SSID:Fazzycool  phy-type:2
    Jan 9 15:43:49 :316069:  <INFO> |wms|  Ageing AP 74:9d:dc:79:4b:c1 SSID:2WIRE027  phy-type:2
    Jan 9 15:43:49 :316069:  <INFO> |wms|  Ageing AP 00:18:0a:04:16:fe SSID:  phy-type:2
    Jan 9 15:43:49 :316070:  <INFO> |wms|  Ageing AP tree node BSSID 48:f8:b3:92:9e:53 Monitor 00:0b:86:69:45:45
    Jan 9 15:43:49 :316070:  <INFO> |wms|  Ageing AP tree node BSSID c8:d7:19:7f:c3:78 Monitor 00:0b:86:69:45:45
    Jan 9 15:43:49 :316095:  <INFO> |wms|  Ageing STA 60:36:dd:88:04:b9
    Jan 9 15:43:50 :316096:  <INFO> |wms|  Ageing STA tree node  MAC 60:36:dd:88:04:b9 Monitor 6c:f3:7f:ca:0b:e7
    Jan 9 15:43:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:44:44 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:44:50 :316095:  <INFO> |wms|  Ageing STA b8:f6:b1:1a:b9:d9
    Jan 9 15:44:50 :316095:  <INFO> |wms|  Ageing STA 4a:1b:6c:c2:97:6b
    Jan 9 15:44:50 :316095:  <INFO> |wms|  Ageing STA b8:e6:25:d2:fd:09
    Jan 9 15:44:50 :316096:  <INFO> |wms|  Ageing STA tree node  MAC 4a:1b:6c:c2:97:6b Monitor 00:0b:86:83:12:4e
    Jan 9 15:44:50 :316096:  <INFO> |wms|  Ageing STA tree node  MAC b8:f6:b1:1a:b9:d9 Monitor 6c:f3:7f:ca:0b:e7
    Jan 9 15:44:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:45:03 :305006:  <INFO> |stm|  AP B06731 rebooted
    Jan 9 15:45:04 :313023:  <INFO> |fpapps|  Adding Tunnel 0x10042 to Vlan 64
    Jan 9 15:45:14 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:45:16 :316046:  <INFO> |wms|  Received PROBE REGISTER from: IP 172.29.69.18 Type 1  AP-name B06731 Status 1
    Jan 9 15:45:29 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:45:50 :316069:  <INFO> |wms|  Ageing AP b8:e6:25:d2:fd:09 SSID:2WIRE162  phy-type:2
    Jan 9 15:45:50 :316070:  <INFO> |wms|  Ageing AP tree node BSSID 48:f8:b3:92:9e:53 Monitor 00:0b:86:69:45:45
    Jan 9 15:45:50 :316070:  <INFO> |wms|  Ageing AP tree node BSSID c8:d7:19:7f:c3:78 Monitor 00:0b:86:69:45:45
    Jan 9 15:45:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:46:04 :304057:  <INFO> |stm|  tunnel_timeout: Tunnel 172.29.69.18 6c:f3:7f:c5:1c:5e last_hbt_seq_num_rcvd 25
    Jan 9 15:46:04 :305003:  <INFO> |stm|  AP B06731 is down
    Jan 9 15:46:04 :313029:  <INFO> |fpapps|  Removing Tunnel 0x1006c from Vlan 64
    Jan 9 15:46:04 :313029:  <INFO> |fpapps|  Removing Tunnel 0x1006d from Vlan 64
    Jan 9 15:46:04 :313029:  <INFO> |fpapps|  Removing Tunnel 0x10042 from Vlan 64
    Jan 9 15:46:14 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:46:50 :316095:  <INFO> |wms|  Ageing STA a4:ee:57:4f:52:3b
    Jan 9 15:46:50 :316096:  <INFO> |wms|  Ageing STA tree node  MAC a4:ee:57:4f:52:3b Monitor 00:0b:86:83:0d:b0
    Jan 9 15:46:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:47:44 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:47:50 :316070:  <INFO> |wms|  Ageing AP tree node BSSID 48:f8:b3:92:9e:53 Monitor 00:0b:86:69:45:45
    Jan 9 15:47:50 :316070:  <INFO> |wms|  Ageing AP tree node BSSID c8:d7:19:7f:c3:78 Monitor 00:0b:86:69:45:45
    Jan 9 15:47:59 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0
    Jan 9 15:48:44 :307218:  <INFO> |cfgm|  CFGM IPSEC   src_net:0.0.0.0:0.0.0.0 dst_net:0.0.0.0:0.0.0.0 vlan:0 mac1: mac2: caCert: serverCert: suitBalgo:0 credType:0



  • 6.  RE: RAP-109 rebooting problem... It reboots over and over again.

    EMPLOYEE
    Posted Jan 09, 2014 04:55 PM

    I would remove the debugs and change all of your logging levels to warnings, so we can see what is really going on...

     



  • 7.  RE: RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 14, 2014 04:03 PM

    I've dug through the logs and the only ones are that the device rebooted:

     

    Jan 14 13:46:55  isakmpd[1542]: <103069> <INFO> |ike|  IKE received AP DOWN for 172.xx.xx.200 (External xx.xx.xxx.xx)

     

    I looked in the controller GUI and it says that the RAP-109 has a "Dirty or no config" flag when it connects. It obviously has enough of a config to get back to the controller, but not enough to stay up.

     

    This will be the second time this RAP has been reconfigured. The first time it had no config, like it had been reset to factory defaults. I think there is something wrong with the RAP itself.



  • 8.  RE: RAP-109 rebooting problem... It reboots over and over again.

    EMPLOYEE
    Posted Jan 14, 2014 04:07 PM

    Is this the only access point with this problem?



  • 9.  RE: RAP-109 rebooting problem... It reboots over and over again.

    Posted Jan 14, 2014 04:08 PM

    Yes, all other RAPs are working fine. This is also the only RAP-109 I have.