Wireless Access

Reply
Highlighted
Contributor II

AP won´t show at controller

Hey,

i have the following problem:

 

I have an 345 which wants correctly connect to our MM.

 

set device anul0 mtu to 2000
Starting watchdog process...
Aruba watchdog daemon started [1 thread(s)]
LLDP not sent yet, DHCP is waiting
Starting DHCP
net.ipv4.conf.all.arp_notify = 1
Getting an IP address...
[   28.001000] device eth0 entered promiscuous mode
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.br0.arp_notify = 1
x.x.x.x 255.255.252.0 x.x.x.x
Running ADP...Done. Master is x.x.x.x
[   43.720909] wl 0000:01:00.0: enabling device (0000 -> 0002)
[   43.823111] wifi0: AP type AP-345, radio 0, max_bssids 16
[   44.174786] usbcore: registered new interface driver usbserial
[   44.237540] usbcore: registered new interface driver usbserial_generic
[   44.315785] usbserial: USB Serial support registered for generic
[   44.393424] usbcore: registered new interface driver cp210x
[   44.454549] usbserial: USB Serial support registered for cp210x
AP Reboot reason:  Power-reset
shutting down watchdog process (nanny will restart it)...

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

I checked the Master IP, it is correct and worked for many other APs before.

At our controller i checked the whitelist entry for this AP:

 

(xxx) *#show whitelist-db cpsec mac-address 90:4C:81:C0:75:EE


Control-Plane Security Whitelist-entry Details
----------------------------------------------
MAC-Address        AP-Group  AP-Name  Enable   State                   Cert-Type     Description  Revoke Text  Last Updated
-----------        --------  -------  ------   -----                   ---------     -----------  -----------  ------------
90:4c:81:c0:75:ee                     Enabled  certified-factory-cert  factory-cert                            Thu Feb 28 15:39:22 2019

Total Entries: 1

I tried to take the AP only today, but it won´t show at our MM. How can i verify, what is causing the problems? We also tried factory resetting the AP.

 

Thanks in advance and kind regards

Daniel

Highlighted
MVP Guru

Re: AP won´t show at controller

What version of code is running on your MD's, you will need a minimum of 8.3.0.0 for an AP345. Just a note, you should be pointing your APs to your MD's not the MM's since the MM's will not terminate an AP.


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Highlighted
Guru Elite

Re: AP won´t show at controller

Try typing "show ap database" at the MD that it connects to.  See if there are any flags.


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Contributor II

Re: AP won´t show at controller

Hey,

 

we are using version 8.4.0.0.

Under sh ap database i see the following entry:

 

NAPXXXX   XX    345     x.x.x.x   Down                2      x.x.x.x  0.0.0.0
Highlighted
Guru Elite

Re: AP won´t show at controller

Does the ap-group have an AP system profile with an LMS-IP that redirects the access point to a controller that doesn't exist?


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Contributor II

Re: AP won´t show at controller

The LMS-IP for the AP Group is correct. It is the vrrp adress for the MC Cluster. There are over 100 APs (345) in the same AP group and they are working just fine.

Highlighted
Guru Elite

Re: AP won´t show at controller

If "show ap database" shows a controller ip address, I would SSH into that controller and type "show log system 50" and see if there is any reference to that access point.  After an AP discovers a cluster, it does not rely on dns/dhcp discovery anymore, it downloads the nodelist of the cluster and connects to one of the controllers in the cluster.  It would seem that controller does not have a standby ip address, which is interesting.


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Contributor II

Re: AP won´t show at controller

I have found the following entries in the log, but under the MAC adress:

 

Mar 18 12:05:05 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:06:01 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:07:06 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:09:07 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:09:56 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:10:55 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:13:10 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:14:03 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:15:16 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Mar 18 12:15:52 :305061:  <4048> <WARN> |stm|  sapm_proc_hello_req: AP x.x.x.x 90:4c:81:c0:75:ee GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO
Highlighted
Guru Elite

Re: AP won´t show at controller

That message is important.  How many controllers do you have an what models are they?


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Contributor II

Re: AP won´t show at controller

We have two controllers for our group subset.

 

Each controller has the following specs:

 

Aruba Operating System Software.
ArubaOS (MODEL: Aruba7210), Version 8.4.0.0

 

They are placed under LAN-Hardware in our MM Tree:

 

MM Setup.jpg

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