- Home
- Multi-Cloud Networking
- Customer Edge diagnostics
- Diagnostic workflows
- Traffic arrives but does not get through
Traffic arrives but does not get through
For a site that is ONLINE with BGP established. If routes are the problem, start
with BGP.
-
Is anything being discarded, and why?
dropstats-non-zero. Run it twice while reproducing the problem: these are lifetime totals, so a non-zero counter means nothing on its own and a rising one means everything. -
Find the specific connection.
flow-l-matchwith the address, or address and port. The action on the flow is the answer:Fforward,Ddrop,NNAT. A flow present with actionDis a deliberate policy decision, and sends you to policy rather than to connectivity. -
No flow at all? The traffic is not reaching the data plane. Confirm the data plane has claimed the interface you expect with
vif, and compare its counters against whatipreports.The two views legitimately differ, because traffic the data plane handles never reaches the kernel. Zero RX on the interface you expect does not.
-
Flow present and forwarding, still not arriving? Check where it is being sent:
rtfor the route, thennhto resolve the next hop. A next hop of typeDropis a blackhole, and aTunnelnext hop puts the tunnel itself in scope. -
If the path is through a tunnel, confirm it is both up and carrying bytes with
ipsec-statusall. A tunnel established for hours with near-zero counters is up and unused, which points back at routing.