A sanitation department runs two SD-Access fabrics that may merge l…

Question

A sanitation department runs two SD-Access fabrics that may merge later. Which planning practice best reduces renumbering chaos at merge time?

Accepted Answer

Keep dual fabrics with carefully unique, non-overlapping IP pools and addressing plans so a future merge does not force mass renumbering. — Two fabrics that might become one are like two towns that might consolidate—duplicate street numbers become a nightmare. Keep IP pools unique and non-overlapping now. Future merge then stitches plans instead of renumbering every truck tablet overnight.

Answer

Reuse identical user subnets at both sites because LISP will permanently hide all overlaps.

Answer

Assign the same edge locator pool to both fabrics to simplify border configurations.

Answer

Number both fabrics from overlapping RFC1918 space and rely on NAT inside every VN by default.

A sanitation department runs two SD-Access fabrics that may merge later. Which planning practice best reduces renumbering chaos at merge time?

Short Explanation

Full Explanation