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 resolved issues in Juniper Paragon Automation Release 23.2.

  • MD5 authentication is not supported on a Path Computation Element Protocol (PCEP) server.

    Workaround: None.

  • Toposerver saves the live properties (ero and rro) path for each LSP twice.

    Workaround: None.

  • The maintenance mode simulation feature and the corresponding maintenance reports are not available.

    Workaround: Run failure simulation in Java Planner.

  • Config viewer in the Integrity Check tab does not work. You can use the config viewer available in Topology tab instead.

    Workaround: None.

  • The P2MP logical tree-view can incorrectly show nodes multiple times resulting in cycles in a tree. This is due to the issue where toposerver saves live properties path for each LSP twice.

    Workaround: None.

  • “Delegation Bit” column in the tunnel table is always empty.

    Workaround: View delegation bit by selecting the LSP, right-click and select Show Details.

  • Admin group of an SR-TE LSP learned from PCEP disappears after topology synchronization, if the LSP has configured state.

    Workaround: Modify SR-TE LSP to persist the admin group learned from PCEP.

  • Demand is missing from the Network Archive in the Java Client, but the demand traffic is available.

    Workaround: None.

  • The root cause analysis (RCA) feature is disabled, by default.

    Workaround: To enable the RCA feature, perform the following steps:

    1. Ensure that you set the kubeconfig environment variable or the ~/.kube/admin.conf file is present.

    2. Ensure that the Paragon Insights services are up and running. To verify that the status of the pods is Running, use one of the following commands.

      root@primary-node:~# kubectl -n healthbot get pods


      root@primary-node:~# kubectl get po -n healthbot

    3. Log in to one of the primary nodes.

    4. Change the working directory to /var/local/healthbot.

      root@primary-node:~# cd /var/local/healthbot

    5. Use a text editor to edit the healthbot.sys file and change the value for ENABLE_RCA to “True” in the inference-engine section.

      Save and close the file.

    6. Publish the changes to all the other nodes in the cluster using the following command.

    7. Restart the inference-engine, alerta, and config-server services using the following commands.

      root@primary-node:~# /var/local/healthbot/healthbot restart -s inference-engine --device-group healthbot

      root@primary-node:~# /var/local/healthbot/healthbot restart -s alerta --device-group healthbot

      root@primary-node:~# /var/local/healthbot/healthbot restart -s config-server --device-group healthbot

    8. Verify that all the services are up and running.

      root@primary-node:~# kubectl -n healthbot get pods


    This procedure enables the feature at the global level. You can continue to use the Root Cause Analysis option on the Configuration > Device Groups and Configuration > Network pages to enable or disable the RCA feature at the device group level.