Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Fusion Enterprise Installation Checklist

The checklist in Table 1 summarizes the tasks you need to perform when installing a Junos Fusion Enterprise. This checklist should be used with the Configuring or Expanding a Junos Fusion Enterprise document, which provides detailed step-by-step instructions for configuring a Junos Fusion Enterprise.

Note:

If your aggregation device is part of an existing Junos Fusion Enterprise installation with satellite device clusters that is running Junos OS Release 16.1 and you want to upgrade to Junos OS Release 17.1 or later, please refer to the upgrade instructions in the Junos OS 17.1R1 Release Notes.
Table 1: Junos Fusion Enterprise Installation Checklist

Task

Additional Information

For More Information

Performed by and Date
Prepare Aggregation Device (Aggregation Devices)

Install a supported version of Junos OS onto each aggregation device.

EX9200 switches can act as aggregation devices in a Junos Fusion Enterprise when running Junos OS Release 16.1R1 or later.

Junos Fusion main software download page and software support matrix: Junos Fusion - Download Software

Junos Fusion Enterprise software requirements:Junos Fusion Hardware and Software Compatibility Matrices

EX9200 switch software installation:Software Installation and Upgrade Guide

Junos Fusion Enterprise software overview:Understanding Software in a Junos Fusion Enterprise

 
Prepare Satellite Devices (Satellite Devices)

Ensure each satellite device is running a version of Junos OS that allows it to be converted into a satellite device.

EX2300 and EX3400 switches must be running Junos OS Release 15.1X53-D55 or later to be converted into a satellite device.

EX4300 switches must be running Junos OS Release 14.1X53-D43 or later to be converted into a satellite device.

QFX5100 switches must be running Junos OS Release 14.1X53-D43 or later to be converted into a satellite device.

Satellite device software requirements:Junos Fusion Hardware and Software Compatibility Matrices

Upgrading Junos OS on an EX2300, EX3400, or EX4300 switch:

Software Installation and Upgrade Guide

Upgrading Junos OS on a QFX5100 switch:

Installing Software Packages on QFX Series Devices

 

Zeroize each satellite device.
Best Practice:

Perform this procedure from the console port.

To zeroize a satellite device:

request system zeroize

Zeroizing a switch:

(EX3400 and EX4300 switches only) Convert the built-in 40-Gbps interfaces from Virtual Chassis ports (VCPs) to network ports.

The number of built-in 40-Gbps interfaces with QSFP+ transceivers varies by EX4300 switch model.

To convert four built-in 40-Gbps interfaces with QSFP+ transceivers on an EX4300 switch:

request virtual-chassis vc-port delete pic-slot 1 port 0
request virtual-chassis vc-port delete pic-slot 1 port 1
request virtual-chassis vc-port delete pic-slot 1 port 2
request virtual-chassis vc-port delete pic-slot 1 port 3

Deleting a VCP:request virtual-chassis vc-port

Configure Cascade Ports and FPC slot IDs (Aggregation Devices)

Configure cascade ports on the aggregation devices.

A cascade port is a port on the aggregation device that connects to a satellite device.

To configure a cascade port:

set interfaces xe-0/0/1 cascade-port

Cascade port overview:

Understanding Junos Fusion Enterprise Components

Cascade port configuration:

 

(Satellite device clusters only) Create and number the satellite device clusters.

Note:

You can skip this step if you are not using satellite device clusters.

Satellite device clustering allows you to connect up to ten satellite devices into a single cluster, then connect the satellite device cluster to the aggregation device as a single group instead of as individual satellite devices.

This configuration must match on both aggregation devices.

To create and number a satellite device cluster:

set chassis satellite-management cluster sd-cluster-building1 cluster-id 1

Satellite device clustering overview:Understanding Satellite Device Clustering in a Junos Fusion

Satellite device clustering configuration:

(Satellite device clusters only) Associate the satellite device clusters with a cascade port.

To associate a cascade port with a satellite device cluster:

set chassis satellite-management cluster sd-cluster-building1 cascade-ports xe-0/0/1

Satellite device clustering configuration: Configuring or Expanding a Junos Fusion Enterprise

Configure the FPC slot Identifiers (IDs) using one of the following methods on both aggregation devices:

  • map FPC slot ID to a satellite device’s MAC address (unique ID-based FPC identification)

  • map FPC slot ID to a satellite device’s serial number (unique ID-based FPC identification)

  • map FPC slot ID with a cascade port (connectivity-based FPC identification)

Each satellite device in a Junos Fusion is identified by it’s FPC slot ID.

To map an FPC slot ID to a satellite device’s MAC address:

  • Satellite device in a cluster:

    set chassis satellite-management cluster sd-cluster-building1 fpc 101 system-id 00:00:5E:00:53:01
    Note:

    You must map the FPC slot ID to the satellite device’s MAC address when the satellite device is a member of a satellite device cluster.

  • Standalone satellite device:

    [edit]
user@aggregation-device# set chassis satellite-management fpc 101 system-id 00:00:5E:00:53:01

To map an FPC slot ID to a satellite device’s serial number:

set chassis satellite-management fpc 101 serial-number TA0123456789

To map an FPC slot ID to a cascade port:

set chassis satellite-management fpc 101 cascade-ports xe-0/0/1

FPC slot ID overview:Understanding Junos Fusion Enterprise Components

Configuring FPC slot IDs:

 

(Satellite device clusters only) Assign a member ID to each satellite device in a satellite device cluster.

To assign a member ID to a satellite device in a satellite device cluster:

set chassis satellite-management cluster sd-cluster-building1 fpc 101 member-id 1

Satellite device cluster member ID configuration must match on both aggregation devices.

Satellite device clustering overview:Understanding Satellite Device Clustering in a Junos Fusion

Satellite device cluster member ID configuration:

Satellite Software Upgrade Group (Aggregation Devices)

Acquire the satellite software image and place it on the aggregation devices (recommended) or on a remote server.

The satellite software image is used to install satellite software onto satellite devices.

Junos Fusion main software download page:Junos Fusion - Download Software

Manage the satellite software upgrade groups.

  • (satellite devices that are part of a satellite device cluster) associate the satellite devices in a cluster with a satellite software image.

  • (standalone satellite devices) create the satellite software upgrade group and include the satellite device in it.

A satellite software upgrade group is used to upgrade the satellite software of all satellite devices in the upgrade group.

A satellite device must be part of a satellite software upgrade group to install satellite software on satellite devices in most installation scenarios.

All satellite devices in a satellite device cluster are automatically part of the same satellite software upgrade group. The satellite software upgrade group for the satellite devices in the cluster is automatically created and has the same name as the satellite device cluster.

Satellite software upgrade group associations must match on both aggregation devices.

  • (satellite device cluster) To associate all satellite devices in the satellite device cluster with a satellite software image. For example:

    request system software add /var/tmp/satellite-3.0R1.2-signed.tgz upgrade-group sd-cluster-building1

  • (standalone satellite device) Create a satellite software upgrade group, and associate the satellite device with a satellite software image. For example:

    set chassis satellite-management upgrade-groups standalone-satdevs-building1 satellite 130-139

    request system software add /var/tmp/satellite-3.0R1.2-signed.tgz upgrade-group standalone-satdevs-building1

Satellite software upgrade group overview: Understanding Software in a Junos Fusion Enterprise

Satellite software upgrade group management:

 
Configuring the Second Aggregation Device (Dual Aggregation Device Topologies Only) (Aggregation Devices)

Delete single home configuration mode on both aggregation devices.

To delete single home configuration mode on aggregation device 1:

delete chassis satellite-management single-home

Enter the same command on aggregation device 2:

delete chassis satellite-management single-home

Dual aggregation device overview: Understanding Junos Fusion Enterprise Components

Deleting single home configuration:

single-home

 

Create and number the redundancy group on both aggregation devices.

To create and number the redundancy group on aggregation device 1:

set chassis satellite-management redundancy-groups junos-fusion-campus-network redundancy-group-id 1

Enter the same command on aggregation device 2:set chassis satellite-management redundancy-groups junos-fusion-campus-network redundancy-group-id 1

Dual aggregation device overview:Understanding Junos Fusion Enterprise Components

Dual aggregation device configuration:Configuring or Expanding a Junos Fusion Enterprise

Define the chassis ID number on each aggregation device.

To define the chassis ID on aggregation device 1:set chassis satellite-management redundancy-groups chassis-id 1

To define the chassis ID on aggregation device 2:set chassis satellite-management redundancy-groups chassis-id 2

Dual aggregation device overview:Understanding Junos Fusion Enterprise Components

Dual aggregation device configuration:Configuring or Expanding a Junos Fusion Enterprise

Define the peer chassis ID number and ICL interface on each aggregation device.

To define the peer chassis ID and ICL interface on aggregation device 1:

set chassis satellite-management redundancy-groups junos-fusion-campus-network peer-chassis-id 2 inter-chassis-link xe-0/0/1

To define the peer chassis ID and ICL interface on aggregation device 2:

set chassis satellite-management redundancy-groups junos-fusion-campus-network peer-chassis-id 1 inter-chassis-link xe-0/0/1

Dual aggregation device overview:Understanding Junos Fusion Enterprise Components

Dual aggregation device configuration:Configuring or Expanding a Junos Fusion Enterprise

Add all satellite devices to the redundancy group on each aggregation device.

On aggregation device 1:

set chassis satellite-management redundancy-groups junos-fusion-campus-network satellite 130-131

set chassis satellite-management redundancy-groups junos-fusion-campus-network cluster building-1

set chassis satellite-management redundancy-groups junos-fusion-campus-network cluster building-2

Enter the same commands on aggregation device 2:

set chassis satellite-management redundancy-groups junos-fusion-campus-network satellite 130-131

set chassis satellite-management redundancy-groups junos-fusion-campus-network cluster building-1

set chassis satellite-management redundancy-groups junos-fusion-campus-network cluster building-2

Dual aggregation device overview:Understanding Junos Fusion Enterprise Components

Dual aggregation device configuration:Configuring or Expanding a Junos Fusion Enterprise

Ensure ICCP is configured:

  • Automatic ICCP provisioning. If you are not integrating your Junos Fusion Enterprise into an existing Enterprise or campus network, ICCP is automatically provisioned. No user action is required.

  • Manual ICCP configuration. If you are integrating your Junos Fusion Enterprise into an existing Enterprise or campus network, you may have to modify some ICCP setting to ensure the Junos Fusion Enterprise functions properly in your environment.

ICCP overview:Understanding ICCP in a Junos Fusion using Dual Aggregation Devices

Manual ICCP configuration:

Adding Satellite Devices (Aggregation Devices)

Install satellite software onto a satellite device that is currently running Junos OS using one of the following methods:

  • (Recommended) Autoconversion—Satellite software installed when satellite device cabled to aggregation device.

  • Manual conversion—Satellite software is installed when user enters CLI command to install satellite software.

  • Pre-installation—Satellite software is installed on satellite device before cabling it into the Junos Fusion.

    A switch may have satellite software pre-installed because it was ordered from the factory running satellite software, it was previously part of a different Junos Fusion, or a user manually installed satellite software onto the switch.

  • To enable autoconversion:

    set chassis satellite-management auto-satellite-conversion satellite 101

  • To manually convert a satellite device:

    Note:

    This command is entered from an aggregation device.

    request chassis satellite interface xe-0/0/1 device-mode satellite

  • To manually install satellite software onto a satellite device:

    Note:

    This command is entered on the satellite device before it is configured into the Junos Fusion Enterprise. Please use the platform specific satellite software package appropriate for the platform as documented in Understanding Platform-specific Satellite Software in Understanding Software in a Junos Fusion Enterprise.

Satellite software installation methods overview:Understanding Software in a Junos Fusion Enterprise

Installing satellite software:

 

Related Documentation