FireSight no receiving data from FirePower

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2017 09:03 AM - edited 03-12-2019 06:17 AM
I have 2 cisco ASA 5525-X which I had disable the policy to send traffic to firepower like 1 month ago because i was having high CPU and memory issue, now I re-apply the policy and I have 2 days with the policy up and there is not data on the FireSight center and i can see everything is normal.
Can someone give me a hand here?
- Labels:
-
NGIPS

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2017 01:15 PM
try to install the latest code to use all new features with the device.After the proper installation and having all the required license including Firesight host license you need to make sure that the traffic has been properly redirected to pass through the Firepower.If the Firepower is redirecting the traffic you can see the same by enabling the logging under the access control policy by Policies > Access Control > Rules > Logging > Logging at beginning of connection or Logging at end of connection . Once after enabling logging, save and reapply or redeploy the policy changes. Each device has its own database connection settings. So you can refer the following link and see how much of events can be logged in the device.
http://www.cisco.com/c/en/us/td/docs/security/firesight/541/user-guide/F...
If you can see the respective connection events under Analysis > Connection Events , the dashboard data also should populate . If you already enabled the above and still no events are coming up then please perform the following by the login to Firesight CLI by elevating to root user.
1) Verify the following service is running
pmtool status | grep SFTop10Cacher
2) Restart the service
pmtool restartbyid SFTop10Cacher
3) You should see the service as running with a different pid
pmtool status | grep SFTop10Cacher
Verify the dashboard after 30 minutes.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2017 08:54 AM
I fixed it by rebooting the defence center
