R12.1-JA-2025June05

Find Next Hop Failed

Find Next Hop Failed

Error Code: NF-008-001

Description

If the path failed, check the node/device which causes the failure and find the cause message in the path logs details. If you see Path Failed message in Find Next Hop procedure, follow the instructions below.

Troubleshoot

  1. Check the path log details and see if the specific route has been matched. For example, if it matches the route in VRT (virtual route table), check if the out interface and next hop device in VRT data look good or not.
  2. Check whether an error message contains "No Azure VNIC Effective Virtual Route Table was found".
  3. Open the VRT from node and check the table content.
    If it is empty, open the plugin manager to debug and run the Azure VRT plugin to trigger the VRT generation again.
  • Check if the VRT becomes normal or not. If not, collect the data and feedback for further troubleshooting.
  • If the out interface and next hop device are correct, then extend the neighbor to find the next hop device and the corresponding out interface on the map.
    • If you cannot find the expected neighbor, then troubleshoot why it is missing.
    • If you cannot find the root cause and fix the issue, collect the data and feedback for further troubleshooting.
  1. 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 the 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 log data).
  • Customer Network Figure: Feedback the network design figure that can show the path flow.

Sample Case

Case 139610: https://nbtech.lightning.force.com/lightning/r/Case/5008Z00001rkr2SQAQ/view.


Python Error Scenario 4: Azure Path Calculation Slowness