Wireless Access

Reply
New Contributor

AP 105 keep getting down

Hi

We have about 10 AP105 in our school, and trying to fix  access issues.  One AP is running for a day then next morning its down.

At first we were powering the AP through POE (Nortel 4526T), but now they are mostly powered with PSU .

Then we checked the cable with a Fluke for noise.

We upgraded firmware, now  6.4.2.0-4.1.1.0_46028 on AP

our Airwave is AMP™ 8.0.5

 

it helped for other AP's problem but one AP keep going down.

Here is the log while this AP was down, through serial port:

----------------------------------------------------------------

User: admin
Password:
080-L252-AP06# NETDEV WATCHDOG: bond0: transmit timed out
ag7100_tx_timeout
ag7100_ring_free Freeing at 0x80394000
ag7100_ring_free Freeing at 0x83f43000
ag7100_ring_alloc Allocated 4800 at 0x80394000
ag7100_ring_alloc Allocated 3024 at 0x84021000
AG7100: cfg1 0xf cfg2 0x7114
ATHRF1: Port 0, Neg Success

ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100

AG7100: unit 0 phy is up...RGMii 100Mbps half 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: 0x27ffef
AG7100: done cfg2 0x7114 ifctl 0x10000 miictrl 0x12
Writing 4
NETDEV WATCHDOG: bond0: transmit timed out
ag7100_tx_timeout
ag7100_ring_free Freeing at 0x80394000
ag7100_ring_free Freeing at 0x84021000
ag7100_ring_alloc Allocated 4800 at 0x80394000
ag7100_ring_alloc Allocated 3024 at 0x84021000
AG7100: cfg1 0xf cfg2 0x7114
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100
AG7100: unit 0 phy is up...RGMii 100Mbps half 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: 0x27ffef
AG7100: done cfg2 0x7114 ifctl 0x10000 miictrl 0x12
Writing 4

 

-------------------------------------------------------------------

Then the log when rebooted :

 

Ethernet uplink not active yet
No uplink active. Becoming Mesh Point
AP xml model 39, num_radios 2 (jiffies 27507)
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=12 HZ=500
IAP client match init
notify asap_mod 3g no present...
Starting watchdog process...
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
Launching NTP Client on pool.ntp.org
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 Right
s 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 Reserve
d
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_attach: scn 86a40280 sc 86960000 ah 86a00000
wifi0: Base BSSID 24:de:c6:55:ee:18, 8 available BSSID(s)
bond0 address=24:de:c6:cd:5e:e1
br0 address=24:de:c6:cd:5e:e1
wifi0: AP type AP-105, radio 0, max_bssids 8
wifi0: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000
ath_attach: scn 85a60280 sc 85a80000 ah 85ac0000
wifi1: Base BSSID 24:de:c6:55:ee:10, 8 available BSSID(s)
bond0 address=24:de:c6:cd:5e:e1
br0 address=24:de:c6:cd:5e:e1
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 watchdog process (nanny will restart it)...
Completed SW FIPS KAT test
           <<<<<       Welcome to the Access Point     >>>>>
User: process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT

 

 

----------------------------------------------------------

 

Help would be appreciated

 

thank

New Contributor

Re: AP 105 keep getting down

Just a try, the switch port was not at autonegotiate, we just change that , maybe it will resolve the problem!!!

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