Troubleshoot AMI/AMX Deployment

This topic helps troubleshoot AMI/AMX deployments on GigaVUE V Series Nodes and focuses specifically on scenarios where AMI is not exporting IPFIX/CEF records and AMX is not receiving traffic or is not exporting JSON records to downstream tools.

Scenario 1: AMI not exporting IPFIX/CEF records (exporter side)

Download exporter records

To download the exporter records:

In GigaVUE-FM, go to Traffic > Virtual > Orchestrated Flows > VMware (You can select the cloud platform which you have configured. This scenario explains the VMware platform). The Monitoring Session page appears.

Select the monitoring session that you want to troubleshoot.

Go to the Traffic Processing tab. The canvas appears with the monitoring session components

Select the AMI application and click Three-dots menu to view the application details.

Select the Statistics tab and the Exporter section appears.

Select the required records and click Download Records. The Exporter Mapping dialog appears.

Select the V Series Node and the tunnels for exporters from the dropdown list.

Click Download Exporter. The PCAP file (for example, Pcap__e1_link3_2026-03-12_174220.pcapng) is downloaded to your local machine. The progress of the PCAP file download appears in the browser.

Note: If there are no packets or records during the capture window, the system displays the message No file captured.

Verify whether the PCAP file contains valid IPFIX/CEF records for the specified exporter instance.

Scenario 2: AMX not receiving AMI/NetFlow records (ingestor side)

Verify topology and mapping

To verify topology and mapping:

Confirm whether the AMI exporter is configured to send records to the data interface of the correct AMX instance.

Use the AMX interface mapping in FM (management/data/tool) to ensure the correct interface is used for receiving records.

Download PCAP file using Download TCP Dump

To download the PCAP file:

In GigaVUE-FM, go to Traffic > Virtual > Orchestrated Flows > VMware. The Monitoring Session page appears. You can select the cloud platform which you have configured. This scenario explains the VMware platform.

Select the monitoring session that you want to troubleshoot.

Go to the Traffic Processing tab. The canvas appears with the monitoring session components

Select the AMX application and click Three-dots menu to view the application details.

Select the Statistics tab and select the V Series node for the AMX instance from the V Series Node IP dropdown list.

In the Ingestor section, select the required record and click Download TCP Dump. The Ingestor Interface Mapping dialog appears.

Select the interface mapping for the ingestor. The AMX interface naming includes the type and IP address of the interface:

For example, Zscaler ingestor - MGMT (ens160) IPv4: 10.114.26.181 IPv6: fcab:0:1:2040:a0a1:874e:7a66:40a2

Other ingestors (AMI, NetFlow/IPFIX, Mobility) - DATA (ens192) IPv4: 10.114.42.135 IPv6: fcab:0:1:2040:a0a1:874e:7a66:40a2

click Download TCP Dump. The PCAP file is downloaded to your local machine. The progress of the PCAP file download appears in the browser.

Note: The PCAP file is stored temporarily on the Application Metadata Exporter virtual machine and is automatically deleted after download.

Verify whether (IPFIX/CEF/NetFlow/JSON-over-UDP/GTPC) records are visible on the ingestor port. If the PCAP is empty or only shows partial traffic, this suggests a datapath issue upstream of AMX (AMI export or fabric).

Scenario 3: AMX not exporting JSON records (exporter side)

Check exporter status and counters

To check exporter status:

In the Exporter section, verify the number of files processed versus files skipped.

Check the error counters (if exposed via UI).

Download exporter records

To download the exporter records:

Select the monitoring session that you want to troubleshoot.

Go to the Traffic Processing tab. The canvas appears with the monitoring session components

Select the AMX application and click Three-dots menu to view the application details.

Select the Statistics tab and select the V Series node from the V Series Node IP dropdown list.

In the Exporter section, verify the number of Files processed vs files skipped.

Select the required records and click Download Records. The exporter JSON file is downloaded to your local machine. The progress of the PCAP file download appears in the browser.

Note: If there are no packets or records during the capture window, the system displays the message No file captured.

Validate the JSON structure and key fields required by the tool (e.g., Splunk, Elastic).

Check for malformed or truncated records.