This article provides troubleshooting steps for the issue where direct and static routes are not being advertised via BGP.

In the problematic state, the policy-options are configured and mapped to BGP; however, the show route advertising-protocol bgp <neighbor_IP> command does not display the direct and static routes as being advertised.

Please follow the steps below to isolate and resolve the issue:

1) Verify route presence:

Ensure that the static and direct routes are present in the routing table.

2) Check route-filter configuration:

If a route-filter is configured with the exact match type, the exact route (including CIDR) must exist in the routing table.

3) Validate policy match criteria:

Confirm that the from clause in the policy-option term includes protocol static and protocol direct, as applicable.

4) Avoid unintended matches:

Make sure the policy is not matching attributes unrelated to static or direct routes (e.g., BGP-specific attributes like bgp-origin), which may prevent the intended routes from being advertised.