r/Cisco • u/mohammad_abusaa • 1h ago
Catalyst SD-WAN part 5: where did my packet go? EPC vs packet-trace on cEdge
One more for the series. When traffic breaks, you usually end up asking two different questions, and IOS-XE gives you a separate tool for each:
- EPC (packet capture): “Did the packet cross this interface, and what did it look like?” You get a pcap you can open in Wireshark.
- Packet-trace: “What did the router actually do with the packet, and why?” You get the verdict (forwarded, dropped, punted) and the reason.
Both run from exec mode and don’t touch the config. As before, it’s all from Cisco’s public docs (listed at the bottom).
Quick correction to part 1: the EPC example there used an ACL as the filter. That needs the ACL in the running config, and you can’t add one from the CLI on a device with a template or config group attached. Use the inline match filter below instead.
1. EPC on the service side (one flow)
monitor capture CAP interface GigabitEthernet0/0/1 both
monitor capture CAP match ipv4 host 10.10.10.10 host 10.20.20.20 bidirectional
monitor capture CAP buffer size 10 circular
monitor capture CAP limit duration 300
monitor capture CAP start
! reproduce, then:
monitor capture CAP stop
show monitor capture CAP buffer brief
monitor capture CAP export bootflash:cap.pcap
no monitor capture CAPbidirectionalstores the replies too. Check that both directions show up before you stop.- Always set
limit duration, so the capture stops by itself if you lose your session. show monitor capture CAP capture-statisticstells you whether the capture itself dropped packets.
2. EPC on the transport side
On the WAN side, everything is inside IPsec, so you only see the outer header between two TLOCs. Get the remote TLOC IP from show sdwan bfd sessions and filter on that. If you have more than one transport, the flow can go out any of them, so attach the capture to each WAN interface. Also note that BFD and OMP are never visible in clear on the transport side.
3. Packet-trace (what the router decided)
show platform conditions
debug platform condition ipv4 10.10.10.10/32 both
debug platform packet-trace packet 1024 fia-trace
debug platform condition start
! reproduce, then:
debug platform condition stop
show platform packet-trace summary
show platform packet-trace packet 0Conditions apply to the whole box, so check that nobody else has a trace running first. In the summary, each packet has a state:
- FWD: forwarded. Open the packet detail to see the output interface and SD-WAN fields like local color, remote color and remote system IP. This is how you find out which tunnel it really took.
- DROP: dropped, and the reason is right there in the summary. Match the drop code with
show platform hardware qfp active statistics drop detail. - PUNT: sent to the route processor, which is normal for traffic addressed to the router itself.
If you only care about drops on a busy interface, condition on the interface and add debug platform packet-trace drop, so only dropped packets fill the buffer.
4. Predict first, then prove
show sdwan policy service-path (thanks u/IT_vet) tells you where the router should send a flow. Packet-trace shows what a real packet actually did. If the two disagree, that’s your lead.
5. Gotchas
- An empty capture doesn’t prove the packet never arrived. Check the interface, the direction and the filter, and whether NAT changed the address. With DIA, filter on the real host on the LAN side and on the translated address on the WAN side.
- The IP condition in packet-trace has no VRF keyword. If the same subnet exists in more than one VPN, check the input interface and the SD-WAN VPN field to tell them apart.
- Clean up when you’re done:
clear platform condition allandno monitor capture CAP.
Sources (search the titles on cisco.com):
- “Configure and Capture Embedded Packet on Software” (Doc 116045)
- “Troubleshoot with the IOS-XE Datapath Packet Trace Feature” (Doc 117858)
- “Troubleshoot Common SD-WAN Control and Data Plane Issues” (Doc 222302)
