Controllerless Networks

 View Only
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
Expand all | Collapse all

Compatibility 303 and 365

This thread has been viewed 64 times
  • 1.  Compatibility 303 and 365

    Posted Mar 06, 2023 11:16 AM

    Hey all,

       I have 3 303 indoor APs in an IAP cluster and a 'new' 365 I need to put outside (they are all used APs that I have factory reset). I've got them all on the most current 8.11.0.1_85785 firmware, but I can't get the 365 to join the 303 cluster. Before I post more details I just want to make sure these models are compatible.

    Should they be able to be in the same cluster?

    What's strange is that when I go to the 365 IP, it redirects to the cluster master, but it doesn't show in the cluster and doesn't have the shared config if I ssh to it.

    I have confirmed they all have different IPs from DHCP reservations.

    Mike



  • 2.  RE: Compatibility 303 and 365

    MVP GURU
    Posted Mar 06, 2023 11:30 AM

    If they can run the same version of OS, then they can cluster. Have you tried to factory reset the outdoor AP. Make sure its in the same VLAN as the other APs when its booting back up for the first time.



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------



  • 3.  RE: Compatibility 303 and 365

    Posted Mar 07, 2023 09:43 AM

    I have done a factory reset, but I will try again and post results.

    Are there any settings that aren't cleared on a factory reset?

    Mike




  • 4.  RE: Compatibility 303 and 365

    Posted Mar 07, 2023 10:26 AM

    Below is console output from the AP. The web gui redirects to the current cluster master, but doesn't load on the AP IP and SSH is not connecting. Confirmed the switch port and vlan config is the same for each AP.

    The console output continues with !!! Init ---> Member

    passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.
    Uncompressing Kernel Image ... OK
    [    0.000000]
    [    0.000000] Aruba Networks
    [    0.000000] ArubaOS Version 8.11.0.1-8.11.0.1 (build 85785 / label #85785)
    [    0.000000] Built by jenkins@pr-hpn-cd-build39 on 2022-12-15 at 00:23:12 PST (gcc version 4.6.3)
    [    0.000000]
    [    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
    [    0.016603] SMP: Total of 4 processors activated (384.00 BogoMIPS).
    [    0.052328] i2c-gpio driver registered
    [   17.139916] 3 ofpart partitions found on MTD device 7980000.qcom,nand
    [   17.206804] Creating 3 MTD partitions on "7980000.qcom,nand":
    [   17.275552] 0x000000000000-0x000002000000 : "aos0"
    [   17.375316] 0x000002000000-0x000004000000 : "aos1"
    [   17.462578] 0x000004000000-0x000008000000 : "ubifs"
    [   17.599380] m25p80 spi0.0: found w25q32, expected n25q128a11
    [   17.694828] Found AT97SC3203 on MSM-I2C-v2-adapter
    [   17.750458] Key type dns_resolver registered
    [   17.790786] Registering SWP/SWPB emulation handler
    [   19.134046] There is no gpio reset info
    [   19.230129]
    Starting Kernel SHA1 KAT ...
    [   19.264607] Completed Kernel SHA1 KAT
    [   19.311452] Starting Kernel HMAC-SHA1 KAT ...
    [   19.361662] Starting Kernel DES KAT ...[   19.407340] Completed Kernel DES KAT
    [   19.451145] Starting Kernel AES KAT ...
    [   19.494856] Completed Kernel AES KAT
    [   19.494856]
    [   19.558373] Starting Kernel AESGCM KAT ...
    [   19.605197] Completed Kernel AESGCM KAT
    [   19.654448] Completed Kernel HMAC-SHA1 KAT
    Thu Jan  1 00:00:00 PST 1970
    Populate AP type info
    Domain Name: SetMeUp.arubanetworks.com
    Current OEM Name : Aruba Networks
    Disabling ipv6 for devices by default
    AP-type has_ble_support: ONBOARD.
    IPv6 capability is supported for devices
    No panic info available
    Enabling ble_daemon and ble_relay via nanny
    glenmorangie: Start hotplug
    per-ap-setting not in backup and restore mode, Backup ENV.
    Installing glenmorangie ethernet driver
    [   32.907238] edma module_init
    Enter non-FIPS mode
    Cfg len is 965
    no SSID detected...
    uap controller less detected
    Mesh enabled
    single uplink platform
    Starting watchdog process...
    Aruba watchdog daemon started [4 thread(s)]
    Loading configuration file of length 965...
    wifi uplink not present...
    No valid ssid was found...
    extended ssid activate due to no valid ssid ...
    touching file /tmp/ip_mode_0
    [   38.995344] bond0: GMAC Link is up with phy_speed=1000
    error in reading source file
    Mesh is DISABLED on this device.
    extended ssid is activated on the platform ...
    copying bootuplog ...
    [   39.830652] uol: module license 'Proprietary' taints kernel.
    [   39.894652] Disabling lock debugging due to kernel taint
    [   39.959687] uol_init_driver:434 HW offload not applicable, AP will use cutting through path!
    allow PAPI
    set device anul0 mtu to 2000
    notify asap_mod 3g no present...
    Starting update SBL1 ...
    SBL1 was updated already
    Done.
    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
    Starting DHCP
    Getting an IP address...
    Jan  1 00:00:24 udhcpc[4225]: udhcpc (v0.9.9-pre) started
    Jan  1 00:00:24 udhcpc[4225]: send_discover: pkt num 0, secs 0
    Jan  1 00:00:24 udhcpc[4225]: Sending discover...
    Jan  1 00:00:24 udhcpc[4225]: send_selecting: pkt num 0, secs 0
    Jan  1 00:00:24 udhcpc[4225]: Sending select for 192.168.1.180...
    Jan  1 00:00:24 udhcpc[4225]: Lease of 192.168.1.180 obtained, lease time 60000000
    [   45.152063] ip_time_handler: Got ip and packets on bond0 Started conductor election 3-0, rand 21
    [   45.970221] (08:00:26) !!! Init ---> Member
    192.168.1.180 255.255.255.0 192.168.1.200
    Compressing all files in the /etc/httpd directory...
    Done.
    Starting Webserver
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    Put ntpdate to the nannylist.
    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
    Power supply mode is POE:, USB Modem is not present.
    User: [   77.002024] Starting Kernel HMAC SHA1 FIPS KAT ...
    [   77.044816] Completed Kernel HMAC SHA1 FIPS KAT
    [   79.008029] Starting Kernel HMAC SHA256 FIPS KAT ...
    [   79.052918] Completed Kernel HMAC SHA256 FIPS KAT
    ble_ready NOT present @init ....
    [   81.008056] Starting Kernel HMAC SHA384 FIPS KAT ...
    [   81.052974] Completed Kernel HMAC SHA384 FIPS KAT
    [   83.008039] Starting Kernel HMAC SHA512 FIPS KAT ...
    [   83.052943] Completed Kernel HMAC SHA512 FIPS KAT
    Firmware AES-CCM Known Answer Test Passed
    [  104.703446] asap_send_elected_conductor: sent successfully
    [  104.970390] asap_send_elected_conductor: sent successfully
    [  106.970351] (15:07:08) !!! Init ---> Member
    [  107.970332] (15:07:09) !!! Init ---> Member
    [  108.970358] (15:07:10) !!! Init ---> Member
    [  109.970363] (15:07:11) !!! Init ---> Member
    [  110.970387] (15:07:12) !!! Init ---> Member
    [  111.970364] (15:07:13) !!! Init ---> Member
    [  112.970348] (15:07:14) !!! Init ---> Member
    [  113.970374] (15:07:15) !!! Init ---> Member
    [  114.970373] (15:07:16) !!! Init ---> Member
    [  115.970369] (15:07:17) !!! Init ---> Member
    [  116.970406] (15:07:18) !!! Init ---> Member
    [  117.970381] (15:07:19) !!! Init ---> Member
    [  118.970384] (15:07:20) !!! Init ---> Member
    [  119.970390] (15:07:21) !!! Init ---> Member
    [  120.970396] (15:07:22) !!! Init ---> Member
    [  121.970395] (15:07:23) !!! Init ---> Member
    [  122.970393] (15:07:24) !!! Init ---> Member
    [  123.970402] (15:07:25) !!! Init ---> Member
    [  124.970402] (15:07:26) !!! Init ---> Member
    [  125.970406] (15:07:27) !!! Init ---> Member
    [  126.970413] (15:07:28) !!! Init ---> Member
    [  127.970410] (15:07:29) !!! Init ---> Member
    [  128.970422] (15:07:30) !!! Init ---> Member
    [  129.970407] (15:07:31) !!! Init ---> Member




  • 5.  RE: Compatibility 303 and 365

    Posted Mar 07, 2023 03:05 PM

    I've done another factory reset and the AP is up now and I can login to the GUI and SSH, but it's still not joining the 303 cluster, so it's just a standalone AP right now.




  • 6.  RE: Compatibility 303 and 365

    MVP GURU
    Posted Mar 07, 2023 03:09 PM

    They are in the same VLAN/Subnet? If not they will not cluster. Also make sure you are on the same version/build number as the current cluster. 



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------



  • 7.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 03:46 AM

    First step is always to upgrade/downgrade APs to the same FW version as you have it in an existing cluster, if this is a new model of AP that is not yet in the cluster.

    If you have Activate, Central or Airwave, this will be taken for you, if you set it up correctly.

    After that you can join a new AP into the cluster. Usually without additional problems.

    As #DB86 already wrote, all APs in the cluster must have the same FW version. 

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 8.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 11:03 AM

    The APs are all running the same fw and there's only one VLAN on the switch. Maybe the CAP-only sku is a problem?

    show log provision

    Provisioning Log
    ----------------
    Time                                        State                   Type                 Log Message                                                                               
    ----                                            -----                      ----                   -----------                                                                               
    Wed Mar  8 15:48:16 2023  UAP ADP             Warning          ADP info: CAP-only sku. Will set it as standalone mode                                    
    Wed Mar  8 15:48:19 2023  DHCP Option      In progress    Performing DHCP discovery                                                                 
    Wed Mar  8 15:48:19 2023  DHCP Option      In progress    DHCP lease of 192.168.1.180 obtained, lease time 60000000 seconds                         
    Wed Mar  8 15:48:56 2023  UAP ADP             Warning          ADP info: CAP-only sku. Set its ccode as WW                                               
    Wed Mar  8 15:49:19 2023  Central                Debug             Init Domain list                                                                          
    Wed Mar  8 15:49:23 2023  UAP ADP             Warning          ADP info: No rule in flash.                                                               
    Wed Mar  8 15:49:26 2023  UAP ADP             Warning          ADP info: Reset the provision status for new conductor.                                   
    Wed Mar  8 15:49:26 2023  Activate               In progress     Attempting provisioning via Activate server: device.arubanetworks.com                     
    Wed Mar  8 15:49:26 2023  UAP ADP             Warning          ADP info: Check with activate after IP ready.                                             
    Wed Mar  8 15:49:26 2023  UAP ADP             Warning          ADP info: Send one first provision request.                                               
    Wed Mar  8 15:49:26 2023  Activate               Debug             Sent challenge response to Activate Server: device.arubanetworks.com                      
    Wed Mar  8 15:49:27 2023  UAP ADP             Warning          ADP info: No rule is configured for the AP.                                               
    Wed Mar  8 15:49:27 2023  UAP ADP             Warning          ADP info: Retrieve the valid provision rule.                                              
    Wed Mar  8 15:49:27 2023  UAP ADP             Warning          ADP info: No Provision rule is found and did not get amp/central rule before.             
    Wed Mar  8 15:49:52 2023  UAP ADP             Warning          ADP info: Apply the provision rule from cloud at begining.                                
    Wed Mar  8 15:49:52 2023  UAP ADP             Warning          ADP info: provision string is NULL.                                                       
    Wed Mar  8 15:50:00 2023  UAP ADP             Warning          ADP info: trigger dns based AMP discovery.                    




  • 9.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 12:04 PM

    Hi Mike.

    AP-303 and AP-365 are all universal type of AP and can be Instant or CAP or standalone. 

    Depend on your country, it can be that the model is wrong. Your model is Rest-of-world (RW) hence it can't be used in specific countries like US, Izrael, Egipt, Japan

    On boot prompt list the environment variables with printenv command. This can give as some clues on how AP is configured.

    Also look into osinfo command to see the FWs available on AP. 

    There are several threads in the community how to upgrade AP from boot prompt.

    Best, Gorazd

    You can also manually boot or upgrade from boot prompt to desired FW version.



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 10.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 12:32 PM

    Hello,

    Here are the printenv and osinfo outputs.

    apboot> printenv
    NEW_SBL1=1
    autoload=n
    autostart=yes
    baudrate=9600
    boardname=Bunker
    bootargs=console=ttyMSM0,9600n8 rdinit=/sbin/init ubi.mtd=aos0 ubi.mtd=aos1 ubi.                                                                                     mtd=ubifs
    bootcmd=boot ap
    bootdelay=2
    bootfile=ipq40xx.ari
    ethact=eth0
    ethaddr=a8:bd:27:c7:a2:26
    machid=8010001
    mtddevname=aos0
    mtddevnum=0
    mtdids=nand0=nand0
    mtdparts=mtdparts=nand0:0x2000000@0x0(aos0),0x2000000@0x2000000(aos1),0x4000000@                                                                                     0x4000000(ubifs)
    partition=nand0,0
    servername=aruba-master
    stderr=serial
    stdin=serial
    stdout=serial
    uap_controller_less=0

    Environment size: 553/65532 bytes
    apboot>


    apboot> osinfo
    Partition 0:
        image type: 0
      machine type: 48
              size: 22414920
           version: 8.11.0.1-8.11.0.1
      build string: ArubaOS version 8.11.0.1-8.11.0.1 for Ursa (jenkins@pr-hpn-cd-build39) (gcc version 4.6.3) #85785 SMP Thu Dec 15 00:23:12 PST 2022
             flags: Instant preserve 0220
               oem: aruba

    Image is signed; verifying checksum... passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.

    Partition 1 does not contain a valid OS image
    apboot>




  • 11.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 12:59 PM

    I see you have the correct Aruba Instant Image. What you can try is to set uap_controller_less=1

    boot> setenv uap_controller_less 1

    boot> saveenv

    This should disable controller discovery process.

    Now check, if we get IP address in the same subnet as AP303s.

    boot> dhcp

    boot> ping <your AP303 or VC IP>

    boot> boot

    Also check, if you have enabled autojoin in your existing cluster.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 12.  RE: Compatibility 303 and 365

    Posted Mar 08, 2023 02:14 PM

    I tried the uap_controller_less 1, but that just resulted in repeated !!! Init ---> Member outputs in the console, so I ran purgeenv to reset everything.

    The AP ip address 192.168.1.180 is a DHCP reservation and the AP can ping the current conductor AP at 192.168.1.153


    apboot> dhcp
    eth0 up: 1 Gb/s full duplex
    DHCP broadcast 1
    DHCP IP address: 192.168.1.180
    DHCP subnet mask: 255.255.255.0
    DHCP def gateway: 192.168.1.200
    DHCP DNS server: 8.8.8.8
    DHCP DNS domain: torchwood.local
    apboot> ping 192.168.1.153
    eth0 up: 1 Gb/s full duplex
    Using eth0 device
    host 192.168.1.153 is alive
    apboot>




  • 13.  RE: Compatibility 303 and 365
    Best Answer

    Posted Mar 10, 2023 08:04 AM

    Hi Mike.

    Can you check logs on AP303? I would suggest to take a show tech-support and look into cluster forming. 

    From your console output I can see that APs are seeing each other but do not complete the forming of the cluster. Usually this is due to FW version mismatch /you wrote that are the same) or it can be, that your 303 cluster does not have "allow-new-aps" enabled or something else.

    There is another observation. As you pointed out in the logs, you are seeing the error "ADP info: CAP-only sku."

    This is very unusual for AP-365 as this should be an universal AP. There are several options.

    Supported one is to use controller to convert CAP to Instant.

    Unsupported can be found on internet 

    Best, Gorazd
      



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 14.  RE: Compatibility 303 and 365

    Posted Mar 11, 2023 03:16 PM

    I went ahead and factory reset all of my 303s and the 365. rebuilt the config (it was small) and the 303s all came back into the cluster, but the 365 did not, so it's still just a standalone AP. This is disappointing, but I can work with it. I don't know of anything else to try except a different firmware version, but I'd rather just stay on the latest version. Thank you for your help.




  • 15.  RE: Compatibility 303 and 365

    Posted Mar 12, 2023 05:36 AM

    You can try the setup from the link from my previous reply.

    Best, Gorazd. 



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 16.  RE: Compatibility 303 and 365

    Posted Mar 12, 2023 03:05 PM

    Ah, the unsupported way seems to have worked, thank you!




  • 17.  RE: Compatibility 303 and 365

    Posted Mar 13, 2023 03:24 AM

    Hi Mike.

    I'm glad that you sorted out the problem.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------