An IT administrator uses AOS-CX switches to send TCP 22 trafficfrom the switch port to...

The question involves an AOS-CX switch administrator using a packet capture (e.g., tshark) to monitor TCP port 22 traffic and wanting to save it locally for later download, instead of sending it to a remote server.

Analysis of Options:

Option A:Correct. The destination file tshark-pcap command specifies that the packet capture output is saved to a local file (e.g., tshark-pcap) on the switch’s flash storage.

Option B:Incorrect. destination tunnel file tshark-pcpap is not a valid AOS-CX command for local storage.

Option C:Incorrect. destination cpu is not relevant for saving packet captures; it may refer to CPU-based monitoring.

Option D:Incorrect. destination flash:/.'my-mirror.pcnap policy Policy Minor22 has invalid syntax and does not align with packet capture storage.

Why Option A is Correct:In AOS-CX, packet captures can be configured using the monitor command (e.g., monitor session 1 source interface 1/1/1 destination file tshark-pcap). The destination file tshark-pcap option saves the captured packets (e.g., TCP port 22 traffic) to a local file on the switch’s flash storage, which can be downloaded later via SCP, SFTP, or the Web UI. This meets the administrator’s requirement to store the capture locally for future analysis, aligning with AOS-CX’s packet capture capabilities.

Relevance to Certification Objectives:

Troubleshooting (10%):Performing advanced troubleshooting using packet captures.

Performance Optimization (6%):Analyzing network traffic for performance issues.

Connectivity (9%):Diagnosing connectivity issues with monitoring tools.