I'm trying to make a few configuration scripts for our "BAU" team. Unfortunately their experiance with networks is... well... they know there's cables involved.
So, keeping that in mind, I'm looking to limit the possibility of them accidently doing things they shouldn't and I'm wondering if, there is a way with a NCM Change Template to limit variable selection to just one node or one port?
My thinking is whilst I know its unlikely someone is going to accidently select multiple ports and turn them all in to trunks. However I'd rather just not give them the chance to do so in the first place.
I've been looking around but to be fair the NCM Documentation could do with some work. Anyone managed this before? Can't seem to find anyone asking similar questions so far in my searches.
I haven't seen this type of limitation built in, though you may be able to write a config change template that limits it. You may be better off using the built-in approval system and judicious use of AAA command limiting to limit any possible issues.