Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.1R2 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

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
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, 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
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