There is quite a bit of confusion right now because of product names and terminology.
The VMS product contained 2 utilities for managing IPS devices:
IPS Management Center (IPS MC) for configuration management of the IPS devices, and
Security Monitoring (SecMon) for the viewing of IPS Alerts.
The Cisco Security Manager (CSM) was being designed primarily as a configuration tool. So Security Monitor from VMS was not carried forward into CSM. So CSM is Not able to "monitor" for IPS Alerts.
If you are using SecMon (VMS) for alert monitoring, then understand that this functionality is not available within CSM 3.0, and no plans exist to add that functionality into later versions of CSM.
Instead customers with a large number of sensors are encouraged to purchase CS MARS. CS MARS is designed specifically for monitoring of security events (both IPS as well as from other security devices).
Customers with a small number of sensors alternatively can download and use Cisco IEV (Intrusion Detection Event Viewer). Cisco IEV version 4.1 is able to monitor version 4.1 sensors as well as 5.0 and 5.1 sensors.
As for Configuration Management, VMS users will be able to upgrade to CSM and continue to be able to manage their IPS devices.
But here is where terminology causes some confusion.
The CSM was also originally designed so that all Cisco security devices could be configured from a single user interface.
This first version of CSM 3.0 does Not, however, have IPS management integrated into this single user interface for managing all Cisco security products.
Because of time to market, and resource constraints the first version of CSM does not have IPS management integrated into the main interface.
BUT, this does Not mean that CSM can not manage an IPS device. Instead what has been done with CSM 3.0 is the IPS MC from VMS has been converted to work on the same system as CSM 3.0 and be started through the CSM main interface.
So CSM 3.0 has what is often termed a "cross launch" of IPS MC for IPS management.
So CSM 3.0 DOES support IPS Management, but that IPS management is not through the primary CSM interface, and is instead through a separate startup of the IPS MC interface that has a different look and feel from the main CSM interface.
The plan, however, still remains to integrate IPS management into the main CSM interface.
This integration is what you may hear referred to as "native" support of IPS configuration in the main CSM interface.
So CSM 3.0 DOES support IPS device configuration through the "cross launched" IPS MC that comes with it (the IPS MC is part of the install package with no extra fee).
A follow on CSM will have the "native" integration of IPS management into the main CSM interface.
But CSM 3.0 DOES NOT support IPS Alert monitoring.
Users would need to purchase CS MARS or download the free IEV for alert monitoring.
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...
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 :