APIN207 bootup time
05-23-2019 03:59 AM
APBoot 220.127.116.11 (build 59208) Built: 2017-04-13 at 18:41:18 Model: AP-207 CPU: BCM47452 revision: 3 Clock: 900 MHz, DDR rate: 533 MHz DRAM: 255 MiB Flash: Detected W25Q32FV: total 4 MiB NAND: Detected a Mxic NAND flash: total 128 MiB PCIe0: RC, link up dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3 00 00 14e4 aa31 00002 02 00000004 00000000 00000004 00000000 Power: POE Net: eth0 Radio: bcm43570#0, bcm47452#1 Reset: cold FIPS: passed Hit <Enter> to stop autoboot: 0 Booting OS partition 1 Checking image @ 0x2000000 Copying image from 0x04100000
Image is signed; verifying checksum... passed SHA2 Signature available Signer Cert OK Policy Cert OK RSA signature verified using SHA2.
[ 0.000000] [ 0.000000] Aruba Networks [ 0.000000] ArubaOS Version 18.104.22.168-22.214.171.124 (build 60834 / label #60834) [ 0.000000] Built by p4build@pr-hpn-build05 on 2017-08-04 at 20:47:54 UTC (gcc version 4.7.2) [ 0.000000] [ 0.000000] Flash variant: default [ 0.000000] MPCORE found at 18310000, SCTLR 0x10c53c7f ACTLR 0x00006040 CPSR 0x600001d3 SPSR 0x000001d3 PRRR 0xff0a81a8 NMRR 0x40e040e0 [ 0.000000] Memory: 256MB = 256MB total [ 0.000000] Memory: 243432k/243432k available, 18712k reserved, 0K highmem [ 0.000000] External imprecise Data abort at addr=0xd7fd28a7, fsr=0xc06 ignored. [ 0.000000] Found ST compatible serial flash with 64 64KB blocks; total size 4MB [ 0.000000] MPCORE Global Timer Clock 35226Hz [ 0.046000] CCA UART Clock Config: Sel=1 Ovr=1 Div=88 [ 0.046000] CCA UART Clock rate 40000000Hz [ 0.048000] ACP (Accelerator Coherence Port) disabled [ 8.618000] PCI: no core [ 8.618000] PCI: no core [ 8.820000] PCI: scanning bus 0 [ 8.820000] PCI: Fixing up bus 0 [ 9.074000] PCIE1 link=1 [ 9.074000] PCIE1 switching to GEN2 [ 9.324000] PCIE1 link=1 [ 9.324000] PCI: Fixing up bus 0 [ 9.326000] PCI: Fixing up bus 1 [ 9.326000] pci 0001:00:00.0: BAR 8: assigned [mem 0x10000000-0x105fffff] [ 9.326000] pci 0001:01:00.0: BAR 2: assigned [mem 0x10000000-0x103fffff 64bit] [ 9.326000] pci 0001:01:00.0: BAR 2: set to [mem 0x10000000-0x103fffff 64bit] (PCI address [0x10000000-0x103fffff] [ 9.326000] pci 0001:01:00.0: BAR 0: assigned [mem 0x10400000-0x10407fff 64bit] [ 9.326000] pci 0001:01:00.0: BAR 0: set to [mem 0x10400000-0x10407fff 64bit] (PCI address [0x10400000-0x10407fff] [ 9.382000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 9.494000] Creating 1 MTD partitions on "bcmsflash": [ 9.496000] 0x000000000000-0x000000400000 : "nor" [ 9.498000] Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012 [ 9.500000] NAND device: Manufacturer ID: 0xc2, Chip ID: 0xf1 (MXIC NAND 128MiB 3,3V 8-bit) [ 9.502000] Scanning device for bad blocks [ 9.954000] Creating 3 MTD partitions on "brcmnand": [ 9.956000] 0x000000000000-0x000002000000 : "aos0" [ 9.958000] 0x000002000000-0x000004000000 : "aos1" [ 9.960000] 0x000004000000-0x000008000000 : "ubifs" [ 11.334000] i2c-springbank: using remapped base d09d0060 [ 11.336000] mpcore_wdt mpcore_wdt: enabling watchdog. [ 11.338000] ramzswap: num_devices not specified. Using default: 1 [ 11.340000] ramzswap: Creating 1 devices ... [ 11.462000] [ 11.462000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT [ 11.466000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT [ 11.488000] Starting Kernel DES KAT ...Completed Kernel DES KAT [ 11.492000] Starting Kernel AES KAT ...Completed Kernel AES KAT [ 11.494000] [ 11.496000] Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT Thu Jan 1 00:00:00 PST 1970 Domain Name: SetMeUp.arubanetworks.com Current OEM Name : Aruba Networks Disabling ipv6 for devices by default AP-type has_ble_support: BRCM_ONBOARD. IPv6 capability is supported for devices No panic info available Enabling bsa_server via nanny Enabling ble_daemon and ble_relay via nanny Backup ENV. Enter non-FIPS mode Cfg len is 2904 Starting watchdog process... Loading configuration file of length 2904... wifi uplink not present... Terminal access enabled... Valid SSID detected... touching file /tmp/ip_mode_0 Enabling DHCPv6 ... IP mode is v4-only ... [ 25.138000] ADDRCONF(NETDEV_UP): bond0: link is not ready do ethtool autoneg on for bond0 eth0 uplink enabled SIOCGIFFLAGS: No such device Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device eth1 admin down SIOCGIFFLAGS: No such device init usb modem ... springbank: Copying BT modules to /tmp USB is not supported on this model Ethernet uplink not active yet [ 30.148000] bond0: link up (1000FD) [ 30.150000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready disable auto topology rules Starting up in standalone mode disable auto topology rules copying bootuplog ... [ 31.752000] AP xml model 96, num_radios 2 (jiffies 15876) [ 31.754000] apType 96 hw_opmode 0 [ 31.756000] radio 0: band 1 ant 0 max_ssid 16 [ 31.758000] radio 1: band 0 ant 0 max_ssid 16 [ 31.760000] init_asap_mod: installation:0 [ 31.762000] election init: rand=16 HZ=500 [ 31.764000] IAP client match init set device anul0 mtu to 2000 notify asap_mod 3g no present... notify asap standalone ap... apdot1x authentication is not enabled LLDP not sent yet, DHCP is waiting LLDP not sent yet, DHCP is waiting LLDP not sent yet, DHCP is waiting LLDP not sent yet, DHCP is waiting Starting DHCP Got all network params from APboot env. Skipping DHCP 10.0.1.249 255.255.255.0 10.0.1.251 ADP is disabled by uap_controller_less Compressing all files in the /etc/httpd directory... [ 36.768000] ip_time_handler: ignore uplink port state, prefer master 0- standalone 1- wifi uplink 0- 3g uplink 0- enforce eth0 0 [ 36.770000] ip_time_handler: Got ip and packets on bond0 Started master election 2-0, rand 20 Done. Starting Webserver bind: Transport endpoint is not connected 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 [ 53.404000] wifi0: AP type AP-207, radio 0, max_bssids 16 [ 53.504000] PCI: Enabling device 0001:01:00.0 (0140 -> 0142) [ 53.562000] wifi1: AP type AP-207, radio 1, max_bssids 16 springbank: Insmod BT modules [ 54.218000] usbcore: registered new interface driver usbfs [ 54.220000] usbcore: registered new interface driver hub [ 54.222000] usbcore: registered new device driver usb [ 54.238000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 54.244000] ehci_hcd 0000:00:04.1: EHCI Host Controller [ 54.246000] ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1 [ 54.270000] ehci_hcd 0000:00:04.1: irq 36, io mem 0x18004000 [ 54.280000] ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00 [ 54.282000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 54.284000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.286000] usb usb1: Product: EHCI Host Controller [ 54.288000] usb usb1: Manufacturer: Linux 2.6.35 ehci_hcd [ 54.290000] usb usb1: SerialNumber: 0000:00:04.1 [ 54.294000] hub 1-0:1.0: USB hub found [ 54.296000] hub 1-0:1.0: 2 ports detected [ 54.312000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 54.314000] ohci_hcd 0000:00:04.0: OHCI Host Controller [ 54.316000] ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2 [ 54.318000] ohci_hcd 0000:00:04.0: irq 36, io mem 0x1800d000 [ 54.376000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 54.378000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.380000] usb usb2: Product: OHCI Host Controller [ 54.382000] usb usb2: Manufacturer: Linux 2.6.35 ohci_hcd [ 54.384000] usb usb2: SerialNumber: 0000:00:04.0 [ 54.388000] hub 2-0:1.0: USB hub found [ 54.390000] hub 2-0:1.0: 2 ports detected [ 54.408000] usbcore: registered new interface driver btusb [ 54.830000] usb 2-1: new full speed USB device using ohci_hcd and address 2 [ 54.980000] usb 2-1: New USB device found, idVendor=0a5c, idProduct=2045 [ 54.982000] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.984000] usb 2-1: Product: BCM2045A0 [ 54.986000] usb 2-1: Manufacturer: Broadcom Corp [ 54.988000] usb 2-1: SerialNumber: 000000000000 AP rebooted caused by cold HW reset(power loss) shutting down watchdog process (nanny will restart it)... <<<<< Welcome to the Access Point >>>>> Completed SW FIPS KAT test User: [ 86.834000] i am master now [ 86.836000] (08:01:18) !!! Init ---> Master [ 86.838000] asap_send_elected_master: sent successfully
2 minutes 25 seconds
Wireless network available after 2 minutes and 45 seconds.
We're going to use this AP in a standalone system, is there any way to reduce this boot time?
Re: APIN207 bootup time
05-23-2019 05:20 AM
My PC with software is ready in less than 90 seconds and my wireless client is ready in 40 second.
PC and AP are turned on at the same time so now is necessary to wait 3 minutes before being able to start to work with the equipment.
Re: APIN207 bootup time
05-23-2019 05:34 AM
I doubt there is much you can do to increase the AP boot time (if its even possible as its pretty much non-configurable). Are you working in an environment where the additional 2 minutes to boot is critical? Is the CAC timer running on the 5Ghz radio as well an issue?
ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Re: APIN207 bootup time
05-23-2019 06:17 AM
I don't know if it's possible but for example maybe just skipping image signature verification, reduce timeout in master election, DHCP timeout, DFS timer.
As we work in a fixed and controlled enviroment there'are some useless step that maybe takes 1 minute all togeter.
Re: APIN207 bootup time
05-24-2019 01:26 AM
Have you converted your AP to standalone mode? If it is a single AP that may skip the master election process and save some time.
From the logs, it looks like the AP has a fixed static IP already so there should not be DHCP timeouts. If you see delays on the 5GHz radio because of DFS waits, manually limit the radio to select non-DFS channels only (36-48) might take that component out, but the 2.4GHz radio should be enabled immediately.
The image verification is important for the AP security and is bound by the CPU capacity of the AP which is considered an entry level AP in the Aruba product line. A higher end AP will boot faster in this case.
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).