Skip to content

virtual-wan-route-maps-troubleshoot.md

Latest commit

 

History

History
47 lines (29 loc) · 3.28 KB

virtual-wan-route-maps-troubleshoot.md

File metadata and controls

47 lines (29 loc) · 3.28 KB
author cherylmc
ms.service azure-virtual-wan
ms.topic include
ms.date 03/01/2024
ms.author cherylmc

Route map has entered the failed state

Please open a support case.

Summary routes aren't showing up as expected

  1. Remove the route map, then view the current routes on the connection. Verify that the routes are the routes you expect to see BEFORE a route map is applied.

  2. Verify the match condition is set correctly. The match condition is used to select the routes you want to modify.

    • If you are matching all routes instead of just the ones you selected: Remember, if a route map is created without a match condition, all routes from the applied connection will be matched.
    • If you have match conditions and you are still not selecting the routes you would like: Check the match criterion to ensure it's set correctly. Remember, equal matches the exact prefix and contains matches prefixes within the route. (e.g 10.2.30.0/24 would be included in a contains for 10.2.0.0/16)
    • If you are using the "contains" match criteria: Verify that your subnetting is correct.

  3. Verify the action is set correctly. Summarizing routes requires the Replace action.

  4. Make sure the Next step setting is configured correctly. If you have multiple route maps rules and you aren't seeing the desired output, make sure the last rule has the Next step setting is set to Terminate. This ensures that no other rules are processed.

  5. After making changes, apply the route map to the connection. Then, use the route maps dashboard to verify the changes had the desired effect.

AS-PATH isn't showing up as expected

  1. If you're summarizing a set of routes, remember the hub router strips the AS-PATH attributes from those routes. You can add the AS-PATH back in the action section.

  2. Remove the route map, then view the current routes on the connection. Verify current routes are the routes you expect to see BEFORE a route map is applied.

  3. Verify the match condition is set correctly. The match condition is used to select the routes you want to modify.

    • If you're matching all routes, instead of just the ones you selected: Remember, if a route map is created without match conditions, all routes from the applied connection will be matched.
    • If you have match conditions and you're still not selecting the routes you would like: Check the match Criterion to ensure it's set correctly. Remember, equal matches the exact prefix and contains matches prefixes within the route. (e.g 10.2.30.0/24 would be included in a contains for 10.2.0.0/16)
    • If you're using the "contains" match criteria: Verify that your subnetting is correct.

  4. Verify the action is set correctly. Make sure the replace or prepend setting is set as desired.

  5. When you're adding ASNs to the AS-PATH, verify you aren't using an ASN reserved by Azure.

  6. Make sure the Next step setting is configured correctly. If you have multiple route maps rules and you aren't seeing the desired output, make sure the last rule has the Next step setting set to Terminate. This ensures no other rules are processed.

  7. After making changes, apply the route map to the connection. Then, use the route maps dashboard to verify the changes had the desired effect.