Solved! Go to solution.
As I said, it won't have any impact. Trust me.
Just, create new networks, bind them on the template and test the configurations before migrating. After you confirm that it all working as expected, migrate It.
why is better to creatte a new network and bind the template ?
Here a documentation that can help you:
I'd just bind the existing network to your template.
MS won't be affected, as you have to separately apply an MS template to a switch for it to have any impact. The MXs are new, so it won't make any difference to them.
Hi @PhilipDAth yes it was my idea .
I notice that some networks are using MX 64, but I'm not sure how this will influence things because I can't see the model current MX in the template. I am able to see the model of the SW trought the ports of the template. The client will switch from the existing MX 64 to MX 75.
It will not affect anything if you bind on the template. I have a client with 800+ on the template and almost every week we need to bind 5+ MX on the template, so you don't need to be afraid.
I am aware that the sw has no impact because the current SW is 250 MS and the templete is 120. However, the model MX is not visible in the template . I'm not sure whether I understand myself, hehehe
As I said, it won't have any impact. Trust me.
Ok thanks I always trust you 👍