This section explains the methods to configure parameters for virtual service and PCAP.

Filtering Based on IP Address

Execute the debug_ip addrs <IP address for filter> command from the debugserviceengine mode to filter the SE packet capture for the specific IP address.

 [admin:cntrl1]: debugserviceengine> debug_ip addrs 10.10.10.10
 [admin:cntrl1]: debugserviceengine:debug_ip>
 [admin:cntrl1]: debugserviceengine:debug_ip> save
 [admin:cntrl1]: debugserviceengine> where
 Tenant: admin
 +----------------+--------------------------+
 | Field          | Value                    |
 +----------------+--------------------------+
 | uuid           | se-10.10.22.107-avitag-1 |
 | name           | 10.10.22.107             |
 | debug_ip       |                          |
 |   addrs[1]     | 10.10.10.10              |
 | tenant_ref     | admin                    |
 +----------------+--------------------------+

Filtering Based on Capture Duration

Execute the capture_params duration <duration in minutes> command from the debugserviceengine mode to capture packets for the specified duration.

[admin:cntrl1]: debugserviceengine> capture_params duration 10
 [admin:cntrl1]: debugserviceengine> where
 Tenant: admin
 +----------------+--------------------------+
 | Field          | Value                    |
 +----------------+--------------------------+
 | uuid           | se-10.10.22.107-avitag-1 |
 | name           | 10.10.22.107             |
 | debug_ip       |                          |
 |   addrs[1]     | 10.10.10.10              |
 | capture_params |                          |
 |   duration     | 10 min                   |
 | tenant_ref     | admin                    |
 +----------------+--------------------------+

Filtering Based on Capture Packet Size

Execute the capture_params pkt_size <packet size in bytes> command from the debugserviceengine mode to capture traffic of the desired packet size.

[admin:cntrl1]: debugserviceengine> capture_params pkt_size 0
[admin:cntrl1]: debugserviceengine> where
Tenant: admin
+----------------+--------------------------+
| Field          | Value                    |
+----------------+--------------------------+
| uuid           | se-10.10.22.107-avitag-1 |
| name           | 10.10.22.107             |
| debug_ip       |                          |
|   addrs[1]     | 10.10.10.10              |
| capture_params |                          |
|   pkt_size     | 0 bytes                  |
|   duration     | 10 min                   |
| tenant_ref     | admin                    |
+----------------+--------------------------+
[admin:cntrl1]: debugserviceengine> save
[admin:cntrl1]:

The above packet filter captures traffic for the Service Engine 10.10.22.107 with the IP address 10.10.10.10 for a duration of 10 minutes with packet size 0.

To stop the ongoing packet capture, re-enter the packet capture sub-mode and execute no capture command.

[admin:cntrl1]: debug service engine 10.10.22.107
[admin:cntrl1]: debugserviceengine> no capture
[admin:cntrl1]: debugserviceengine> save

Export the packet capture to a remote system and use tools like TCPdump or Wireshark for further analysis.

For more information on exporting packet capture, see Exporting Packet Capture for Virtual Service and Service Engine Pcaps.

Configurable Size for Both Virtual Service and SE PCAPs

The following are the configurable size for both virtual service and SE PCAPs:

  • The maximum PCAP file size per SE can be specified in this section. Each core gets configured (maximum size)/(total number of cores).

  • absolute_size: The maximum PCAP file size in MegaBytes.

  • percentage_size: The percentage of free disk space available in Avi Load Balancer partition. The valid range is 0-75%. The free size is instantaneous free size at the time of configuration. This should be used with caution.

  • Set absolute_size and percentage_size to 0 to use Avi Load Balancer’s default maximum allowed PCAP size (100MB) per core.

  • The maximum of absolute_size and percentage_size will be considered as maximum PCAP file.

[admin:ctrl]: > debug serviceengine 10.10.100.10
[admin:ctrl]: debugserviceengine> capture_params
[admin:ctrl]: debugserviceengine:capture_params> capture_file_size
[admin:ctrl]: debugserviceengine:capture_params:capture_file_size> absolute_size 500
[admin:ctrl]: debugserviceengine:capture_params:capture_file_size> save
[admin:ctrl]: debugserviceengine:capture_params> save
[admin:ctrl]: debugserviceengine> save
Note:

  • You need to observe caution while using the percentage_size value. It is the instantaneous free size which is taken into consideration.

  • With virtual service and SE PCAP configured with percentage_size, the cumulative number of these sizes during configuration is not supported. This could lead to disk space problems. Excessive enabling of debugs could also aggravate the same.