ACI stretched Fabric to Multi Pod

[mannycho]

Hello,

I am migrating from stretched Fabric to Multipod. When I make the connection from the pair of spine nodes (Pod1) in the stretched fabric to the IPN nodes and connect the spines in Pod2 to IPN nodes, then run through the pod setup in APIC. Will there be any traffic interruptions (downtime) in the already established stretched Fabric (Pod1) in production. There will be a scheduled downtime in the environment to perform this change.

Are there any gotchas I should watch out for as I bring Pod2 online to join Pod1 (stretched fabric) that has production workloads? Pod2 will be a fabric of new spine and leaf switches.

Thank you

[M02@rt37]

Hello @mannycho,

It's advisable to perform a phased migration approach to minimize traffic interruptions and downtime. Start by establishing the connectivity between the IPN nodes and spine switches in Pod2 without affecting the existing production environment. Gradually transition the workloads from Pod1 to Pod2 in a controlled manner, ensuring proper testing and validation at each stage. During the cutover from Pod1 to Pod2, plan for a scheduled downtime to perform the necessary changes and minimize potential disruptions.

Monitor the network during the migration process to ensure that traffic is being properly rerouted and workloads are functioning as expected.

[sk37]

@mannycho How was your experience with the migration? As I have to perform a similar migration in the upcoming therefore would like to know the insights.

[mannycho]

Hello,

Migration is still ongoing, I just brought up pod2 so in process of testing traffic on the multipod. No issues yet at this time (and hopefully in future :), old stretched fabric which is pod 1 operating as normal.