Controllerless Networks

last person joined: 15 hours 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
Expand all | Collapse all

APi105 crashes in mixed environment after firmware upgrade

This thread has been viewed 3 times
  • 1.  APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 08:44 AM

    Day started out normally untill I upgraded the firmware on my 4 iAP's using virtual controller.

    3 iap205's and 1 iap105

    iap105 never came back up

    Factory reset unit on it's own seperate network and let it update itself fine.

    Still could not join the mixed ap environment.

    Took unit to another site and until powered up and joined this network fine?

    See Below slice of log file

    Thanks in advance.

     

    APBoot 1.2.4.4 (build 26618)
    Built: 2011-01-07 at 13:42:04

    Model: AP-10x
    CPU: AR7161 revision: A2
    Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
    DRAM: . 128 MB
    POST1: mem 0 mem 1 mem 2 mem 3 passed
    Copy: ....    done
    Flash: 16 MB
    PCI: scanning bus 0 ...
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 168c 0029 00002 01 10000000 00000000 00000000 00000000
    01 00 168c 0029 00002 01 10010000 00000000 00000000 00000000
    Net: eth0
    Radio: ar922x#0, ar922x#1

    Hit <Enter> to stop autoboot: 2  0
    apboot> factory_resetClearing state... Checking OS image and flags

    Image is signed; verifying checksum... passed
    Dont_clear flag set -- skipping OS clear
    Erasing flash sector @ 0xbff80000....done
    Erased 1 sectors

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

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

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

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

    done
    Purging environment... preserving os_partition (0)
    Un-Protected 1 sectors
    .done
    Erased 1 sectors

    Writing
    Un-Protected 1 sectors
    .done
    Erased 1 sectors

    Writing
    done
    apboot>

    APBoot 1.2.4.4 (build 26618)
    Built: 2011-01-07 at 13:42:04

    Model: AP-10x
    CPU: AR7161 revision: A2
    Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
    DRAM: . 128 MB
    POST1: mem 0 mem 1 mem 2 mem 3 passed
    Copy: ....    done
    Flash: 16 MB
    PCI: scanning bus 0 ...
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 168c 0029 00002 01 10000000 00000000 00000000 00000000
    01 00 168c 0029 00002 01 10010000 00000000 00000000 00000000
    Net: eth0
    Radio: ar922x#0, ar922x#1

    Hit <Enter> to stop autoboot: 2  1  0
    Booting OS partition 0
    Checking image @ 0xbf100000

    Image is signed; verifying checksum... passed
    Signer Cert OK
    Policy Cert OK
    RSA signature verified.
    ELF file is 32 bit
    Loading .text @ 0x80e00000 (6305896 bytes)
    Loading .data @ 0x81403870 (32 bytes)
    Clearing .bss @ 0x81403890 (16 bytes)
    ## Starting application at 0x80e00000 ...
    Uncompressing............................................................

    þ

    Aruba Networks

    ArubaOS Version 6.2.1.0-3.4.0.1 (build 39461 / label #39461)

    Built by p4build@crete on 2013-08-15 at 19:25:52 PDT (gcc version 4.3.3)

    CPU Rev: aa

    71x CPU

    Flash variant: default

    Cache parity protection disabled

    Using 340.000 MHz high precision timer. cycles_per_jiffy=680000

    Memory: 120576k/131072k available (1687k kernel code, 10408k reserved, 625k data, 5492k init, 0k highmem)

    available.

    detected lzma initramfs

    initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=27187200

    LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ...............................................................................................................................................................................................................................................................................................................................................................................................................................

    AR7100 GPIOC major 0

    wdt: registered with refresh

    Enabling Watchdog

    Talisker RSSI LED initialization

    Creating 1 MTD partitions on "ar7100-nor0":

    0x00000000-0x01000000 : "flash"

    i2c /dev entries driver

    i2c-talisker: using default base 0x18040000

    AD7416 driver probing for devices on AR7100 I2C

    .<6>lo: Disabled Privacy Extensions

    IPv6 over IPv4 tunneling driver


    Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT

    Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT

    Starting Kernel DES KAT ...Completed Kernel DES KAT

    Starting Kernel AES KAT ...Completed Kernel AES KAT


    Domain Name: 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
    Testing TPM... Passed
    apfcutil: sector MESH Prov: Cache uninitialized
    ag7100_mod: module license 'unspecified' taints kernel.

    AG7100: Length per segment 512

    AG7100: Max segments per packet 4

    AG7100: Max tx descriptor count 400

    AG7100: Max rx descriptor count 252

    AG7100: fifo cfg 3 018001ff

    AG7100CHH: Mac address for unit 0

    AG7100CHH: 00:0b:86:cf:8e:aa

    ATHRF1: Port 0, Neg Success

    ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0

    ag7100_ring_alloc Allocated 4800 at 0x8035c000

    ag7100_ring_alloc Allocated 3024 at 0x86013000

    AG7100: cfg1 0xf cfg2 0x7014

    ATHRF1: Port 0, Neg Success

    ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100

    AG7100: unit 0: phy not up carrier 1

    Writing 4

    ADDRCONF(NETDEV_UP): bond0: link is not ready

    AG7100: unit 0 phy is up...RGMii 1000Mbps full duplex

    AG7100: pll reg 0x18050010: 0x110000 AG7100: cfg_1: 0x1ff0000

    AG7100: cfg_2: 0x3ff

    AG7100: cfg_3: 0x18001ff

    AG7100: cfg_4: 0xffff

    AG7100: cfg_5: 0xfffef

    AG7100: done cfg2 0x7215 ifctl 0x0 miictrl 0x22

    ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready

    wifi uplink not present...
    Ethernet uplink active. Becoming Mesh Portal
    AP xml model 39, num_radios 2 (jiffies 15901)

    init_asap_mod: installation:0

    radio 0: band 1 ant 0 max_ssid 8

    radio 1: band 0 ant 0 max_ssid 8

    election init: rand=1d HZ=500

    setting bond0 as bridge child

    setting gre0 as split child

    notify asap_mod 3g no present...
    Starting watchdog process...
    Getting an IP address...
    Dec 31 16:00:32 udhcpc[801]: udhcpc (v0.9.9-pre) startedDec 31 16:00:32 udhcpc[801]: send_discover: pkt num 0, secs 0Dec 31 16:00:32 udhcpc[801]: Sending discover...Dec 31 16:00:32 udhcpc[801]: send_selecting: pkt num 0, secs 0Dec 31 16:00:32 udhcpc[801]: Sending select for 10.10.0.180...Dec 31 16:00:32 udhcpc[801]: Lease of 10.10.0.180 obtained, lease time 3600Dec 31 16:00:32 udhcpc[801]: DHCP OPT 43 deleted airwave config
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    10.10.0.180 255.255.255.0 10.10.0.1
    Compressing all files in the /etc/httpd directory...
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    ip_time_handler: Got ip and packets on bond0 Started master election 74-0

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    Done.
    Starting Webserver
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    NTP Server not saved in flash... using default
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)

    ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved

    ath_rate_atheros: Aruba Networks Rate Control Algorithm

    ath_dfs: Version 2.0.0

    Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved

    ath_spectrum: Version 2.0.0

    Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved

    ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved

    ath_pci: 0.9.4.5 (Atheros/multi-bss)

    Adding bridge entry for magic vlan GW, ifindex 8195, 04:bd:88:c3:49:4c

    (12:15:26) !!! Init ---> Slave

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    wifi0: Base BSSID 00:0b:86:78:ea:a8, 8 available BSSID(s)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    bond0 address=00:0b:86:cf:8e:aa

    br0 address=00:0b:86:cf:8e:aa

    wifi0: AP type AP-105, radio 0, max_bssids 8

    wifi0: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    wifi1: Base BSSID 00:0b:86:78:ea:a0, 8 available BSSID(s)

    bond0 address=00:0b:86:cf:8e:aa

    br0 address=00:0b:86:cf:8e:aa

    wifi1: AP type AP-105, radio 1, max_bssids 8

    wifi1: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000

    ath_ahb: 0.9.4.5 (Atheros/multi-bss)


    Starting FIPS KAT ... Completed FIPS KAT

    shutting down wafunction - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    tchdog process (nanny will restart it)...
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)


    <<<<< Welcome to the Access Point >>>>>

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    Launching IAP CLI...
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    process `snmpd' is using obsolete setsockopt SO_BSDCOMPAT

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)
    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    asap_send_elected_master: sent successfully

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    wait for stm to initialize over

    asap_send_elected_master: sent successfully

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    User: function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function - asap_mob_pkt_rcv dropped invalid beacon frame type (36861) magic(48879) version(4)

    function

     

     



  • 2.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 09:24 AM

    What did you update it to?

     



  • 3.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 10:20 AM

    Hi,

     

    I would try the following commands to gather some info:

     

    - show log system

    - show log debug

    - show election

    - show swarm mode

    - show swarm state

    - show upgrade info

    - show log kernel

     

    To see if we can find more information



  • 4.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 12:29 PM
      |   view attached

    log files attached

    Attachment(s)

    txt
    putty.txt   38 KB 1 version


  • 5.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 12:47 PM

    This firmware is almost 3 years old.

    ArubaOS Version 6.2.1.0-3.4.0.1 (build 39461 / label #39461)

    Built by p4build@crete on 2013-08-15 at 19:25:52 PDT (gcc version 4.3.3)

     

    Are you saying that you cannot even upgrade it?  You should...



  • 6.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 01:06 PM

    Please guide me to the proper upgrade files

    I cannot finfd them manually

     



  • 7.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 01:05 PM

    I should add that I am able to setup the unit fine on a new network.

    It's only when I try and add it to the existing cluster does it fail

    IAP 105 firmware level : 6.2.1.0-3.4.0.1._39461

    Cluster firmware : 6.5.4.6_63925

     

    The ip105 says it has the latest firmware?



  • 8.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 01:06 PM

    Please try to update it manually using the firmware here: http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/20374/Default.aspx

     

    That firmware is probably so old, that it cannot upgrade with the cloud.



  • 9.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 01:12 PM

    Update:

     

    According to the 6.5.0.0 release notes:

    http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/Command/Core_Download/Default.aspx?EntryId=24557

    Screenshot 2018-03-28 at 12.10.30.png

    The IAP-105 is not supported past 6.4.4.4-4.2.3.2.



  • 10.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 02:34 PM

    UGH is all I can say..

     

    iap105 upgraded to 6.4.4.8.4.2.4.10_62611

    Now it boots fine, identifies itself as a slave, sends out it's request to the master....and never hears back.

    I assume it will never get to a level to re-join the rest of my iap units at 63925

    I wish I had never pushed that upgrade button yesterday, now I have one whole segment of my world down.

     



  • 11.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 02:43 PM

    So, the rest of your cluster also has to be on 6.4.x.x or below or the IAP-105 won't be able to join.  What are you trying to do?

     



  • 12.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 03:04 PM

    Just trying to get my world back the way it was yesterday when I had 5 working iap units

    2 iap 105

    3 iap 205 units

    They were all working fine and humming along with out of date firmware.

    I hit the system update and now 2 iap105's are as good as bricks to me.

     

    Only myself to blame...I get that...just frustrating

     



  • 13.  RE: APi105 crashes in mixed environment after firmware upgrade

    EMPLOYEE
    Posted Mar 28, 2018 03:22 PM

    Any idea what version of firmware it was on before?



  • 14.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 03:25 PM

    Not when we started but everything was working so probably very old

     



  • 15.  RE: APi105 crashes in mixed environment after firmware upgrade
    Best Answer

    EMPLOYEE
    Posted Mar 28, 2018 04:00 PM

    So why not upgrade the whole cluster to what all APs would support?  the 6.4.4.4 http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/21998/Default.aspx

     

     



  • 16.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Mar 28, 2018 04:42 PM

    wouldn't that be a downgrade?

    can I go backwards in firmware?



  • 17.  RE: APi105 crashes in mixed environment after firmware upgrade
    Best Answer

    EMPLOYEE
    Posted Mar 28, 2018 05:40 PM

    It would be an upgrade from where you started, and gets you to the latest version of code that supports all of your current APs.

     

    The current version of IAP code does not support the IAP105, which is why it can not rejoin the cluster.



  • 18.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Jun 05, 2018 08:26 AM

    HI,

     

    Sorry to hijack this post, but I have a similar cluster with mixed IAP105s and IAP205s.  You have stated that 6.4.4.4-4.2.3.2 is the highest firmware version that IAP105s will still cluster with IAP205s.  I have looked on the support downloads and you can get version 6.4.4.8-4.2.4.4 for IAP105s.  Would it be OK to upgrade the whole cluster to this version of firmware? (6.4.4.8-4.2.4.4).  I don't want to break the cluster!

     

    Thanks



  • 19.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Jun 05, 2018 08:33 AM

    Yes, I think it should work with 6.4.4.8-4.2.4.4 as well

    Kevin



  • 20.  RE: APi105 crashes in mixed environment after firmware upgrade

    Posted Jun 06, 2018 04:46 AM

    Thanks Kevin.