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.2.0:

  • When you use the Release Router option to release a device from being managed by Paragon Automation, the device might not be released as the service orchestration engine might still be referencing the device that you want to release.

  • The onboarding of a device fails if you use NETCONF EDIT or NETCONF RPC configuration formats in the configuration templates.

  • A warning message is not displayed when you try to delete a configuration template that is used in the network implementation plan.

  • For PTX10001, PRX10004, and PTX10016 devices, the Linecards graph on Hardware details for Device-Name (Observability > Troubleshoot Devices > Device-Name > Hardware accordion) page does not display any data.

    Workaround: None.

  • For PTX Series, MX Series, and ACX Series devices, the RSVP TE Global Errors graph on the RSVP Routing Details for Device-Name (Observability > Troubleshoot Devices > Device-Name > Routing and MPLS accordion) page does not display any data.

  • If you modify an existing Monitor and then restart the Monitor, the events that are raised before modifying the Monitor are not cleared.

  • The latest audit log messages may not be displayed on the Audit Logs page.

  • The history of service orders that are generated for a service instance is saved in the Order History Tab for auditing purposes. However, when you delete the service instance, the service order history gets deleted.

  • Sometimes, the publishing of a service order fails due to existing placements.

  • When you edit a topology resource instance, the POP page may not list the latest sites or nodes.

  • The publishing of an EVPN service order fails if you modify an existing EVPN service order to add a new site. This issue occurs only when you modify an existing EVPN using the GUI.

  • The VPN Node Id field on the VPN Node page (Service Orchestration > Instances > Add L2 Circuit) field may not list all the onboarded devices.

  • While creating an EVPN site, if the value that you have specified for the Minimum number of links field is greater than the number of Member Links, then the EVPN service order fails.

  • If you try to modify an existing resource instance that does not have a device or a site, then the Inventory section of the Modify Resource-Instance-Name page does not load.

  • Even though the EVPN service order is successfully created and the configurations are pushed to the devices, the following error message is displayed and the communication between the customer Edge (CE) devices fails:

    Status: Configuration Error

    This issue occurs in a multi-homing scenario (multiple provider edge (PE) devices are connected to the same customer edge device) with single-active or all-active redundancy mode.

  • All access circuits must have the same VLAN configured, failing which the service may not function as desired.

  • If there are multiple node failures, the OpenSearch database may fail to start and rejoin the cluster.

  • If the PCE Server VIP address is not configured, kube-proxy is set to a random port.

  • There is no synchronization between accessing and configuring devices. A workflow might fail if a device is configured by more than one service order.

  • If you modify an L3VPN service, the historical data for Monitors related to the modified L3VPN service are deleted.