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 Enterprise

 

These release notes accompany Junos OS Release 17.1R3 for Junos Fusion Enterprise. Junos Fusion Enterprise is a Junos Fusion that uses EX9200 switches in the aggregation device role. These release notes describe new and changed features, limitations, and known problems in the hardware and software.

Note

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

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 the Junos OS main release and the maintenance releases for Junos Fusion Enterprise.

Note

For more information about the Junos Fusion Enterprise features, see the Junos Fusion Enterprise User Guide.

Release 17.1R3 New and Changed Features

There are no new features or enhancements to existing features for Junos Fusion Enterprise in Junos OS Release 17.1R3.

Release 17.1R2 New and Changed Features

There are no new features or enhancements to existing features for Junos Fusion Enterprise in Junos OS Release 17.1R2.

Release 17.1R1 New and Changed Features

Hardware

  • Satellite device support (EX2300 and EX3400)—Starting with Junos OS Release 17.1R1, you can configure EX2300 and EX3400 switches as satellite devices in a Junos Fusion Enterprise topology. The satellite device in a Junos Fusion topology is managed and configured by the aggregation device. Junos Fusion Enterprise uses EX9200 switches in the aggregation device role.

    [See Junos Fusion Enterprise Overview.]

Authentication, Authorization, and Accounting (AAA) (RADIUS)

  • Authentication and access control features (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, Junos Fusion Enterprise supports controlling access to the network by using the following features:

    • 802.1X authentication

    • MAC RADIUS authentication

    • Server-fail fallback

    • TACACS+ authentication

    • Central Web authentication

    • RADIUS-initiated changes to an authorized user session (RFC 3576)

    • Flexible authentication order

    • RADIUS accounting interim updates

    • Dynamic filtering with multiple filter terms using VSAs

    • EAP-PAP protocol support for MAC RADIUS authentication

    • RADIUS accounting attributes Client-system-Name, Framed-MTU, Session-timeout, Acct-authentic, Nas-port-ID, and Filter-ID

    [See Understanding Authentication on Switches.]

Class of Service (CoS)

  • Class of Service support (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, Junos Fusion Enterprise supports the standard Junos CoS features and operational commands. 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. An EX9200 aggregation device supports the following CoS features for each extended port:

    • BA classifier

    • Multifield classifier

    • Input and output policer

    • Egress rewrite

    The satellite devices support the following CoS features for each extended port:

    • BA classifier

    • Queuing and scheduling

    A cascade port is a physical interface on an aggregation device that provides a connection between the aggregation device and a satellite device. Port scheduling is supported on cascade ports. A Junos Fusion Enterprise 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 Enterprise.]

Layer 2 Features

  • Support for Layer 2 Features (Junos Fusion Enterprise)—Starting in Junos OS Release 17.1R1, the following features are supported:

    • Storm control—Monitor traffic levels and take a specified action when a defined traffic level (called the storm control level) is exceeded, preventing packets from proliferating and degrading service. You can configure the switch to drop broadcast and unknown unicast packets, shut down interfaces, or temporarily disable interfaces when a traffic storm occurs. [See Understanding Storm Control for Managing Traffic Levels on Switching Devices.]

    • Persistent MAC learning (Sticky MAC)—Configure persistent MAC addresses (also called sticky MAC addresses) to help restrict access to an access port by identifying the MAC addresses of workstations that are allowed access to a given port. Secure access to these workstations is retained even if the switch is restarted. [See Understanding Persistent MAC Learning (Sticky MAC).]

    • MAC limiting—Configure MAC limiting on an interface or a VLAN, and specify the action to take on the next packet the interface or the VLAN receives after the limit is reached. Limiting the number of MAC addresses protects the switch from flooding the Ethernet switching table (also known as the MAC forwarding table or Layer 2 forwarding table). [See MAC Limiting.]

    • Loop detection on extended ports—Enable downstream loop detection on the satellite device to prevent accidental loops caused by miswiring or misconfiguration on the extended ports.

  • Support for MAC/PHY features on Junos Fusion Enterprise—Starting with Junos OS Release 17.1R1, the following MAC/PHY features are supported on Junos Fusion Enterprise:

    • Digital optical monitoring (DOM)—You can run the show interfaces diagnostics optics interface-name command to display the DOM information. The information includes diagnostics data and alarms for Gigabit Ethernet optical transceivers.

    • Energy Efficient Ethernet (EEE)—EEE reduces the power consumption of physical layer devices during periods of low link utilization. EEE saves energy by putting part of the transmission circuit into low power mode when a link is idle. You can run the set interfaces interface-name ether-options ieee-802-3az-eee command at the [edit] hierarchy level to enable energy efficiency at the Ethernet ports. You can view the EEE status by using the show interfaces interface-name detail command. By default, EEE is disabled on EEE-capable ports.

    • Jumbo frames—You can configure jumbo frames by using the set interfaces interface-name mtu 9216 command at the [edit] hierarchy level.

    • Medium-dependent Interface (MDI)—By default, the auto MDI/MDI-X feature is enabled on Junos Fusion Enterprise. This feature eliminates the need for a cross-over cable to connect the LAN port to a port on another device, as the crossover function is automatically enabled, when required.

Multicast

  • Support for multicast traffic forwarding (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, multicast traffic forwarding is supported in Junos Fusion Enterprise. Multicast replication is supported only on the aggregation device. The aggregation device performs ingress multicast replication to a set of extended ports. On the satellite device, multicast traffic is received for each of the extended ports. The following scenarios are supported for both IPv4 and IPv6 traffic: Layer 2 multicast with VLAN flooding and Layer 3 multicast.

    [See Understanding Multicast Forwarding on a Junos Fusion Enterprise.]

Network Management and Monitoring

  • Network monitoring and analysis (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, sFlow monitoring and port mirroring and analyzers are supported in Junos Fusion Enterprise:

    • sFlow technology, which is a monitoring technology for high-speed switched or routed networks, randomly samples network packets and sends the samples to a monitoring station. You can configure sFlow technology to continuously monitor traffic at wire speed on all interfaces simultaneously.

    • Port mirroring and analyzers facilitate analyzing traffic on switches at the packet level. You configure port mirroring on a switch to send copies of unicast traffic to an output destination such as an interface, a routing instance, or a VLAN. You can configure an analyzer to define both the input traffic and output traffic in the same analyzer configuration. The input traffic to be analyzed can be traffic that enters or exits an interface, or traffic that enters a VLAN.

    [See Understanding sFlow Technology on a Junos Fusion Enterprise and Understanding Port Mirroring Analyzers on a Junos Fusion Enterprise.]

Port Security

  • Media Access Control Security (MACsec) support on extended ports (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, MACsec is supported on extended ports in a Junos Fusion Enterprise topology. MACsec is an 802.1AE IEEE industry-standard security technology that provides secure communication for all traffic on point-to-point Ethernet links. MACsec is capable of identifying and preventing most security threats and can be used in combination with other security protocols to provide end-to-end network security. Enabling MACsec on extended ports in a Junos Fusion Enterprise topology provides secure communication between the satellite device and connected hosts.

    [See Understanding Media Access Control Security (MACsec).]

  • Access security support (Junos Fusion Enterprise)—Starting with Junos OS Release 17.1R1, the following access security features are supported in Junos Fusion Enterprise:

    • DHCP snooping—DHCP snooping allows the switch to monitor and control DHCP messages received from untrusted devices connected to the switch. When DHCP snooping is enabled, the system snoops the DHCP messages to view DHCP lease information, which it uses to build and maintain a database of valid IP-address-to-MAC-address (IP-MAC) bindings called the DHCP snooping database. Clients on untrusted ports are only allowed to access the network only if they are validated against the database.

    • DHCPv6 snooping—DHCP snooping for DHCPv6.

    • Dynamic ARP inspection (DAI)—DAI inspects Address Resolution Protocol (ARP) packets on the LAN and uses the information in the DHCP snooping database on the switch to validate ARP packets and to protect against ARP spoofing (also known as ARP poisoning or ARP cache poisoning). ARP requests and replies are compared against entries in the DHCP snooping database, and filtering decisions are made based on the results of those comparisons.

    • IP source guard—IP source guard prevents IP address spoofing by examining each packet sent from a host attached to an untrusted access interface on the switch. The IP address, MAC address, VLAN, and interface associated with the host are checked against entries stored in the DHCP snooping database. If the packet header does not match a valid entry in the DHCP snooping database, the packet is discarded.

    • IPv6 source guard—IP source guard for IPv6.

    • IPv6 neighbor discovery (ND) inspection—IPv6 ND inspection mitigates attacks based on Neighbor Discovery Protocol; by inspecting neighbor discovery messages and verifying them against the DHCPv6 snooping table.

    [See Understanding Port Security Features to Protect the Access Ports on Your Device Against the Loss of Information and Productivity.]

Changes in Behavior and Syntax

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 17.1R3 for Junos Fusion Enterprise.

System Management

  • Peers option not supported in batch configuration mode— Starting in Junos OS Release 17.1R1, the peers option at the [edit system commit] hierarchy level is not supported in batch configuration mode.

Known Behavior

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

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

Junos Fusion Enterprise

  • While applying a loopback filter on aggregation devices in a Junos Fusion Enterprise, Callback Control Protocol (CBCP) packets might be filtered, which might cause CBCP sessions to be dropped and one of the satellite devices in a redundant pair to be in the SplitBrainDn state. To work around this issue, you can add a filter similar to the following to the existing set of loopback filters:

    set firewall family inet filter accept-icl term accept-icl from source-address 10.0.0.0/30
    set firewall family inet filter accept-icl term accept-icl from destination-address 10.0.0.0/30

    PR1183680

  • On a Junos Fusion, when using LLDP, the "Power via MDI" and "Extended Power via MDI" TLVs are not transmitted. PR1105217

  • In a Junos Fusion Enterprise topology with dual aggregation devices, firewall statistics are not synchronized across the aggregation devices. PR1105612

  • On a Junos Fusion Enterprise, 'show ethernet-switching table' takes a few minutes to show entries when an extended port receives with MAC count set to 150K. PR1117567

  • In a Junos Fusion Enterprise, Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) fast start does not work. PR1171899

  • On a Junos Fusion Enterprise, when the satellite devices of a cluster are rebooted, the output of the CLI command show chassis satellite shows the port state of the cascade ports as Present. PR1175834

  • In a Junos Fusion Enterprise, conversion of EX2300 and EX3400 switches from satellite devices to Junos OS devices cannot be performed from the aggregation device using the command request chassis satellite install junos-package-name fpc-slot slot-id. As a workaround, use the following procedure:

    1. If automatic satellite conversion is enabled for the satellite device’s FPC slot ID, remove the FPC slot ID from the automatic satellite conversion configuration.
      [edit]

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

      For example, to remove FPC slot ID 101 from the Junos Fusion.

      [edit]

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

      If automatic satellite conversion is enabled for the FPC slot ID, the Junos Fusion tries to convert the device back into a satellite device later in this procedure.

      You can check the automatic satellite conversion configuration by entering the show statement at the [edit chassis satellite-management auto-satellite-conversion] hierarchy level.

    2. Log in to the satellite software (SNOS) on the switch to be converted back to Junos OS and use the following sequence of commands to install the Junos package:

    PR1213023

  • In a Junos Fusion Enterprise, conversion of an EX2300 switch from Junos OS to satellite software (SNOS) takes 13-14 minutes. PR1213853

  • In a Junos Fusion Enterprise, analyzer output is not supported for the aggregation device native interfaces. As a workaround, use RSPAN to capture analyzer output for the aggregation device. PR1214596

  • In a Junos Fusion Enterprise, EX3400 and EX2300 operating as satellite devices might take longer time to re-converge from single-home to dual-home cluster due to a hardware limitation, compared to an EX4300 switch operating as a satellite device. PR1226366

  • In a Junos Fusion Enterprise with dual aggregation devices, duplicate multicast packets are observed until L3 convergence happens between the aggregation devices, which might take a few seconds. PR1231101

  • In a Junos Fusion Enterprise, a delay might result from moving a satellite device from cluster to non-cluster mode and vice versa. PR1231678

  • Loss of connectivity of the link connecting the standalone switch might lead to conversion failure from Junos OS to satellite software (SNOS). As a workaround, reboot the standalone switch again to restart the conversion process. PR1232798

  • In a Junos Fusion Enterprise, in order to use a non-default port as a clustering port in a clustering port policy, the policy must include at least one port that is a default uplink/clustering port for that platform. PR1241808

  • In a Junos Fusion Enterprise, a satellite device might not come online when it is converted from cluster to non-cluster mode without accompanying topology changes. As a workaround, ensure the configuration of satellite devices matches the wiring topology: non-cluster devices should not be connected to other clustered devices by means of default or configured clustering/uplink ports. PR1251790

  • In Junos Fusion Enterprise, when 802.1X authentication is configured in single-secure mode, a firewall counter is created for the default discard term in addition to the configured term. PR1254503

  • In a Junos Fusion Enterprise it can take 6 to 30 seconds for the traffic to converge when the aggregation device is powered off or powered on. PR1257057

  • During RE switchover on a Junos Fusion Enterprise, the BUM traffic is duplicated to indirectly connected satellite devices. This is because there is no current support to notify the GRES event to indirectly connected satellite devices. PR1298434

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 17.1R3 for Junos Fusion Enterprise.

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

Junos Fusion Enterprise

  • In a Junos Fusion Enterprise that has enabled PoE for all extended ports, the show poe interface command output displays the PoE administrative status as Enabled for non-PoE-capable interfaces. PR1150955

  • On a Junos Fusion Enterprise, control packets from the aggregation device - including ping and DHCP packets - might not be forwarded to hosts connected to extended ports when the cascade ports on the aggregation device are down. PR1173212

  • In a Junos Fusion Enterprise, restarting satellite processes from the aggregated device might not work. As a workaround, use the following commands to get the process ID and restart the process:

    user@aggregated-device> request chassis satellite shell-command fpc-slot <slot-id> "ps -aef | grep <process> | grep -v grep”
    user@aggregated-device> request chassis satellite shell-command fpc-slot <slot-id> "kill -9 <process-id>”

    Processes details:

    amdapi-management-daemon
    lcmdchassis-management-daemon
    dpddiscovery-and-provisioning-daemon
    spfepacket-forwarding-engine
    ppmanppman
    ppman-liteppman-lite

    PR1244166

  • In a Junos Fusion Enterprise, backup link information might not be displayed in the output of the show chassis satellite command if cluster configuration is deleted and then added again on a single aggregated device. As a workaround, delete and then add configuration on both aggregated devices. PR1247633

  • The ppm-lite process might generate a core file on the Fusion satellite devices. It is unexpectedly treating the IEEE PORT VLAN ID TLV on LLDP packets as a DCBXv1.01 TLV. PR1364265

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases.

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

Resolved Issues: 17.1R3

Junos Fusion Enterprise

  • Mirrored packets are dropped if analyzer output extended port is reachable via the ICL link. PR1211123

  • On a Junos Fusion Enterprise with dual aggregation devices (ADs), if you apply Routing Engine loopback filters and bring down the cascade port on one of the ADs, the satellite device (SD) on the AD where the cascade port is down goes to ProvSessDown due to a TCP session drop over the ICL interface. PR1275290

  • DHCP Snooping entry is deleted after l2ald restart. PR1281824

  • VRRP has a split-brain in dual autodiscovery Junos Fusion. PR1293030

  • An aggregation device without a cascade port cannot reach hosts over the ICL link if they are authenticated by 802.1X in a different VLAN than the default (manually assigned) VLAN. PR1298880

  • 802.1X authentication might fail in a Junos Fusion setup. PR1299532

  • 802.1X authentication might fail in a Junos Fusion setup with dual aggregation devices. PR1303909

  • In Junos Fusion environment SD displays U-Boot on the LCD screen. PR1304784

  • Packet loss of 2-3 secs is seen every 5 minutes on Junos Fusion. PR1320254

  • A satellite device does not recover PoE after the device is offline for more than 10 minutes and rejoins the aggregation device. PR1356478

Resolved Issues: 17.1R2

Junos Fusion Enterprise

  • EX4300 with Junos OS Release 17.1R1 cannot be converted to satellite mode. PR1267767

  • In Junos Fusion Enterprise, for show ethernet-switching table, a few entries are stuck in DLR state after l2-learning restart. PR1268619

Resolved Issues: 17.1R1

Junos Fusion Enterprise

  • For Junos Fusion Enterprise, PoE telemetrics is not working. PR1112953

  • Changes made in PoE configuration during SD Offline state are not getting reflected once the SD is back Online. PR1154486

  • Some ARPs are not resolving on Spirent when you exceed 6000 extended ports. PR1186077

  • Traffic loss is seen after rebooting a satellite device in a satellite device cluster. PR1168820

  • SNMP trap for satellite device reboot is not sent. PR1182895

  • LLDP might stop working if manually deactivated and reactivated. PR1188254

  • SDPD core files might be generated during conversion of EX2300/EX3400 cluster from JUNOS OS to SNOS. PR1239915

Documentation Updates

There are no errata or changes in Junos OS Release 17.1R3 for Junos Fusion Enterprise documentation.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade or downgrade Junos OS and satellite software for a Junos Fusion Enterprise. Upgrading or downgrading Junos OS and satellite software might take several hours, depending on the size and configuration of the Junos Fusion Enterprise topology.

Basic Procedure for Upgrading Junos OS on an Aggregation Device

When upgrading or downgrading Junos OS for an aggregation device, always use the junos-install 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 junos-install 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 Installation and Upgrade Guide.

To download and install Junos OS:

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

    https://support.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 on 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 junos-install 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 commands.

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

    All other customers, use the following commands.

    user@host> request system software add validate 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 might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note

After you install a Junos OS junos-install package, you cannot return to the previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the junos-install package that corresponds to the previously installed software.

Upgrading from Junos OS Release 16.1 to 17.1 in a JUNOS OS Fusion Enterprise System

When the Junos Fusion Enterprise System includes clustered devices, use the following procedure to first upgrade the clustered devices to SNOS 3.0R1 and then upgrade the aggregation device from 16.1 to 17.1.

  1. Enable hop-by-hop forwarding for control-traffic the on aggregation device using VTY commands.
    1. Start a shell on the aggregated device:
      user@aggregation-device> start shell
    2. For each FPC which has cascade ports, start a VTY session. For example:
      root@aggregation-device% vty fpc1
    3. At the VTY prompt, enter the following command:
    FPC1(aggregation-device vty)# set jnh ep stack-hostpath 0
  2. Enable hop-by-hop forwarding for control-traffic on all satellite devices in a cluster.
    user@aggregation-device> request chassis satellite shell-command vty -c 'test sd-cluster hop-to-hop enable' range fpc-start fpc-end
  3. Update the satellite device cluster to the new image, which must be SNOS 3.0R1 or higher.
    user@aggregation-device> request system software add upgrade-group cluster-upgrade-group image-location
  4. Confirm all satellite devices are upgraded to the new image.
    user@aggregation-device> show chassis satellite upgrade-group upgrade-group-name
  5. Upgrade the aggregation device to the 17.1 image.
    user@aggregation-device> request system software add aggregation-device-package-name
  6. To complete the upgrade, reboot the system, including all satellite devices and aggregation device.
    • To reboot the satellite devices:

      user@aggregation-device> request chassis satellite reboot range fpc-start fpc-end
    • To reboot the aggregation device:

      user@aggregation-device> request system reboot

Upgrading an Aggregation Device with Redundant Routing Engines

If the aggregation device has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to minimize disrupting network operations as follows:

  1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

  2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

  3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

  4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Preparing the Switch for Satellite Device Conversion

There are multiple methods to upgrade or downgrade satellite software in your Junos Fusion Enterprise. See Configuring or Expanding a Junos Fusion Enterprise.

For satellite device hardware and software requirements, see Understanding Junos Fusion Enterprise Software and Hardware Requirements.

Use the following command to install Junos OS on a switch before converting it into a satellite device:

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

The following conditions must be met before a Junos switch that is running Junos OS Release 17.1 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 later.

  • 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.

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 you enter the request system zeroize command.

    If you lose 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, or preconfiguration. See Configuring or Expanding a Junos Fusion Enterprise for detailed configuration steps for each method.

Converting a Satellite Device to a Standalone Switch

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 15.1, 16.1 and 16.2 are EEOL releases. You can upgrade from Junos OS Release 15.1 to Release 16.1 or even from Junos OS Release 15.1 to Release 16.2. However, you cannot upgrade directly from a non-EEOL 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 Release 17.1

Junos Fusion Enterprise is first supported in Junos OS Release 16.1R1, although you can downgrade a standalone EX9200 switch to earlier Junos OS releases.

Note

It is not recommended to downgrade the aggregation device from 17.1 to 16.1 if there are cluster satellite devices in the setup.

To downgrade a Junos Fusion Enterprise from Junos OS Release 17.1 to 16.1, you must first downgrade the satellite software version on the satellite devices from 3.0R1 to 2.0R1.

  1. Downgrade the satellite software on the satellite devices from 3.0R1 to 2.0R1:
    user@aggregation-device> request system software add satellite-2.0R1-signed.tgz no-validate upgrade-group cluster1

    After the satellite devices are downgraded to satellite software 2.0R1, they will not show as being online until the aggregation device is downgraded to 16.1.

  2. Downgrade the aggregation device. Follow the procedure for upgrading, but replace the 17.1 junos-install package with one that corresponds to the appropriate 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 Enterprise, including which Juniper Networks devices function as satellite devices, see Understanding Junos Fusion Enterprise Software and Hardware Requirements in the Junos Fusion Enterprise User Guide.

Hardware Compatibility Tool

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