300-710 · Question #291
An engineer must investigate a connectivity issue from an endpoint behind a Cisco FTD device and a public DNS server. The endpoint cannot perform name resolution queries. Which action must the…
The correct answer is A. Use the Capture w/Trace wizard in Cisco FMC. To trace a real packet is very useful to troubleshoot connectivity issues. It allows you to see all the internal checks that a packet goes through. Add the trace detail keywords and specify the number of packets that you want to be traced. By default, the FTD traces the first…
Question
An engineer must investigate a connectivity issue from an endpoint behind a Cisco FTD device and a public DNS server. The endpoint cannot perform name resolution queries. Which action must the engineer perform to troubleshoot the issue by simulating real DNS traffic on the Cisco FTD while verifying the Snort verdict?
Options
- AUse the Capture w/Trace wizard in Cisco FMC.
- BRun the system support firewall-engine-debug command from the FTD CLI.
- CCreate a Custom Workflow in Cisco FMC.
- DPerform a Snort engine capture using tcpdump from the FTD CLI.
How the community answered
(58 responses)- A76% (44)
- B3% (2)
- C5% (3)
- D16% (9)
Explanation
To trace a real packet is very useful to troubleshoot connectivity issues. It allows you to see all the internal checks that a packet goes through. Add the trace detail keywords and specify the number of packets that you want to be traced. By default, the FTD traces the first 50 ingress In this case, enable capture with trace detail for the first 100 packets that FTD receives on the INSIDE interface: > capture CAPI2 interface INSIDE trace detail trace-count 100 match icmp host 192.168.103.1 host 192.168.101.1
Topics
Community Discussion
No community discussion yet for this question.