We're discussing a scenario where a large, central fabric deployment needs to be broken into two by inserting a transit area. The user is encountering issues with IP shortcuts (routes) not propagating between the two newly separated halves, likely due to loop prevention mechanisms.
This post explores whether this is achievable and if a VSP can support multiple remote areas. We've identified that achieving this separation with inter-area connectivity is indeed possible, with potential solutions including explicit routing in the transit area, logical segmentation, or configuring the transit area as a pure forwarding domain.
Furthermore, it's generally the case that a VSP can support multiple remote areas, as the core function of such platforms is often to interconnect different network segments.
To provide a more tailored solution for the user's specific situation, we've requested more details about the underlying fabric technology being used.
