Use Case Overview
Junos Fusion Enterprise provides an architecture that simplifies Enterprise network management and topologies by allowing a large number of switches to interconnect and be managed as a single device. A Junos Fusion Enterprise can manage up to 128 switches from a single management point.
A typical campus network has multiple buildings that are either located in the same area or spread out and connected over a WAN connection. A typical building in a campus network rarely exceeds 100 switches, so a Junos Fusion Enterprise is often deployed per building in a campus network to streamline the network management of the network devices in each building. In this network configuration example, two campus buildings—each with their own Junos Fusion Enterprise—are deployed and connected using a WAN that is running MPLS.
The following list provides typical requirements in campus deployments with multiple buildings.
Optimized intrasubnet and intersubnet learning and forwarding across campus buildings.
Extended VLANs across multiple buildings. For example, wireless guest VLAN or facilities equipment that need layer 2 adjacency across buildings.
Effective network segmentation inside and across campus buildings.
These requirements are addressed in this example by utilizing EVPN-MPLS Layer 2 VPN and Layer 3 VPN technologies to connect multiple Junos Fusion Enterprises in a campus network with multiple buildings.
In this example, the two Junos Fusion Enterprises in different campus buildings are interconnected using MPLS. The topology in this document does not have a need to use GRE tunnelling. If your campus buildings are interconnected using simple layer 3 connectivity provided by your service provider, you can configure MPLS between the Junos Fusion Enterprises using GRE tunnels between the Junos Fusion Enterprise topologies. See Configuring Generic Routing Encapsulation Tunneling.