Understanding Junos Fusion

Rashmi Bhardwaj | Blog,Config & Troubleshoot,Routing & Switching

Interconnectivity between aggregation and satellite devices is called Junos fusion. This approach expands the number of network interface on aggregation devices, and henceforth makes it appear as a single point that can be managed using an IP address.Junos fusion Enterprise supports IEEE 802.1BR standard.

  Junos fusion enterprise benefits –

  • It combines multiple device network into a topology makes large network appear as a single device which can be managed using a single IP address.
  • We can expand network by adding more satellite devices.

Understand the Juniper Fusion Terms –


  • Aggregation devices (AD): EX9200
  • Satellite devices (SD): EX2300, EX4300, EX3400, or QFX5100
  • We can use one or two aggregations devices. If we use two aggregations then it can be multihomed to each satellite device or satellite clustering devices. When we use two aggregation peers, then it’s called Junos Fusion Enterprise.
  • Aggregation devices are also responsible for
    • running Junos OS software for entire Junos fusion enterprise
    • all management tasks and
    • Interface configuration of all satellite devices.
  • Satellite devices provide network interfaces that send and receive network traffic, and the traffic is forwarded between satellite devices through aggregation.
  • Satellite cluster: – it allows you to connect up to Ten satellite device into a single cluster/group.
  • Cascade Port: It’s a port on an aggregate switch connected with satellite devices that send/receive control and network traffic. it can be 10Gbps or 40Gbps.
  • Uplink Port: – It’s a port on satellite device that connected with aggregation devices.
  • Extented Port(EP): it’s a port on Satellite device that connects host and other devices.
  • Multichassis link aggregation groups (MC-LAGs): it enables a Satellite device to form a logical LAG interface between two aggregation devices. Which provides redundancy and load balancing between the two aggregation switches, multihoming support, and a loop-free Layer 2 topology (without the need of STP).
  • ICL Link: -The peers in an MC-LAG use an interchassis control link-protection link (ICL-PL) to forward data traffic across the MC-LAG peers. ICL link can be single link or an aggregated link.
  • The Interchassis Control Protocol (ICCP) Link: This link is used for LAG synchronization between Aggregation devices (MC-LAG switches). A dedicated ICCP link is recommended, but not required. ICCP traffic can be transmitted across ICL link when ICCP link is not configured. ICCP link can be single link or an aggregated link.
  • Flexible PIC Concentrator identifier (FPC ID): Every satellite device must have FPC ID, that is used for Junos Fusion configuration, monitoring, and maintenance. The valid range for the FPC ID is 100 -255 in Junos OS Release 14.2 and 65 to 254 in Junos OS Release 16.1 and later. When Satellite device is participating in Junos Fusion it uses interface names like “type-fpc/pic/port”.
    • – Where “type” is media type like ge, at, so, tl, xe etc.
    • – “fpc” is FPC ID
    • – “PIC” stand for Physical Interface Card
    • – “Port” means switch port no


There are two methods for assigning FPC identifier –

  1. Unique-ID based FPC identification: In this case FPC ID is mapped to the serial number or MAC address of the satellite device.

 To configure the FPC slot IS using unique-ID based FPC identifier:

  • To map the FPC slot ID to a satellite device’s serial number:
user@AD# set chassis satellite-management fpc serial-number

 Example: –

user@AD# set chassis satellite-management fpc 201 serial-number xxxxxxxxxxxx
  • To map the FPC slot ID to a satellite device’s MAC address:
user@AD# set chassis satellite-management fpc < slot-id> system-id <mac-address>

 Example: –

user@AD# set chassis satellite-management fpc 201 system-id aa:aa:aa:aa:aa:aa


2. Connectivity-based FPC identification: in this case FPC ID is mapped to the cascade port.

 To configure the FPC slot IS using connectivity-based FPC identifier:

user@AD# set chassis satellite-management fpc <slot-id> cascade-ports <interface-name>

Example: –

user@AD#set chassis satellite-management fpc 201 cascade-ports xe-0/0/1


Leave a Comment

Your email address will not be published. Required fields are marked *

Shopping Cart