Controllerless Networks

Hey Everybody,

 

We have an IAP 105 cluster that is on 6.3.1.8-4.0.0.7_44641, we recently purchased a couple of IAP 205s to add to it, i see that the minimum software version for the 200 series is Aruba InstantOS 4.1.1.0

 

When i try and update the cluster further, it says no new version available, Is it possible to add these IAP 205s to our IAP 105 cluster?

initially, i plugged in the new iap 205 and it never seemed to show up on the virtual controller, i then saw that there was a minimum aruba instant os of 4.1.1 and figured the 105s could be updated to that, but they dont seem to want to update any further than the version i mentioned in my previous post

Go to the support.arubanetworks.com and download the new version based on the IAP type

 

Thanks so much for the quick response!

 

Can i update straight from my 6.3.1.8-4.0.0.7_44641 to the 4.1.1.0 release?

 

Thanks again for the help

Yes

So i updated the firmware to 6.4.2.0-4.1.1.0_46028 and went to plug in the iap205 but it still doesnt seem to be autoconfiguring and joining the cluster, there are 2 amber lights lit up for 2.5 and 5, i will keep looking around to see what could be the issue, and connect to it with a console cord when booting up, but if anyone has any ideas, it would be appreciated. i know the port is configured to the right vlan

IN the console did you see the IAP get an IP address ?

just thinking out loud, maybe i need to check the 205s firmware too

Both the 205's and 105's should be running the same version.

 

Also, check the sticker on the back of the IAPs and make sure the IAP-205 has the same country code as the 105's.  The sticker is a small white sticker that will say, for example, IAP-205-US.  If the country codes don't match this is expected behavior.  Also, make sure the 205 is an IAP and not a regular campus AP.

 

Lastly, do you have Auto-Join disabled on the existing cluster?

Thanks again guys for the help,

 

They all have the US country code, later today i will plug in a console cord and see whats going on a little better and get back to yall, 

 

Ill be sure that its an iap too, its what we ordered

APBoot 1.5.3.12 (build 45191)

Built: 2014-08-04 at 11:37:23

 

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.2.0-4.1.1.0 (build 45444 / label #45444)

[    0.000000] Built by p4build@cartman on 2014-08-15 at 21:51:21 PDT (gcc version 4.7.2)

[    0.000000]

[    0.000000] Flash variant: variant0

[    0.000000] Memory: 128MB = 128MB total

[    0.000000] Memory: 117892k/117892k available, 13180k reserved, 0K highmem

[    0.052000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

[    5.142000] PMU: registered new PMU device of type 0

[    5.648000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]

[    5.650000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]

[    5.652000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]

[    6.154000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]

[    6.156000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]

[    6.158000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]

[    6.504000] i2c-springbank: using remapped base c8904060

[    6.506000] mpcore_wdt mpcore_wdt: enabling watchdog.

[    6.510000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address

[    6.512000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)

[    6.514000] Creating 1 MTD partitions on "spi1.0":

[    6.516000] 0x000000000000-0x000002000000 : "qspi"

[    6.520000]

[    6.520000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT

[    6.524000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT

[    6.538000] Starting Kernel DES KAT ...Completed Kernel DES KAT

[    6.542000] Starting Kernel AES KAT ...Completed Kernel AES KAT

[    6.544000]

Domain Name: instant.arubanetworks.com

No panic info available

Check backup ENV.

Cfg len is 0

Configuration file is empty, turning on default services...

extended ssid activate due to no AP config ...

[   12.008000] ADDRCONF(NETDEV_UP): bond0: link is not ready

[   14.010000] bond0: link up (1000FD)

[   14.012000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready

Mesh is DISABLED on this device.

Disabling wpa_supplicant for this paltform

[   15.074000] AP xml model 81, num_radios 2 (jiffies 7537)

[   15.076000] init_asap_mod: installation:0

[   15.078000] radio 0: band 1 ant 0 max_ssid 16

[   15.080000] radio 1: band 0 ant 0 max_ssid 16

[   15.082000] election init: rand=10 HZ=500

[   15.084000] IAP client match init

notify asap_mod 3g no present...

Starting watchdog process...

Getting an IP address...

Dec 31 16:00:17 udhcpc[1354]: udhcpc (v0.9.9-pre) started

Dec 31 16:00:17 udhcpc[1354]: send_discover: pkt num 0, secs 0

Dec 31 16:00:17 udhcpc[1354]: Sending discover...

Dec 31 16:00:17 udhcpc[1354]: send_selecting: pkt num 0, secs 0

Dec 31 16:00:17 udhcpc[1354]: Sending select for 172.25.3.90...

Dec 31 16:00:17 udhcpc[1354]: Lease of 172.25.3.90 obtained, lease time 86400

Dec 31 16:00:17 udhcpc[1354]: DHCP OPT 43 deleted airwave config

 

172.25.3.90 255.255.255.0 172.25.3.1

Compressing all files in the /etc/httpd directory...

[   20.096000] ip_time_handler: Got ip and packets on bond0 Started master election 14-0, rand 15

[   20.936000] Adding bridge entry for magic vlan GW, ifindex 8450, 24:de:c6:cd:b5:f1

[   20.938000] (00:00:22) !!! Init ---> Slave

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

[   21.784000] wifi0: AP type AP-205, radio 0, max_bssids 16

[   21.828000] wifi1: AP type AP-205, radio 1, max_bssids 16

shutting down watchdog process (nanny will restart it)...

Completed SW FIPS KAT test

 

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

 

User: [   52.054000] asap_send_elected_master: sent successfully

[   52.070000] process `snmpd_sap' is using obsolete setsockopt SO_BSDCOMPAT

[   52.536000] wait for stm to initialize over

[   52.538000] asap_send_elected_master: sent successfully

[   57.076000] turn off mobility

[   57.392000] (00:00:59) !!! Init ---> Slave

connected

bind: Transport endpoint is not connected

Launching NTP Client on pool.ntp.org

System uptime is 126 seconds and CLI is not ready yet, please try again later.

 

 

Our cluster was being managed by an airwave server previously, but we have since powered down the server, would something like that be interfering with the iap joining the cluster?

#AP205

Hi

 

I have got the same issue with IAP105's and IAP204's.  Upgraded all units to the latest firmware 6.4 and checked country code and auojoin options.  All getting DHCP.

 

The 204's will not join the IAP105 cluster and boot as a master.

 

Puzzled....

 

Any help appreciated

 

Thanks

You might want to open a case with TAC for further debugging.

I believe the issue is due to the fact that your cluster was managed by AMP; the AMP configuration in the IAP will cause the IAP205 to want to pull the image from airwave but it cannot do it successfully.

I recommend upgrading Airwave to the latest 8.0 version which has official support for 4.1.1.0, and adding the 4.1.1.0_46028 firmware version for both the 105 (Orion) and the 205 (Taurus) into Airwave, and try to bring up the network again.

Thanks,

Yan Liu
Product Manager
Aruba Instant
US: +1 650 996-3520
China: +86 136 2121 6844

I have since blanked out the airwave fields in the virtual controller, ill keep looking around and troubleshooting

The firmware on the 205 was a different build, i updated it by itself  to the latest 6.4.2.0-4.1.1.0 46028 and it joined with the others immediatly

I also have this same exact problem.   I have a cluster of 10 W-IAP105's and just bought 5 new W-IAP205 to add to them.   the new ones do not see the cluster but i am able to find what IP address they're getting.    When i try to browse to that ip, it redirects back to the original cluster IP.      I updated the firmware of the cluster to the most current version availible through the automatic update button.  it's at 6.3.1.8-4.0.0.9_47220.   When i try to go on to https://support.arubanetworks.com/ to try to download the newest firmware, i have to register and supply my serial number.  now tech support replies back saying:

 

Access to the site is granted to existing Aruba customers, resellers or customers evaluating our products. From our database we find that you have purchased the switch from  Dell  Internetworking Inc. who are our partners. In order to gain access to our documentation or any related software you will have to get in touch with Dell  Internetworking regarding that as they would be able to help you out.

 

If you have further question, please feel free to contact Aruba Technical Support

 

 

WTH??  Just because i bought the device from Dell instead of Amazon or Tiger Direct or Newegg, etc they're not going to allow me access to the newest firmware?   Dell support site has NO DOWNLOADS whatsoever.     Now i'm stuck with 5 $600 devices that i cant add to our existing network?

 

 

 

tle2099,

 

Please send me a message with the ticket# and we will get you taken care of.

 

 

Almost the same issue.  I have 8 IAP running using firmware version 6.4.2.0-4.1.1.1_46936.  Purchased 5 new IAPs from CDW. The new IAPs are running version 6.4.2.0-4.1.1.0_46028.  Can not update the firmware on the new IAPs becauce I have standard care and not Arubacare???  Charging for a firmware update on a new product??

 

Windsor, the built in certificate for that so expired, not allowing it to update to the latest GA code.. Contact TAC and they should be able to help you.

windor are do you have the Dell branded arubas or the non dell branded ones?

Hi guys! I have the same problem.

 

I need add 3 IAP205 to a IAP105 cluster.

 

There are have the same version of firmware (ArubaInstant_Orion_6.4.2.6-4.1.1.10_51810, ArubaInstant_Taurus_6.4.2.6-4.1.1.10_51810) for 105 and 205 respectibily.

 

The 205 AP doesnt take DHCP address after a factory reset. If i set any option in the Instant SSID, then take IP but doesnt join to IAP105.

 

There is any way to help me to make this work?

 

Update:

All my IAP105 are US region, but my new IAP205 are RW. I read that must be same region. There is any way to convert a RW in US?

---

@sdedurana wrote:

Hi guys! I have the same problem.

 

I need add 3 IAP205 to a IAP105 cluster.

 

There are have the same version of firmware (ArubaInstant_Orion_6.4.2.6-4.1.1.10_51810, ArubaInstant_Taurus_6.4.2.6-4.1.1.10_51810) for 105 and 205 respectibily.

 

The 205 AP doesnt take DHCP address after a factory reset. If i set any option in the Instant SSID, then take IP but doesnt join to IAP105.

 

There is any way to help me to make this work?

 

Update:

All my IAP105 are US region, but my new IAP205 are RW. I read that must be same region. There is any way to convert a RW in US?

im not 100% sure on this, but if you reset a ROW AP can you select US as regulatory domain? if not, then you should look into changing the ROW ones for US ones, if you are in the US that is. your vendor probably made an error.

I think I have the same problem.. vendor sent -RW unit to add to my -US units.

I'm in Canada so I can understand why they wouldn't have expected me to have -US units.

 

Am I to return the -RW unit and order a -US unit? Or can the -RW unit be 'configure' to -US ? I've upgraded the firmware on my 105's to the same as the new one and still doesn't autojoin.

 

Appreciate any response or clarification.

Thanks.

You need to return it.  A RW Unit will not join a US unit, unfortunately.

The newest version isn't posted to the cloud update servers right away, so in cases like that you'll have to download it from support.arubanetworks.com and manually update.