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

  • You cannot delete a Monitor from the Monitor-Name page (Observability > Active Assurance > Monitors > Monitor-Name).

  • When you upload the topology network resources for a service, you must ensure that the interfaces are not channelized; otherwise, the placement fails.

  • The following ports are reachable from outside the Paragon Automation cluster; we recommend that you block access to these ports: 22, 443, 2222, 2379, 2380, 5473, 6443, 7472, 7946, 8443, 9345, 10250, 10260.

    Note:

    These ports should not be blocked for intra-cluster communication.

  • The request service project add /data-models/projects/project-name command fails if the project that is being added has a dependency on another project. For example, if the onboard.tgz has a dependency on network-resource.tgz, then the request service project add /data-models/projects/onboard.tgz command fails.

  • When you enable the Show LEDs, Ports & Cables on Chassis toggle button on the Hardware accordion (Observability > Troubleshoot Device > Device-name > Overview Tab), the chassis view displays the port status incorrectly.

  • On the Hardware accordion (Observability > Troubleshoot Device > Device-Name), the value of available units for CPU and Memory is always displayed one extra compared to the units that are actually available on the device. This issue occurs for the following devices: ACX7100-32C, ACX7100-48L, ACX7024, ACX7024X, ACX7509, ACX7348, MX204, MX240, MX304, MX480, MX960, MX10004, MX10008, MX10016.

  • While configuring a Site Network Access for an L3VPN service, the minimum value that you must specify for Service Input Bandwidth and Service Output Bandwidth fields must be 20,000 bps. Otherwise, the service provisioning fails.

  • The customer name and the VPN ID must be unique when you create an L3VPN service order. Otherwise, the service order creation fails.

  • If an adopted device and a node that is not yet onboarded have the same serial number, then they are listed as two different devices on the Put Device Into Service page (Inventory > Onboarding Dashboard).

  • The Optical Rx Power and Optical Tx Power charts do not display any data when you click the Input Traffic data-link on the Interfaces accordion (Observability > Health > Troubleshoot Devices > Device-Name > Overview).

  • While creating or modifying an L3VPN service, you cannot set the Access Diversity settings parameters on the Site Network Access page and set the device references simultaneously. The placement fails to place the site network access on an available port.

  • When you navigate to chassis view (Observability > Troubleshoot Device > Device-name > Overview Tab > Hardware accordion) and either try to access the minimize/maximize controls or wait for a minute or two, sometimes an “Error occurred in the component” message is displayed and the entire Overview tab blanks out.

  • The VPN ID field on the Add or Modify L3VPN page is restricted to 9 characters to avoid failure of L3VPN service provisioning. This restriction is due to a configuration field size limit on Junos OS.

  • When you run the request paragon ssh-key command, the previously-generated SSH keys in .ssh/authorized_keys and the SSH keys that you have added are cleared, and new SSH keys are generated for nodes.

  • Paragon Automation does not push firewall filter configuration to ACX Series devices as firewall filter configuration is not supported on them.

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

  • If you make multiple changes to a service order before executing a service order then only the last service order has a workflow associated with it. When you delete a service instance the order history also gets deleted.

  • The output of the request paragon storage cleanup command erroneously displays the total reclaimed space as 0 bytes even though multiple files are cleared after executing this command.

  • If you modify an existing L3VPN service to update certain fields such as access diversity, zip code, or device reference, the service provisioning fails as the outdated placement-related information is sent to the REST API.

  • When SMTP is configured through Paragon Shell, and you enable e-mail notification for alerts and alarms, the e-mails are sent from no-reply@mailservices.juniper.net, instead of what is configured through Paragon shell.

  • When you enable e-mail notification for alerts and alarms, e-mails are sent to the recipients even if system-wide SMTP is not configured through Paragon Shell.

  • You might be able to execute REST APIs that are not supported.

  • Initially, no data is displayed on the Fans charts when you select time ranges other than 30m on the Hardware Details for Device-Name page in the Hardware accordion (Observability > Troubleshooting Devices > Device-Name). Based on the time range you have selected, you need to wait for the following time duration for the data to be populated:

    • 3h—Approximately 10 minutes.

    • 1d—Approximately 1 hour.

    • 1w—Approximately 7 hours.

  • Even though the Delete L3VPN Service operation is successful, the service order and the resources allocated to the service are not removed.

  • When you modify the VPN ID for an existing L3VPN service, the provisioning fails because the PAA RPM monitor refers to the old routing instance.

  • The service orchestration engine onboards nodes in a network implementation plan sequentially even if the devices are adopted simultaneously. The service orchestration engine can onboard devices in different plans concurrently. We recommend that you do not onboard more than 3 devices, spread across 3 different plans, concurrently.