Controllerless Networks

Reply
Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

Colin, as I indicated in my earlier reply, the AP reboots before the CLI is ready to accept logins (59 seconds). There is no way to run any command at all since I cannot login via serial connection before it resets.

 

 

Highlighted
Guru Elite

Re: Why does IAP-205 continuously reboot?

Are these new?  You should open a TAC case..

 


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
MVP Expert

Re: Why does IAP-205 continuously reboot?

Hi Doug,

 

Does any of these non-working IAP's are 205-H?

 

The question might not be relevant to this issue. But I wanted to check as IAP-205 are supported on

4.1 release whereas IAP-205H are only supported from 4.2.

Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

New: yes, though I got them off Amazon new. Working on entitlement/support registration now. I was hoping that somebody else might have seen something similar to this. I looked through the forums and see a few other issues about continuous rebooting, but wasn't able to find anything like this exactly (that had a working solution)

 

Version: here's the relevant info for one of the units currently in a reboot loop (none are 205H). They boot up and contact the master just fine, run for 59 seconds, then reboot (before CLI i ready). They also manage to get the new code from the master into Partition 1.

 

 

apboot> mfginfo
Inventory:
Card 0: System
        Wired MAC           : 84:d4:7e:c4:15:e0
        Wired MAC Count     : 2
        Date Code           : 102915
        Serial              : CM0624875
        Country             : CCODE-US-c3d8e0aa31b3d54d2674f7f45a339af06d31d135
Card 1: CPU
        Assembly            : 2010202D
        Serial              : TB5AL10B8
        Date Code           : 102815
        Major Rev           : 03
        Minor Rev/Variant   : 01

 

apboot> osinfo
Partition 0:
    image type: 0
  machine type: 30
          size: 10085068
       version: 6.4.2.6-4.1.1.6
  build string: ArubaOS version 6.4.2.6-4.1.1.6 for Taurus (p4build@tortuga) (gcc version 4.7.2) #50009 Tue May 12 10:27:51 PDT 2015
         flags: Instant preserve

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

 

Partition 1:
    image type: 0
  machine type: 30
          size: 10100796
       version: 6.4.2.6-4.1.1.11
  build string: ArubaOS version 6.4.2.6-4.1.1.11 for Taurus (p4build@chios) (gcc version 4.7.2) #52666 Sun Nov 22 16:25:55 PST 2015
         flags: Instant preserve

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

MVP Expert

Re: Why does IAP-205 continuously reboot?

Hi Doug,

 

1. Is it possible for you power on one of these non-working IAP's using POE injector or adaptor & see the behavior.?

 

2. Did you had the chance to try factory reset on one of the non-working IAP's & verify the behavior?

 

apboot>factory_reset

 

In case, they still do not work, please open TAC case.

 

 

Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

re: POE - same thing across 2 different switches (HP/Brocade) - so I'm pretty sure this is not POE. We also have countless phones, cameras, wireless antennas, and other POE devices on both.

 

re: factory reset, yes. still same. Could it be something about the specific config that is causing this? (a little bit of my added text all the way at the bottom)

 

 

apboot> factory_reset
Clearing state... Checking OS image and flags

Image is signed; verifying checksum...

Preserving image partition 0
Erasing flash sector @ 0x1ff90000....done
Erased 1 sectors

Erasing flash sector @ 0x1ffb0000....done
Erased 1 sectors

Erasing flash sector @ 0x1ffc0000....done
Erased 1 sectors

Erasing flash sector @ 0x1ffd0000....done
Erased 1 sectors

done
Purging environment... preserving os_partition (1)
Erasing flash...Writing to flash..................done
Erasing flash...Writing to flash..................done
done
apboot> boot

Booting OS partition 1
Checking image @ 0x1ef00000
Copying image from 0x1ef00000

Image is signed; verifying checksum...

Signer Cert OK
Policy Cert OK
RSA signature verified.
Uncompressing... done
[    0.000000]
[    0.000000] Aruba Networks
[    0.000000] ArubaOS Version 6.4.2.6-4.1.1.11 (build 52666 / label #52666)
[    0.000000] Built by p4build@chios on 2015-11-22 at 16:25:55 PST (gcc version 4.7.2)
[    0.000000]
[    0.000000] Flash variant: variant0
[    0.000000] MPCORE found at 19020000, SCTLR 0x10c53c7f ACTLR 0x00000040 CPSR 0x600001d3 SPSR 0x02004058 PRRR 0x000a81a8 NMRR 0x40e040e0
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 117680k/117680k available, 13392k reserved, 0K highmem
[    0.052000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    5.328000] PMU: registered new PMU device of type 0
[    5.834000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
[    5.836000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
[    5.838000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
[    6.340000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
[    6.342000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
[    6.344000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
[    6.688000] i2c-springbank: using remapped base c8914060
[    6.692000] mpcore_wdt mpcore_wdt: enabling watchdog.
[    6.696000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address
[    6.698000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)
[    6.700000] Creating 1 MTD partitions on "spi1.0":
[    6.702000] 0x000000000000-0x000002000000 : "qspi"
[    6.706000]
[    6.706000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[    6.710000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[    6.722000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[    6.726000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[    6.728000]
Domain Name: instant.arubanetworks.com
No panic info available
apfcutil: sector CACHE: Cache uninitialized
apfcutil: sector RAP: Cache uninitialized
apfcutil: sector FAT: Cache uninitialized
apfcutil: sector SCRATCH: Cache uninitialized
Check backup ENV.
apfcutil: sector MESH Prov: Cache uninitialized
Cfg len is 0
Configuration file is empty, turning on default services...
extended ssid activate due to no AP config ...
[   14.610000] ADDRCONF(NETDEV_UP): bond0: link is not ready
[   16.614000] bond0: link up (1000FD)
[   16.616000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Mesh is DISABLED on this device.
Disabling wpa_supplicant for this paltform
[   17.684000] AP xml model 81, num_radios 2 (jiffies 8842)
[   17.686000] init_asap_mod: installation:0
[   17.688000] radio 0: band 1 ant 0 max_ssid 16
[   17.690000] radio 1: band 0 ant 0 max_ssid 16
[   17.692000] election init: rand=15 HZ=500
[   17.694000] IAP client match init
notify asap_mod 3g no present...
Starting watchdog process...
Getting an IP address...
Dec 31 16:00:19 udhcpc[1385]: udhcpc (v0.9.9-pre) started
Dec 31 16:00:19 udhcpc[1385]: send_discover: pkt num 0, secs 0
Dec 31 16:00:19 udhcpc[1385]: Sending discover...
Dec 31 16:00:19 udhcpc[1385]: send_selecting: pkt num 0, secs 0
Dec 31 16:00:19 udhcpc[1385]: Sending select for 10.0.2.23...
Dec 31 16:00:19 udhcpc[1385]: Lease of 10.0.2.23 obtained, lease time 3600
Dec 31 16:00:19 udhcpc[1385]: DHCP OPT 43 deleted airwave config

10.0.2.23 255.255.255.0 10.0.2.1
Compressing all files in the /etc/httpd directory...
[   22.704000] ip_time_handler: Got ip and packets on bond0 Started master election 12-0, rand 29
[   23.124000] Adding bridge entry for magic vlan GW, ifindex 8450, 40:e3:d6:ce:8f:2e
[   23.126000] (00:00:25) !!! Init ---> Slave
Done.
Starting Webserver
bind: Transport endpoint is not connected
bind: Transport endpoint is not connected
bind: Transport endpoint is not connected
Launching NTP Client on pool.ntp.org
[   24.696000] wifi0: AP type AP-205, radio 0, max_bssids 16
[   24.740000] wifi1: AP type AP-205, radio 1, max_bssids 16
shutting down watchdog process (nanny will restart it)...
 
        <<<<<       Welcome to the Access Point     >>>>>
Completed SW FIPS KAT test
 
User: admi[   44.354000] asap_send_elected_master: sent successfully
[   44.374000] process `snmpd_sap' is using obsolete setsockopt SO_BSDCOMPAT
n
System uptime is 46 seconds and CLI is not ready yet, please try again later.
User: [   44.722000] wait for stm to initialize over
[   44.724000] asap_send_elected_master: sent successfully
admin
System uptime is 53 seconds and CLI is not ready yet, please try again later.
User: admin
System uptime is 56 seconds and CLI is not ready yet, please try again later.
User: admin
System uptime is 60 seconds and CLI is not ready yet, please try again later.
User: [   60.094000] asap_send_elected_master: sent successfully

<reset here>

APBoot 1.5.3.14 (build 45815)
Built: 2014-09-05 at 11:23:04

Model: AP-20x
CPU:   BCM53011/15, revision A0
I2C:   ready

 

 

So, this is the first time I've actually seen it hit 60 seconds. It appears there is some internal watchdog timer or something that is hitting at exactly 60 seconds, but I can't figure out what.

 

 

MVP Expert

Re: Why does IAP-205 continuously reboot?

Please open a TAC case.

Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

Hi,

 

is there any solution or Idea yet?

 

I'm also currently hitting (and hunting) some similar symptoms and what I just stumbled over:

It seems that the latest IAP software releases require a reachable NTP server to boot up proplery.

And as your IAP is saying a second timestamp:

 

 

User: [   60.094000] asap_send_elected_master: sent successfully

 

 

it might be that it is also not able to fetch a proper time from an NTP server.

 

Was it the NTP time issue? Did TAC find a solution?

 

Thanks & Bye,

     Chris

 

 

Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

My case is still open. This seems to be isolated (for me) to my Brocade switches. if I plug the IAP-205 into an HP switch it is working fine. Very odd. My next step is to collect trace/mirror data from the brocade, but your theory is interesting. In my case, it's exactly the same DHCP config no matter which switch I plug it into.

Meanwhile, I have plugged a Dell branded IAP-205 into the same port on the same Brocade and it comes up fine, but then I can't login to it because of an Internal Error 8, which is a different issue.

Occasional Contributor II

Re: Why does IAP-205 continuously reboot?

Hi DougDoug,

 

I know TAC tickets currently take very long, so I'm also searching the forum for odd things before contacting TAC.

 

I might have an other hint for you: (While building my survey eqipment) I also stumbled over a quite odd behaviour for IAP's - When it is the only device on an switch it doesn't go into the election mode properly. It needs some 'real' traffic to start the election mode - I had to connect a RasperryPI to the switch that just ping's the IAP's IP and then the IAP started working properly...

 

But when i remember right the key was the message

[   22.704000] ip_time_handler: Got ip and packets on bond0 Started master election 12-0, rand 29

which is here in your case...

 

odd thing. Maybe the brocade is blocking some of the Layer2 broadcast traffic flowing between the IAP's?

Do you have an ethertap or a similar box to capture the l2 traffic between the switch and iap? mabye this gives you an idea ;)

 

Bye,

     Chris

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: