My organization is soon going to be deploying approximately 600 new Cisco 2602i access points in a CAPWAP deployment with several 5508 controllers.
This is an infrastructure refresh; currently we have a mix of older Cisco AP's using CAPWAP with several sets of WiSM controllers. Our current procedure for deploying new/replacement AP's is, to my understanding, the standard priming procedure as listed in this Cisco Support Forum document.
- Connect new access point to the network at our desks
- AP gets a DHCP address
- DHCP Option 43 points AP to a controller
- Log into NCS Prime and find the new AP
- Change AP name and Primary/Secondary controller
- Box AP back up and take to site for deployment
I know there are other options for initially getting the AP to talk to a controller, such as Over-the-Air-Provisioning or placing the AP into a Layer 2 VLAN with a controller. But these seem focused on just getting the AP connected to ANY controller, not priming it for a specific Primary/Secondary controller.
I would like to setup some sort of staging/prep area for pre-configuring the new access points, conducting inventory, tagging with asset tags, sorting AP by final deployment area, and so on.
In setting up this staging area, is there a better way to prime these AP's quickly and easily? Or are we already doing this in the most efficient manner?