This article describes a scenario where traffic is dropped by the SRX with the reason "no route to destination", even though the destination route is present in the routing table of a routing instance.

The following symptoms may be observed:

The issue may occur when the routing instance is missing the required virtual-router configuration statement. As a result, the routing instance is not functioning as intended, causing route lookups to fail during packet forwarding even though the route appears in the routing table.

• Traffic is dropped on the SRX firewall.
• Flow trace or security logs indicate the drop reason as "no route to destination".
• The destination route is present and active in the routing table.
• The route is learned or configured under a specific routing instance.
• Route lookup appears successful when verifying the routing table, but traffic continues to be dropped.

The issue may occur when the routing instance is missing the required virtual-router configuration statement. As a result, the routing instance is not functioning as intended, causing route lookups to fail during packet forwarding even though the route appears in the routing table.

Verify the configuration of the affected routing instance and ensure that the routing instance type is configured correctly.

Example:

set routing-instances <instance-name> instance-type virtual-router