Wireless Access

last person joined: 15 minutes ago 

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

205 AP not booting

Jump to Best Answer
  • 1.  205 AP not booting

    Posted Aug 02, 2018 06:13 PM

    With two of the 205 AP's (not IAP), I am getting the following when the AP is booting:

     

    Running ADP...cat: /tmp/master: No such file or directory
    Done. Master is
    killall: nanny: no process killed
    killall: sapd: no process killed
    Sending SIGKILL to all processes.
    Please stand by while rebooting the system.
    [ 159.876000] Restarting system.

     

    This isn't happening accross the board with AP's but two of the 5 have done this.  I have factory reset the devices and Still nothing.  

     

    Here is the full readout from the Console:

    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
    SKU: 2
    OTP: 0xeca01028
    Clock:
    CPU: 800 MHz
    DDR: 533 MHz
    AXI: 400 MHz
    APB: 200 MHz
    PER: 400 MHz
    DRAM: 128 MB
    POST1: memory passed
    SF: Detected MX25L25635E with page size 4 kB, total 32 MB
    Flash: 32 MB
    PCIe0: RC, link up
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 14e4 4360 00002 03 08000004 00000000 00000000 00000000
    PCIe1: RC, link up
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 14e4 4360 00002 03 40000004 00000000 00000000 00000000
    Power: POE
    Net: eth0
    Radio: bcm43460#0, bcm43460#1

    Hit <Enter> to stop autoboot: 0
    Checking image @ 0x1e100000
    Copying image from 0x1e100000

    Image is signed; verifying checksum... passed
    Signer Cert OK
    Policy Cert OK
    RSA signature verified.
    Uncompressing... done
    [ 0.000000]
    [ 0.000000] Aruba Networks
    [ 0.000000] ArubaOS Version 6.4.3.9 (build 55230 / label #55230)
    [ 0.000000] Built by p4build@lemnos on 2016-05-27 at 13:43:11 PDT (gcc versio n 4.7.2)
    [ 0.000000]
    [ 0.000000] Flash variant: variant0
    [ 0.000000] MPCORE found at 19020000, SCTLR 0x10c53c7f ACTLR 0x00000040 CPSR 0x600001d3 SPSR 0x60000013 PRRR 0x000a81a8 NMRR 0x40e040e0
    [ 0.000000] Memory: 128MB = 128MB total
    [ 0.000000] Memory: 120660k/120660k available, 10412k reserved, 0K highmem
    [ 0.050000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counter s available
    [ 3.450000] PMU: registered new PMU device of type 0
    [ 3.958000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
    [ 3.960000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bi t]
    [ 3.962000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
    [ 4.466000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
    [ 4.468000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bi t]
    [ 4.470000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
    [ 4.816000] i2c-springbank: using remapped base c9e5c060
    [ 4.820000] mpcore_wdt mpcore_wdt: enabling watchdog.
    [ 4.824000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address
    [ 4.826000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)
    [ 4.828000] Creating 1 MTD partitions on "spi1.0":
    [ 4.830000] 0x000000000000-0x000002000000 : "qspi"
    [ 4.844000]
    [ 4.844000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
    [ 4.848000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
    [ 4.908000] Starting Kernel DES KAT ...Completed Kernel DES KAT
    [ 4.912000] Starting Kernel AES KAT ...Completed Kernel AES KAT
    [ 4.914000]
    AP-type has_ble_support: .
    Domain Name: arubanetworks.com
    No panic info available
    [ 13.632000] AP xml model 81, num_radios 2 (jiffies 6816)
    [ 13.634000] init_asap_mod: installation:0
    [ 13.636000] radio 0: band 1 ant 0 max_ssid 16
    [ 13.638000] radio 1: band 0 ant 0 max_ssid 16
    Starting watchdog process...
    Getting an IP address...
    [ 18.018000] ADDRCONF(NETDEV_UP): bond0: link is not ready
    [ 20.022000] bond0: link up (1000FD)
    [ 20.024000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    192.168.0.151 255.255.255.0 192.168.0.1
    Running ADP...cat: /tmp/master: No such file or directory
    Done. Master is
    killall: nanny: no process killed
    killall: sapd: no process killed
    Sending SIGKILL to all processes.
    Please stand by while rebooting the system.
    [ 159.876000] Restarting system.


    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
    SKU: 2
    OTP: 0xeca01028
    Clock:
    CPU: 800 MHz
    DDR: 533 MHz
    AXI: 400 MHz
    APB: 200 MHz
    PER: 400 MHz
    DRAM: 128 MB
    POST1: memory passed
    SF: Detected MX25L25635E with page size 4 kB, total 32 MB
    Flash: 32 MB
    PCIe0: RC, link up
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 14e4 4360 00002 03 08000004 00000000 00000000 00000000
    PCIe1: RC, link up
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 14e4 4360 00002 03 40000004 00000000 00000000 00000000
    Power: POE
    Net: eth0
    Radio: bcm43460#0, bcm43460#1



  • 2.  RE: 205 AP not booting

    Posted Aug 03, 2018 04:17 AM

    Are the VLAN's correct on the switch port? The AP is obtaining an IP address but failing to locate a master via any of the discovery mechanism. Do you have ADP enabled on your controller? Do you have the DHCP or DNS options configured?



  • 3.  RE: 205 AP not booting

    Posted Aug 03, 2018 10:08 AM

    @Apollo_1776 wrote:

    Getting an IP address...
    [ 18.018000] ADDRCONF(NETDEV_UP): bond0: link is not ready
    [ 20.022000] bond0: link up (1000FD)
    [ 20.024000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    192.168.0.151 255.255.255.0 192.168.0.1
    Running ADP...cat: /tmp/master: No such file or directory
    Done. Master is
    killall: nanny: no process killed
    killall: sapd: no process killed
    Sending SIGKILL to all processes.
    Please stand by while rebooting the system.


    The AP is getting an IP via DHCP, but is not discovering the controller. Sounds like either the AP has been moved to a new VLAN or the DHCP scope has changed. DHCP could be providing either option 43 for master discovery, or it provides DNS information so that the AP can search DNS for the master controller.



  • 4.  RE: 205 AP not booting
    Best Answer

    Posted Aug 03, 2018 11:03 AM

    This seems to be something related to the Switch, as I plugged it into another port to a different switch and it worked like a charm.  Sorry for the run around.