User anchor controller communication within a network environment

1. A non-transitory computer readable medium comprising instructions which, when executed by a processor, causes the processor to:

configure, by a first controller, a first access point on a first subnet;

manage, by the first controller, the first access point, wherein a client device is connected with the first access point;

identify a second controller on the first subnet that is different than the first controller, wherein the second controller is a primary controller of the client device that manages network traffic of the client device and maintains state information corresponding to the client device when the client device is connected to the first access point, and wherein the second controller does not manage the first access point that the client device is connected to;

instruct the second controller to update a controller configuration table for the second controller that identifies that the first access point is assigned to the first controller;

determine that the client device roams to connect with a second access point on a second subnet that is different than the first subnet, wherein the second access point is managed by a third controller that is different than the first and second controller;

query, by the third controller, the second controller to obtain the state information of the client device in response to the determination that the client device is connected with the second access point; and

direct the network traffic of the client device on the second subnet through the second controller, wherein the second controller remains on the first subnet.

2. The medium of claim 1 , wherein the first access point obtains the information corresponding to the client device using a data path that does not include the first controller.

3. The medium of claim 1 , wherein:

the second controller is a primary controller to maintain information corresponding to the client device;

a fourth controller is a backup controller to maintain information corresponding to the client device;

the second controller is a primary controller to maintain information corresponding to a second client device that is different than the first client device; and

a fifth controller is a backup controller to maintain information corresponding to the second client device.

4. The medium of claim 1 , further comprising instructions to select the second controller as a primary controller to maintain information corresponding to the client device independent of any access point with which the client device is currently associated.

5. The medium of claim 1 , further comprising instructions to select a fourth controller as a backup controller to maintain the information corresponding to the client device, wherein the selection of the fourth controller is independent of the second controller that is configured as a primary controller to maintain the information corresponding to the client device.

6. The medium of claim 1 , further comprising instructions to select the second controller as a primary controller to maintain the information corresponding to the client device, wherein the selection is based in part on applying a hash function to an identifier associated with the client device.

7. The medium of claim 6 , wherein the applying operation is performed by the first access point.

8. The medium of claim 1 , further comprising instructions to select a fourth controller as a backup controller for maintaining the information corresponding to the client device, wherein the selection of the fourth controller is based in part on applying a hash function to an identifier associated with the client device.

9. The medium of claim 1 , further comprising instructions to:

select a fourth controller as a backup controller for maintaining the information corresponding to the client device; and

select the fourth controller as a primary controller for maintaining information corresponding to a second client device.

10. The medium of claim 1 , wherein:

the second controller is a primary controller to maintain information for a first plurality of client devices;

a plurality of controllers, other than the second controller, are backup controllers to maintain information for the first plurality of client devices; and

the plurality of controllers are primary controllers for a second plurality of client devices.

11. The medium of claim 1 , further comprising instructions to receive, at the first access point, a plurality of data for a respective plurality of client devices associated with the first access point, wherein the plurality of data is received from a plurality of controllers maintaining information corresponding to the respective plurality of client devices.

12. The medium of claim 1 , further comprising instructions to configure a fourth controller as a primary controller to maintain the information corresponding to the client device in response to a failure of the second controller, wherein the fourth controller was selected as a backup controller to maintain the information corresponding to the client device prior to the failure of the second controller.

13. The medium of claim 1 , further comprising instructions to modify a primary controller to maintain the information corresponding to the client device from the second controller to a fourth controller, wherein the modification improves a balance of primary controller configurations across a plurality of controllers comprising the second controller and the fourth controller.

14. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device from a particular plurality of controllers based on one or more attributes of the client device.

15. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device from a particular plurality of controllers based solely on one or more attributes of the client device.

16. The medium of claim 1 , wherein the information corresponding to the client device comprises:

a security clearance of the client device;

a priority level of the client device;

a type of data transmitted to or from the client device; and

a location of the client device.

17. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a security clearance level of the client device.

18. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a location of the client device.

19. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a functionality of the client device.

20. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on actions performed by the client device or data transmitted by the client device.

21. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a priority level associated with the client device.

22. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a type of the client device.

23. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a capability of the second controller.

24. The medium of claim 1 , wherein the second controller is selected to maintain information corresponding to the client device based on a current load at the second controller.

25. The medium of claim 1 , wherein the first controller does not maintain an access to the state information corresponding to the client device when the client device is connected to the first access point.