Resolved Issues | Juniper Routing Director 2.10.0

If you use previously-deleted tunnel names, creation of NETCONF RSVP tunnels sometimes fails on Cisco devices.

Telemetry backup does not include information about airflow workflows. As a result, when running the following command, you may encounter an error:

Under high system load, the following stream processes may exhibit sustained 100% CPU utilization:

alarm-event
device-profiles
papi-events
papi-mon-v2
papi-switch-stats

This behavior occurs when a stream process becomes stuck in a processing loop. No known functional impact has been observed. However, affected processes may consume excessive CPU resources.

The gnmi-term pod may exhibit a gradual increase in memory usage over time. This behavior is most noticeable in environments where a large number of devices repeatedly fail session creation, typically because the devices have not been onboarded in PAPI. Continuous session creation failures can lead to sustained memory growth in the pod.

If there are multiple ECMP diverse paths and if you have enabled periodic re-optimization, then the diverse LSPs might switch back and forth between two routing paths.

The Re‑parse option on the Advanced tab of the Topology Settings page (Observability > Network > Topology > Topology Menu Bar > Settings icon) is currently not functional. When invoked, previously-collected device configuration output is not re-parsed as expected.

When you create a Monitor with 600 streams, you might encounter Monitor Creation Timeout error and the Monitor might automatically stop.

The results produced by the Test Agent are impacted if the Test Agent clock has a large offset. That is, if the local time is in the past or future. This means:

Timestamps for Metrics for any Stream produced by a Measurement running on that Test Agent are affected.
Event activation time and event deactivation time are affected.

Therefore, it can result in the incorrect evaluation of Test Execution, as Metrics or Events are not included in the time range the system considers as the Test Execution run time. You may not be explicitly warned about this situation. However, the issue manifests with time shifted metrics or events.

Deleted Test Agents are not listed on the Test Agents tab of the Applications page (Observability > Health > Health Dashboard > Active Assurance (Tab) > View Details > Application page > Affected Items).

The victoria‑metrics service in routingbotdb may crash because the required cache folder is not created under /vm-data during deployment. This causes the victoria‑metrics pods to restart after running for some time.

Under high load, the summarization of licensing information shown on the Features tab (Observability > Health > Troubleshoot Devices > Device-Name > Inventory) may be delayed. However, the licensing information will eventually be consistent with the network.

While creating or editing a device profile, if you have enabled ORE and Smart KPI Engine toggle buttons, then AI-ML-related rules are not instantiated.

Workaround: None.

When you import devices in bulk into Routing Director, any device that is part of a network implementation plan may cause the plan to be locked while the configuration from the plan is being committed. During this period, imports for other devices in the batch can fail with the error code, HTTP 423 Locked.

You cannot import the devices that fail to import by adding them to a new batch because they have already been registered in the inventory as part of the original batch. In large batches, the network implementation plan locks may remain active for an extended period, as configuration commits must complete on all devices in the batch before the lock is released. As a result, device import failures can persist until all the device onboarding operations associated with the Network Implementation Plan have finished.

The following unintended configurations, which are part of the paragon-service-orchestration group, are automatically pushed to ACX devices at the time of onboarding.

After you install or upgrade Routing Director, the status of OpenSearch may be shown as yellow (amber) or red.

Monitors do not enforce a limit on the number of measurements they can generate, and Routing Director does not restrict the number of monitors you can create. In large‑scale setups, starting or stopping a very high number of measurements (for example, 25,000) across multiple monitors at once can trigger a burst of operations. This leads to significant delays before operations are complete.

In EVPN VPWS deployments, placement validation may fail for certain multihomed Customer Edge (CE) topologies when access links connected to the same physical CE device are configured with different CE reference names.

You cannot use a Transport Layer Security (TLS) certificate to onboard Nokia devices.

When you assign a new site to a device, although you receive a confirmation message about the site change, the change may not be reflected on the Inventory page (Inventory > Devices > Network Inventory) or the Troubleshoot Devices page (Observability > Health).

If a superuser triggers a password reset and you have enabled two-factor authentication, then you will be prompted to change your password. However, when you click the change password option, you may encounter the following error:

Request failed with status code 401

After you take a backup and restore a Routing Director instance, some Test Agents might incorrectly display status as Online.

The Task Config section may sometimes not be rendered in the generated PDF when Monitor reports are generated repeatedly.

There is an unexpected delay in reporting an anomaly related to a sudden decrease in nodes. The anomaly is reflected only after the total delay period has passed.

Alerts are not displayed on the Relevant Events section of all accordions on the Passive Assurance tab (Orchestration > Instances > Service Instances > Service-Instance-Name hyperlink).

When devices under monitoring fail catastrophically and are subsequently offboarded from Routing Directory, these stale devices may still show up in the Route Explorer's devices table (Observability > Routing > Devices tab).

For devices running on Junos OS or Junos OS Evolved Release 22.3R1 or later, IS-IS interface statistics are streamed at the IS-IS level. This behavior can cause duplicate counter processing for the same interface, which may result in false interface‑level ISIS alerts.

The following KPIs are impacted: CSNP drops, ESH drops, IIH drops, ISH drops, LSP drops, PSNP drops, and unknown drops.

When using LLM Connector, you can change models within the chat window during an active conversation. However, selecting a different model does not actually switch the model. The LLM Connector continues to use the originally selected model, which can be confusing if you are expecting a live model change.

When querying the MCP server, inconsistent argument naming for MAC address parameters across multiple tools (For example, mac, router_mac, device_mac) causes the AI model to hallucinate incorrect argument names.

When using the LLM connector in Firefox, the response text appears garbled in streaming mode. The same response renders correctly from Conversation History.

When the http_url in the MCP configuration file (config.json) ends with a trailing slash (/) and when the Routing Director's MCP server functionality (junos_config_commit tool call) for pushing commits onto the Junos device is called, the MCP server incorrectly constructs the API URL with a double slash (//). This results in a 400 Bad Request error and fails to execute the tool call.

When configuring Document Connector Configuration (Settings Menu > System Settings > Organization Settings page > Configure LLM Connector title > Documentation tab > + ), the base URL must not end with a trailing slash (/). URLs ending with / are currently not supported and may cause errors during connector operations.

While editing a rule (Observability > Health > Smart KPI Assistant > KPI Workspace > Rules > Edit option), if you modify any organization-level variable, then all other unmodified variables are reset to empty strings, overriding their default values.

Workaround: While modifying organization-level variables, you must also set default values for all other variables to preserve their intended defaults.

The approval status of a recommended KPI may remain unchanged even after the recommendation is removed.

The system rules are not automatically enabled for recommendation when you upgrade a Routing Director setup that has custom rules with the specific topic “custom”.

In some scenarios, after you restart the RESTHandler service, the topology map may stop receiving live updates for link utilization labels and link state changes. The topology data itself remains current; however, updates may not be reflected on the map until the browser is refreshed.