512 Mbps is the maximum supported memory on the sensor.
The 98% usage you see in "show version" is misleading.
This percentage includes both the memory actively being used by the IDS processes, as well as any memory the OS is using for cache recently accessed files.
Unfortunately "show version" doesn't tell you what percent is being used by the IDS processes, and what percent is being used by cache.
It is the percent used by the IDS processes that is of interest for determine sensor problems.
The Eventstore where are alarms are stored on the sensor is a large 4 gig file. This file is accessed everytime IEV or SecMon queries for new alarms, or when sensorApp writes a new alarm. Because it is accessed so often, the OS caches as much of the file as possible into memory. So the OS uses up as much available memory as it can to cache portions of this file.
So even though the sensor reports that 98% of the memory is used it may be that the largest portion of this is just the cache for the eventStore.
In these cases the processes already have more than enough memory, and adding memory would just give the OS a larger area in which to cache the eventStore file.
Because of this a perfectly normal sensor that is not overloaded could still show memory usage at 98%.
So the memory usage currently being reported by show version is not a good gage to determine if something is wrong on the sensor.
If you are experiencing a problem then you should contact the TAC. This way the problem can be diagnosed. Development can then determine that actual memory percentage being used by the IDS processes.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :