Hi
I am trying to work out the best/most efficient method to get clients migrated from old switches to new ones in SD Access. I have a requirement to maintain much of my address space so I need to have a scenario where clients can be on the same subnet inside and outside SDA for a period. I'll use a L2 Border to facilitate this.
I've come to the conclusion that when I first migrate users in a subnet I need to move the gateway for that subnet into SDA. However, I cannot pre-create the SDA Anycast gateway and leave it shutdown as DNAC doesn't have this feature. Until I create the Anycast gateway and the associated vlan name/ID I don't have the address pools available in the Port assignment area. So, again I can't preconfigure my new Edge ports until I have the Anycast gateways in place. So on the first occasion I migrate a subnet int SDA I have a bit of work to do at migration time. I was hoping to find a way to be able to pre-assign the ports on the edge switches.
When I create an Anycast gateway I usually allow DNAC to select the Vlan ID. So I thought if I create a template with a vlan ID I pre-define I could push out the vlan and the edge port configurations in one provisioning task. Then at migration time I create the Anycast gateways and define the vlan ID's to use in line with what I used in my template. This works to an extent. However, when I do this and then go to the Port assignment area my Edge ports in the GUI do not reflect what I pushed out in the template. They are all blank and look as if they are all available to be assigned when in fact they have vlan assignments from my template. Additionally this means I need to track the vlan ID's rather than just letting DNAC get on with it.
Tracking the vlan ID's isn't a great chore but not having the Edge ports reflect what is in the template is. It seems strange DNAC does not pick up the new Edge port config via a resync and reflect it in the port assignment area. If I look at the Edge switch details and then the config drift area DNAC does know the port config has changed.
Are there any recommendatins on the most efficient way to do this to save me having to create Anycast gateways and assign what could be a great many ports at the first migration window?
Once I've moved a gateway into SDA subsequent Edge migrations are easier because the address pool is then available to assign to ports in the GUI. So I can do that work prior to the migration window.
Thanks, Kev.
