This section of the network configuration example provides an overview of the major components of a Junos Fusion Enterprise, and a brief description of how each component is applied in this network configuration example.
Aggregation and Satellite Devices
The two primary building blocks of any Junos Fusion topology are aggregation devices and satellite devices.
provide the point of management for all interfaces and devices in the Junos Fusion Enterprise. All configuration in a Junos Fusion Enterprise is done from the aggregation device.
run Junos OS software.
are one or two EX9200 switches in a Junos Fusion Enterprise.
have at least one connection to each satellite device.
are able to simultaneously provide ports to devices that are and are not participating in the Junos Fusion Enterprise.
In this network configuration example, two EX9208 switches act as aggregation devices in the Junos Fusion Enterprise topology.
provide access interfaces in a Junos Fusion Enterprise.
run satellite software that has the built-in intelligence to extend features on the Junos OS software running on the aggregation device onto the satellite device interfaces.
have at least one connection to each aggregation device.
Figure 1 provides an illustration of a basic Junos Fusion Enterprise topology..
In this network configuration example, EX4300-48T and EX4300-48P switches are used as satellite devices to provide access interfaces to the various buildings.
See Understanding Junos Fusion Enterprise Components for additional information on aggregation and satellite devices.
Dual Aggregation Device Topology
Junos Fusion Enterprise supports dual aggregation device topologies.
The advantages of a dual aggregation device topology include:
Load balancing. Traffic traversing the Junos Fusion Enterprise can be load balanced across both aggregation devices.
Redundancy. The Junos Fusion Enterprise can pass traffic even in the unexpected event of an aggregation device failure.
A Junos Fusion Enterprise supports multiple aggregation devices using Multichassis Link Aggregation (MC-LAG) groups and the Inter-Chassis Control Protocol (ICCP). A Junos Fusion Enterprise with dual aggregation devices is configured as an MC-LAG with one redundancy group. The redundancy group includes two peer chassis IDs—the aggregation devices—and all satellite devices in the Junos Fusion Enterprise. The aggregation devices are connected using an interchassis link (ICL) and an ICCP link in the MC-LAG topology.
Junos Fusion Enterprise supports automatic ICCP provisioning, which automatically configures ICCP in a dual aggregation device setup without any user action. Automatic ICCP provisioning is enabled by default and is often the preferred method of enabling ICCP for a Junos Fusion in greenfield deployments that are not being integrated into an existing network. Automatic ICCP provisioning is described in more detail in Understanding Automatic ICCP Provisioning and Automatic VLAN Provisioning of an Interchassis Link.
Many Junos Fusion Enterprise installations occur in brownfield deployments and the Junos Fusion Enterprise has to be integrated within an existing campus network. Brownfield deployments often have a need to maintain existing ICCP settings, in particular in scenarios where a Junos Fusion Enterprise is replacing an MC-LAG topology or is supporting a campus network that includes other MC-LAG topologies. This document provides a section on manual ICCP configuration for environments that require it.
Figure 2 provides an illustration of a complex Junos Fusion Enterprise setup that uses a dual aggregation device topology.
The topology provided in this network configuration example is a dual aggregation device topology, using two EX9208 switches as aggregation devices.
See Understanding Junos Fusion Enterprise Components for additional information on dual aggregation device topologies.
Satellite Device Clusters
Satellite device clustering allows you to connect up to ten satellite devices into a single cluster, and connect the satellite device cluster to the aggregation device as a single group instead of as individual satellite devices.
Satellite device clustering is particularly useful in scenarios where optical cabling options between buildings are limited and in scenarios where you want to preserve optical interfaces for other purposes. If you have, for instance, two buildings that have limited optical interfaces between each other and you want to put an aggregation device in one building and ten satellite devices in the other building, you can group the ten satellite devices into a cluster and connect the cluster to the aggregation device with a single cable.
Figure 2 provides an illustration of a more complex Junos Fusion Enterprise topology that is using satellite device clustering and dual aggregation devices.
Satellite device clusters include uplink ports—ports that connect a satellite device in a cluster to an aggregation device—and clustering ports—ports that interconnect two satellite devices in a cluster.
Cluster interfaces are typically 10-Gbps SFP+ interfaces. 10-Gbps SFP+ and 40-Gbps QSFP+ interfaces can be used as default cluster interfaces. Other interfaces can be used as cluster interfaces but require additional configuration because they are not usable as cluster interfaces by default. See the Default Uplink Interfaces for Junos Fusion Enterprise Satellite Devices table for a full list of 10-Gbps SFP+ and 40-Gbps QSFP+ interfaces on satellite devices that are default cluster interfaces. See Configuring Uplink Port Policies for additional information on configuring a non-default cluster interface into a cluster interface.
In this network configuration example, building 1 uses a satellite device cluster with six member satellite devices and building 2 uses a satellite device cluster with three member satellite devices. The building 1 satellite device cluster has two member satellite devices with uplinks to both aggregation devices; the building 2 satellite device cluster has one member satellite device with uplinks to both aggregation devices. Only default clustering policies are used in this network configuration example.
See Understanding Satellite Device Clustering in a Junos Fusion for additional information on satellite device clustering.
FPC Identifiers in a Junos Fusion
In a Junos Fusion, each satellite device—including each member satellite device in a satellite device cluster—must have a Flexible PIC Concentrator identifier (FPC ID). The FPC ID is in the range of 65-254, and is used for Junos Fusion configuration, monitoring, and maintenance. Interface names—which are identified using the type-fpc / pic / port format—use the FPC ID as the fpc variable when the satellite device is participating in a Junos Fusion. For instance, built-in port 2 on PIC 0 of a satellite device—a Gigabit Ethernet interface on a satellite device that is using 101 as its FPC ID— uses ge-101/0/2 as its interface name.
See Understanding Junos Fusion Enterprise Components for additional information on FPC ID numbers in a Junos Fusion Enterprise.
Satellite Software Upgrade Groups
A satellite software upgrade group is a group of satellite devices that are designated to upgrade to the same satellite software version using the same satellite software package. The two most common methods of installing satellite software—autoconverting a device into a satellite device when it is cabled to an aggregation device and manually converting a device that is cabled into an aggregation device into a satellite device—require the presence of a configured satellite software upgrade group.
For standalone satellite devices—satellite devices that are not part of a satellite device cluster—you must configure a satellite software upgrade group and add the standalone satellite device or devices to the satellite software upgrade group.
For satellite devices in satellite device clusters, a software upgrade group matching the name of the satellite device cluster is automatically created.
In this network configuration example, the two satellite device clusters each have their own automatically-created satellite device software upgrade group while a user-created satellite software upgrade group is created for the satellite device in branch office 1. Autoconversion—which installs satellite software onto a satellite device when it is connected into the Junos Fusion using a properly-enabled cascade port—is used to install satellite software in this network configuration example.
See Understanding Software in a Junos Fusion Enterprise for additional information for satellite software upgrade groups.
Both aggregation devices in this network configuration example run Junos OS Release 17.2R1, and all satellite devices run satellite software version 3.1R1. We strongly recommend that both aggregation devices in a Junos Fusion Enterprise run the same version of Junos OS.
You can see software version compatibility information for any Junos Fusion Enterprise using the Junos Fusion Hardware and Software Compatibility Matrices.
You can see detailed information regarding hardware and software support for any Junos Fusion Enterprise in the Understanding Junos Fusion Enterprise Software and Hardware Requirements document.
This network configuration example walks users through the satellite software installation process as part of the Junos Fusion Enterprise setup. An appendix is also provided that provides software upgrade instructions for various software upgrades—including Junos OS upgrades on aggregation devices and converting a satellite switch running satellite software into a standalone switch running Junos OS—in a Junos Fusion Enterprise. See Software Conversion and Upgrades in a Junos Fusion Enterprise.
Cascade, Uplink,and Extended Ports
A cascade port is a port on an aggregation device that sends and receives control and network traffic from an attached satellite device or satellite device cluster. All traffic passed between a satellite device or cluster and the aggregation device in a Junos Fusion traverses the cascade port.
An uplink port is a port on a satellite device that connects a satellite device or a satellite device cluster to an aggregation device. Uplink ports have to carry large amounts of traffic between endpoint devices and the aggregation device and are typically 10-Gbps or 40-Gbps interfaces. Any interface on a satellite device, however, can be used as an uplink port.
An extended port in a Junos Fusion Enterprise is an access port—a port that connects an end user device such as a PC, phone, wireless access point (WAP or other endpoint device—on a satellite device. Any port on a satellite device can be used as an extended port.
Figure 3 illustrates the location of these ports in a Junos Fusion Enterprise.
In this network configuration example, an EX9200-6QS line card (6-port 40-Gigabit Ethernet QSFP+, 24-port 10-Gigabit Ethernet SFP+ line card) is installed in slot 0 of each aggregation device. All of the cascade ports on both aggregation devices are on this line card. The uplink ports for satellite device cluster building1 are on the satellite devices using FPC 102 and 105. The uplink ports for satellite device cluster building 2 are on FPC 112. FPC 121 is a standalone satellite device that has its own uplink port to the aggregation devices.
See Understanding Junos Fusion Enterprise Components for additional information on cascade, uplink, and extended ports.
Configuration Synchronization on Aggregation Devices
In a Junos Fusion Enterprise using a dual aggregation device topology, either aggregation device can be used to configure features on extended ports.
The configuration of extended ports in a Junos Fusion Enterprise should always match between aggregation devices in order to prevent unpredictable or unwanted network behavior on an extended port.
You can ensure configuration synchronization between aggregation devices by manually entering each extended port configuration command identically on each aggregation device. In this network configuration example, Power over Ethernet (PoE), Link Layer Discovery Protocol (LLDP), and Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) are all configured manually on each aggregation device.
A more efficient method of ensuring extended port configuration synchronization is through the use of commitment synchronization and configuration groups. You can configure the aggregation devices as commit peers and synchronize all configurations in groups to both aggregation devices, which allows you to configure the extended port configuration once instead of manually repeating the configuration on each aggregation device.
The available group configuration options are beyond the scope
of this document; see Understanding MC-LAG Configuration Synchronization and Synchronizing and Committing MC-LAG Configurations for additional
information on using group configurations in an MC-LAG topology and Network Configuration Example: Configuring MC-LAG on EX9200 Switches
in the Core for Campus Networks
Many features in this guide are configured in groups and shared between aggregation devices using commitment synchronization.
Understanding Local Switching On a Satellite Device in a Junos Fusion Enterprise
All traffic originating from an endpoint device in a Junos Fusion Enterprise is sent to the aggregation devices for forwarding. Local switching from a satellite device—the ability for a satellite device to recognize that it has received traffic destined for one of it’s extended ports and forwarding it onward without passing the traffic to the aggregation device—is not currently supported in Junos Fusion Enterprise.
Understanding Routing Protocols in a Junos Fusion Enterprise
The network ports on an EX9200 switch acting as an aggregation device in a Junos Fusion Enterprise support the same routing protocols as any other EX9200 switch. See the Layer 3 protocols section on the Junos OS for EX9200 Switches portal.
Traffic is moved between Layer 2 and Layer 3 in this network configuration example using integrated routing and bridging (IRB) interfaces on aggregation devices. See the Adding Layer 3 Support to a Junos Fusion Enterprise section of this network configuration example.
Extended ports in a Junos Fusion Enterprise cannot be configured as Layer 3 ports and cannot, therefore, send or receive Layer 3 traffic.
Junos Fusion Enterprise Hardware and Software Support
A Junos Fusion Enterprise runs Junos OS software on the aggregation devices and satellite software on the satellite devices. The Junos OS and satellite software must be compatible for the Junos Fusion Enterprise to operate.
Additionally, a switch acting as a satellite device must be running a minimum version of Junos OS software before it can be converted into a satellite device.
See Junos Fusion Hardware and Software Compatibility Matrices for software version compatibility information for any Junos Fusion Enterprise.
See Understanding Junos Fusion Enterprise Software and Hardware Requirements for detailed information regarding hardware and software support for any Junos Fusion Enterprise.
Junos Fusion Enterprise Feature Support
A list of available features for Junos Fusion Enterprise is available using the Feature Explorer tool.
To view the list of features supported on Junos Fusion Enterprise in Junos OS Release 17.2R1, see Features Supported in Junos OS 17.2R1 on Junos Fusion Enterprise.
To search the features available in other versions of Junos Fusion Enterprise, select Junos Fusion Enterprise from the Switching products page in Feature Explorer. Select your desired Junos OS Release from the Supported Releases menu.