Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring or Expanding a Junos Fusion Enterprise

 

This topic provides the instructions needed to configure a Junos Fusion Enterprise—a Junos Fusion using EX9200 switches as aggregation devices—and to add satellite devices or an aggregation device to an existing Junos Fusion Enterprise. It covers:

Preparing the Aggregation Devices

Ensure your aggregation devices are running a version of Junos OS software that is compatible with Junos Fusion Enterprise. Junos Fusion Enterprise support was introduced for EX9200 switches in Junos OS Release 16.1R1. See Junos Fusion Hardware and Software Compatibility Matrices to learn more about Junos OS software compatibility requirements and to obtain Junos OS and satellite software for your Junos Fusion Enterprise. See Understanding Junos Fusion Enterprise Software and Hardware Requirements for additional information on Junos Fusion Enterprise hardware and software requirements.

If the aggregation device does not have the correct version of Junos OS installed, upgrade the Junos OS on both Routing Engines on your aggregation device.

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 wish to upgrade to Junos OS Release 17.1 or later, please refer to the upgrade instructions in the 17.1R1 release notes.

The following procedure shows one method of upgrading Junos OS software. The instructions assume that you know the basics of Junos OS image file management and have already acquired the target Junos OS image. The target Junos OS image can be obtained using the Junos Fusion Hardware and Software Compatibility Matrices. This upgrade procedure causes avoidable system downtime.

The number of Junos OS software upgrade options available for EX9200 switches is beyond the scope of this document. For information on Junos OS software installation options for EX9200 switches, see the Software Installation and Upgrade Guide.

To upgrade Junos OS software, enter the following commands on the aggregation device:

user@aggregation-device> request system software add aggregation-device-package-name re0
user@aggregation-device> request system software add aggregation-device-package-name re1

After performing the upgrade, reboot both Routing Engines to complete the software upgrade.

user@aggregation-device> request system reboot both-routing-engines

Preparing a Switch Running Junos OS to Become a Satellite Device

Use this procedure to prepare all switches running Junos OS software to become satellite devices. This procedure must be performed on all satellite devices, regardless of whether the satellite device will be converted into a standalone satellite device or be part of a satellite device cluster.

This section can be skipped if your satellite device or all satellite devices in your satellite device cluster are already running satellite software.

Note

The following conditions must be met before a Junos switch that is running Junos OS Release 17.1R1 can be converted to a satellite device when the action is initiated from the aggregation device:

  • The Junos switch can only be converted to SNOS 3.0 and higher.

  • The Junos switch must be either set to factory default configuration, or the following command must be included in the configuration: set chassis satellite-management auto-satellite-conversion.

To prepare a switch running Junos OS software to become a satellite device:

  1. Log into the device that will become a satellite device through the console port.
  2. Ensure the device is running a version of Junos OS that allows it to be converted into a satellite device. See Junos Fusion Hardware and Software Compatibility Matrices and Understanding Junos Fusion Enterprise Software and Hardware Requirements for information on minimum Junos OS requirements for satellite devices.Note

    In case of difficulty moving to the required versions of U-boot and JLOADER, please contact the Juniper Networks Technical Assistance Center.

    If you need to upgrade Junos OS on your satellite device before proceeding, see the Junos Fusion Hardware and Software Compatibility Matrices to obtain the software. Upgrade Junos OS before converting your switch into a satellite device.

  3. (Satellite devices providing interfaces for PoE only) If you plan on using the satellite device interfaces to provide PoE, check the satellite device’s PoE firmware version:
    • Enter the show chassis firmware detail command to learn the PoE firmware version running on the device.

    • The satellite device must have the following minimum PoE versions to support PoE in a Junos Fusion Enterprise.

      Table 1: Minimum PoE Firmware Versions

      Satellite Device PlatformMinimum PoE Firmware Version

      EX2300

      1.6.1.1.9

      EX3400

      1.6.1.1.9

      EX4300

      2.6.3.92.1

      QFX5100

      No minimum version requirement

      See Minimum Satellite Device Firmware Version Requirements table for additional information on firmware version requirements for devices in a Junos Fusion Enterprise.

    • If your device meets the minimum PoE firmware requirement, proceed to the next step.

      If a PoE firmware update is required, upgrade the PoE firmware. See Upgrading the PoE Controller Software.

  4. Zeroize the device:
    [edit]

    user@satellite-device# request system zeroize
    Note

    The device reboots to complete the procedure for zeroizing the device.

    If you are not logged into the device using the console port connection, your connection to the device is lost after entering the request system zeroize command.

    If you lose your connection to the device, log in using the console port.

  5. (EX3400 and EX4300 switch uplink ports only) After the reboot is complete, convert the built-in 40-Gbps interfaces with QSFP+ transceivers from Virtual Chassis ports (VCPs) into network ports:
    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port port-number

    For example, to convert all four built-in 40-Gbps interfaces with QSFP+ transceivers on an EX4300-24P switch into network ports:

    user@satellite-device>request virtual-chassis vc-port delete pic-slot 1 port 0

    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 1

    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 2

    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 3

    The number of built-in 40-Gbps interfaces with QSFP+ transceivers varies by switch model. See the hardware documentation for your switch.

    This step is required for the 40-Gbps interfaces with QSFP+ transceivers that will be used as uplink interfaces to directly connect to the aggregation device in a Junos Fusion Enterprise, because zeroizing the devices restores the default settings and 40-Gbps interfaces with QSFP+ transceivers on EX3400 and EX4300 switches are configured into VCPs by default. VCPs cannot be used as uplink ports to connect to aggregation devices in a Junos Fusion.

  6. Commit the configuration.
    user@satellite-device# commit

Configuring the FPC Slot IDs, Cascade Ports, and Satellite Device Clusters on the Junos Fusion

Use this procedure to configure FPC slot IDs, cascade ports, and satellite device clusters.

For more information on FPC slot IDs, cascade ports, and satellite device clusters, see Understanding Junos Fusion Enterprise Components.

This section provides separate instructions for configuring FPC slot IDs and cascade ports for standalone satellite devices and satellite devices in a satellite device cluster. A Junos Fusion Enterprise can and often does support standalone satellite devices and satellite device clusters in the same Junos Fusion topology.

This section covers the following procedures:

  1. Configuring the FPC Slot ID and Cascade Ports for a Standalone Satellite Device

  2. Configuring the FPC Slot ID, Cascade Ports, and Satellite Device Clusters for Satellite Devices in a Satellite Device Cluster

Configuring the FPC Slot ID and Cascade Ports for a Standalone Satellite Device

Use this procedure to configure the FPC slot IDs and cascade ports for standalone satellite devices, which are satellite devices that are not part of a satellite device cluster:

  1. Configure the cascade ports, and commit the configuration.

    A cascade port is a port on an aggregation device that connects to a satellite device or a satellite device cluster. Data and control traffic is passed between the aggregation device and the satellite devices over the cascade port link.

    To configure a cascade port:

    [edit]

    user@aggregation-device# set interfaces interface-name cascade-port

    where interface-name in the cascade port interface on the aggregation device.

    For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

    [edit]

    user@aggregation-device# set interfaces xe-0/0/1 cascade-port

    Commit the configuration on both Routing Engines:

    [edit]

    user@aggregation-device# commit synchronize

    or onto a single Routing Engine:

    [edit]

    user@aggregation-device# commit
  2. Configure the FPC slot ID number of each satellite device.

    In a Junos Fusion Enterprise, each satellite device, including each satellite device in a satellite device cluster, must be mapped to an FPC identifier (FPC ID). The FPC ID is in the range of 65 through 255, and it is used for Junos Fusion Enterprise 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 Enterprise.

    You can assign an FPC identifier to the satellite device based on either the satellite device’s MAC address, serial number, or cascade port.

    • To map the FPC slot ID to a standalone satellite device’s MAC address:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc slot-id system-id mac-address

      where slot-id becomes the FPC slot ID of the satellite device and mac-address is the satellite device’s MAC address. The FPC slot ID must be 65 or larger, and it functions as the FPC slot identifier.

      For example, to map FPC slot ID to the satellite device using MAC address 00:00:5E:00:53:00:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc 110 system-id 00:00:5E:00:53:00
      Note

      To find out the system MAC of the satellite device, use the show chassis mac-addresses command on the satellite device.

    • To map the FPC slot ID to a standalone satellite device’s serial number:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc slot-id serial-number serial-number

      where slot-id becomes the FPC slot ID of the satellite device and serial-number is the satellite device’s serial number. The FPC slot ID must be 65 or larger, and it functions as the FPC slot identifier.

      For instance, to map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc 101 serial-number ABCDEFGHIJKL
      Note

      To find out the serial number of the satellite device, use the show chassis hardware command on the satellite device.

    • To configure the FPC slot ID for a standalone satellite device—a satellite device not part of a satellite device cluster—to a cascade port, enter:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc slot-id cascade-ports interface-name

      where slot-id becomes the FPC slot ID of the satellite device, and interface-name is the name of the interface.

      For example, to configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:

      [edit]

      user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports xe-0/0/1

      If a prospective satellite device is connected to a Junos Fusion Enterprise without having a configured FPC slot ID, the prospective satellite device does not participate in the Junos Fusion Enterprise until an FPC ID is associated with it. The show chassis satellite unprovision output includes a list of satellite devices that are not participating in a Junos Fusion Enterprise because of an FPC ID association issue.

      The FPC slot ID configuration must match on both aggregation devices in dual-homed dual aggregation device topologies.

Configuring the FPC Slot ID, Cascade Ports, and Satellite Device Clusters for Satellite Devices in a Satellite Device Cluster

Use this procedure to configure the FPC slot IDs, cascade ports, and satellite device clusters for satellite devices in a satellite device cluster:

  1. Configure the cascade ports, and commit the configuration.

    A cascade port is a port on an aggregation device that connects to a satellite device in a satellite device cluster. An aggregation device can have multiple cascade ports connecting to multiple satellite device member switches in the same satellite device cluster. Data and control traffic is passed between the aggregation device and the satellite devices over a cascade port link.

    Best Practice

    Use the show interfaces command to confirm your interface is up before configuring it into a cascade port.

    To configure a cascade port:

    [edit]

    user@aggregation-device# set interfaces interface-name cascade-port

    For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

    [edit]

    user@aggregation-device# set interfaces xe-0/0/1 cascade-port

    Commit the configuration on both Routing Engines:

    [edit]

    user@aggregation-device# commit synchronize

    or onto a single Routing Engine:

    [edit]

    user@aggregation-device# commit
  2. Create the satellite device clusters, and assign a name and a cluster ID to each satellite device cluster:
    [edit]

    user@aggregation-device# set chassis satellite-management cluster cluster-name cluster-id cluster-id-number

    For instance, to create a satellite device cluster named building-1 and assign it cluster ID 1:

    [edit]

    user@aggregation-device# set chassis satellite-management cluster building-1 cluster-id 1

    The cluster-name and cluster-id-number specified in this step must match on both aggregation devices in dual aggregation device topologies.

  3. Define the cascade ports associated with the satellite device cluster.

    An aggregation device can have multiple cascade port connections to the satellite devices in the satellite device cluster, and it must have at least one cascade port connection to one of the satellite devices in the satellite device cluster.

    For example, to configure interfaces xe-0/0/1 and xe-0/0/2 on the aggregation device into cascade ports connecting to the satellite device cluster named building-1:

    [edit]

    user@aggregation-device# set chassis satellite-management cluster building-1 cascade-ports xe-0/0/1

    user@aggregation-device# set chassis satellite-management cluster building-1 cascade-ports xe-0/0/2
    Note

    This step defines which aggregation device ports will be used as cascade ports with the satellite device cluster only.

    The aggregation device interfaces still must be configured into cascade ports, which is accomplished in step 1 of this procedure.

  4. Configure the FPC slot ID number of each satellite device.

    In a Junos Fusion Enterprise, each satellite device, including each satellite device in a satellite device cluster, must be mapped to an FPC identifier (FPC ID). The FPC ID is in the range of 65 through 255, and it is used for Junos Fusion Enterprise 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 Enterprise.

    • To map the FPC slot ID to the MAC address of a satellite device in a satellite device cluster:

      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.

      [edit]

      user@aggregation-device# set chassis satellite-management cluster cluster-name fpc slot-ID system-id mac-address

      where cluster-name is the name of the satellite device cluster, slot-id becomes the FPC slot ID of the satellite device, and mac-address is the satellite device’s MAC address. The FPC slot ID must be 65 or larger, and it functions as the FPC slot identifier.

      For instance, to map FPC slot ID 101 to the satellite device using MAC address 00:00:5E:00:53:00, FPC slot ID 102 to the satellite device using MAC address 00:00:5E:00:53:01, and FPC slot 103 to the satellite device using MAC address 00:00:5E:00:53:02 in the satellite device cluster named building-1:

      [edit]

      user@aggregation-device# set chassis satellite-management cluster building-1 fpc 101 system-id 00:00:5E:00:53:00

      user@aggregation-device# set chassis satellite-management cluster building-1 fpc 102 system-id 00:00:5E:00:53:01user@aggregation-device# set chassis satellite-management cluster building-1 fpc 103 system-id 00:00:5E:00:53:02
    Note

    To find out the system MAC of the satellite device, use the show chassis mac-addresses command on the satellite device.

  5. Assign a member ID to each satellite device in the satellite device cluster:
    [edit]

    user@aggregation-device# set chassis satellite-management cluster cluster-name fpc fpc-slot-ID member-id member-ID-number

    For instance, to assign member ID numbers 1,2, and 3 to FPC ID numbers 101, 102, and 103 in the satellite device cluster named building-1:

    [edit]

    user@aggregation-device# set chassis satellite-management cluster building-1 fpc 101 member-id 1

    user@aggregation-device# set chassis satellite-management cluster building-1 fpc 102 member-id 2

    user@aggregation-device# set chassis satellite-management cluster building-1 fpc 103 member-id 3

    The member ID assignments for a satellite device cluster must match on both Routing Engines in a dual aggregation device topology.

  6. (Dual-homed dual aggregation device topologies only) Repeat this procedure to configure the FPC slot IDs, cascade ports, and satellite device clusters on the other aggregation device.Note

    The cluster name, ID and FPC information for each satellite device in the cluster must be the same on both aggregation devices.

Managing Software Upgrade Groups on the Aggregation Device

A satellite software upgrade group is a group of satellite devices that are designated to run the same satellite software version using the same satellite software package. One Junos Fusion Enterprise can contain multiple software upgrade groups, and multiple software upgrade groups should be configured in most Junos Fusion Enterprises to avoid network downtimes during satellite software installations.

When a satellite device is added to a Junos Fusion Enterprise, the aggregation device checks if the satellite device is using an FPC ID that is included in a satellite software upgrade group. If the satellite device is using an FPC ID that is part of a satellite software upgrade group, the device upgrades its satellite software to the version of software associated with the satellite software upgrade group - unless it is already running the defined version.

When the satellite software package associated with an existing satellite software group is changed, the satellite software for all member satellite devices is upgraded using a throttled upgrade. The throttled upgrade ensures that the aggregation device is not overwhelmed with providing satellite software simultaneously to many satellite devices.

The two most common methods for installing satellite software onto a Junos OS device—autoconverting a device into a satellite device when it is cabled into an aggregation device and manually converting a device that is cabled into an aggregation device into a satellite device—require that a satellite software upgrade group is configured.

Software upgrade groups are managed from the aggregation device. All satellite devices in a satellite device cluster are part of the same software upgrade group, and a software upgrade group with the name of the satellite device cluster is automatically created when the satellite device cluster is created.

To manage a software upgrade group:

  1. Log into the aggregation device.
  2. Download the satellite software onto both aggregation devices (recommended) or onto a remote server.

    The satellite software can be downloaded from the main Junos Fusion software download page:

    Junos Fusion - Download Software

  3. (Standalone satellite device only) Create a satellite software upgrade group, and associate the standalone satellite device with the satellite software upgrade group:
    [edit]

    user@aggregation-device# set chassis satellite-management upgrade-groups upgrade-group-name satellite slot-id-number-or-range

    where upgrade-group-name is the name of the upgrade group, and the slot-id-number-or-range is the FPC slot ID number or range of numbers, of the satellite devices that are being added to the upgrade group.

    Note

    If you enter the name of an existing satellite software upgrade group as the upgrade-group-name, the specified satellite devices are added to the existing software upgrade group.

    For example, to create a software upgrade group named group1 that includes all satellite devices numbered 101 through 120:

    [edit]

    user@aggregation-device# set chassis satellite-management upgrade-groups group1 satellite 101-120

    The satellite software upgrade group name and associated FPC slot ID configurations must match on both Routing Engines in a dual-homed dual aggregation device topology.

  4. Commit the configuration to both Routing Engines on the aggregation device:
    [edit]

    user@aggregation-device# commit synchronize

    If you are using an aggregation device with a single Routing Engine or want to commit the configuration to a single Routing Engine only:

    [edit]

    user@aggregation-device# commit

    The configuration must be committed before associating a satellite software image with the satellite software upgrade group, which is done in Step 5.

  5. Associate the satellite software upgrade group with a satellite software image.
    • Satellite device clusters:

      • Associate all satellite devices in the cluster with the automatically-created satellite software upgrade group:

        user@aggregation-device> request system software add package-name upgrade-group upgrade-group-name

        where package-name is the URL to the satellite software package, and upgrade-group-name is the name of the satellite device cluster.

        For example, to associate a satellite software image named satellite-3.0R1.2-signed.tgz that is currently stored in the /var/tmp directory on the aggregation device to the upgrade group named building1:

        user@aggregation-device> request system software add /var/tmp/satellite-3.0R1.2-signed.tgz upgrade-group building1
    • Standalone satellite devices:

      • Associate the satellite device with the previously-configured satellite software upgrade group:

        user@aggregation-device> request system software add package-name upgrade-group upgrade-group-name

        where package-name is the URL to the satellite software package, and upgrade-group-name is the name of the upgrade group that was assigned by the user earlier in this procedure.

        For example, to associate a satellite software image named satellite-3.0R1.2-signed.tgz that is currently stored in the /var/tmp directory on the aggregation device to the upgrade group named group1:

        user@aggregation-device> request system software add /var/tmp/satellite-3.0R1.2-signed.tgz upgrade-group group1

    Associating a satellite software image to a new satellite software package can trigger a satellite software upgrade. A throttled satellite software upgrade might begin after entering the request system software add command to associate a satellite software package with a satellite software upgrade group. A satellite software upgrade might also be triggered when a configuration that uses the satellite software upgrade group is committed.

  6. (Dual-homed dual aggregation device topology only) Repeat Steps 1 through 4 using the exact same configuration—including the same package-name and upgrade-group-name—to configure software upgrade groups on the second aggregation device.

    The software upgrade group configurations must match in dual aggregation topologies for the satellite software upgrade to proceed. If you do not associate the software upgrade group on the second aggregation device with a satellite software version, then the satellite device software upgrade will be managed only by the other aggregation device. If you associate the software upgrade group on the second aggregation with a satellite software version, then the satellite software version must be the same on both aggregation devices.

Configuring the Dual Aggregation Device Topology (Dual Aggregation Device Topologies Only)

Use this procedure to connect and configure a second aggregation device into a Junos Fusion Enterprise topology.

Before you begin:

  • Ensure that a Junos Fusion topology has already been configured, and that the topology includes a satellite software upgrade group.

  • Ensure that the aggregation devices are already cabled together and that all cabling to all satellite devices has been completed for both aggregation devices. For information on cabling requirements, see Understanding Junos Fusion Enterprise Software and Hardware Requirements.

  1. (Required only if aggregation device was previously configured into single home mode) Delete single home configuration mode:

    On aggregation device 1 and 2:

    [edit]

    user@aggregation-device# delete chassis satellite-management single-home
    Note

    Single home mode is not supported in a dual-aggregated device Junos Fusion Enterprise topology.

  2. Create and configure a redundancy group on the first aggregation device.

    A dual aggregation device topology in a Junos Fusion is a multichassis link aggregation group (MC-LAG) that uses the Inter-Chassis Communications Protocol (ICCP) to communicate between the aggregation devices. ICCP is typically used in an MC-LAG to exchange information between MC-LAG peers. The MC-LAG peers in a Junos Fusion dual aggregation topology are the aggregation devices.

    A redundancy group is required to enable ICCP in a Junos Fusion. A Junos Fusion topology supports one redundancy group that includes two member devices—the aggregation devices—while also including a configuration parameter that allows users to specify that the satellite devices or satellite clusters also belong to the redundancy group.

    Note

    All satellite devices, whether standalone satellites or satellite clusters, must be associated to a redundancy group on both aggregated devices; otherwise, they act as single-homed devices, which are not supported in a dual-aggregation device Junos Fusion Enterprise topology.

    To create and configure the redundancy group on the first aggregation device:

    1. Specify the redundancy group ID number on both aggregation devices. The redundancy group name is created and named as part of this process.

      The redundancy group ID number and name must match on both aggregation devices.

      On aggregation device 1 and 2:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set redundancy-group-name redundancy-group-id redundancy-group-id-number

      For instance, to create a redundancy group named junos-fusion-campus-network that uses redundancy group ID 1 on aggregation device 1:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set junos-fusion-campus-network redundancy-group-id 1

      Repeat this procedure on aggregation device 2:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set junos-fusion-campus-network redundancy-group-id 1

    2. Define the chassis ID number of the each aggregation device:
      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set chassis-id chassis-id-number

      For instance, to assign the aggregation device 1 the chassis ID of 1 for the junos-fusion-campus-network redundancy group:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set chassis-id 1

      To assign aggregation device 2 the chassis ID of 2 for the junos-fusion-campus-network redundancy group:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set chassis-id 2

      The chassis ID numbers cannot match and are used to create the ICL that interconnects the aggregation device in the Junos Fusion topology.

    3. Define the peer chassis ID number—the chassis ID number of the other aggregation device—and interface to use for the ICL:
      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set redundancy-group-name peer-chassis-id peer-chassis-id-number inter-chassis-link interface-name

      For instance, to use the xe-0/0/1 interface on aggregation device 1 to create an ICL that connects to aggregation device 2:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set junos-fusion-campus-network peer-chassis-id 2 inter-chassis-link xe-0/0/1

      To complete the configuration by defining the peer chassis ID and interface on aggregation device 2:

      [edit chassis satellite-management redundancy-groups]

      user@aggregation-device# set junos-fusion-campus-network peer-chassis-id 1 inter-chassis-link xe-0/0/1

      The ICL is used to pass traffic between the aggregation devices.

    4. Define the satellite devices that are part of the redundancy group.

      You can add a standalone satellite device or a satellite device cluster to the redundancy group in this step.

      The satellite devices added to the redundancy group in this step must match on both redundancy groups.

      All satellite devices in the Junos Fusion should be added to the redundancy group in this step.

      • To add standalone satellite devices to the redundancy group:
        [edit chassis satellite-management redundancy-groups]

        user@aggregation-device# set redundancy-group-name satellite satellite-device-fpc-IDs

        For instance, to include satellite devices using FPC IDs 100-140 in the redundancy group:

        [edit chassis satellite-management redundancy-groups]

        user@aggregation-device# set junos-fusion-campus-network satellite 100-140

      • To add a satellite device cluster to the redundancy group:
        [edit chassis satellite-management redundancy-groups]

        user@aggregation-device# set redundancy-group-name cluster cluster-name

        For instance, to include satellite device cluster building-1 to the redundancy group:

        [edit chassis satellite-management redundancy-groups]

        user@aggregation-device# set junos-fusion-campus-network cluster building-1

        Repeat the same configuration steps on the other aggregation device.

        For instance:

        [edit chassis satellite-management redundancy-groups]

        user@aggregation-device# set junos-fusion-campus-network satellite 100-140

        user@aggregation-device# set junos-fusion-campus-network cluster building-1
  3. (Recommended) Ensure at least one link besides the ICL is connecting the aggregation devices. This link automatically becomes the ICCP link.

    An ICCP link can be one link or an aggregated ethernet interface. In most Junos Fusion Enterprise deployments, we recommend using a 40-Gbps link or an aggregated ethernet interface as the ICCP link.

    An ICCP link is recommended but is optional because ICCP traffic is transmitted across the ICL when a dedicated ICCP link is not configured.

    ICCP configuration is not required. ICCP is automatically provisioned in a Junos Fusion using dual aggregation devices, by default. User configuration of ICCP is not required and is only recommended for expert users.

    If you configure an ICCP parameter in a Junos Fusion, the user-configured parameter overrides the automatically provisioned parameter for the configured parameter only.

    You can disable automatic ICCP provisioning using the no-auto-iccp-provisioning statement.

    If you decide to configure ICCP, you must configure matching configurations on both aggregation devices.

    Note

    ICCP configuration is beyond the scope of this document. See Unresolved topic-ref: "129944".

  4. Configure ICCP.

    ICCP can be configured in one of the following ways:

    • Automatic ICCP provisioning

      Automatic ICCP provisioning 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.

      No user action is required to configure ICCP if automatic ICCP provisioning is used.

    • Manual ICCP configuration.

      Manual ICCP configuration is typically used to integrate a Junos Fusion Enterprise into an existing network or by expert users that want to finely tune ICCP settings.

      Many Junos Fusion Enterprise installations occur in brownfield deployments and the Junos Fusion Enterprise has to be integrated into an existing Enterprise 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 network that includes other MC-LAG topologies. ICCP must be configured manually in these scenarios.

      See Unresolved topic-ref: "129944" for the steps and options available to configure ICCP.

      If you configure an ICCP parameter in a Junos Fusion, the user-configured parameter overrides the automatically provisioned parameter for the configured parameter only. You can disable all automatic ICCP provisioning using the no-auto-iccp-provisioning statement.

      If you decide to manually configure ICCP, you must configure matching configurations on both aggregation devices.

Installing Satellite Software and Adding Satellite Devices to the Junos Fusion

Use this procedure to install satellite software onto a satellite device. A satellite device is not active in a Junos Fusion until satellite software is installed.

Before you begin:

  • Ensure you have prepared your satellite device, as described in the “Preparing a Switch Running Junos OS to Become a Satellite Device” section.

  • Ensure that the satellite software package is compatible with the aggregation device software. See Junos Fusion Hardware and Software Compatibility Matrices at https://www.juniper.net/support/downloads/solutions/fusion/.

  • Ensure the minimum satellite device version requirements are met. For information on requirements, see Understanding Junos Fusion Enterprise Software and Hardware Requirements.

  • Complete the other steps in this document—created cascade ports, associated FPC slot IDs with satellite devices, and created the satellite software upgrade groups—to ensure the satellite software can be successfully installed.

To install satellite software onto a satellite device and add it to the Junos Fusion Enterprise.

  1. Decide how satellite software will be installed onto the satellite devices:
    • Autoconversion(Recommended)—Satellite software is installed onto satellite device automatically when it is cabled to the aggregation device.

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

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

  2. Install the satellite software, or configure how it will be installed:
    • To enable autoconversion for a standalone satellite device or a satellite device in a satellite device cluster, enter the following commands from an aggregation device:

      [edit]

      user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite slot-id

      user@aggregation-device# commit

      For example, to automatically convert FPC 101 into a satellite device:

      [edit]

      user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite 101

      user@aggregation-device# commit

      In this example, autoconversion installs the satellite software associated with FPC slot 101, which was defined in the satellite software upgrade group configuration.

      The process to install the satellite software onto the satellite device with the specified FPC slot ID does not begin until the configuration is committed.

    • To manually install satellite software onto a satellite device, enter the following command from an aggregation device:

      user@aggregation-device> request chassis satellite interface interface-name device-mode satellite

      where interface-name is one of the following values:

      • standalone satellite device: the interface-name is the cascade port interface on the aggregation device.

      • satellite device in satellite device cluster that is directly cabled to the aggregation device: the interface-name is the cascade port interface on the aggregation device.

      • satellite device in satellite device cluster that is not directly cabled to an aggregation device: the interface-name is a clustering port—a port on a satellite device in a satellite device cluster that interconnects satellite devices—on a satellite device.

      For example, to manually configure the switch that is connecting the satellite device to interface xe-0/0/1 on the aggregation device into a satellite device:

      user@aggregation-device> request chassis satellite interface xe-0/0/1 device-mode satellite

      To manually configure a switch connecting to interface xe-101/2/0 on a satellite device in a satellite device cluster into a satellite device:

      user@aggregation-device> request chassis satellite interface xe-101/2/0 device-mode satellite
    • To pre-install software onto a satellite device before connecting it into the Junos Fusion Enterprise:

      1. Copy a version of satellite software onto the satellite device running Junos OS.

        For EX2300, EX3400, and EX4300 switches, you must install a platform specific satellite software image in order to pre-install satellite software. See Understanding the Platform Specific Satellite Software Image in Understanding Software in a Junos Fusion Enterprise.

        Satellite software images can be downloaded from the Junos Fusion software download page.

      2. Enter the following command from the satellite device:
        user@satellite-device> request chassis device-mode satellite URL-to-satellite-software

        For instance, to install the satellite software package satellite-ppc-3.0R1.2-signed.tgz stored in the /var/tmp/ folder on an EX4300 switch:

        user@satellite-device> request chassis device-mode satellite /var/tmp/satellite-ppc-3.0R1.2-signed.tgz
      3. Cable the satellite device directly to the aggregation device or into a satellite device cluster.Note

        The satellite device version is compared against the satellite device version associated with the software upgrade group upon insertion into the Junos Fusion. If the satellite device is running a version of satellite software that is different than it’s associated satellite software upgrade group, the satellite software upgrade group installs the satellite software associated with the satellite software upgrade group onto the satellite device.

      The procedure for adding a satellite device running satellite software into a Junos Fusion is also covered in Adding a Switch Running Satellite Software to a Junos Fusion Enterprise.