To specify a subnet, use the following format: 10.1.1.1/24.

To specify a list, use a space between each address.The IP addresses can be client or server addresses. Choose Client IP, IP Range, Subnet Mask – Select this option to capture traffic only for the specified IP address, list or range of IP addresses, or subnet.

All Traffic – Select this option to capture all traffic.

The traffic will be captured on all SEs handling traffic for that virtual service. This capture includes both the client-to-SE and SE-to-server side of the connection. Select Virtual Service – From the drop-down list, select the virtual service you want to capture the traffic for. The Capture Configuration section displays the parameters defined for captures currently in progress.Ĭlick on the edit icon to start a new capture. Navigate to Operations > Traffic Capture. The following are the steps to capture virtual service traffic using UI: Capturing Virtual Service Traffic using CLI/ UI Capturing Virtual Service Traffic using UI After reaching the limit, the capture will be terminated and sent to the Controller. This limit may either be the maximum number of packets to receive or the duration of the capture, in minutes. Note: It is highly recommended to set a limit for the capture. After the capture is completed, the SE will forward the pcap file to the Controller, which aggregates and sorts the client and server data into a single file. The traffic captures will be automatically run on all SEs actively handling traffic for a virtual service. Virtual services may be on a single Service Engine (SE) or scaled out across multiple active SEs. Packet capture in NSX Advanced Load Balancer runs a TCP dump for the designated virtual service or Service Engine and provides complete visibility into the packet transmission.

Tcpdump wireshark pcap format