Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Issues


This section lists the known issues in Juniper Paragon Automation Release 21.1.


  • In the absence of a time series database (TSDB) HA replication, if a Kubernetes worker node running a TSDB pod goes down, even though there is capacity in the pod, the TSDB service is not spun up on a new node. This is because of the volume of data that would need to be transferred.

    Workaround: The Kubernetes worker node must be restored. Alternatively, you can move influxDB to another node using the force option.

  • If you have dedicated a node for a time series database (TSDB), some services (for example, AtomDB, ZooKeeper, and so on) in the common namespace that have PersistentVolumeClaim set can be affected if the relevant pods are running on the dedicated node.

    Workaround: There is no known workaround.

  • The Postgres database becomes inoperational in some systems, which leads to connection failure.

    Workaround: Execute the following command in the master node:

    kubectl exec -n common $pod -- chmod 750 /home/postgres/pgdata/pgroot/data
  • If you try to deploy any configuration during a swap of Postgres mastership, the deployment fails.

    Workaround: Redeploy after the new master is elected.

  • When you use the destroy command to uninstall Paragon Automation, uninstall fails if the persistent volume that is used for backup and restore contains backup files. An error similar to the following occurs:

    Workaround: Delete the backup files in the persistent volume or copy them elsewhere. Manually delete the persistent volume and execute the destroy command again.


  • The Save option is not displayed if you create more than one filter.

    Workaround: There is no known workaround.

  • You cannot view the segment routing LSP statistics.

    Workaround: To view the segment routing LSP statistics, you must upgrade Junos OS on the device to Release 20.2 or later.

  • An error message is not displayed if the add device operation fails.

    Workaround: There is no known workaround.

  • On the Devices page, there is no correlation between the Management Status column and the Sync Status column. For example, even if the device discovery fails, the Sync Status column may display the status as In Sync, which is incorrect. The In Sync state only represents that inventory information stored in Paragon Automation is synchronized with the device in the network.

    Workaround: There is no known workaround.

  • The restore configuration operation fails for devices running Cisco IOS XR Release 7.1.1.

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

  • While you are adding or editing a point-to-multipoint (P2MP) group, the value is not auto-populated for both MVPN Instance and Route Distinguisher fields. The values are auto-populated only for either of the fields.

    Workaround: There is no known workaround.

  • While adding a maintenance event, you must not include a space in the Name field.

    Workaround: There is no known workaround.

  • If you specify an incorrect URL to access the Paragon Automation GUI, a 404 error is not displayed and you are not redirected to a known page or to an error page.

    Workaround: Remove all the URL path parameters and specify only the hostname (https://<hostname>) or the dashboard landing page (https://<hostname>/app/dashboard).

  • While adding a filter to a table in GUI pages that support filtering, if you use both AND and OR logical operators as filter conditions, the results are not as expected.

    Workaround: There is no known workaround.

  • While the config-server microservice is rescheduled on another node (For example, when a node is down), if there happens to be Kubernetes-related issues, then the Postgress database will be cleaned up and the data may not be repopulated. Due to this issue, the device groups are not listed on the Device Groups page. The Device Groups page appears to be blank.

    Workaround: Restart the config-server microservice.

  • If you add an unmanaged device on the Device page and later edit the hostname of the unmanaged device, the hostname is not reflected in the device group and in the Devices dashlet on the Dashboard.

    Workaround: There is no known workaround.

  • You cannot provision a segment routed LSP (through PCEP or Netconf) on Cisco IOS XR devices.

    Workaround: There is no known workaround.

  • The Bring Your Own Ingest (BYOI) feature is not supported. You cannot define your own ingest types.

    Workaround: There is no known workaround.

  • On the Configuration > Device page, sometimes the management status of a device is displayed as Down even though the connection is established.

    Workaround: There is no known workaround.

  • If you change the hostname of a device on the Configuration > Device page or through APIs, the changes are not reflected on the Add Device Group page.

    Workaround: There is no known workaround.

  • The periodic aggregation function in the ingest pipeline ignores the packets that are arrived out of sequence (for example, this can happen for the UDP ingest). These packets are later not considered in the aggregation calculation, which in turn can result in some data deviation in the JTI telemetry data (bps/pps).

    Workaround: There is no known workaround.

  • If you deploy playbook instances back-to-back, the deployment may fail due to a database error. This is a rare scenario.

    Workaround: You can redeploy or roll back the configuration as this is a timing issue.

  • The Edit Device Group operation fails if you try to add an unmanaged device to an existing device group.

    Workaround: There is no known workaround.

  • For Cisco IOS XR devices, you must set the default Netconf port to 22, otherwise you cannot view alarms on the Alarm page.

    Workaround: Manually set the Netconf port to 22.

  • If you select a saved query on the Alarms page, the alarms are filtered based on the saved query. But, the graph and the date are not updated.

    Workaround: There is no known workaround.

  • P2MP groups configured by PCEP with flowspec mapping to multicast VPN service is not supported

    Workaround: There is no known workaround.

  • Cisco MDT is not supported.

    Workaround: There is no known workaround.

  • After you reset the topology, if the NETCONF connection status for a node is blank, then select the node and click More > Request NETCONF Reconnect, otherwise the NETCONF provisioning fails for such nodes.

    Workaround: There is no known workaround.

  • When you update a playbook, the new changes in the playbook are not applied to the existing instances of the playbook. For example, a playbook instance that is associated to a device group is not updated when the playbook is edited or updated. Workaround: You must delete the existing playbook instance and create a new one for updates to be applied.

    Workaround: There is no known workaround.

  • By default, the topology filter is disabled. You cannot enable the topology filter field using GUI.

    Workaround: You can enable the topology filter using the following procedure:

    1. Log in to the ns-toposerver pod:

      kubectl exec -ti -n northstar ns-toposerver-Pod ID-c ns-toposerver -- bash
    2. Update the northstar.cfg file that is available at the /opt/northstar/data/ location.

      sed -i "s|^bmp_host=.*|bmp_host=ns-filter|;s|^bmp_port=10002|bmp_port=10004|;" /opt/northstar/data/northstar.cfg
    3. Apply changes to the configMap file.

      sed -i "s|^bmp_host=.*|bmp_host=ns-filter|;s|^bmp_port=10002|bmp_port=10004|;" /opt/northstar/data/northstar.cfg
    4. Verify whether the Topology Filter field is enabled in the GUI.

  • You cannot export audit logs in the pdf format.

    Workaround: There is no known workaround.

  • If you use Flex Software License Model for a device or if you are using devices running Junos OS Evolved, then those devices are not discovered in Paragon Automation.

    Workaround: You can add such devices as unmanaged devices.