Wireless Access

Reply
New Contributor

AP-207 not listed in virtual controller

Hallo,

 

we have some aruba AP-207 and IAP-207-RW. There are no problems with the IAPs, which are all working fine. But we are not able to connect the AP-207 APs with the virtual controller. To configure them we are using a control cable and the settings (command: printenv) are equal to the IPA-207, also they have the same firmware 6.5.1.0-4.3.1.2. The AP-207 is pingable in the wireless network and i can even connect with the webinterface but for any reason the default username/password (admin/admin) doesn't work. Also reseting the device (command purgeenv) doesn't help.

 

Best regards

Contributor I

Re: AP-207 not listed in virtual controller

Hi,

 

I think you have only IAP-207 and not an AP-207. Are the country codes the same? All the AP's needs the same country code. 

 

http://community.arubanetworks.com/t5/Controller-less-WLANs/What-are-requirements-to-form-Instant-AP-cluster-with-mixed-IAP/ta-p/178020

 

If the country code is the same. Please take a look in the logs add the VC > show log system 50. If the AP is rejected you will see it in the logs.

 

Regards,

 

Willem Bargeman
ACMX#935 | ACCX #822
New Contributor

Re: AP-207 not listed in virtual controller

Hallo,

thanks for your answer. The Countrycodes on the packaging are all ROW. But I guess I need to have a chat with our supplier cause the SN, MAC, etc. are different (packaging label and device label). I think we need to workout a solution with the supplier, that we received the APs we ordered. We hoped that we can use the AP-207 after configure them with the console cable but it looks like it won't be working in this combination.

 

Best regards

Aruba Employee

Re: AP-207 not listed in virtual controller

You cannot convert an AP-207 to an IAP-207. The other way round will work.

You have to talk to your Distributer to get an Instant AP instead.

Occasional Contributor II

Re: AP-207 not able to configure

Dear Team,

 

we have AP 207 device and not able to login through UI interface. i have tried with APboot and configured the ENET0 port.

 

APBoot 2.1.1.4 (build 56212)
Built: 2016-08-23 at 16:43:42

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
Checking image @ 0x0
Invalid image format version: 0x0
Checking image @ 0x2000000
Copying image from 0x04100000

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.5.1.0-wave2mesh (build 55258 / label #55258)
[ 0.000000] Built by p4build@lemnos on 2016-05-30 at 22:26:54 PDT (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: 247136k/247136k available, 15008k reserved, 0K highmem
[ 0.000000] External imprecise Data abort at addr=0x72584, fsr=0xc06 ignored.
[ 0.000000] Found ST compatible serial flash with 64 64KB blocks; total size 4MB
[ 0.000000] MPCORE Global Timer Clock 34602Hz
[ 0.044000] khelper used greatest stack depth: 7024 bytes left
[ 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
[ 0.052000] khelper used greatest stack depth: 6984 bytes left
[ 0.054000] khelper used greatest stack depth: 6688 bytes left
[ 6.256000] PCI: no core
[ 6.256000] PCI: no core
[ 6.458000] PCI: scanning bus 0
[ 6.460000] PCI: Fixing up bus 0
[ 6.714000] PCIE1 link=1
[ 6.714000] PCIE1 switching to GEN2
[ 6.964000] PCIE1 link=1
[ 6.964000] PCI: Fixing up bus 0
[ 6.964000] PCI: Fixing up bus 1
[ 6.964000] pci 0001:00:00.0: BAR 8: assigned [mem 0x10000000-0x105fffff]
[ 6.964000] pci 0001:01:00.0: BAR 2: assigned [mem 0x10000000-0x103fffff 64bit]
[ 6.964000] pci 0001:01:00.0: BAR 2: set to [mem 0x10000000-0x103fffff 64bit] (PCI address [0x10000000-0x103fffff]
[ 6.964000] pci 0001:01:00.0: BAR 0: assigned [mem 0x10400000-0x10407fff 64bit]
[ 6.964000] pci 0001:01:00.0: BAR 0: set to [mem 0x10400000-0x10407fff 64bit] (PCI address [0x10400000-0x10407fff]
[ 7.024000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 7.026000] cryptomgr_test used greatest stack depth: 6552 bytes left
[ 7.026000] cryptomgr_test used greatest stack depth: 6508 bytes left
[ 7.026000] cryptomgr_test used greatest stack depth: 5768 bytes left
[ 7.028000] cryptomgr_test used greatest stack depth: 5464 bytes left
[ 7.136000] Creating 1 MTD partitions on "bcmsflash":
[ 7.138000] 0x000000000000-0x000000400000 : "nor"
[ 7.140000] Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
[ 7.142000] NAND device: Manufacturer ID: 0xc2, Chip ID: 0xf1 (MXIC NAND 128MiB 3,3V 8-bit)
[ 7.144000] Scanning device for bad blocks
[ 7.594000] Creating 3 MTD partitions on "brcmnand":
[ 7.596000] 0x000000000000-0x000002000000 : "aos0"
[ 7.598000] 0x000002000000-0x000004000000 : "aos1"
[ 7.600000] 0x000004000000-0x000008000000 : "ubifs"
[ 8.970000] i2c-springbank: using remapped base d09d0060
[ 8.972000] mpcore_wdt mpcore_wdt: enabling watchdog.
[ 9.094000]
[ 9.094000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 9.098000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[ 9.184000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 9.188000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 9.190000]
[ 9.192000] Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT
AP-type has_ble_support: .
Domain Name: arubanetworks.com
No panic info available
[ 21.928000] chipid ERROR: UNKNOWN Device ID (0x43c8)
[ 33.230000] chipid ERROR: UNKNOWN Device ID (0x43c8)
[ 33.346000] chipid ERROR: UNKNOWN Device ID (0xaa31)
[ 34.776000] AP xml model 96, num_radios 2 (jiffies 17388)
[ 34.778000] init_asap_mod: installation:0
[ 34.780000] radio 0: band 1 ant 0 max_ssid 16
[ 34.782000] radio 1: band 0 ant 0 max_ssid 16
springbank: Copying BT modules to /tmp
Starting watchdog process...
[ 39.646000] Temporary disable the external watchdog for AP-207 P3 board
Got all network params from APboot env. Skipping DHCP
[ 40.360000] ADDRCONF(NETDEV_UP): bond0: link is not ready
192.168.0.100 255.255.255.0 192.168.0.1
[ 42.364000] bond0: link up (1000FD)
[ 42.366000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Running ADP...

 

Help me how to solve the issue.kindly need your help.

 

Regards,

jose jesuratnam

 

Re: AP-207 not able to configure

The AP is running ArubaOS Version 6.5.1.0 so it will not have a GUI you can log in to. If this is an IAP and running InstantOS then the (I)AP will have a GUI you can log in to.


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Occasional Contributor II

Re: AP-207 not able to configure

Thank you sir.

Can you please guide how to configure it.
Is AP207 has to be configured from master controller?

We have a master controller : 7205.

Please guide.

Regards,
Jose

Re: AP-207 not able to configure

Occasional Contributor II

Re: AP-207 not able to configure

Thank you sir for the quick responce. i will update the status

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: