Migrating and creating Microcell

[craiglebutt]

I’ve got around 1200 x 2800 APs to migrate from 5520 -> 9800, over 2 site, pre installing image, then change the Primary and priority of the AP.

1 Site is a has the standard Hospital H Blocks build with multiple levels, with 4 wards on each.

Looking at this opportunity of looking at creating a TAG for each ward, turning in to a micro cell.

All will use the default-rf tag at first to go more granular with each cell.

My question, is there any gotchas that might come up or need to look out for?

9800-80s running 17.15.5

Cheers

Craig

[Leo Laohoo]

Please confirm the 17.15.5 firmware has been successfully upgraded to the APs.

I use tag filters.  

[Mark Elsen]

  - @craiglebutt               Have a look at this document :
                                              https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/226331-wi-fi-cell-sizing-and-overlapping-with.html

                                      - In general do not use defaults on the 9800 platform such as a default rf-tag.
                                         Create configuration values and elements  according to your needs.

                                      + Validate the configuration of your 9800 wireless controller before production using
                                         the CLI command show tech wireless  and feed the output from that into
                                         WCAE
                                         For a more technical overview and when clients are using  the 9800 based wireless
                                         environment feed the output from show tech wireless in the desktop version
                                         of the 9800 configuration analyzer which you can find at :
                                        https://github.com/CiscoDevNet/wcae
                                        At the right pane you have this menu :  which will give more detailed insight in
                                        client behavior