Resolved Issues | Juniper Routing Director 2.8.0

When you download the Tunnels or Demands table using the Download option (Planning > Networks > Offline Models > Model-Name > Open > Tunnels or Demands tab), the CSV file incorrectly displays the Route Object value as [object Object].

Sometimes, continuous packet drops that happen under some specific trap codes may not be classified as a blackhole.

If the node name contains uppercase letters, then the request deployment backup schedule command fails. This occurs because of the RFC 1123 host name validation rules.

The signal functionality section (Observability > Health > Troubleshoot Devices > Device-Name > Overview > Interfaces (accordion) > Output Traffic) does not display any alerts even when alerts exist.

Management of Link Aggregation Groups (LAGs) from the Aggregated Ethernet Interfaces section of the topo resource instance is deprecated. Instead, LAGs are pre-created outside of the overlay service designs, which consumes only individual units on the Aggregated Ethernet (AE) interface. Additionally, upgrading to release 2.7.0 or later is not supported for instances using overlay-provisioned LAG interfaces.

Alert notifications through webhook and e-mail do not contain certain information, such as which alert triggered the notification, the device ID, and so on. The email notification that is sent to the users does not include essential information, such as message, hostname, deviceMAC, Key, and so on.

New network events (such as link status and LSP path changes) received through Web Socket do not support custom port forwarding. The Topology page (Planning > Networks > Offline Models > Model-Name > Open) does not automatically reflect network status changes.

When you update the AS number on the Dynamic Topology tab of the Topology Settings Options page (Observability > Topology > Settings icon), the updated AS number is not reflected in the containerized routing protocol process (daemon) (cRPD).

You cannot undelegate an SR LSP that is configured using NETCONF from Cisco devices.

When you try to delete segment routing (SR) tunnels using the Routing Director GUI, the tunnels may not be deleted in the first attempt if there is a color conflict. This issue is seen in only SR tunnels that have a color conflict.

During the installation of Test Agent on the JunOS EVO (such as ACX) devices, there can be few scenarios where the installation may get stuck in CONFIGURING state (due to slowness in router or some environment issue) for more than 10-15 minutes.

Before you upgrade an EVPN service instance that was created in a release earlier to Release 2.5.0, ensure that you update the vpn-resources instance to Release 2.5.0.

When a user with an administrator role clears the explicitly configured link speed on a physical interface within an EVPN LAG, the speed resets to 10 Mbps. Currently, only explicit speed values are supported. For help in removing the default value, contact Juniper Networks® Technical Assistance Center (JTAC).

Although the qinq option is listed for the Tag Type field, we do not support qinq in VLAN-aware tagged EVPN services. We recommend that you do not select the qinq option as the L3VPN provisioning might fail with a validation error.

The traffic statistics are not displayed on the Passive Assurance tab (Orchestration > Instances > Service-Instance-Name > Service-Instance-Name Details) for an L3VPN service with Integrated Routing and Bridging (IRB) interfaces.

When you stitch a Layer 2 circuit with an L3VPN service, the Input Traffic Rate and Output Traffic Rate columns on the logical Interfaces accordion of the Passive Assurance tab (Orchestration > Instances > Service-Instance-Name > Service-Instance-Name Details) are blank.

When there are two VLAN-aware tagged EVPN services, in placement section of an L3VPN service with Integrated Routing and Bridging (IRB) interfaces, both EVPN instances are not listed.

When you change the IRB reference in the L3VPN configuration, the L3VPN service might display an error when you perform the placement operation.

In a scaled setup, while provisioning VPN instances with a large Site Network Access (SNA) or access interfaces, you might notice VPN resource placement conflicts in the Arango database. Due to this conflict, you won’t be able to onboard any device and provision a VPN instance.

Note: For EVPN or L3VPN deployments, we recommend that you limit each VPN instance to a maximum of 20 SNAs or access interfaces.

You might encounter a placement failure-related error when you try to upgrade the service instance for EVPN from Release 2.4.1 to Release 2.7.0.

The placement fails because the speed field is marked as a key for placement_interface options in Release 2.7.0, while the options generated in the Release 2.4.0 service instance do not have the speed field.

In a multihomed EVPN service, the GUI and the device configuration show different Ethernet Segment Identifier (ESI) values.

After you upgrade Routing Director from Release 2.5.0 to 2.7.0, the provisioning of a service order with LAG interfaces configured fails. This is because provisioning of LAG Interfaces is deprecated starting from Release 2.7.0, and you need to configure LAG Interfaces through the network implementation plan.

When you create an L3VPN service order with two OSPF sessions, and if one of those sessions fails, then the alerts are not displayed on the VPN State accordion of the L3VPN details for L3VPN-Name page (Orchestration > Instances > Service Instances > service-instance-name hyperlink > Passive Assurance tab > L3VPN accordion > L3VPN-Name).

The Input Traffic boundary is incorrectly displayed for Optical Rx power and Input Traffic KPIs. This issue occurs when you onboard a device and then stream data at a later point.

The SPFRun anomaly might not get detected when both levels are enabled in IS-IS.

This issue does not apply to devices where only one level is enabled in IS-IS. A level can be disabled in IS-IS using the set protocol isis level <level-number> disable command.

When onboarding and enabling BGP analytics for vMX routers, sometimes, the BMP configuration fails because Routing Director components cannot resolve the management IP address of the vMX routers. This issue is limited to vMX routers.