Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configuring Junos Fusion Provider Edge

This topic provides the instructions needed to configure a Junos Fusion Provider Edge. The instructions in this topic can also be used to add a new satellite device to a Junos Fusion Provider Edge after initial installation. It covers:

Preparing the Aggregation Device

This section provides instructions on the required steps to prepare a switch to become the aggregation device in a Junos Fusion Provider Edge.

This section does not discuss the cascade port, FPC slot identification, or the software upgrade group configuration, which are important elements of preparing your aggregation device for a Junos Fusion Provider Edge installation and are discussed in Configuring the Cascade Ports on the Aggregation Device, Configuring the FPC Slot Identifiers, and Configuring Software Upgrade Groups on the Aggregation Device. The instructions for adding satellite devices to the Junos Fusion Provider Edge are also provided later in this topic.

To prepare your aggregation device for a Junos Fusion Provider Edge:

  1. Enable Enhanced IP:
  2. Configure the Junos Fusion into single home mode:
    Note:

    Configuring the Junos Fusion into single home mode using this step is optional when the aggregation device is running Junos OS Release 14.2R5 or later.

    Configuring the Junos Fusion into single home mode is required when the aggregation device is running Junos OS Release 14.2R3 or 14.2R4.

  3. Commit the configuration to both Routing Engines:

    If you are using an aggregation device with a single Routing Engine:

  4. Ensure your aggregation device is running a version of Junos OS software that is compatible with Junos Fusion Provider Edge, such as Junos OS Release 14.2R3 or later. If the aggregation device does not have the correct version installed, upgrade your aggregation device.
  5. Reboot both Routing Engines:

    A reboot is required to enable enhanced IP.

    If you only want to reboot a single Routing Engine:

    Reboot the other Routing Engine at a later time to ensure it is ready to manage the Junos Fusion in the event of a Routing Engine switchover.

Configuring the Cascade Ports on the Aggregation Device

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

A cascade port must be configured before a satellite device is recognized by the Junos Fusion Provider Edge. Cascade port configuration, therefore, is always a required step for configuring a Junos Fusion Provider Edge.

To configure a cascade port or ports:

  1. Log in to the aggregation device.
  2. Configure the interface on the aggregation device side of the link into a cascade port:

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

  3. Commit the configuration:

    If you want to commit the configuration to both Routing Engines:

Configuring the FPC Slot Identifiers

In a Junos Fusion, each satellite device must be mapped to an FPC identifier (FPC ID). The FPC ID 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—a gigabit Ethernet interface on a satellite device that is using 101 as it’s FPC ID— uses ge-101/0/2 as it’s interface name. The 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.

A Junos Fusion Provider Edge provides two methods of assigning an FPC identifier: Unique-ID based FPC identification and connectivity-based FPC identification. Unique-ID based FPC identification maps an FPC slot ID to a satellite device’s MAC address or serial number, while Unique-ID based FPC identification maps an FPC slot ID to a cascade port. Both options are discussed in Understanding Junos Fusion Provider Edge Components.

  • To configure the FPC slot ID using connectivity-based FPC identification, enter:

    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:

  • To configure the FPC slot ID using unique-ID based FPC identification, use one of the following options:

    • To map the FPC slot ID to a satellite device’s 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 functions as the FPC slot identifier.

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

    • To map the FPC slot ID to a satellite device’s 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 functions as the FPC slot identifier.

      For example, to map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:

If a prospective satellite device is connected to a Junos Fusion Provider Edge without having a configured FPC slot ID, the prospective satellite device does not participate in the Junos Fusion Provider Edge 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 Provider Edge due to an FPC ID association issue.

Configuring Software Upgrade Groups on the Aggregation Device

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. One Junos Fusion can contain multiple software upgrade groups, and multiple software upgrade groups should be configured in most Junos Fusions to avoid network downtimes during satellite software installations.

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

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 only a few satellite devices are updated at a time to minimize the effects of a traffic disruption due to too many satellite devices upgrading software simultaneously.

The two most common methods of installing satellite software onto an aggregation 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 configured and managed from the aggregation device.

To configure a software upgrade group:

  1. Log in to the aggregation device.
  2. Create the software upgrade group, and add the satellite devices to the group.

    where upgrade-group-name is the name of the upgrade group, and the slot-id-number-or-range is FPC slot ID number or range of numbers, of the satellite devices that are being added to the upgrade group. If you enter an existing upgrade group name as the upgrade-group-name, you add new satellite devices 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:

  3. Commit the configuration to both Routing Engines on the aggregation device:

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

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

  4. Associate a satellite software package with the software upgrade group:

    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-1.0R1.1-signed.tgz that is currently stored in the /var/tmp directory on the aggregation device to the upgrade group named 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.

Preparing the Satellite Device

This section discusses the steps that must be performed on a standalone switch before converting it into a satellite device in a Junos Fusion Provider Edge.

To perform this procedure:

These instructions assume your device is already running Junos OS Release 14.1X53-D16 or later.

  1. Log in to the device using the console port.
  2. Zeroize the device:
    Note:

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

    If you are not logged in to 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, login using the console port.

  3. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:

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

    This step is required for the 40-Gbps QSFP+ interfaces that will be used as uplink interfaces in a Junos Fusion.

    This step is needed because the built-in 40-Gbps QSFP+ interfaces on EX4300 switches are configured into VCPs by default, and the default settings are restored after the device is zeroized.

    The number of built-in 40-Gbps QSFP+ interfaces varies by EX4300 switch model. See EX4300 Switches Hardware Overview.

Adding Satellite Devices to the Junos Fusion Provider Edge

This section discusses the processes for adding satellite devices to a Junos Fusion Provider Edge.

A switch must be running the satellite software to operate as a satellite device. The instructions in this procedure include the required steps to install the satellite software onto your satellite device.

You can add satellite devices to your Junos Fusion Provider Edge using one of the following procedures:

Autoconverting a Switch into a Satellite Device

Use this procedure to automatically configure a switch into a satellite device when it is cabled into the aggregation device.

You can use the autoconversion procedure to add one or more satellite devices to your Junos Fusion topology. The autoconversion procedure is especially useful when you are adding multiple satellite devices to your Junos Fusion, because it allows you to easily configure the entire topology before or after cabling the satellite devices to the aggregation devices.

Before you begin:

  • Ensure that your aggregation device is running Junos OS Release 14.2R3 or later, and that the satellite devices are running Junos OS Release 14.1X53-D16 or later.

  • Ensure that you have prepared your satellite device for the installation, following the instructions in Preparing the Satellite Device.

To autoconvert a switch into a satellite device:

  1. Cable a link between the aggregation device and the satellite device, if desired.
    Note:

    You can cable the aggregation device to the satellite device at any point in this procedure.

    When the aggregation device is cabled to the satellite device during this procedure, the process for converting a switch into a satellite device to finalize this process occurs immediately.

    If the aggregation device is not cabled to the satellite device, the process for converting a switch into a satellite device to finalize this process starts when the satellite device is cabled to the aggregation device.

  2. Log in to the aggregation device.
  3. Configure the cascade ports. See Configuring the Cascade Ports on the Aggregation Device.

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

  4. Associate an FPC slot ID with each satellite device.

    There are multiple methods of assigning FPC slot IDs. See Configuring the FPC Slot Identifiers.

    Examples:

    • To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:

    • To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:

    • To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:

  5. (Recommended) Configure an alias name for the satellite device:

    where slot-id is the FPC slot ID of the satellite device defined in the previous step, and alias-name is the alias.

    For example, to configure the satellite device numbered 101 as qfx5100-48s-1:

  6. Configure an FPC slot ID into a software upgrade group. See Configuring Software Upgrade Groups on the Aggregation Device.

    For example, to add the satellite device using FPC slot ID 101 to an existing software group named group1, or create a software upgrade group named group1 and add the satellite device using FPC slot 101 to the software upgrade group:

    If you are creating a new software upgrade group in this step, you also need to associate the group with a satellite software image. You can skip this final step if the software upgrade group has already been created and a satellite software package association exists.

    The configuration with the satellite software upgrade group must be committed before a satellite software image is associated with a satellite software upgrade group:

    After committing the configuration, associate a satellite software image named satellite-1.0R1.1-signed.tgz to the upgrade group named group1:

  7. Enable automatic satellite conversion:

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

  8. Commit the configuration:

    If you want to commit the configuration to both Routing Engines:

    The satellite software upgrade on the satellite device begins after this final step is completed, or after you cable the satellite device to a cascade port using automatic satellite conversion if you have not already cabled the satellite device to the aggregation device.

    After the satellite software update, the switch operates as a satellite device in the Junos Fusion.

Manually Converting a Switch into a Satellite Device

Use this procedure to manually convert a switch into a satellite device after cabling it into the Junos Fusion Provider Edge.

This procedure should be used to convert a switch that is not currently acting as a satellite device into a satellite device. A switch might not be recognized as a satellite device for several reasons, including that the device was not previously autoconverted into a satellite device or that the switch had previously been reverted from a satellite device to a standalone switch.

Before you begin:

  • Ensure that your aggregation device is running Junos OS Release 14.2R3 or later, and that the switches that will become satellite devices are running Junos OS Release 14.1X53-D16 or later.

  • Ensure that you have prepared your switches that will become satellite devices for the installation, following the instructions in the Preparing the Satellite Device section.

To manually convert a switch into a satellite device:

  1. Cable a link between the aggregation device and the satellite device.
  2. Log in to the aggregation device.
  3. Configure the link on the aggregation device into a cascade port, if you have not done so already. See Configuring the Cascade Ports on the Aggregation Device.

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

  4. Associate an FPC slot ID with the satellite device.

    There are multiple methods of assigning FPC slot IDs. See Configuring the FPC Slot Identifiers.

    Examples:

    • To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:

    • To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:

    • To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:

  5. Configure the interface on the aggregation device into a software upgrade group. See Configuring Software Upgrade Groups on the Aggregation Device.

    For example, to add the satellite device using FPC slot ID 101 to an existing software group named group1, or create a software upgrade group named group1 and add the satellite device using FPC slot 101 to the software upgrade group:

    If you are creating a new software upgrade group in this step, you also need to associate the group with a satellite software image. You can skip this final step if the software upgrade group has already been created and a satellite software package association exists.

    The configuration with the satellite software upgrade group must be committed before a satellite software image is associated with the satellite software upgrade group:

    After committing the configuration, associate a satellite software image named satellite-1.0R1.1-signed.tgz to the upgrade group named group1:

  6. Commit the configuration:

    If you want to commit the configuration to both Routing Engines:

  7. Manually configure the switch into 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:

    The satellite software upgrade on the satellite device begins after this final step is completed.

    After the satellite software update, the switch operates as a satellite device in the Junos Fusion Provider Edge.

Configuring a Switch into a Satellite Device Before Interconnecting It into a Junos Fusion Provider Edge

Before you begin:

  • Ensure that your switch that will become a satellite device is running Junos OS Release 14.1X53-D16 or later. See Installing Software Packages on QFX Series Devices for information on upgrading Junos OS on your device.

  • Ensure that you have copied the satellite software onto the device that will become a satellite device.

Use this procedure to install the satellite software onto a switch before interconnecting it into the Junos Fusion Provider Edge as a satellite device. Installing the satellite software on a switch before interconnecting it into the Junos Fusion Provider Edge allows you to more immediately deploy the switch as a satellite device by avoiding the downtime associated with the satellite software installation procedure in the Junos Fusion Provider Edge.

You can manually install the satellite software onto a switch by entering the following command:

For instance, to install the satellite software package satellite-1.0R1.1-signed.tgz stored in the /var/tmp/ folder on the switch:

The device will reboot to complete the satellite software installation.

After the satellite software is installed, follow this procedure to connect the switch into the Junos Fusion Provider Edge:

  1. Log in to the aggregation device.
  2. Configure the link on the aggregation device into a cascade port, if you have not done so already. See Configuring the Cascade Ports on the Aggregation Device.

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

  3. Associate an FPC slot ID with the satellite device.

    There are multiple methods of assigning FPC slot IDs. See Configuring the FPC Slot Identifiers.

    Examples:

    • To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:

    • To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:

    • To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:

  4. Configure the satellite switch into a satellite software upgrade group that is using the same version of satellite software that was manually installed onto the switch. See Configuring Software Upgrade Groups on the Aggregation Device.

    This step is advisable, but not always required. Completing this step ensures that the satellite software on your device is not upgraded to the version of satellite software associated with the satellite software upgrade group upon installation.

  5. Commit the configuration to both Routing Engines:

    If you want to commit the configuration to a single Routing Engine:

  6. Cable a link between the aggregation device and the satellite device.

Related Documentation