Configuration deployment failed with IDS MC 1.2 and Sensor V4.1(1)S50
we have a problem deploying configuration file on a IDS 4235 v4.1(1)S50 from the IDS MC 1.2
Here is the error message report :
c4235-midi1.OrganizationName: Error deploying configuration files to the sensor - The system exec did not complete within the given watchdog time(120 seconds) - ActionProcessor.close caught: com.cisco.nm.mdc.ids.common.communication.exec.action.ActionExecE
We have updated the IDS MC and the Monitor Center from 1.1 to 1.2 (we only upgraded IDS MC and montoring center with the VMS 2.2 CD, VMS "modules" stay ni "old" version)
All signatures updates have been done on the IDS MC (when we update sensor signature, we update IDS MC too)
Moreover, if we try to update a v4.0(1)S37 sensor (an other 4235 IDS), deployement succeed.
Re: Configuration deployment failed with IDS MC 1.2 and Sensor V
I've had this problem in the past (only once) when trying to install a signature update using the VMS MC. I've found that a way around this is to telnet to the sensor and manually install the update. Then after this is done, go back into your VMS MC and run the query on the sensor to update the MC's information. This is a very easy process and one I did not have to repeat the next time I updated the signature file on the sensor.
To install the version S50 signature update on a 4.1 sensor,
follow these steps:
1. Download the binary file IDS-sig-4.1-1-S50.rpm.pkg
to an ftp, scp, http, or https server on your network from:
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...