R12.1-JA-2025June05

Lack of Out Interface in Route Table

Lack of Out Interface in Route Table

Error Code: OM-009-001

Description

If the path calculation is very slow, follow the instructions below.

Troubleshoot

  1. Enable the path debug mode.
    Graphical user interface, text, application, email Description automatically generated
  2. Check the path execution time info and find out which node and which procedure costs longer than expected.

  3. If you cannot fix the issue, collect the required data and feedback to NetBrain Platform/Dev team for troubleshooting.
  4. Collect Data:
  • Map Data:
    • Enable the path debug mode.
      Graphical user interface, text, application, email Description automatically generated
    • Export Map by clicking Contact NetBrain to export node data. Remember to draw all the nodes/devices involved in the path on the map and expand all their neighbors before exporting the map.
      Diagram Description automatically generated
  • Python Error &Debug Logs: Copy the python error logs from the worker server and front server. Make sure the timestamp of the log is within the issue happened (Enable the python log print first before collecting logs data).
  • Customer Network Figure: Feedback the network design figure that can show the path flow.

Sample Case

Case 137041: https://nbtech.lightning.force.com/lightning/r/Case/5008Z00001quQxBQAU/view.
 
Root Cause: Many VMs have been configured under the VNet Router. So when the path reaches VNet Router and tries to find the destination VM, the route of VRT matched does not have an out interface but only destination IP, so it costs a long time to search all VMs globally.
Solution: Add the subnet routes that include the out interface to destination VM.

The blue highlighted routes were matched before and caused the path slowness issue. The red highlighted routes were newly added to fix this issue.


Scenario 4: Azure Path Calculation Slowness Scenario 5: Azure NCT Live Retrieve Failure