Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for Junos Fusion Data Center

 

These release notes accompany Junos OS Release 18.1R3 for the Junos Fusion Data Center. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os

New and Changed Features

This section describes the new features and enhancements to existing features in Junos OS Release 18.1R3 for Junos Fusion Data Center.

Release 18.1R3 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos OS Release 18.1R3.

Release 18.1R2-S2 New and Changed Features

Class of Service

  • Class of service support (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, Junos Fusion Data Center supports the standard Junos class of service (CoS) features and operational commands in a quad-aggregation device configuration. Each extended port on a satellite device is a logical extension to the aggregation device. Therefore, the default CoS policy on the aggregation device applies to each extended port. You can also create standard CoS policies for extended ports.

    A cascade port is a physical port or interface on an aggregation device that provides a connection to a satellite device. Port scheduling is supported on cascade ports. Junos Fusion technology reserves a separate set of queues with minimum bandwidth guarantees for in-band management traffic to protect against congestion caused by data traffic.

    [See Understanding CoS in Junos Fusion Data Center.]

EVPN

  • Designated event forwarding of SNMP traps in an EVPN topology (Junos Fusion Data Center)—Starting with Junos OS Release 18.1R2-S2, you can enable SNMP on the aggregation device and designate trap forwarding in an EVPN topology in Junos Fusion Data Center. In an EVPN topology, the satellite device generates an SNMP trap event when a change occurs on any of the associated satellite devices. This trap event information is sent to all connected aggregation devices who then sends the trap request to the SNMP server. Because each aggregation devices sends its own copy of the trap, the SNMP server receives multiple copies of the trap for the same event on the satellite device, thereby causing overhead to the SNMP server. To prevent the trap from being generated for each aggregation device, you can enable designated trap forwarding so that the trap request is only sent by the aggregation device selected as the designated router. You enable designate trap forwarding under the [satellite-management] hierarchy. Designated event forwarding is disabled by default.

    [See Understanding Designated Event Forwarding of SNMP Traps in an EVPN Junos Fusion Data Center.]

Interfaces and Chassis

  • Configuration synchronization for up to four aggregation devices (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, configuration synchronization enables you to easily propagate, synchronize, and commit configurations from one aggregation device (AD) to another AD. Log in to either AD to manage the other three ADs, and use configuration groups to simplify the configuration process. You can create one configuration group each for the local ADs, and a global configuration common to all ADs.

    Create conditional groups to specify when configurations are synchronized. Enable peers-synchronize at the [edit system commit] hierarchy to synchronize configurations and commits across ADs by default. NETCONF over SSH provides a secure connection between ADs. Secure Copy Protocol (SCP) copies configurations securely between them.

    [See Understanding Multichassis Link Aggregation Group Configuration Consistency Check.]

  • Increased number of aggregated Ethernet interfaces (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, you can configure up to 1750 aggregated Ethernet interfaces for a Junos Fusion Data Center system. To configure, include the device-count statement with a value of 1000 at the [edit chassis aggregated-devices ethernet] hierarchy level and add member links in each bundle.

    [See Understanding Link Aggregation and Link Aggregation Control Protocol in a Junos Fusion.]

Junos Fusion Data Center

  • Junos Fusion Data Center with four aggregation devices and EVPN infrastructure (Junos Fusion Data Center)—Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center supports four aggregation devices to which each satellite device can be multihomed in active-active mode. In this topology, the four aggregation devices comprise a core fabric in which Ethernet VPN (EVPN) is implemented as the control plane in which host and server MAC addresses, network reachability, and other states learned by an aggregation device are advertised to the other aggregation devices. For the data plane, the aggregation devices use Virtual Extensible LAN (VXLAN) encapsulation when forwarding a Layer 2 data packet to other aggregation devices. Namely, an aggregation device encapsulates a data packet in a VXLAN UDP header and sends the packet by means of the Layer 3 network to another aggregation device. Upon receipt of the packet, the aggregation device de-encapsulates the packet and forwards it as appropriate.

    Junos Fusion Data Center with four aggregation devices and an EVPN architecture implements IEEE 802.1BR processing between the aggregation devices and satellite devices.

    [See Understanding EVPN in a Junos Fusion Data Center.]

  • Layer 2 unicast forwarding on extended ports (Junos Fusion Data Center)—Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center supports Layer 2 unicast forwarding on extended ports. When a remote MAC address is learned from a Type-2 MAC route advertisement, the aggregation device determines the corresponding extended port next hop from the Ethernet Segment Identifier (ESI) carried in the MAC route advertisement. This extended port next hop is resolved in the set of local cascade interfaces that are used to reach that extended port. Traffic sent to a destination extended port only traverses the EVPN tunnel if the destination extended port cannot be resolved to a local cascade interface. For non-extended port destinations located on a remote aggregation device (or external Provider Edge (PE) device in the same EVPN), traffic is carried in the EVPN tunnel. When EVPN MAC aliasing is enabled, aggregation devices signal their reachability towards the destination extended port using the per-EVI Ethernet A-D route, so that a list of aggregation devices can be built for load-balancing even if those aggregation devices have not advertised that specific MAC route.

    [See Understanding EVPN in a Junos Fusion Data Center.]

  • Satellite device support (QFX5110 and QFX5200)—Starting with Junos OS Release 18.1R2-S2, you can configure QFX5110-48S and QFX5200-32C switches as satellite devices in a Junos Fusion Data Center topology. The satellite device in a Junos Fusion topology is managed and configured by the aggregation device. Junos Fusion Data Center uses QFX10002, QFX10008 and QFX10016 switches in the aggregation device role.

    [See Junos Fusion Data Center Software and Hardware Requirements.]

  • Flow-based uplink selection (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, you can configure flow-based uplink selection for satellite devices by defining a chassis group to which the uplink traffic flows will be directed.

    [See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.]

Multicast

  • Layer 2 multicast support with local replication in an EVPN topology (Junos Fusion Data Center)—Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center with EVPN combines elements of an EVPN multicast infrastructure with 802.1BR local replication to support Layer 2 multicast forwarding. In this environment, each extended port on a satellite device is multihomed to all aggregation devices and modeled as an EVPN Ethernet Segment (ES). One aggregation device is elected as the designated forwarder (DF) for each ES (based on the extended port’s satellite device DF), and the IGMP snooping state is synchronized on all aggregation devices connected to that ES for faster convergence when DF re-election is required.

    To forward multicast traffic, a source aggregation device employs local bias forwarding towards any locally reachable extended port multicast destinations, and uses ingress replication to the other aggregation devices in the EVPN/VxLAN tunnel acting as DFs for other ES destinations. Any forwarding aggregation device also uses 802.1BR local replication to destination satellite devices if you configure the local-replication statement at the [edit forwarding-options satellite] hierarchy level. Local replication, also referred to as egress replication at the satellite devices, helps distribute packet replication load and reduce traffic on cascade ports for multicast traffic by having the forwarding aggregation device send only one copy of a packet to each satellite device that has an extended port in the multicast group, and the satellite device then does the replication for its local extended ports.

    [See Multicast Forwarding at Layer 2 in a Junos Fusion Data Center with EVPN.]

  • Layer 3 multicast support in an EVPN topology (Junos Fusion Data Center)— Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center with EVPN includes support for sending Layer 3 multicast traffic between extended ports, or link aggregations of extended ports, that are located in different VLANs. Instead of running PIM on the aggregation devices, IGMP reports are sent to the gateways.

    In the EVPN topology, two or more satellite devices are multihomed to four QFX10002 aggregation devices, and a multicast VLAN is provisioned between the aggregation devices and the external gateways. Both the source and receiver ports can be inside the fabric, or one can be external to the fabric while the other is internal. Likewise, participating servers can be connected to the fabric through the same or different tenants (in which case traffic must transit an external gateway so the gateway can handle the routing between tenants).

    [See Multicast Forwarding at Layer 3 in a Junos Fusion Data Center with EVPN.]

  • VLAN flooding support with local replication in an EVPN topology (Junos Fusion Data Center)—Starting with Junos OS Release 18.1R2-S2, Junos Fusion Data Center with EVPN combines elements of an EVPN multicast infrastructure with 802.1BR local replication to support Layer 2 VLAN flooding. Local replication helps distribute packet replication load and reduce traffic on cascade ports for multicast and flooded VLAN traffic. In this environment, each extended port on a satellite device is multihomed to all aggregation devices and modeled as an EVPN Ethernet Segment (ES). One aggregation device is elected as the designated forwarder (DF) for each ES (based on the extended port’s satellite device DF).

    An aggregation device might initiate VLAN flooding (broadcasting or flooding the packet out to all interfaces in the VLAN) to learn the MAC address for a destination that is not already in its Ethernet switching tables. With local replication enabled, the aggregation device requests multicast ECIDs to represent the extended ports in the VLAN on each satellite device. You configure 802.1BR local replication to destination satellite devices by configuring the local-replication statement at the [edit forwarding-options satellite] hierarchy level.

    [See local-replication.]

Port Security

  • Storm control on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, storm control is supported on the extended ports of the satellite device in a Junos Fusion Data Center. You can configure storm control from the aggregation device to rate-limit broadcast traffic, multicast traffic, and unknown unicast traffic level so that the fabric drops packets when the specified traffic level is exceeded, thus preventing packets from proliferating and degrading the LAN. You specify the storm control level as the traffic rate in kilobits per second (Kbps) of the combined traffic streams, or as the percentage of available link bandwidth used by the combined traffic streams. If the storm control is exceeded, you can also configure the extended ports to shut down interfaces by using the action-shutdown command, or by temporarily disabling the interfaces by using the port-error-disable command. Additionally, you can disable storm control on registered or unregistered multicast traffic.

    [See Understanding Storm Control.]

  • Firewall filter support on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release 18.1R2-S2, you can configure firewall filters on extended ports in a Junos Fusion Data Center. An extended port is a physical interface on the satellite device that is managed through the aggregation device. From the aggregation device, you can configure a firewall filter to accept or discard a packet before it enters or exits the port. If a packet is accepted, you can configure additional actions to perform on the packet, such as class-of-service (CoS) marking (grouping similar types of traffic together and treating each type of traffic as a class with its own level of service priority) and traffic policing (controlling the maximum rate of traffic sent or received).To use a firewall filter, you must first configure the filter and then apply it to the port. Firewall filters are defined under the [edit firewall] hierarchy level. This feature was previously supported in an "X" release of Junos OS.

    [See Overview of Firewall Filters.]

Storage

  • DCBX Version 1.01 sequence number TLV mapping for multiple aggregation devices (Junos Fusion Data Center)—Starting in Junos OS 18.1R2-S2, to ensure Junos Fusion Data Center with EVPN appears as a single device to a DCBX Version 1.01 peer, satellite devices maintain a sequence number TLV mapping table to coordinate DCBX message sequence numbers with those on multiple aggregation devices. The satellite device maintains a local sequence number that is exchanged with the DCBX peer, and maps that value to and from each aggregation device’s corresponding local sequence number before relaying DCBX messages in either direction. The show dcbx neighbors interface interface-name command displays both the aggregation device local sequence number (in the sequence-number field) and the satellite device local sequence number (in the satellite sequence-number field) in the Local-Advertisement section of the output. In addition, the peer-chassis sequence-number field displayed with dual aggregation devices for Junos Fusion Data Center with MC-LAG is no longer included that section of the output.

    [See Understanding DCBX on Junos Fusion Data Center.]

Release 18.1R2 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos OS Release 18.1R2.

Release 18.1R1 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos OS Release 18.1R1.

Changes in Behavior and Syntax

There are no changes in behavior and syntax for Junos Fusion Data Center in Junos OS Release 18.1R3.

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 18.1R3 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Junos Fusion Data Center

  • The license installed will not be deleted, unless it is explicitly deleted using the request command. After disabling the cascade port, the license count will be marked as zero only after the satellite information is purged from the neighbor database. Previously, this satellite neighbor information persisted only for 8 minutes; now, neighbor information is being held for 8 hours. This time delay is introduced to avoid repeating the initial recognition of the satellite device for interface-down events. As a workaround, delete the FPC instance for the satellite device to see the license removed for the corresponding satellite device. PR1192886

  • In a Junos Fusion Data Center, auto-channelization is not supported on 100G interfaces. As a workaround, you can set the channelization using the channel-speed CLI statement at the [edit policy-options satellite-policies extended-ports-template template-name pic pic-number port port-number] hierarchy level.

  • The license installed will not be deleted, unless it is explicitly deleted using the request command. After disabling the cascade port, the license count will be marked as zero only after the satellite information is purged from the neighbor database. Previously this satellite neighbor information persisted for only for 8 minutes; now neighbor information is being held for 8 hours. This time delay is introduced to avoid repeating the initial recognition of the satellite device for interface-down events. user@host> show configuration | display set | grep et-0/0/30 set groups user-host-grp interfaces et-0/0/30 cascade-port set chassis satellite-management fpc 101 cascade-ports et-0/0/30 set interfaces et-0/0/30 disable {master:0} user@host> show chassis satellite terse Device Extended Ports Slot State Model Total/Up Version 100 Online EX4300-48T 50/1 17.4-20170726_common_xxx.0 102 Online QFX5200-32C-32Q 2/1 17.4-20170726_common_xxx.0 103 Online QFX5110-48S-4C 3/2 17.4-20170726_common_xxx.0 {master:0} user@host> show chassis satellite neighbor Interface State Port Info System Name Model SW Version et-0/0/30 Dn et-0/0/18 Two-Way et-0/0/18 sd102 QFX5200-32C-32Q 17.4-20170726_common_xxx.0 et-0/0/12 Two-Way et-0/0/50 sd103 QFX5110-48S-4C 17.4-20170726_common_xxx.0 et-0/0/6 Two-Way et-0/1/3 sd100 EX4300-48T 17.4-20170726_common_xxx.0 {master:0} user@host> show system license License usage: Licenses Licenses Licenses Expiry Feature name used installed needed bgp 1 0 1 invalid SD-QFX5100-48SH-48TH 0 4 0 permanent Licenses installed: License identifier: JUNOSxxxxxx License version: 4 Software Serial Number: 99999B99999999 Customer ID: USER-SWITCH Features: SD-QFX5100-48SH-48TH-4PK - SD 4 pack QFX5000-10-JFD permanent {master:0} user@host> show system license usage Licenses Licenses Licenses Expiry Feature name used installed needed bgp 1 0 1 invalid SD-QFX5100-48SH-48TH 0 4 0 permanent {master:0} user@host> show system alarms 4 alarms currently active Alarm time Class Description 2017-08-29 13:14:27 UTC Minor BGP Routing Protocol usage requires a license 2017-08-28 17:25:27 UTC Major FPC0: PEM 1 Not Powered 2017-08-28 17:25:27 UTC Major FPC Management1 Ethernet Link Down PR1294951

  • In a Junos Fusion Data Center, configuration synchronization is not triggered when you issue the rollback command on the local aggregation device (AD). PR1298747

  • During a satellite device (SD) upgrade in Junos Fusion, there is a condition that the Link Aggregation Control Protocol (LACP) defaulted PDU received from the peer device connected in a link aggregation group (LAG) is incorrectly sent to an aggregation device (AD) with aggregated Ethernet e-Channel Identifier (ECID) instead of member ECID, which causes that LACP PDU to be received on another member in the LAG, resulting in the LAG interface flapping. PR1321575

  • In a Junos Fusion Data Center with EVPN solution, when an Aggregation Device loses EVPN connectivity with rest of the aggregation devices, then LACP over extended ports on this core isolated aggregation device will be brought down until EVPN connectivity is restored. PR1327784

  • On a Junos Fusion Data Center, traffic is dropped when the aggregation device (AD) goes down because the routes advertised by that AD are withdrawn. As a workaround, configure the hold-time on uplink interfaces using the set interfaces interface hold-time up <300 * 1000> command. PR1331465

  • On the QFX10000, EVPN NSR Unicast is not currently supported.PR1337645

  • This issue was seen with UBS scale: however, with PLM scale this issue is not seen in latest releases. PR1338659

  • In the following Junos OS releases, the EVI-RT extended community as defined in draft-ietf-bess-evpn-igmp-mld-proxy-00 was not being attached to advertised Type 7 routes: 17.2, 17.3R1, 17.3R2, and 17.4R1. Starting with the following Junos OS releases, the EVI-RT is mandatory and Type 7 routes that do not carry this community will be ignored: 17.3R3, 17.4R2, 18.1R1 and later. An EVPN network enabled with IGMP snooping and having a mix of multi-homed peer PEs with some running the older releases (17.2, 17.3R1, 17.3R2, 17.4R1) and some running the newer releases (17.3R3, 17.4R2, 18.1R1 and later) will not be able to inter-operate since Type 7 routes advertised without the EVI-RT community by PEs running an older release will be ignored by PEs running the newer releases and will not result in creation of IGMP snooping state. PR1341807

  • In Junos Fusion with EVPN solution when an Aggregation Device looses EVPN connectivity with rest of the aggregation devices, then LACP over extended ports on this core isolated Aggregation Device will be brought down until EVPN connectivity is restored. PR1342045

  • When some of the EX4300 satellite devices are rebooted, they stay in offline state as packets get corrupted or dropped due to internal FIFO logic error. As a workaround, restart the satellite device PFE process. PR1349508

  • On platforms with dual routing engines, GRES will result in considerable traffic loss/duplication for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1350744

  • Partial ingress traffic can be mirrored on Junos Fusion Data Center setup with a few triggers, such as aggregation device and satellite device reboot, configuration reboot of traffic generator connected to satellite devices etc. As a workaround, flap of mirror output interface resolves the issue. PR1352827

  • In Junos OS, two different input filters cannot be configured on the same interface; if two filters are configured, only the second filter (the one that was configured most recently) takes effect. Ingress mirroring on extended ports in Junos Fusion Data Center (JFDC) can only be done by using firewall filters. Due to the Junos OS filter behavior, in JFDC, ingress mirroring on extended ports and other firewall filter configurations cannot be done on the same port. PR1353065

  • Since EVPN graceful restart is not supported, restart of the rpd process will result in considerable traffic loss for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1353742

  • Two aggregation devices going down at the same time will result in considerable traffic loss/duplication for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1354443

  • On an aggregation device (AD), if the mirror destination interface is down then the mirror gets globally removed from all FPCs of the AD. The mirror is reprogrammed back when the mirror destination interface is up again. Until the mirror stays down, sampling won’t be functional on the given AD. PR1360003

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 18.1R3 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Junos Fusion Data Center

  • Partial ingress traffic can be mirrored on Junos Fusion setup with some triggers, such as a reboot of the aggregation or satellite device or a configuration reboot of traffic generator connected to the satellite devices. As a workaround, flapping the mirror output interface resolves the issue. PR1352827

Resolved Issues

This section lists the issues fixed in the Junos OS Release 18.1R3 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 18.1R3

  • In a Junos Fusion setup, a DCPFE core file is generated after executing the sh shim bridge bd bd-index command in the PFE. PR1296738

Resolved Issues: 18.1R2

Junos Fusion Data Center

  • On a Junos Fusion topology with QFX10002 switches as aggregate devices having dual cascade links to each satellite devices for redundancy, duplicated multicast traffic might be seen on downstream devices and multicast receivers if the multicast traffic passes through the aggregate devices. As a workaround, deactivate and re-activate the VLAN in which duplicated multicast traffic is seen. PR1316499

  • In a Junos Fusion setup, an aggregate device may show a plus sign on the ICL link for a satellite device. PR1335373

Resolved Issues: 18.1R1

Junos Fusion Data Center

  • In a Junos Fusion topology with LAG on extended ports from satellite devices which are dual-homed to aggregation devices, the LAG interface might flap if rebooting one of the aggregation devices. PR1315879

Documentation Updates

This section lists the errata or changes in Junos OS Release 18.1R3 for Junos Fusion Data Center documentation.

New Simplified Documentation Architecture

  • With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make it easier for you to find information and know that you can rely on it when you find it. In the past, we organized documentation about Junos OS software features into platform-specific documents. In many cases, features are supported on multiple platforms, so you might not easily find the document you want for your platform.

    With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For example, if you want to find documentation on OSPF, there is only one document regardless of which platform you have. Here are some of the benefits of our new simplified architecture:

    • Over time, you will see better search results when looking for Juniper documentation. You will be able to find what you want faster and be assured that is the right document.

    • If a software feature is supported on multiple platforms, you can find information about all the platforms in one place.

    • Because we have eliminated many documents that covered similar topics, you will now find one document with all the information.

    • You can know that you are always getting the most current and accurate information.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for Junos Fusion Data Center. Upgrading or downgrading Junos OS can take several hours, depending on the size and configuration of the network.

Basic Procedure for Upgrading an Aggregation Device

When upgrading or downgrading Junos OS, always use the jinstall package. Use other packages (such as the jbundle package) only when so instructed by a Juniper Networks support representative. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide.

Note

Before upgrading, back up the file system and the currently active Junos OS configuration so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:

The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the routing platform, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. See the Junos OS Administration Library.

To download and install Junos OS:

  1. Using a Web browser, navigate to the Download Software URL on the Juniper Networks webpage:

    https://www.juniper.net/support/downloads/

  2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  3. Select By Technology > Junos Platform > Junos Fusion to find the software that you want to download.
  4. Select the release number (the number of the software version that you want to download) from the Version drop-down list to the right of the page.
  5. Select the Software tab.
  6. Select the software package for the release.
  7. Review and accept the End User License Agreement.
  8. Download the software to a local host.
  9. Copy the software to the routing platform or to your internal software distribution site.
  10. Install the new jinstall package on the aggregation device.Note

    We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

    Customers in the United States and Canada, use the following command.

    user@host> request system software add reboot source/package-name

    All other customers, use the following command.

    user@host> request system software add reboot source/package-name

    Replace source with one of the following values:

    • /pathname—For a software package that is installed from a local directory on the router.

    • For software packages that are downloaded and installed from a remote location:

      • ftp://hostname/pathname

      • http://hostname/pathname

      • scp://hostname/pathname (available only for Canada and U.S. version)

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process can take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Preparing the Switch for Satellite Device Conversion

Satellite devices in a Junos Fusion topology use a satellite software package that is different from the standard Junos OS software package. Before you can install the satellite software package on a satellite device, you first need to upgrade the target satellite device to an interim Junos OS software version that can be converted to satellite software. For satellite device hardware and software requirements, see Junos Fusion Hardware and Software Compatibility Matrices.

Note

The following conditions must be met before a Junos switch that is running Junos OS Release 14.1X53-D43 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.1 and higher.

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

Customers with EX4300 switches, use the following command, replacing n with the spin number:

user@host> request system software add validate reboot source/jinstall-ex-4300-14.1X53-D43.n-domestic-signed.tgz

Customers with QFX5100 switches, use the following command, replacing n with the spin number:

user@host> request system software add validate reboot source/jinstall-qfx-5-14.1X53-D43.n-domestic-signed.tgz

When the interim installation has completed and the switch is running a version of Junos OS that is compatible with satellite device conversion, perform the following steps:

  1. Log in to the device using the console port.
  2. Clear the device:
    [edit]

    user@satellite-device# request system zeroize
    Note

    The device reboots to complete the procedure for resetting 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, log in 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:
    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 QSFP+ interfaces 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

    This step is required for the 40-Gbps QSFP+ interfaces that will be used as uplink interfaces in a Junos Fusion topology. 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 reset.

After this initial preparation, you can use one of three methods to convert your switches into satellite devices—autoconversion, manual conversion, and preconfiguration. See Configuring or Expanding a Junos Fusion Data Center for detailed configuration steps for each method.

Configuring Satellite Device Upgrade Groups

To simplify the upgrade process for multiple satellite devices, you can create a software upgrade group at the aggregation device, assign satellite devices to the group, and install the satellite software on a groupwide basis.

To create a software upgrade group and assign satellite devices to the group, include the satellite statement at the [edit chassis satellite-management upgrade-groups upgrade-group-name] hierarchy level.

To configure a software upgrade group and assign satellite devices to the group:

  1. Log in to the aggregation device.

  2. Create the software upgrade group, and add the satellite devices to the group.

    [edit]
    user@aggregation-device# set chassis satellite-management upgrade-groups upgrade-group-name satellite satellite-member-number-or-range

upgrade-group-name is the name of the upgrade group, and the satellite-member-number-or-range is the member 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, configure the following:

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

To install, remove, or roll back a satellite software version on an upgrade group, issue the following operational mode commands:

  • request system software add upgrade-group group-name—Install the satellite software on all members of the specified upgrade group.

  • request system software delete upgrade-group group-name—Remove the satellite software association from the specified upgrade group.

  • request system software rollback upgrade-group group-name—Associate an upgrade group with a previous version of satellite software.

Customers installing satellite software on EX4300 and QFX5100 switches referenced in a software upgrade group, use the following command:

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

Before issuing request system software add upgrade-group group-name, you must issue a one-time command to expand the storage capacity. Use the request system storage user-disk expand command to increase the size of /user partition.

A copy of the satellite software is saved on the aggregation device. When you add a satellite device to an upgrade group that is not running the same satellite software version, the new satellite device is automatically updated to the version of satellite software that is associated with the upgrade group.

You can issue the show chassis satellite software command to see which software images are stored on the aggregation device and which upgrade groups are associated with the software images.

Converting a Satellite Device to a Standalone Device

In the event that you need to convert a satellite device to a standalone device, you will need to install a new Junos OS software package on the satellite device and remove it from the Junos Fusion topology. For more information, see Converting a Satellite Device to a Standalone Device.

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1, 17.2 and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or even from Junos OS Release 17.1 to Release 17.3.

You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information about EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.

Downgrading from Junos OS Release 18.1

To downgrade from Junos OS Release 18.1 to another supported release, follow the procedure for upgrading, but replace the 18.1 jinstall package with one that corresponds to the appropriate downgrade release.

Note

You cannot downgrade more than three releases.

For more information, see the Installation and Upgrade Guide.

Product Compatibility

Hardware and Software Compatibility

For a complete list of all hardware and software requirements for a Junos Fusion Data Center, including which Juniper Networks devices function as satellite devices, see Understanding Junos Fusion Data Center Software and Hardware Requirements in the Junos Fusion Data Center User Guide.

To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guides for the devices used in your Junos Fusion Data Center topology.

To determine the features supported in a Junos Fusion, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at https://pathfinder.juniper.net/feature-explorer/

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.