Access Points

Reply
Occasional Contributor II

AP not appear on controller

I'm very fresh with aruba I have 650 controller and 125 ap
I had config IP address for controller and DHCP pool for AP but after I connected AP125 direct to port gi1/2 on controller I'm not found AP for provision and text from AP console below.


Domain Name: arubanetworks.com
No panic info available
Ethernet port 1 mode: active-standby<6>Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

bonding: bond0: enslaving eth0 as a backup interface with a down link.
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 24, num_radios 2 (jiffies 2292)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
ethernet_device_event: dev eth0 is register
ethernet_device_event: dev eth0 is up
asap_gre_init: ADDED GRE protocol c0000000001deba0
setting bond0 as bridge child
setting gre0 as split child
USB not provisioned
Starting watchdog process...
Getting an IP address...
Kernel watchdog refresh ended.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
10.1.10.254 255.255.255.0 10.1.10.2
Running ADP...Done. Master is 172.16.0.254
ath_hal: module license 'Proprietary' taints kernel.
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:b0:1b:10, 16 available BSSID(s)
edev->dev_addr=d8:c7:c8:c3:01:b0
edev->dev_addr=d8:c7:c8:c3:01:b0
wifi0: AP type AP-125, radio 0, max_bssids 16
wifi0: Atheros 9160: mem=0x11b00f0000000, irq=44 hw_base=0x90011b00f0000000
wifi1: Base BSSID d8:c7:c8:b0:1b:00, 16 available BSSID(s)
edev->dev_addr=d8:c7:c8:c3:01:b0
edev->dev_addr=d8:c7:c8:c3:01:b0
wifi1: AP type AP-125, radio 1, max_bssids 16
wifi1: Atheros 9160: mem=0x11b00f0010000, irq=45 hw_base=0x90011b00f0010000
shutting down watchdog process (nanny will restart it)...
<<<<< Welcome to the Access Point >>>>>

~ # Kernel watchdog refresh ended



Please help me by suggest way to solve it

regards,
Chaiyapruk
Guru Elite

Re: AP not appear on controller

You need to change the controller-ip from 172.16.0.254 to the ip address of the controller on 10.1.10.x

Running ADP...Done. Master is 172.16.0.254

Change it like this:

config t
controller-ip vlan

No matter how an AP discovers a controller, it is redirected to that controller-ip parameter, so if it is unreachable, like in your case, the access point will end up in limbo trying to find a non-routable address

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Occasional Contributor II

Re: AP not appear on controller

after change IP ap still not appear

Starting HW AES KAT ...Completed HW AES KAT

Domain Name: arubanetworks.com
No panic info available
Ethernet port 1 mode: active-standby<6>Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

bonding: bond0: enslaving eth0 as a backup interface with a down link.
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 24, num_radios 2 (jiffies 2292)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
ethernet_device_event: dev eth0 is register
ethernet_device_event: dev eth0 is up
asap_gre_init: ADDED GRE protocol c0000000001deba0
setting bond0 as bridge child
setting gre0 as split child
USB not provisioned
Starting watchdog process...
Getting an IP address...
Kernel watchdog refresh ended.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
10.1.10.254 255.255.255.0 10.1.10.2
Running ADP...Done. Master is 10.1.10.2
ath_hal: module license 'Proprietary' taints kernel.
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:b0:1b:10, 16 available BSSID(s)
edev->dev_addr=d8:c7:c8:c3:01:b0
edev->dev_addr=d8:c7:c8:c3:01:b0
wifi0: AP type AP-125, radio 0, max_bssids 16
wifi0: Atheros 9160: mem=0x11b00f0000000, irq=44 hw_base=0x90011b00f0000000
wifi1: Base BSSID d8:c7:c8:b0:1b:00, 16 available BSSID(s)
edev->dev_addr=d8:c7:c8:c3:01:b0
edev->dev_addr=d8:c7:c8:c3:01:b0
wifi1: AP type AP-125, radio 1, max_bssids 16
wifi1: Atheros 9160: mem=0x11b00f0010000, irq=45 hw_base=0x90011b00f0010000
shutting down watchdog process (nanny will restart it)...

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

~ # Kernel watchdog refresh ended.
Guru Elite

Re: AP not appear on controller

Please post the output of "show ap database long"

When you can, please take a look at the video about setting up an Aruba Controller here: http://www.arubanetworks.com/training/controller_setup_video.html

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Occasional Contributor II

Re: AP not appear on controller

(Aruba650) #show ap database long

AP Database
-----------
Name Group AP Type IP Address Status Flags Switch IP Wired MAC Address Serial # Slot/Port FQLN Outer IP User
---- ----- ------- ---------- ------ ----- --------- ----------------- -------- --------- ---- -------- ----

Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
I = Inactive; H = Using 802.11n license
X = Maintenance Mode; P = PPPoE AP; B = Built-in AP
R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP; c = CERT-based RAP
M = Mesh node; Y = Mesh Recovery

Total APs:0

(Aruba650) #
Guru Elite

Re: AP not appear on controller

Okay. Type "show datapath session table 10.1.10.254" and run it for a few times. That will tell you if the access point is indeed contacting the controller. Also send the output of "show log system 50"

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Occasional Contributor II

Re: AP not appear on controller

(Aruba650) #show datapath session table 10.1.10.254

Datapath Session Table Entries
------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT
D - deny, R - redirect, Y - no syn
H - high prio, P - set prio, T - set ToS
C - client, M - mirror, V - VOIP
I - Deep inspect, U - Locally destined

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Flags
-------------- -------------- ---- ----- ----- ---- ---- --- --- ----------- ---- -----

(Aruba650) #show log system 50

Apr 20 09:51:05 KERNEL: 0:<6>: Found BCM59103 on Grenache I2C_0
Apr 20 09:51:05 KERNEL: 0:<6>: Found BCM59103 on Grenache I2C_1
Apr 20 09:51:05 KERNEL: 0:<6>802.1Q VLAN Support v1.8 Ben Greear
Apr 20 09:51:05 KERNEL: 0:<6>All bugs added by David S. Miller
Apr 20 09:51:05 KERNEL: 0: ^H2:flushing more than page size of icache addresses starting @ c00c1000
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/usb-serial.c: USB Serial Driver core
Apr 20 09:51:05 KERNEL: 2:flushing more than page size of icache addresses starting @ c00b9000
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
Apr 20 09:51:05 KERNEL: 2:flushing more than page size of icache addresses starting @ c00b5000
Apr 20 09:51:05 KERNEL: 2:<4>sierra: Ignoring new-style parameters in presence of obsolete ones
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem
Apr 20 09:51:05 KERNEL: 2:<6>drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.2.7
Apr 20 09:51:05 KERNEL: 2:flushing more than page size of icache addresses starting @ c00d9000
Apr 20 09:51:05 KERNEL: 2:<4>hso: Ignoring new-style parameters in presence of obsolete ones
Apr 20 09:51:05 KERNEL: hso.c: 1.2 Option Wireless
Apr 20 09:51:05 KERNEL: 2:<6>hso: Registering procfs
Apr 20 09:51:05 KERNEL: 2:<4>process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 09:51:05 KERNEL: 0:<4>process `soed' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 09:51:07 :314800: |fpapps| NVRAM checksum error detected
Apr 20 09:51:07 :399816: |fpapps| poe download start
Apr 20 09:51:51 :313078: |fpapps| XSec Vlan Interface 10 not found line 877
Apr 20 09:51:51 :313078: |fpapps| XSec Vlan Interface 10 not found line 877
Apr 20 09:51:51 :313256: |fpapps| Route resolve returned an Error
Apr 20 09:51:54 :306510: |publisher| Dropping message from 8214 for service 'aaa-idle-user-timeout (service not found)'
Apr 20 09:51:58 KERNEL: 1:<4>process `snmpd' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 09:52:01 KERNEL: 2:<4>process `trapd' is using obsolete setsockopt SO_BSDCOMPAT
Apr 20 09:52:03 :325022: |authmgr| Bogus VLAN ID:4095 received.
Apr 20 09:52:14 :304001: |stm| Unexpected stm (Station managment) runtime error at data_path_handler, 649, data_path_handler: recv - Network is down
Apr 20 09:53:00 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 09:58:21 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:11 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 09:59:59 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: No reboot message found.
Apr 20 10:05:20 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:10 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:12:58 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:18:21 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:23:44 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:29:07 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:34:30 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:39:53 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:45:16 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:50:40 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 10:56:03 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:01:26 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:06:49 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:12:12 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:17:35 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:22:58 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:28:21 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Apr 20 11:33:44 :303022: |AP d8:c7:c8:c3:01:b0@10.1.10.254 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:13 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Guru Elite

Re: AP not appear on controller

Reboot the controller so that the change in controller-ip can take effect.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: