Wireless Access

Reply
Occasional Contributor I
Posts: 5
Registered: ‎04-19-2011

AP 175 is not pingable on local switch

What are the possible reasons that an AP 175 is not pingable at a local switch? The power and ethernet cable tested satisfactorily. The vlan and trunk ports are set correctly at the local switch. There are no errors on the switchport. The trunk is flapping due to non dot1q trunk. The portal AP 175 is constantly rebooting due to a non-certified antenna for the North American market.

Aruba Employee
Posts: 571
Registered: ‎04-17-2009

Re: AP 175 is not pingable on local switch

Is the switch providing PoE+ power or just regular PoE?
Thanks,

Zach Jennings
Guru Elite
Posts: 20,819
Registered: ‎03-29-2007

Re: AP 175 is not pingable on local switch


lacker6284 wrote:

What are the possible reasons that an AP 175 is not pingable at a local switch? The power and ethernet cable tested satisfactorily. The vlan and trunk ports are set correctly at the local switch. There are no errors on the switchport. The trunk is flapping due to non dot1q trunk. The portal AP 175 is constantly rebooting due to a non-certified antenna for the North American market.


How do you know what ip address it has, or if it even got an ip address?  Do you have the USB console cable to take a look?

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I
Posts: 5
Registered: ‎04-19-2011

Re: AP 175 is not pingable on local switch

The switch is PoE. The AP 175 was working a few weeks ago.

Occasional Contributor I
Posts: 5
Registered: ‎04-19-2011

Re: AP 175 is not pingable on local switch

The usb connection to the AP reveals the following below. Aruba TAC said that the the 5146 antenna was not certified for use in the North American market. The Territory Manager admitted quoting the 5146 antenna instead of the 5146U antenna. The antenna is constantly scanning for the channels. This AP 175 was working earlier. Since the AP 175 is no longer pingable from the switch, the controller cannot enforce a policy.

 

host 172.16.2.1 is alive
apboot> print
bootdelay=2
baudrate=9600
autoload=n
boardname=MSR2K
bootcmd=boot ap
autostart=yes
bootfile=mips32.ari
ethaddr=00:24:6c:cd:87:cb
ethact=eth0
masterip=10.0.10.21
server=10.0.10.21
name=UTA-SCST-Data-Point
group=uta-data
syslocation=UTA-SCST-Data-Point
master=10.0.10.21
netmask=255.255.255.0
dnsip=10.0.3.4
domainname=sandiego.edu
serverip=10.0.10.21
a_ant_gain=9ffb5d68dad36e1a090a6f7466ef3cce4468317470028x002
g_ant_gain=9ffb5d68dad36e1a090a6f7466ef3cce4468317470028x002
ap70_ext_ant=1
a_antenna=0
g_antenna=0
usb_type=0
auto_prov_id=0
is_rmp_enable=0
priority_ethernet=0
priority_cellular=0
cert_cap=0
mesh_role=1
installation=0
mesh_sae=0
ipaddr=172.16.2.249
gatewayip=172.16.2.1
num_ipsec_retry=360
stdin=serial
stdout=serial
stderr=serial

Environment size: 744/65532 bytes
apboot>

Unknown command '
                 ' - try 'help'
apboot>
apboot>
apboot>
apboot> cat /etc/resolv.conf
Unknown command 'cat' - try 'help'
apboot>
Timed out waiting for command
Resetting...

APBoot 1.2.2.16 (build 26085)
Built: 2010-11-15 at 10:47:17

Model: AP-175X
CPU:   AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM:  128 MB
POST1: 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:  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 (3304904 bytes)
Clearing .bss @ 0x81126dd0 (16 bytes)
Loading .data @ 0x81126de0 (32 bytes)
## Starting application at 0x80e00000 ...
Uncompressing..............................
þ
Aruba Networks
ArubaOS Version 5.0.3.0 (build 26207 / label #26207)
Built by p4build@cyprus on 2010-11-30 at 07:56:21 PST (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 (1639k kernel code, 7520k reserved, 716k data, 2584k init, 0k highmem)
 available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13638144
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

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: arubanetworks.com
No panic info available
<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: 00:24:6c:cd:87:cb
AG7100: cfg1 0xf cfg2 0x7014
VSC8601: Found 0  unit 0:0  phy_addr: 1  id: 02430d91
VSC8601: PHY is unknown, using generic IEEE interface
VSC8601: unit 0  phy_addr 1
AP xml model 47, num_radios 2 (jiffies 1906)
init_asap_mod: installation:0
radio 0: band 1 ant 1 max_ssid 8
radio 1: band 0 ant 1 max_ssid 8
asap_gre_init: ADDED GRE protocol c00a4e40
setting bond0 as bridge child
setting gre0 as split child
USB not provisioned
Starting watchdog process...
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)
Kernel watchdog refresh ended.
wifi0: Base BSSID 00:24:6c:58:7c:b8, 8 available BSSID(s)
edev->dev_addr=00:24:6c:cd:87:cb
edev->dev_addr=00:24:6c:cd:87:cb
wifi0: AP type AP-175P, radio 0, max_bssids 8
wifi0: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000
wifi1: Base BSSID 00:24:6c:58:7c:b0, 8 available BSSID(s)
edev->dev_addr=00:24:6c:cd:87:cb
edev->dev_addr=00:24:6c:cd:87:cb
wifi1: AP type AP-175P, radio 1, max_bssids 8
wifi1: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000
AP rebooted Fri Dec 31 16:11:32 PST 1999: Mesh link could not be sustained for 15 minutes.
shutting down watchdog process (nanny will restart it)...

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

~ # vap aruba001 vlan is 0. fwd-mode:0 mesh

~ #
~ #
~ #
~ #
~ # Switching to Full Access
~ # apfcutil -r mesh0 MESH
domain uta-data
mesh_rf_band a
mesh_opmode opensystem
mesh_wpa_hexkey
mesh_wpa_passphrase
priority 1
~ # apfcutil -r meshrecovery MESH
domain Recovery-VU-bqzQve-UNg/3
mesh_rf_band a
mesh_opmode wpa2-psk-aes
mesh_wpa_hexkey 1DEE11AC63F22FD27363E889439BBF09BB494E8B084CB8A2A0CF9021ADBB239F02FB739F28D94768EF16AA27209F0CACDF9237863E727F8CE1F975E96184CCF81FED1246F5E0C5979F416C1401FA659229ABC918EAC65DCB
mesh_wpa_passphrase
priority 16
~ # apfcutil -r meshcc MESH
0
United States
~ # cat /tmp/mesh_role
1~ # cat /tmp/meshd_debug_log
[222]1999-12-31 16:01:03.040 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:03.040 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:03.040 meshd_scan_complete: num_scans 13, disconnected-time: 47 (secs)
[222]1999-12-31 16:01:04.026 meshd_timer_handler: rescan started, assoc 0, scan_active 0
[222]1999-12-31 16:01:04.059 meshd_scan_init: getApChanList() gave 9 chans, mcc:0, ccode:20, cname:"US" band:1
[222]1999-12-31 16:01:04.059 meshd_scan_all_channels: num_scan_channels: 9, scan_ch_index: 7, start-tick: 52. Scanning...
[222]1999-12-31 16:01:05.568 meshd_scan_timer_handler: not scanning as channel 36 is indoor
[222]1999-12-31 16:01:05.568 meshd_scan_timer_handler: not scanning as channel 40 is indoor
[222]1999-12-31 16:01:05.568 meshd_scan_timer_handler: not scanning as channel 44 is indoor
[222]1999-12-31 16:01:05.568 meshd_scan_timer_handler: not scanning as channel 48 is indoor
[222]1999-12-31 16:01:07.080 scan-summary: 36:n 40:n 44:n 48:n 149:s 153:s 157:s 161:3 165:s
                                Key: n:not-set,i:invalid,s:set,<number>:probe-resp-cnt.
[222]1999-12-31 16:01:07.080 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:07.080 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:07.080 meshd_scan_complete: num_scans 14, disconnected-time: 51 (secs)
[222]1999-12-31 16:01:08.066 meshd_timer_handler: rescan started, assoc 0, scan_active 0
[222]1999-12-31 16:01:08.105 meshd_scan_init: getApChanList() gave 9 chans, mcc:0, ccode:20, cname:"US" band:1
[222]1999-12-31 16:01:08.105 meshd_scan_all_channels: num_scan_channels: 9, scan_ch_index: 4, start-tick: 56. Scanning...
[222]1999-12-31 16:01:11.126 meshd_scan_timer_handler: not scanning as channel 36 is indoor
[222]1999-12-31 16:01:11.126 meshd_scan_timer_handler: not scanning as channel 40 is indoor
[222]1999-12-31 16:01:11.126 meshd_scan_timer_handler: not scanning as channel 44 is indoor
[222]1999-12-31 16:01:11.126 meshd_scan_timer_handler: not scanning as channel 48 is indoor
[222]1999-12-31 16:01:11.126 scan-summary: 36:n 40:n 44:n 48:n 149:s 153:s 157:s 161:3 165:s
                                Key: n:not-set,i:invalid,s:set,<number>:probe-resp-cnt.
[222]1999-12-31 16:01:11.126 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:11.126 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:11.126 meshd_scan_complete: num_scans 15, disconnected-time: 55 (secs)
[222]1999-12-31 16:01:12.110 meshd_timer_handler: rescan started, assoc 0, scan_active 0
[222]1999-12-31 16:01:12.155 meshd_scan_init: getApChanList() gave 9 chans, mcc:0, ccode:20, cname:"US" band:1
[222]1999-12-31 16:01:12.155 meshd_scan_all_channels: num_scan_channels: 9, scan_ch_index: 3, start-tick: 60. Scanning...
[222]1999-12-31 16:01:12.656 meshd_scan_timer_handler: not scanning as channel 48 is indoor
[222]1999-12-31 16:01:15.176 meshd_scan_timer_handler: not scanning as channel 36 is indoor
[222]1999-12-31 16:01:15.176 meshd_scan_timer_handler: not scanning as channel 40 is indoor
[222]1999-12-31 16:01:15.177 meshd_scan_timer_handler: not scanning as channel 44 is indoor
[222]1999-12-31 16:01:15.177 scan-summary: 36:n 40:n 44:n 48:n 149:s 153:s 157:s 161:3 165:s
                                Key: n:not-set,i:invalid,s:set,<number>:probe-resp-cnt.
[222]1999-12-31 16:01:15.177 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:15.177 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:15.177 meshd_scan_complete: num_scans 16, disconnected-time: 59 (secs)
[222]1999-12-31 16:01:16.158 meshd_timer_handler: rescan started, assoc 0, scan_active 0
[222]1999-12-31 16:01:16.195 meshd_scan_init: getApChanList() gave 9 chans, mcc:0, ccode:20, cname:"US" band:1
[222]1999-12-31 16:01:16.195 meshd_scan_all_channels: num_scan_channels: 9, scan_ch_index: 1, start-tick: 64. Scanning...
[222]1999-12-31 16:01:16.696 meshd_scan_timer_handler: not scanning as channel 40 is indoor
[222]1999-12-31 16:01:16.696 meshd_scan_timer_handler: not scanning as channel 44 is indoor
[222]1999-12-31 16:01:16.696 meshd_scan_timer_handler: not scanning as channel 48 is indoor
[222]1999-12-31 16:01:19.214 meshd_scan_timer_handler: not scanning as channel 36 is indoor
[222]1999-12-31 16:01:19.214 scan-summary: 36:n 40:n 44:n 48:n 149:s 153:s 157:s 161:2 165:s
                                Key: n:not-set,i:invalid,s:set,<number>:probe-resp-cnt.
[222]1999-12-31 16:01:19.214 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:19.214 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:19.214 meshd_scan_complete: num_scans 17, disconnected-time: 63 (secs)
[222]1999-12-31 16:01:20.200 meshd_timer_handler: rescan started, assoc 0, scan_active 0
[222]1999-12-31 16:01:20.237 meshd_scan_init: getApChanList() gave 9 chans, mcc:0, ccode:20, cname:"US" band:1
[222]1999-12-31 16:01:20.238 meshd_scan_all_channels: num_scan_channels: 9, scan_ch_index: 2, start-tick: 68. Scanning...
[222]1999-12-31 16:01:20.740 meshd_scan_timer_handler: not scanning as channel 44 is indoor
[222]1999-12-31 16:01:20.740 meshd_scan_timer_handler: not scanning as channel 48 is indoor
[222]1999-12-31 16:01:23.262 meshd_scan_timer_handler: not scanning as channel 36 is indoor
[222]1999-12-31 16:01:23.262 meshd_scan_timer_handler: not scanning as channel 40 is indoor
[222]1999-12-31 16:01:23.262 scan-summary: 36:n 40:n 44:n 48:n 149:s 153:s 157:s 161:3 165:s
                                Key: n:not-set,i:invalid,s:set,<number>:probe-resp-cnt.
[222]1999-12-31 16:01:23.262 meshd_scan_complete: recovery: FALSE
[222]1999-12-31 16:01:23.262 meshd_scan_complete: No candidate neighbors found in all the 1 profiles
[222]1999-12-31 16:01:23.262 meshd_scan_complete: num_scans 18, disconnected-time: 67 (secs)
~ #

Aruba Employee
Posts: 571
Registered: ‎04-17-2009

Re: AP 175 is not pingable on local switch

It doesn't look like it is getting an IP address.

 

From the apboot prompt, try running the command: dhcp

 

If it gets an IP address, then try pinging the gateway using the ping command.

 

My guess is that the dhcp command will not work. That is why it is trying to go into full mesh mode, since it cannot obtain an IP address.

Thanks,

Zach Jennings
Occasional Contributor I
Posts: 5
Registered: ‎04-19-2011

Re: AP 175 is not pingable on local switch

I stand corrected. The AP175P is POE+.

Aruba Employee
Posts: 571
Registered: ‎04-17-2009

Re: AP 175 is not pingable on local switch

Excellent. That is the preferred method. Supposedly they are supposed to work on just regular PoE. However, at least when they were first released, mine sat in a reboot cycle on just PoE. On PoE+ it worked just fine.

Thanks,

Zach Jennings
Search Airheads
Showing results for 
Search instead for 
Did you mean: