Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Configuration deployment failed with IDS MC 1.2 and Sensor V4.1(1)S50

Hello,

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.

Any idea ?

2 REPLIES
Cisco Employee

Re: Configuration deployment failed with IDS MC 1.2 and Sensor V

Try deleting that sensor and add it back into the IDSMC. By the way what did you mean by "(we only upgraded IDS MC and montoring center with the VMS 2.2 CD, VMS "modules" stay ni "old" version)

What has remained in the old version?

Thanks,

yatin

New Member

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.

INSTALLATION

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:

http://www.cisco.com/cgi-bin/tablebuild.pl/ids4

CAUTION: You must preserve the original file name.

2. Log in to the IDS CLI using an account with administrator privileges.

3. Type the following command to upgrade the sensor:

configure terminal

4. Execute the upgrade command by typing the following:

upgrade [URL]/IDS-sig-4.1-1-S50.rpm.pkg

where the [URL] is uniform resource locator pointing to where

the signature update package is located. For example, to retrieve

the update via FTP, type the following:

upgrade ftp://@///IDS-sig-4.1-1-S50.rpm.pkg

The available transport methods are: SCP, FTP, HTTP, or HTTPS

5. Enter the appropriate password when prompted.

6. To complete the upgrade, type yes when prompted.

176
Views
0
Helpful
2
Replies