October 15, 2024
New Features
This section describes the new features released in Juniper Mist Routing Assurance.
Support for ACX7100-48L Router
You can onboard the ACX7100-48L Cloud Metro Router to Juniper Mist Routing Assurance. Juniper Mist Routing Assurance enables you to monitor the performance of these routers by viewing the insights collected from them.
You onboard a router by logging into the router's CLI and committing the outbound SSH configuration that Juniper Mist Routing Assurance provides. After a router is onboarded and is assigned to a site, you can start monitoring it.
[See Onboard a Router.]
Monitor Router Throughput SLE
Router Throughput SLE enables network administrators to assess the network's ability to pass traffic without impedance. The Router Throughput SLE score is an indicator of how the router is performing in the network. You can use the actionable insights and visualizations displayed in the Monitor > Service Levels > Routing Tab to evaluate the end-user experience on the network.
You can:
View the percentage of time when the network throughput was optimal.
View specific factors contributing to degradation of router throughput.
View visualizations for distribution, timeline, and statistics of service level failures on the Root Cause Analysis page. You can use these visualizations to understand the scope of issues that impact a router's throughput.
You can use the Router Throughput widget to assess the routing efficiency and the network's overall performance.
[See Router Throughput SLE.]
Known Issues
This section lists the known issues in Juniper Mist Routing Assurance.
For MX304 routers running Junos OS release 22.4R3.25 or earlier, Throughput SLE reports auto-negotiation failure. This is because auto-negotiation is not supported in Junos OS releases prior to 23.1.
Workaround: Upgrade the router to Junos OS release 23.1 or later. Auto negotiation feature was introduced in Junos OS release 23.1.
Sometimes, Throughput SLE reports the SLE score based on a single interface without considering the contribution from other interfaces.
Workaround: None.