The EventStore wrapping around is actually due to the fact that the events are not pulled out fast enough, not the other way around. A general recommendation when facing such issues would be to identify heavy firing signatures and reduce them to silence or almost (as it is quite useless to had millions to time alarm about a TCP segment being retransmitted for instance). The default sig set will have TCP normalization engine alarms enabled (1330's) , this is the first ones to look at. Others more than likely shoot a lot too. The command to check is "show stat virt"
The sensors are usually very good at analysing traffic very fast but once eventing start and actions are taken, the load is increasing significantly and this make sense.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...