Wireless Access

Reply
Highlighted
MVP Expert

Re: AP with Flag ID

What do you mean a different profile on each controller ?
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Occasional Contributor II

Re: AP with Flag ID

Each has a different AP system Profile.

 

So When assigned to the Master or Local controller the appropriate AP has the correct controller as its primary/backup LMS.

Highlighted
Occasional Contributor II

Re: AP with Flag ID

If the AP's are losing heartbeat to the controller.... Why does it only effect those AP's that had been configured with the Local as the primary LMS?

 

All AP's now have the Master LMS profile and have been reprovisioned.

Highlighted
MVP Expert

Re: AP with Flag ID

Do you have other APs that are the IP segment join to the master controller with no issues ?

Under the AP provisioning settings what do you have configured ? Can you remove any manual settings and allow the APs to find the controller based on the ap system profile ?
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Occasional Contributor II

Re: AP with Flag ID

Hi Victor,

 

Q: Do you have other APs that are the IP segment join to the master controller with no issues?

  •  A: Yes, I have a site which has 6 AP's. Two of which are newly deployed AP's and I set via console on my desk with the serverip and master as the "MASTER" IP address. The already installed AP's orignally had the Local IP set as both server and master IP as the Local address.
  • The newly deployed AP's work as expected. The AP's previously configured to use the local do not.
  • Regards, Red.
Highlighted
MVP Expert

Re: AP with Flag ID

Why do you assign the controller manually that way ?

You should implement either dhcp option 43 or DNS Aruba-master for APs to discover your controller.

To get to the bottom of this you should probably open a TAC they will be able to look at your environment and determine what's causing this issue
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Occasional Contributor II

Re: AP with Flag ID

Hi Victor,

 

We only have two controllers and the IP's are static and not going to change so it was our preference to use static IP.

 

Thankyou for your help.

 

Regards,

Chris,

Occasional Contributor II

Re: AP with Flag ID

Hello All,

 

Just wanted to update this post with a solution.

 

To recap..... We have two controllers

   North-(Local (Backup))   &   South-(Master)

 

We originally configured (via console) our AP's according to which controller was the closest e.g.

 

Northern-AP                                              Southern-AP

  setenv ipaddr 10.3.1.1                          10.2.1.1
  setenv netmask 255.255.0.0               255.255.0.0
  setenv gatewayip 10.3.0.1                    10.2.0.1
  setenv serverip 192.168.1.10             192.168.0.10
  setenv master 192.168.1.10               192.168.0.10

 

Everything was working until.....

We then needed to change (re-provision) all Northern AP's to use the Southern controller.

Doing this via the GUI lead to the Northern AP's constatnly flapping between both controllers and showing/flapping the flags D (Dirty) & I (inactive).

 

The solution-

Disbale ADP on the Northern-(Local) controller.

Although configured manually we found that ADP was not helping our setup.

This fixed the majority of re-provisioned AP's

 

Next for those stuborn AP's  that still kept falpping. We re-re-provisioned with a new IP in the same range.

E.g for an AP that had IP 10.3.1.1 we moved it to 10.3.1.10.

 

All AP's are now using the Southern-(Master) controller.

 

View solution in original post

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