Wireless Access

Today I opened the new AP-105 box which was shipped 2 weeks ago. If firmware is loaded, it must be matching to the OS 6.1 code.

I experienced static IP setting (setenv ipaddr) was not accepted by new AP.

After the AP picked up DHCP IP, default gateway and connected to master controller (resolved host name aruba-master),

code upgrade (I think downgrade) occured. After the code downgrade, the AP is now capable for static IP setting.

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  ======> I set static IP address here
apboot> setenv delayboot 5
apboot> setenv ipaddr 172.200.250.11
apboot> setenv netmask 255.255.255.0
apboot> setenv gatewayo ip 172.200.250.1
apboot> setenv master 172.200.10  1.208
apboot> setenv servername aruba-master-sidc
apboot> save
Saving Environment to Flash...
Un-Protected 1 sectors
.done
Erased 1 sectors
Writing
apboot> printenv
bootdelay=2
baudrate=9600
autoload=n
boardname=Talisker
bootcmd=boot ap
autostart=yes
bootfile=mips32.ari
ethaddr=d8:c7:c8:ce:3c:30
stdin=serial
stdout=serial
stderr=serial
ethact=eth0
delayboot=5
ipaddr=172.200.250.11
netmask=255.255.255.0
gatewayip=172.200.250.1
master=172.200.1.208
servername=aruba-master-sidc

Environment size: 312/65532 bytes
apboot> reset

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
Checking image @ 0xbf100000

Image is signed; verifying checksum... failed! 0xc0890e85
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 100 Mb/s full duplex
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3

Retry count exceeded
eth0 up: 100 Mb/s full duplex
ADP broadcast 3
ADP multicast 4
ADP broadcast 4
ADP multicast 5
ADP broadcast 5

Retry count exceeded
eth0 up: 100 Mb/s full duplex
ADP multicast 6
ADP broadcast 6
ADP multicast 7
ADP broadcast 7
ADP multicast 8   ======> But static IP did not work.

I purged saved reset, then AP picked up DHCP ip address, then rebooted itself to upgrade the code.

apboot> purge
Un-Protected 1 sectors
.done
Erased 1 sectors
Writing
apboot> save
Saving Environment to Flash...
Un-Protected 1 sectors
.done
Erased 1 sectors
Writing
apboot> reset

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
Checking image @ 0xbf100000

Image is signed; verifying checksum... failed! 0xc0890e85
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 100 Mb/s full duplex
DHCP broadcast 1
DHCP IP address: 172.200.250.103
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 172.200.250.1
DHCP DNS server: 172.200.201.20
DHCP DNS domain: test.local
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3

Retry count exceeded
DNS request 1 for aruba-master.test.local to 172.200.201.20
T Using eth0 device
TFTP from server 172.200.1.208; our IP address is 172.200.250.103; sending through gateway 172.200.250.1
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: *################T ###T #################T ################
done
Bytes transferred = 3391196 (33bedc hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x02000000 ...
ELF file is 32 bit
Loading .text @ 0x80e00000 (3322328 bytes)
Clearing .bss @ 0x8112b1e0 (16 bytes)
Loading .data @ 0x8112b1f0 (32 bytes)
## Starting application at 0x80e00000 ...
Uncompressing..............................

Aruba Networks
ArubaOS Version 5.0.4.6 (build 33270 / label #33270)
Built by p4build@corsica on 2012-04-13 at 06:47:14 PDT (gcc version 3.4.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: 123392k/131072k available (1640k kernel code, 7540k reserved, 720k data, 2600k init, 0k highmem)
 available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13807616
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
.
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: aru banetworks.com
No panic info available
Testing TPM... Passed
<4>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: d8:c7:c8:ce:3c:30
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0
AP xml model 39, num_radios 2 (jiffies 3467)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 8
radio 1: band 0 ant 0 max_ssid 8
asap_gre_init: ADDED GRE protocol c00a5d60
setting bond0 as bridge child
setting gre0 as split child
USB not provisioned
Starting watchdog process...
Getting an IP address...
ag7100_ring_alloc Allocated 4800 at 0x80592000
ag7100_ring_alloc Allocated 3024 at 0x8079f000
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
Kernel watchdog refresh ended.
AG7100: unit 0 phy is up...RGMii 100Mbps full duplex
AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
AG7100: cfg_2: 0x3ff
AG7100: cfg_3: 0x18001ff
AG7100: cfg_4: 0xffff
AG7100: cfg_5: 0x7ffef
AG7100: done cfg2 0x7115 ifctl 0x10000 miictrl 0x12
172.200.250.103 255.255.255.0 172.200.250.1
Running ADP...Done. Master is 172.200.1.208
ath_hal: 0.9.17.1 (AR5416, 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_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
wifi0: Base BSSID d8:c7:c8:63:c3:08, 8 available BSSID(s)
edev->dev_addr=d8:c7:c8:ce:3c:30
edev->dev_addr=d8:c7:c8:ce:3c:30
wifi0: AP type AP-105, radio 0, max_bssids 8
wifi0: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000
wifi1: Base BSSID d8:c7:c8:63:c3:00, 8 available BSSID(s)
edev->dev_addr=d8:c7:c8:ce:3c:30
edev->dev_addr=d8:c7:c8:ce:3c:30
wifi1: AP type AP-105, radio 1, max_bssids 8
wifi1: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000
shutting down watchdog process (nanny will restart it)...
 
 <<<<<       Welcome to the Access Point     >>>>>
 
~ #

(Continued from the previous post)

Then AP rebooted to upgrade (downgrade) the code.

OS of the controller is 5.0.4.6

~ # The system is going down NOW !!
Sending SIGTERM to all processes.
Please stand by while rebooting the system.
Restarting system.
.

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
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 (3322328 bytes)
Clearing .bss @ 0x8112b1e0 (16 bytes)
Loading .data @ 0x8112b1f0 (32 bytes)
## Starting application at 0x80e00000 ...
Uncompressing..............................

Aruba Networks
ArubaOS Version 5.0.4.6 (build 33270 / label #33270)
Built by p4build@corsica on 2012-04-13 at 06:47:14 PDT (gcc version 3.4.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: 123392k/131072k available (1640k kernel code, 7540k reserved, 720k data, 2600k init, 0k highmem)
 available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13807616
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
.
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: aru banetworks.com
No panic info available
Testing TPM... Passed
<4>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: d8:c7:c8:ce:3c:30
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0
AP xml model 39, num_radios 2 (jiffies 3467)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 8
radio 1: band 0 ant 0 max_ssid 8
asap_gre_init: ADDED GRE protocol c00a5d60
setting bond0 as bridge child
setting gre0 as split child
USB not provisioned
Starting watchdog process...
Getting an IP address...
ag7100_ring_alloc Allocated 4800 at 0x80592000
ag7100_ring_alloc Allocated 3024 at 0x8079f000
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
Kernel watchdog refresh ended.
AG7100: unit 0 phy is up...RGMii 100Mbps full duplex
AG7100: pll reg 0x18050010: 0x1099  AG7100: cfg_1: 0x1ff0000
AG7100: cfg_2: 0x3ff
AG7100: cfg_3: 0x18001ff
AG7100: cfg_4: 0xffff
AG7100: cfg_5: 0x7ffef
AG7100: done cfg2 0x7115 ifctl 0x10000 miictrl 0x12
172.200.250.103 255.255.255.0 172.200.250.1
Running ADP...Done. Master is 172.200.1.208
ath_hal: 0.9.17.1 (AR5416, 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_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
wifi0: Base BSSID d8:c7:c8:63:c3:08, 8 available BSSID(s)
edev->dev_addr=d8:c7:c8:ce:3c:30
edev->dev_addr=d8:c7:c8:ce:3c:30
wifi0: AP type AP-105, radio 0, max_bssids 8
wifi0: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000
wifi1: Base BSSID d8:c7:c8:63:c3:00, 8 available BSSID(s)
edev->dev_addr=d8:c7:c8:ce:3c:30
edev->dev_addr=d8:c7:c8:ce:3c:30
wifi1: AP type AP-105, radio 1, max_bssids 8
wifi1: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000
AP rebooted Wed May 16 14:32:10 EST 2012: SAPD: Reboot after image upgrade   ====> It says reboot after image upgrade.
shutting down watchdog process (nanny will restart it)...
 
 <<<<<       Welcome to the Access Point     >>>>>
 
~ #

After this, I can set static IP (setenv ipaddr).

I am not sure if latest AP code does not allow static IP setting ...

Also, I have found that bootdelay (default 2 seconds) can be changed , and servername (host name of the master controller) can be changed by setenv. Is this right things to do?

Purge and then save wipes everything out.

What are you trying to accomplish?  Boot the access point to the controller and set the static ip address in Configuration> Wireless> AP Installation. 

Static ip parameters, believe it or not, were not meant to be set on the console.

Hi cjoseph,

Yes, we can set static ip address / netmask / default gateway in AP Installation - Provision.

Our final goal is to send pre-configured AP-105 to branch offices.

Do you think - assigning static IP address through serial console is informal? 

When I read Aruba documents, they always say that for initial AP deployment, IP should be obtained by DHCP then set static ip from Provision.

But I know other document (Old Polycom setup manual for Aruba) introduces setting static IP using serial interface.

Do you need static ip addresses for APs?  Is there No DHCP at those offices?

Hi cjoseph,

What we are planning here is remote branch office deployment.

The reason why we need static ip is because we can manage APs easily by IP addresses.

We set static IP addresses and AP names , etc on each AP, then send them to remote branch offices for installation.

The controller keeps a record of each ip address that an access points has, so you don't have to.  Trying to manage the ip address of each AP statically is alot of administrative overhead.

Just configure a discovery method, use DHCP and the controller will take care of the rest

Could really use an answer for this???I need to assign static ip addresses to AP-105 for remote office deployment ( 1 per office, no controller)

Seriously, how the heck would someone thing using DHCP only would be the way to go? Someone actually believes this is manageable by looking up the dhcp assignment for each location????

I want to assign the same address, just changing the 3rd octet for each location, duh, and manage them by ip address.

---

@stephenlisle wrote:

Could really use an answer for this???I need to assign static ip addresses to AP-105 for remote office deployment ( 1 per office, no controller)

 

Seriously, how the heck would someone thing using DHCP only would be the way to go? Someone actually believes this is manageable by looking up the dhcp assignment for each location????

I want to assign the same address, just changing the 3rd octet for each location, duh, and manage them by ip address.

---

Stephenlisle,

The original question was that the AP-105 did not accept static ip address entries.  It should accept those static entries and if it does not, it is a bug and TAC should be contacted.  A follow up question discussed the strategy of using DHCP vs. Static.  Users are well within their rights to use whatever method they feel to accomplish their goals.  There are systems that have thousands of access points that exclusively use DHCP and they function as intended.  The system is designed to support either DHCP or the static approach based on administrator preference.