Wireless Access

Reply
Highlighted
Guru Elite

Re: AP won´t show at controller

Is that the only access point with that problem?


*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

No, i have looked after the warning and have found at least one more AP with the same errors on both controllers.

Highlighted
Contributor II

Re: AP won´t show at controller

Should i open a ticket or can anyone help me with my problems?

Highlighted

Re: AP won´t show at controller

Yes, if your issue is critical, a ticket with TAC should be created. 


@DanielEbling wrote:

Should i open a ticket or can anyone help me with my problems?


 


Charlie Clemmer
Aruba Customer Engineering
Highlighted

Re: AP won´t show at controller

How does the cluster look when you use the command "show lc-cluster group-membership" from both of the 7210 mds? Do they show as L2 connected, or something else?


Charlie Clemmer
Aruba Customer Engineering
Highlighted
Frequent Contributor I

Re: AP won´t show at controller

Are the working and none working aps in the same subnet? 

Contributor II

Re: AP won´t show at controller

(cluster1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "LC-LAN-Controller"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 50%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 30
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address    Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self    x.x.x.x      	  128             N/A CONNECTED (Member)
peer    y.y.y.y           128    L2-Connected CONNECTED (Leader, last HBT_RSP 82ms ago, RTD = 0.000 ms)

(cluster2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "LC-LAN-Controller"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 50%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 30
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address    Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer    x.x.x.x           128    L2-Connected CONNECTED (Member, last HBT_RSP 67ms ago, RTD = 0.396 ms)
self    y.y.y.y           128             N/A CONNECTED (Leader)

Looks pretty normal to me.

 

Yes, there are working and non-working APs in the same subnet.

Highlighted
Frequent Contributor II

Re: AP won´t show at controller

Did you find the solution?  I have the exact same problem. I have 6 controllers. All 7280s and have APs running on them with no problem. I get the following error?

 

sapm_proc_hello_req: GSM CLUSTER_AAC is not copied to assigned A-AAC, ignore HELLO

 

It seems my whitelist isn't being copied to all the controllers and the AP shows denied when I do a sh ap database long command

Highlighted
Contributor II

Re: AP won´t show at controller

Hi,

 

i have opened a case with Aruba and send them the same logs and the answer was, that it seems like a hardware failure in the AP, so they had send me a spare AP.

Highlighted
Frequent Contributor II

Re: AP won´t show at controller

I'm sure that wasn't the problem. I noticed that the whitelist on my 6 controllers doesn't match. I added this entry to the MM and since all 6 controllers are part of a cluster they should sync up. We had a problem adding 4 controllers (7280s) to our exising cluster. The TAC solution was to delete the cluster and rebuild it with the new controllers added. I'm hoping that's no the solution this time. We currently have 2,000 APs running on 6.4 and migrated 1,000 over to 8.3.0.3 and are seeing these little bugs and are nervous about moving the remaining 2,000 this summer.  

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