You don'treally need to delete and add the sensor everytime you upgrade the sensor signature. If you upgrade the signature for IDSMC as well, you should be able to get the right information when you do query the sensor.
It means, that I have to upgrade/update my Sensors manually every time? I know, the IDSM is able to upgrade itself automaticaly. Isn't this feature in the 4.x IDS software there? It would be very important.
NOTE: We strongly discourage updating sensor software versions and signature release levels in a direct session to an individual sensor if you manage that sensor with the IDS MC. You should instead use this procedure of performing updates through the IDS MC. If you have changed the configuration of a sensor, or updated a sensor, outside of the IDS MC, we recommend that you delete that sensor from your configuration and then add it to your configuration.
NOTE: Updating sensor software in a direct session to an individual sensor instead of by performing an update through the IDS MC will result in the rejection of the SSH fingerprint for that sensor. This is because the IDS MC is not involved in a session to an individual sensor.
With that said, if you decide to implement the auto update then I think you can do the following.
NOTE: I have not tried this myself so I am just theorizing.
1) Download the IDS MC update.
2) Install the IDS MC update on the IDS MC, this is so IDS MC has it's own conf files updated.
3) Download the IDS sensor update and put on your FTP server.
4) Wait for the sensor to automatically update itself.
5) Go to IDS MC and in the Identification screen for the sensor there is a Query button. This will cause the IDS MC to query the sensor for it's current version (the same version must already have been updated on IDS MC itself in step 2 above).
6) If the query fails you may need to re-establish the SSH keys as statd in the notes from the IDS MC guide above.
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 :