Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues

This section lists the issues resolved in Juniper Paragon Automation Release 2.4.0:

  • Onboarding an ACX7024 device fails with the following error:

    task_failure, Failed to launch Software update. Timed out or waiting for the launch message. Try again later.

  • If the device onboarding fails, the device onboarding status is displayed as Status is not available in the Devices section of the Network Implementation Plan page (Inventory > Device Onboarding > Network Implementation Plan).

  • On the Interfaces Details for Device-Name Page (Interfaces accordion > Interfaces data-link), the link flaps count erroneously drops to zero and reverts to the same count as before.

  • You cannot provision an L3VPN service on an ACX7024 device with Junos OS Release 23.2R2 installed.

  • The Hardware accordion does not display the following information for the listed devices:

    • Chassis temperature (chassis-temperature) for MX204, MX240, MX304, MX10004, MX10008, and MX10016 devices.

    • Charts related to the fan speed (rpm-percent) for MX480, MX960, MX10004, MX10008, and MX10016 devices.

    • Power supply module temperature (psm-temperature) for MX204, MX480, and MX960 devices.

    • CPU utilization (cpu-utilization) information is not available for PTX10002 device.

    • Line card charts are not available for some ACX Series, MX Series, and PTX Series devices as the flexible PIC concentrator (FPC) fields are not supported on these devices. See Table 1 for more information.

      Table 1: Line Card Charts Support

      Device Family

      Device Series

      FPC Fields Not Supported

      ACX Series

      ACX7100-32C, ACX7100-48L, ACX7024, ACX7024X, ACX7509, ACX7348

      fpc-temperature, fpc-cpu-utilization, fpc-buffer-memory-utilization

      MX Series

      MX204, MX240, MX304, MX480, MX960, MX10004, MX10008, MX10016

      fpc-temperature, fpc-cpu-utilization

      PTX Series

      PTX10002

      fpc-temperature, fpc-cpu-utilization, fpc-buffer-memory-utilization

  • After the primary node is switched off, the OC-term and GNMI state on the Remote Management accordion (Observability > Troubleshoot Devices > Device-Name) are displayed as disconnected.

  • The values for Input Utilization and Output Utilization are represented in terms of percentage of interface utilization instead of Mbps.

    This issue is seen in Physical Interfaces Details for Service-Instance-Name tab (Orchestration > Instances > Service Instances > Service-Instance-Name hyperlink > Service-Instance-Name Details > Passive Assurance ) and Input Traffic Details for Device-Name page (Observability > Health > Troubleshoot Devices > Device-Name > Overview > Interfaces (accordion) > Input Traffic data-link).

  • For EX9204 devices, the Optical Tx power and Optical Rx Power graphs on the Pluggables Details for Device-Name page (Observability > Health > Troubleshoot Devices > Device-Name > Overview> Interfaces accordion > Pluggables data-link) do not show any warnings for critical thresholds.

  • For EX4300-48MP devices, the Signal Functionality graph on the Input Traffic Details for Device-Name page (Observability > Health > Troubleshoot Devices > Device-Name > Overview> Interfaces accordion > Pluggables), does not display any data.

  • You won’t be able to provision an LSP using the Paragon Automation GUI if the provisioning type is SRv6.

  • The changes are not reflected when you update the following fields on the Constraints tab of the Edit LSP page:

    • Admin Group Include All

    • Admin Group Include Any

    • Admin Group Exclude

    This issue occurs only when you try to edit an LSP that doesn’t have at least one of these attributes set at the time of LSP creation.

  • For some devices such as ACX7204, if you configure VLANs on unused ports, the following error occurs:

    VLAN must be specified on tagged interfaces.

  • After you upgrade Paragon Automation from Release 2.1.0 to Release 2.2.0, L2VPN and L3VPN accordions (Orchestration > Instances > Service Instances > Service-Instance-Name hyperlink > Service-Instance-Name Details > Passive Assurance tab) show no data for service instances that were provisioned in Release 2.1.0. This issue does not occur if you install Paragon Automation afresh.

  • While creating topo resources, the node name is not populated. This issue occurs only after you upgrade to Release 2.3.0.

  • The EVPN service order creation fails if you try to create an EVPN service order by importing an existing JavaScript Object Notation (JSON) file.

  • Although multiple VLAN IDs are available in the topology resources, the Placement section of the EVPN service order lists only one VLAN ID in the drop down.

  • While modifying a service order, you cannot clear the existing placements.

  • If you have referenced a device in a service order and if you try to release the router from the organization, then you cannot delete the service.

    Workaround: We recommend that you deprovision the service and offboard the device before you release the router from the Network Inventory page.

  • Scheduling provisioning of service orders does not work if you upgrade Paragon Automation to Release 2.2.0.

  • When you upgrade an L2 circuit service design, you are prompted to update the L2 address even when there is no dependency on L2 addresses.

  • The onboarding of a device fails if you configure only IPv6 addresses at the time of installation and enable Trust in the device profile. This issue does not occur if you have configured IPv4 addresses.

  • If you have enabled the Trust option in the device profile, the onboarding workflow may fail with the following error:

    Onboarding workflow failed reason: task_failure, Trust score computation failed.

  • The graphs related to cyclic redundancy check (CRC) errors display No Results Found as the CRC errors-related data is not streamed from the devices for the management ports.

  • Sometimes, the graph on the Output Traffic Details for Device-Name page (Observability > Health >Troubleshoot Devices > Device-Name > Overview > Interfaces (accordion) > Output Traffic data link) displays a sudden spike in data. This issue occurs because some devices might erroneously send data more than once with the same time stamp.

  • If you have installed a Junos OS or Junos OS Evolved release other than Release 22.1R1.10, you may not be able to view the historical data for link delays. For any other versions of Junos OS or Junos EVO release, you may see discrepancies in the graph as delay statistics are sent only when there are changes.

  • Your hard disk may be full because of the LSP event-related data retention.

  • In this release, single node failure and restart might cause inconsistencies in device inventory.

  • The historical data for tunnel traffic (Observability > Topology > Tunnels > View >Tunnel Traffic) is not displayed for ACX Series devices.

  • VLAN drop down under Placement section doesn't display all the available VLANs as per the topology service order and it shows only the selected VLAN.

  • During device onboarding, pings from the device to Microsoft Azure and Google Cloud Platform endpoints fail.

  • While creating an EVPN service order, if the MAC Address Limit that you have specified is out of the defined range then the service order fails.

  • While creating or modifying an EVPN service order, the MAC Address Limit configuration is ignored if you specify Drop as the action to be taken when the upper limit for customer MAC addresses exceed.

  • After you upgrade Paragon Automation to Release 2.3.0 and upgrade the L3VPN service instance to the latest service design, you may not see the physical interface of one of the devices.