Wireless Access

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.

Subject: Ongoing Issue with 2ID and 2D Flags on Controller 9012 (Version 8.12.0.5)

Hello,

We are currently experiencing an issue with 2ID and 2D flags on our Controller 9012, which is running software version 8.12.0.5.

Network Setup:

• Controller A IP: 192.168.203.134 (Physical)

• Controller B IP: 192.168.203.135 (Physical)

• Both controllers are managed by the Mobility Master (MM) at IP: 192.168.203.133 (VM)

Issue Summary:

• The 9012 controller has a known limitation of supporting only 32 Access Points (APs).

• We opened a case with TAC, and they recommended upgrading the controller version to increase the AP limit.

• After the upgrade, the controller now supports 36 APs, but the remaining APs (total of 52 in production) are showing D and ID flags.

• We have a total of 100 licenses available.

Observations:

• If we decommission any one of the currently working 36 APs, one of the flagged APs takes its place and starts serving clients as expected.

• As a temporary workaround, we moved the flagged APs to Controller B, and they are now functioning properly.

• The TAC case remains open and unresolved for the past three weeks.

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.

If you have more APs on a controller than the hardware capacity of that controller, it's expected that only the hardware capacity number of APs come up.

In the case of an AOS8 cluster of two controllers, the APs should be load-balanced over the two controllers, and as long as both are up all APs should be able to connect. If you lose one of the controllers, APs that won't fit on the remaining controller will go inactive. So this situation/design is quite deprecated if availability is of your concern.

Without clustering, it's expected to only have 32/36 APs up at the same time unless you distribute manually over the controllers, what you did.

I can't imagine that it is this simple and TAC can't solve it, so make sure you escalate the TAC case, which you should do as soon as you feel there is not enough progress or the assigned TAC engineer doesn't fully understand your issue.

Subject: Ongoing Issue with 2ID and 2D Flags on Controller 9012 (Version 8.12.0.5)

Hello,

We are currently experiencing an issue with 2ID and 2D flags on our Controller 9012, which is running software version 8.12.0.5.

Network Setup:

• Controller A IP: 192.168.203.134 (Physical)

• Controller B IP: 192.168.203.135 (Physical)

• Both controllers are managed by the Mobility Master (MM) at IP: 192.168.203.133 (VM)

Issue Summary:

• The 9012 controller has a known limitation of supporting only 32 Access Points (APs).

• We opened a case with TAC, and they recommended upgrading the controller version to increase the AP limit.

• After the upgrade, the controller now supports 36 APs, but the remaining APs (total of 52 in production) are showing D and ID flags.

• We have a total of 100 licenses available.

Observations:

• If we decommission any one of the currently working 36 APs, one of the flagged APs takes its place and starts serving clients as expected.

• As a temporary workaround, we moved the flagged APs to Controller B, and they are now functioning properly.

• The TAC case remains open and unresolved for the past three weeks.

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.

Yes, we have escalated the case to the L3 engineer. As per their instructions, we upgraded the firmware. The documentation also mentions that the hardware limit should increase from supporting 32 APs to 64 APs after the upgrade. However, we are currently seeing support for only 36 APs.

As per TAC's recommendation, we removed the L2 redundancy and configured the LMS. In doing so, we also disabled ADP on the controller.

When we manually move the working AP-69 to the secondary controller, the 'D' flag that was previously shown for AP-78 is no longer visible.

Before

After



Regards,

 Rakesh Biradar

If you have more APs on a controller than the hardware capacity of that controller, it's expected that only the hardware capacity number of APs come up.

In the case of an AOS8 cluster of two controllers, the APs should be load-balanced over the two controllers, and as long as both are up all APs should be able to connect. If you lose one of the controllers, APs that won't fit on the remaining controller will go inactive. So this situation/design is quite deprecated if availability is of your concern.

Without clustering, it's expected to only have 32/36 APs up at the same time unless you distribute manually over the controllers, what you did.

I can't imagine that it is this simple and TAC can't solve it, so make sure you escalate the TAC case, which you should do as soon as you feel there is not enough progress or the assigned TAC engineer doesn't fully understand your issue.

Subject: Ongoing Issue with 2ID and 2D Flags on Controller 9012 (Version 8.12.0.5)

Hello,

We are currently experiencing an issue with 2ID and 2D flags on our Controller 9012, which is running software version 8.12.0.5.

Network Setup:

• Controller A IP: 192.168.203.134 (Physical)

• Controller B IP: 192.168.203.135 (Physical)

• Both controllers are managed by the Mobility Master (MM) at IP: 192.168.203.133 (VM)

Issue Summary:

• The 9012 controller has a known limitation of supporting only 32 Access Points (APs).

• We opened a case with TAC, and they recommended upgrading the controller version to increase the AP limit.

• After the upgrade, the controller now supports 36 APs, but the remaining APs (total of 52 in production) are showing D and ID flags.

• We have a total of 100 licenses available.

Observations:

• If we decommission any one of the currently working 36 APs, one of the flagged APs takes its place and starts serving clients as expected.

• As a temporary workaround, we moved the flagged APs to Controller B, and they are now functioning properly.

• The TAC case remains open and unresolved for the past three weeks.

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.