Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

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: Release 14.2R8

This section lists the issues fixed since Junos OS Release 14.2R7 for Junos Fusion Provider Edge.

Junos Fusion

  • On a Junos Fusion Provider Edge topology, if you configure dual VLAN tags on a logical interface of an extended port, the MX Series aggregation device might send extra VLAN tags for Routing Engine-generated packets on the extended ports. For example:
    user@aggregation-device#
    interfaces {
    xe-102/0/1 {
    flexible-vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 192 {
    vlan-tags outer 200 inner 100;
    family inet {
    address 192.168.100.101/30;
    }
    }
    }
    }

    As a workaround, instead of configuring an IPv4 address on the logical interface, configure Ethernet switching on the logical interface and associate the extended port with an IRB interface to perform the routing tasks. PR1184850

  • On a Junos Fusion topology, if you issue the request support information operational mode command, the logs do not include satellite device information. PR1220575
  • On a Junos Fusion topology, transit unicast traffic might be discarded when it passes through different logical interfaces of the same extended port on the same satellite device. The reason for this behavior is that the aggregation device uses the ingress ECID if the ingress and egress satellite device is the same. When the ingress ECID is equal to the egress ECID, the split-horizon check on the satellite device is affected. This issue only impacts unicast traffic and does not impact multicast or broadcast traffic. PR1264900

Resolved Issues: Release 14.2R7

This section lists the issues fixed since Junos OS Release 14.2R6 for Junos Fusion Provider Edge.

Junos Fusion

  • On a Junos Fusion Provider Edge topology, when you issue the show chassis satellite device-alias ? command, the list of available satellite devices is not displayed. PR1148762
  • On a Junos Fusion Provider Edge topology, if you configure BFD and reboot the system, the periodic packet management process (ppmd) might stop operating and dump core. As a workaround, set the BFD transmit interval to 300 msec with a multiplier of 3. PR1170800
  • On a Junos Fusion Provider Edge topology, if a cascade port transitions down and up, and the diagnostics data sent from a satellite device exceeds 25 kilobytes, the satellite platform management process (spmd) might dump core. PR1175591
  • On a Junos Fusion Provider Edge topology, if you issue the request chassis satellite shell-command command and the output generates more than 24 kilobytes of data, the satellite discovery and provisioning process (SDPD) might stop operating. As a workaround, issue the request chassis satellite login command and run the commands in the resulting session. PR1188712

Resolved Issues: Release 14.2R6

This section lists the issues fixed since Junos OS Release 14.2R5 for Junos Fusion Provider Edge.

Junos Fusion

  • On a Junos Fusion Provider Edge topology, if you configure CoS classifiers on an aggregated Ethernet bundle comprised of satellite device extended ports, the configuration commits and the classifiers are applied correctly. However, the output of the show class-of-service interface ae-interface-name command does not display the configured classifiers. As a workaround, apply the classifier on unit 0 of the LAG and the show command output will display the correct information. PR1062500
  • On a Junos Fusion Provider Edge topology, broadcast Ethernet traffic with an unknown Ethertype might generate the following log entries: fpc0 XL[0:0]_PPE 1.xss[0] ADDR Error and fpc0 XL[0:0]_PPE 1 Errors async xtxn error. PR1123040
  • On a Junos Fusion Provider Edge topology, if you configure Junos Fusion on an MX Series aggregation device, corresponding system log messages might not be received by a remote syslog server. PR1134269
  • On a Junos Fusion Provider Edge topology, when you insert a field-replaceable unit (FRU) into a satellite device, the aggregation device might not generate the expected SNMP traps for this event (such as jnxFruOnline and jnxFruInsertion). PR1136566
  • On a Junos Fusion Provider Edge topology configured with LACP, if a Routing Engine switchover causes the Periodic Packet Manager (ppman) to lose connectivity with the Periodic Packet Management Process (ppmd), and the reconnection results in new interface entries that do not have a valid interface name, the reconnection attempt might exceed 120 seconds and cause the LACP adjacencies to remain in the detached state as seen in the output of the show lacp interfaces command. PR1147546
  • On a Junos Fusion Provider Edge topology, if you configure the aggregation device for the first time, the satellite device to standalone device conversion might fail if the satellite discovery and provisioning process (sdpd) has not restarted. This happens because you perform the initial satellite management configuration on the aggregation device. As a workaround, restart the process by issuing the restart satellite-discovery-provisioning-process command before performing the satellite device conversion. PR1148786
  • On a Junos Fusion Provider Edge topology, when you configure an integrated routing and bridging (IRB) interface that includes both regular and extended ports, multicast traffic might not flow to the satellite device extended ports. PR1156750
  • On a Junos Fusion Provider Edge topology, you could only assign satellite all privileges to a single user class. In Junos OS Release 14.2R6, you can now include the satellite all statement at the [edit system login class class-name] hierarchy level for multiple classes. PR1161531

Resolved Issues: Release 14.2R5

This section lists the issues fixed since Junos OS Release 14.2R4 for Junos Fusion Provider Edge.

Junos Fusion

  • On a Junos Fusion Provider Edge topology, if you deactivate and reactivate et-interfaces, LACP might not come back up. As a workaround, deactivate and reactivate the aggregated Ethernet interface that contains the et- interface. PR1078299
  • On a Junos Fusion Provider Edge topology, if you issue the show interfaces media command on an extended port, the output does not show the autonegotiation information for the port. As a workaround, upgrade the satellite device to software version 1.0R3 or later and the aggregation device to Junos OS Release 14.2R5 or later. PR1078301
  • On a Junos Fusion Provider Edge topology, if you issue the show interfaces diagnostics optics satellite interface-name command for a satellite device extended port, the output does not provide any optical transceiver diagnostic data. PR1087366
  • On a Junos Fusion Provider Edge topology running bidirectional PIM, if you issue a nonstop active routing graceful Routing Engine switchover, multicast routes are not synchronized correctly between the master and standby Routing Engines. PR1095993
  • On a Junos Fusion Provider Edge topology, if you turn off a power supply, the system might not send an SNMP trap for this event. PR1116266

Resolved Issues: Release 14.2R4

This section lists the issues fixed since Junos OS Release 14.2R3 for Junos Fusion Provider Edge.

Junos Fusion

  • On a Junos Fusion Provider Edge topology configured for MC-LAG, if you perform an snmpwalk on iso, the operation times out with the error message “Request failed: OID not increasing: dot3adAggPortStatsLACPDUsRx.2387 >=dot3adAggPortStatsLACPDUsRx.2387.” PR1071050
  • On a Junos Fusion Provider Edge topology, if a QFX5100 switch is running Junos OS Release 14.1X53-D16 with Enhanced Automation, and you try to convert the switch into a satellite device by using either the automatic or manual conversion method, the conversion might fail. PR1072806
  • On a Junos Fusion Provider Edge topology, if you issue any of the show chassis commands available for satellite devices (such as show chassis hardware satellite) and include the device-alias option to display output for a specific device, the output might still include all the devices. PR1080516

Resolved Issues: Release 1.0R4

This section lists the issues fixed since satellite software release 1.0R3 for Junos Fusion.

Satellite Software

  • On a Junos Fusion topology with QFX5100 satellite devices, if the satellite device has a bad power supply, the output of the show chassis environment pem satellite and show chassis alarms satellite commands might not indicate there is a problem. PR1161861
  • On a Junos Fusion topology, the CCC-DOWN state (the asynchronous notification of link state from the remote end of a Layer 2 circuit) is not supported on satellite device extended ports. PR1162899
  • On a Junos Fusion topology with EX4300 satellite devices, some physical interfaces for the 10-Gigabit Ethernet ports on the uplink PIC (PIC2) are created while others are not, and the system log might show a transceiver EPROM failure. This issue might be resolved by removing the PIC and reinserting it, or restarting the satellite device. PR1169555
  • On a Junos Fusion topology, when the port channelization state changes (for example, et-0/0/1:0 to et-0/0/0) on a satellite device extended port, the system might assign the same ECID to more than one port and the following message might be generated: “IFRT: 'IFD hardware address configuration' (opcode 226) failed.” PR1170428
  • On a Junos Fusion topology with a QFX5100-96S satellite device, channelized interfaces are not supported on 40-Gigabit Ethernet uplink ports. PR1179317
  • On a Junos Fusion topology with dual aggregation devices, if you issue the show snmp mib walk command on one aggregation device, the output might not display PEM and fan information correctly for the 124th satellite device. As a workaround, issue the command on the second aggregation device. PR1182030
  • On a Junos Fusion topology, you might not be able to disable autonegotiation on fiber-based Gigabit Ethernet ports in a QFX5100 switch acting as a satellite device. PR1183112
  • On a Junos Fusion topology, if you configure CoS on an aggregation device, in some cases the satellite devices do not get provisioned and the DPD process might stop operating and dump core. As a workaround, disable CoS on interfaces, scheduler maps, and traffic control profiles. PR1184828
  • On a Junos Fusion topology, if you issue the request chassis satellite shell-command command and the output generates more than 24 kilobytes of data, the satellite discovery and provisioning process (SDPD) might stop operating. As a workaround, issue the request chassis satellite login command and run the commands in the resulting session. PR1188712
  • On a Junos Fusion topology, in some cases after a satellite device PFE restart, some of the channelized ports on a QFX5100-24Q satellite device cannot transmit or receive traffic. PR1192218
  • On a Junos Fusion topology, if an EX4300 satellite device is connected to an aggregation device over a copper, 40-Gigabit Ethernet uplink port, sometimes the link might transition down and up. PR1197913
  • On a Junos Fusion topology, if you issue the show interfaces command on a 40-Gigabit Ethernet port on a QFX5100 satellite device, the output does not display the correct bits per second if the traffic is 32 Gbps or larger. PR1197916
  • On a Junos Fusion topology, in some cases the ppman-lite or ppman process running on the satellite device might attempt to view information in the packet beyond the packet length, which might cause the process to stop operating. Issues with the ppman-lite process impact LLDP functionality, while issues with the ppman process impact LACP functionality. PR1208058
  • On a Junos Fusion topology, if you issue the request support information operational mode command, you expect that the system will consolidate and collect information from the /var/log directory of all the satellite devices and place it into the /var/home/ftp/sd_logs directory of the aggregation device. However, the collected logs (for example, sd101.tgz) do not contain relevant satellite device information from the consolidated log files. PR1208066
  • On a Junos Fusion topology, when a QFX5100 satellite device operates continuously for more than 140 days, or an EX4300 satellite device operates continuously for more than 280 days, the output of the show chassis routing-engine satellite command might indicate very high CPU utilization for the satellite device, even when the actual CPU utilization is very low. PR1208846

Resolved Issues: Release 1.0R3

This section lists the issues fixed since satellite software release 1.0R2 for Junos Fusion.

Satellite Software

  • On a Junos Fusion Provider Edge topology, if you issue the show interfaces extensive command on a copper-based satellite device extended port, the output does not show autonegotiation information. As a workaround, upgrade the aggregation device to Junos OS Release 14.2R5 or later and upgrade the satellite device to satellite software version 1.0R3. PR1107243

Resolved Issues: Release 1.0R2

This section lists the issues fixed since satellite software release 1.0R2 for Junos Fusion.

Satellite Software

  • On a Junos Fusion Provider Edge topology, if you issue the show interfaces diagnostics optics satellite interface-name command for a satellite device extended port, the output does not provide any optic transceiver diagnostic data. PR1087366
  • On a Junos Fusion Provider Edge topology, if you issue the show chassis hardware satellite command, the output indicates that EX4300-24T satellite devices are unsupported. As a workaround, upgrade the satellite devices to satellite software 1.0R2 and the aggregation devices to Junos OS Release 14.2R5 or later. PR1126060
  • On a Junos Fusion Provider Edge topology with QFX5100 satellite devices running satellite software version 1.0R1-S2 or earlier, if you remove a 1-gigabit small-form factor pluggable (SFP) fiber transceiver and replace it with a copper transceiver, the port might not transmit or receive traffic. As a workaround, restore the fiber transceiver in the port or upgrade the satellite software to version 1.0R2 or later. PR1140313
  • In a Junos Fusion Provider Edge topology, if there are power failures or the power is not connected to a power supply on a satellite device, the jnxPowerSupplyFailure traps are not generated by the aggregation device. For example, if there are two Power Entry Modules (PEMs) inserted on the satellite device and one PEM is not powered on, the aggregation device does not generate a trap for the PEM without power. PR1140097

Modified: 2017-12-12