Move L3Out to different Tenant using POST?

[bl80]

Hopefully this is simple solution question - Looking to move a bunch of L3Outs that exist in a Tenant we are decommissioning.  All the L3Outs are pretty straightforward SVI or routed interfaces, single contract to Provide the external resources.  

Saving out the configuration/subtree/JSON file I can see the reference to the current Tenant and Contract.  All other elements will be exact same when built in the new Tenant.  Hoping its a easy as editing the JSON file for the appropriate new Tenant and contract and then POSTing accordingly. 

Plan would be to delete the old L3out completely before POSTing to the new Tenant so no double reference to the topology path/interfaces/etc.

Anyone have experience in this?  Appreciate any advice or concerns I might not be considering.

Thank you

[Sergiu.Daniluk · Accepted solution]

Hi @bl80 

The plan sounds good. Should work like a charm.

Don't forget to change the VRF name as well in case it has a different one in the new tenant.

Take care,

Sergiu

[bl80]

Perfect. Thank you Sergiu - and yes, VRF name is same in new Tenant and understand that would change if different.  

Appreciate the quick reply.  

[bl80]

Wanted to update - using the above method I was able to move 4 L3 outs to a different tenant with zero loss of data connectivity for all services.  Prepped new contracts in the target tenant and pre-populated as consumer for all EPGs that needed the specific access.  Saved all L3Outs as Json, edited the appropriate elements (Tenant, VRF, Contracts) and posted to the target Tenant.  Worked exactly as I hoped.  

[Sergiu.Daniluk]

Happy to hear no issues where encountered!