sensor monitoring

Hi,

installed :

Serverscheck version standard monitoring 7.12 with license only for environmental sensors.

6 sensors connected

Monitoring web application is on : 64bit W2003 server with .NET framework 1.1 (& other version also).

Error message : time out (when the monitoring software try to connect with the devices), when we run the following command in the /agents subdirectory

sensor_check -L log.txt -C TCP X.X.X.X:3001 (xxxx is the Ip sensor address), we get a good reply with the temperature value (in that case).



More, when we try with the same config on a XP sp2 : serverscheck is working fine.



Question : why it does not work in the primary config ?

thanks for your quick reply.

Detail :

when we try with the same config on a XP sp2 (32bit): serverscheck is working fine.

When ServersCheck runs a service, it uses the service credentials and it may not have all required network access to connect to the sensors.



As it works fine on XP SP2, something must be wrong on the Windows 2003 box causing it to be unable to connect to the system when running as a service.

Thank you for your reply.

Following several test made on W2003 server, it seems serverscheck can now reach only the T°&Humidity sensors (value can be retreived). Not the POWER and the FLOODING sensor (because timed out). We can PING the IP addresses of the Power and of the FLOODING. All the installed sensors are new and connected through Tibbo DS 202 (SERIAL/Ethernet).



Question : as only T° and Humidity sensors can be readed, how can we test the POWER and the FLOODING to be sure that they are not defect ?

Make sure you can connect on port 3001 to the power and flooding sensor.



Do they respond when testing in debug mode?

In debug mode, the flooding and Power sensors don't respond (time out). They are connected through port 3001.

What are the settings of the Ethernet device servers for flooding & power sensors? Baud rate etc...



A quick way to test if it is the ethernet device server (tibbo) or the sensors, simply connect to the flooding sensor to the tibbo device and perform the debug test again:

sensor_check -L log.txt XXXXX:3001



Each sensor is manually tested prior to shipment.



If defective, which can always happen, then products can be returned under warranty for replacement. However if they are not defective but incorrectly configured, then a 50 EURO service charge per sensor applies - excluding return shipping & handling.

Ok for testing tibbo device and isolate the sensors.

But how can we check the sensors without the tibbo device ?

Serial connexion do not exist any more on laptop and or the blade in the server room.

In the command : sensor_check -L log.txt XXXXX:3001.

xxxxx = ? (comport ?)

There was a mistake in the command:

sensor_check - L log.txt -C TCP XXXX:3001



for serial or usb enabled sensors this is

sensor_check -L log.txt -C COM XXX

where XXX is the COM port



http://kb.serverscheck.com/index.php?page=index_v2&id=40&c=8