Has anyone successfully used a source-port or destination-port filter in a packet-capture command on a waas? Anytime I try to filter on any port # I capture no packets. If I however remove the port # and run a packet-capture I capture packets and see the traffic my filter should have caught. I'm not sure if I'm looking at a bug since it seems straightforward.
Thank you Srinivasa. I tried the tcpdump, but get the same behavior. As soon as I remove the filter all the packets come pouring in. I've tried different ports such as 445, but with the same results, 0 packets.
pa-harr-0-7571a#tcpdump -i eth0 -s 3200 tcp port 1494 -w ctxcapnew.pcap
Note : The tcpdump and tethereal CLIs are planned to be deprecated in a future release. The use of 'packet-capture' CLI is recommended.
tcpdump: Setting virtual memory/file size limit to 524288000
tethereal seems to be the only utility that works with a filter. The command below performed as expected, which is odd since it's advertised as working with 4.0 and earlier and I'm running 5.1.1d where I'm warned that tethereal and tcpdump are soon to be deprecated; hopefully not before the issue with packet-capture not working with filters is resolved.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...