TIM is not analyzing packets.

Document ID : KB000009858
Last Modified Date : 14/02/2018
Show Technical Document Details

 After a new deploy, the TIM is not able to analyze packets.

TIM 9.5x and later.

Check the following to resolve this issue:

- Ethn port is not configured at the TIM UI as a network interface.
- Network Drive issue, preferably check with your Network group.
- Check protocolstats file, If it is not showing packets (like captured, dropped and analyzed). It means that TIM is not seeing traffic.
- If protocolstats file is showing packets (like captured, dropped and analyzed). It means that traffic is reaching the TIM and for some reason it is not able to analyze that.
- Check the Apmpacket log detailed errors.
- Check if the Apmpacket service is not running.
- Check if any traffic is being seen on that interface set, run below command to make sure:

netstat --interfaces=<interfaceName>

If there are no packets being seen, then check with your network team that the traffic is being pushed from the switch, SPAN port, or TAP to that interface correctly.




Btstats file:

Apmpacket log:


Additional Information:

https://en.wikipedia.org/wiki/Berkeley_DB - BDB Overview

http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html - BDB Downloads

http://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec1420872.html  - Reducing dropped packets

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1688747.aspx - Napatech drivers

http://cookbooks.ca.com/caapm/2016/06/03/seeing-dropped-packets-in-protocolstats-log-and-how-to-reduce-them/ - Seeing Dropped Packets in Protocolstats.log and How to Reduce Them