You can verify that these fields are being sent by running WireShark on the Harvester which the device is sending data to.
**Note that the steps for the Capture Filter may vary slightly depending on the version of Wireshark this example is based off of version 1.8.6**
- Open WireShark on the Harvester server and go to the "Capture" top menu and then "Options"
- Click the Interface which is receiving the NetFlow, and then enter the Capture Filter string like below:
host x.x.x.x and udp port 9995
3. Click "Capture->Start" to begin capturing data.
4. Allow the pcap to run for at least 5 minutes to ensure a Netflow template is received, which is necessary to decode the Netflow data. Click stop to stop the capture.
5. Click Analyze->Decode As...
6. Click the + sign and change the drop down menu to "Destination (->9995)" and select "CFLOW" on the right and click OK.
Note if this is SFLOW data, decode as SFLOW instead of CFLOW.
7. Verify that there is a template and the flows have been decode, by expanding where you see a line like "Cisco Netflow/IPFIX" and see if you can see Flows listed below this. If there is No Template Found, you will not be able to see the flows below this and you will see a message stating "No Template Found". If this is the case, you will need to get a longer pcap in order to capture the template.
8. To find the data gram that has the Netflow template you can enter "cflow.template_id" in the Filter field and it will filter down to only data grams that contain a Netflow Template.
Here you can check to see if the required NetFlow fields are being sent in the template.
If you expand the section below which says "Template (ID = ....)" You can see a list of the fields being sent and match them up with the required fields from above.
9. To view the actual values for these fields being sent, clear the cflow.template_id filter and click on any other data gram.
Expand where it says "Cisco NetFlow/IPFIX" and expand one of the Flowsets until you can see a list of the fields and values like below, make note that the "FlowSet Id: (Data)" value matches the template ID, like in this case it is 256, to ensure you are looking at the correct flow: