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 Routing Director Release 2.5.0:

  • If you have upgraded the topology resource from Release 2.2.0 or Release 2.3.0 to Release 2.4.0 and if you later edit and provision a service instance (L3VPN or EVPN) that was created in an older release (Release 2.3.0 or Release 2.2.0), then the provisioning of the service instance fails.

  • While creating or modifying an EVPN service order, you cannot configure multiple VLAN IDs on the Aggregated Ethernet (AE) interface. The EVPN considers the AE port as a single resource and therefore an AE interface cannot be reused across service instances even when the VLAN IDs on the AE IFL differ.

  • When the worker node is down, there might be issues if you create an organization or onboard a device.

  • When you run the request paragon deploy cluster or request paragon service start commands, sometimes deployment may fail because the config.yml is empty. In such cases, the log file might display an error similar to this:

  • Due to the changes in telemetry paths, you cannot view IS-IS data for ACX7020 devices on the Routing and MPLS accordion (Observability > Health > Troubleshoot > Devices > Device-Name).

  • If a device is discovered through a BGP-LS peering session even before you onboard the device, then duplicate LSPs are created when a PCEP session is established with the device. In rare cases, the duplicate LSPs that are created will continue to remain.

  • The "vpn_svc_type" service type is displayed as "pbb-evpn" instead of "evpn-mpls" on the Routing Director GUI and through the REST API.

  • You cannot run multiple versions of plug-ins on a Test Agent.

  • If no valid interface option is available for a CE and PE device combination, then the Interface drop-down will be empty.

  • The Route Explorer page (Observability > Routing) displays data only if you have installed Junos OS or Junos OS Evolved Release 23.2 or earlier.

  • In a rare case of running multi-level ISIS protocols on a link, the topology map might not be updated or might not reflect the latest live operation status.

  • After you update a Monitor or a Test Template that is created by another user, the Updated By column on the Monitors (Observability > Active Assurance) and Test Template (Inventory > Active Assurance) pages do not reflect the name of the user that modified the Monitor or the Test Template.

  • When you onboard devices in batches, due to Kubernetes' horizontal pod autoscaling of airflow-worker pods, the onboarding might fail for the devices that are in the middle of the onboarding process.

  • The Output Traffic rate column on the Logical Interface accordion (Orchestration > Instances > Service Instances page > service-instance-name hyperlink > Service-Instance-Name Details) displays some data even when there is no traffic through the devices.

  • While modifying an existing L3VPN service instance, if you try to remove a device that is already a part of a network implementation plan then the modify workflow fails.

  • After you upgrade Paragon Automation from Release 2.2.0 to Release 2.4.0, ensure that you upgrade the L3VPN service instance before you upgrade the topology resource instance; otherwise, you might encounter issues.

  • If you upgrade Paragon Automation from Release 2.3.0 to 2.4.0, then you might not be able to modify VLANs for Site Network Accesses on the existing L3VPN service instances.

  • The maximum size of a configuration template supported is 1 MB and not 10 MB as indicated in the error message on the GUI.

  • The devices table on the Devices tab (Observability > Health > Health Dashboard > Active Assurance (Tab) > Click any accordion > View Details > Affected Items tab) does not list devices that have unhealthy measurements.

  • When you click a Monitor on the Monitors page (Observability > Active Assurance), the Monitor-Name page takes approximately a minute to load the data. This issue occurs only when there are more number of events in the system.

  • If you had installed Test Agent on a router while using Juniper Paragon Automation Release 2.3.0 or earlier releases, and later if you upgrade to Paragon Automation Release 2.4.0, then Test Agent that was installed earlier will not be upgraded to the latest version of Test Agent. You cannot run Tests or Monitors on this router.

  • Due to changes in XML Path Language (XPath), some custom rules cannot collect KPI information from the device.

  • The View Network Resources page (Inventory > Device Onboarding > Network Implementation Plan > More) doesn't display AE interfaces-related details.

  • Onboarding a QFX device to Routing Director fails if Trust is enabled in a device profile applied to the QFX device.

  • You might not be able to view the Tests page (Observability > Active Assurance) if your role type is Observer.

  • The vmrestore tool restores data into vmstorage pods. While performing restore, the tool creates a lock file that prevents any other application from accessing data during the restore phase. However, sometimes the vmrestore tool fails to clear the lock file and the vmstorage pods cannot access data.

  • If you have onboarded a Cisco device, but later changed the TLS settings on the device (either turn it on or off), the status of the device will show as Disconnected on the Inventory page.