NCSO20070: One or more AAA CLI(s) are already present on the device

[DJW487]

This might be more of a complaint than a question...

But I have a switch that I PnP onboarded. I assigned to a site and provisioned the switch. Then I realised I assigned it to the wrong site.

I deleted the switch from inventory, and readded it to the correct site and tried to provision again.

However provisioning fails since it doesn't like the fact there were already radius groups and accounting settings on the switch. The exact ones it previously provisioned, and were the same as what it was about to provision anyway.

So I have to go in and manually remove all the 'conflicting' aaa config, resync then reprovision just for it to put the exact same settings back on the switch.

This is on 2.3.5.5. Hopefully it's fixed in later versions...

[Torbjørn]

While I do agree that this is annoying - I think this might be a good precaution for the catalyst center to take.

A couple of years ago I experienced a situation where a non-Cisco automation tool that broke authentication on a few hundred IOS-XE devices. This happened as the tool wasn't able to "understand" and account for certain lines of existing configuration.