This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.2R2 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
When a QFX10002 switch functions as an aggregation device in a Junos Fusion Data Center topology, it only supports cascade port-based slot assignments for satellite devices. In addition, any change in the configuration for a cascade port connected to a satellite device is treated as a catastrophic event and results in the deletion of any related interface state (including the extended ports), which is rebuilt after a period of time. The following additional restrictions also apply:
You cannot configure dual-homed satellite device extended ports as pure Layer 3 interfaces. As a result, family inet and family inet6 are not supported on dual-homed extended ports.
If the ICL interface goes down, traffic loss will occur. As a workaround, we recommend you configure the ICL interface over an aggregated Ethernet interface with multiple links in the bundle to prevent single-point failures that would cause the ICL interface to shut down.
On a Junos Fusion Data Center, configuring the following options for CoS forwarding class sets (fc-sets) incorrectly triggers a syslog message but does not result in any commit errors:
Priority of strict-high and normal (strict-high mixed with (low and high) queue) mixed in a single fc-set.
Total number of strict-high fc-sets configured is more than 1.
Transmit rate or guaranteed rate is configured on strict-high fc.
If the incorrect configuration is applied and the aggregation device is restarted, COSD does not start, and the CoS configuration is not sent to the Packet Forwarding Engine. The system will be in an inconsistent state.