Error connecting through IPS Device Manager

[ajuba]

Hi,

I keep getting this error when I try to access the IPS 4255 thro' the IDM.

“Error Connecting to sensor. Failed to load Sensor- errSystemError-ct-sensorApp332 not responding, please check the system processes- the connect to the specified lo:: ClientPipe Failed”

Any idea on what this issue could be and what i could do to fix it?

[umedryk]

Did you find this error in syslog ?

[jpoudereux]

I get the same error, but only after a short period of time. When this happens, Security Monitor in VMS doesn't show any alarm. I can actually ssh into this IPS 5.0.2 sensor, but typing 'show ver' I realize that 'AnalysisEngine' is "NotRunning". And trying to log into IDM I get the same error than you, ajuba.

I don't know what to do... If I restart the sensor everything works OK and after a short period of time this strange error starts again.

How can I restart the 'AnalysisEngine' service without rebooting the sensor?

What do you think I can do to make my IDSM2 work with no error?

thank you very much

[hwon]

You can restart the service via following command logged on as service:

Turn the services off

[root@ips50 sbin]# cd /etc/init.d

[root@ips50 init.d]# ./cids stop

Turn the services back on

[root@ips50 sbin]# cd /etc/init.d

[root@ips50 init.d]# ./cids start

You will still lose connectivity if the sensor is configured as inline but much faster than reloading the IPS.

[h-rupawala]

Hello Ajuba,

I get exactly the same message while connecting to a IPS 4240 using IDM.

The only solution is to telnet to the IPS and reset it.

Is this a bug in IDM ? Has CISCO come up with a solution ?

Pls. get back.

Thanks and Regards

Honeid.

[jstewart]

Yes, I have a similar problem with a couple of IDSM-2s running IPS-K9-sp-5.0-4. With the previous version I also received the NotRunning error, with the current version I now get Stopping. The last time this happened to me was after upgrading to signature S190, both machines fell into the endless Stopping mode. The workaround provided in the thread above works, first stop then start cids. The workaround seems to me to work better than resetting the IDSM-2s as they usually don't reconnect to the Security Monitor after a reset, and you have to delete the sensor and import it again to get them to talk to the Security Monitor.

MainApp 2005_Mar_04_14.23 (Release) 2005-03-04T14:35:11-0600 Running

AnalysisEngine 2005_Aug_15_09.41 (Release) 2005-08-15T10:00:52-0500 Stopping

CLI 2005_Mar_04_14.23 (Release) 2005-03-04T14:35:11-0600

Upgrade History:

* IPS-K9-sp-5.0-4 09:33:24 UTC Wed Sep 07 2005

IPS-sig-S190-minreq-5.0-1.pkg 08:56:05 UTC Thu Sep 08 2005

[hquiros]

hello everybody, now yet i has the same problem, inclusive with the 5.1.1d version. I dont know what is the source of the problem, Maybe cisco have the answer.

Cisco give us answers!!!!!

[hquiros]

Too, when IDM loads, the time for load the IDM is 50 seconds.

[bitterman]

Also with 5.1.1d on an IDSM2.