https://community.extremenetworks.com/t5/extremecloud-iq/dividing-a-large-fabric-with-a-transit-area-routing-challenges/m-p/118872#M4615 <P>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.</P><P>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.</P><P>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.</P><P>To provide a more tailored solution for the user's specific situation, we've requested more details about the underlying fabric technology being used.</P> Tue, 03 Jun 2025 06:46:43 GMT mooze84jet 2025-06-03T06:46:43Z https://community.extremenetworks.com/t5/extremecloud-iq/dividing-a-large-fabric-with-a-transit-area-routing-challenges/m-p/118872#M4615 <P>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.</P><P>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.</P><P>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.</P><P>To provide a more tailored solution for the user's specific situation, we've requested more details about the underlying fabric technology being used.</P> Tue, 03 Jun 2025 06:46:43 GMT https://community.extremenetworks.com/t5/extremecloud-iq/dividing-a-large-fabric-with-a-transit-area-routing-challenges/m-p/118872#M4615 mooze84jet 2025-06-03T06:46:43Z https://community.extremenetworks.com/t5/extremecloud-iq/dividing-a-large-fabric-with-a-transit-area-routing-challenges/m-p/118881#M4616 <P>Hello,</P><P>It looks like you are discussing an OSPF setup?</P><P>A VOSS/FabricEngine device can support a maximum of TWO AREA's in the FABRIC, HOME and REMOTE AREA.</P><P>We had also to split a customers large FABRIC only network and did it the following way.<BR />The Multi-AREA setup is running as stable as the Single-AREA setup did before.</P><UL><LI>One HOME AREA: for the DC sites (this was the existing AREA before migration).</LI><LI>Four REMOTE AREA's:&nbsp; for the ACCESS sites.</LI></UL><P>Traffic between ACCESS sites is forwarded via the HOME AREA between the Multi-AREA switches.<BR />To avoid routing loops, it is never a good idea to interconnect two ACCESS AREA's.</P><P>regards<BR />WillyHe</P> Tue, 03 Jun 2025 14:27:32 GMT https://community.extremenetworks.com/t5/extremecloud-iq/dividing-a-large-fabric-with-a-transit-area-routing-challenges/m-p/118881#M4616 WillyHe 2025-06-03T14:27:32Z