Losing connection to external sensors

twaatwaa
edited March 2015 in InfraSensing Sensors
Hello,



We have a wired servercheck gateway (v5) with a humidity, flooding and external temperature probe attached to it.



We monitor this device by SNMP. (SNMP gets) and notice that often there are no values for these external probes (the internal temperature however is always working.)



Recently we verified this behavior by looking at the display on the servercheck gateway and we noticed the indications for the humidity and flooding probes were frequently disappearing and reappearing again.



The power supplies for the sensors are connected. We have updated to the latest firmware. Is there perhaps a hardware issue with the sensor or are there any other steps we can take to resolve this?



Thank you for any assistance you can provide.








Comments

  • AdministratorAdministrator
    Have you tried changing the cables from the SensorGateway to the sensors?
  • BernBern
    This has been happening since v4

    if you monitor the device via nagios or the servercheck monitoring software the probe 1 and 2 are not always contactable. if you watch the display the values move / disappear, where as in v3.06 the values were always static on the display. if you do a MIB walk on the device you can see the values are also missing every now and then.

    i reported this last year.
  • AdministratorAdministrator
    Bern, on how many SensorGateway units are you experiencing the issue?
  • BernBern
    v3.06 always works

    When you get to v4 or above we have this issue unless the sensor is behind a silver peak as this make the connection and does not care what size the sync window is

    Did you see from my info the difference in the window size.

    Can you see there is a difference.



    We have around 80 with this issue as sine work via the silver peak




  • AdministratorAdministrator
    The window size shouldn't matter since we're only dealing with the sensors' connectivity to the SensorGateway.



    May we just know which external sensors are losing connection? And are all of them constantly being lost every now and then?
  • BernBern
    Sorry wrong thread

    Connection to external sensors





    Since v4

    As soon as you connect them to the cloud the sensor display is no longer static with the main and external 2 probes listed.

    It's like it looses connection to the probe 1 and probe 2 become probe 1 for a few seconds

    If the snmp monitor device is checking at that point either the external temp sensor becomes not a number but dry for example if you have a flood cable

    And the 3rd sensor is missing

    Then it's all back as it should be



    This does not star until it's connected to the cloud



    B
  • AdministratorAdministrator
    So the issue only occurs if the SensorGateway is configured to connect to your Cloud account?



    Also, does the issue also happen on FWv3.06?
  • BernBern
    The display stops being static when you connect t the cloud

    As no cloud on v3..06 it is always static and works

    It is intermittent and if you alarm from snmp monitoring the. You get false alerts
  • twaatwaa
    Thank you for the replies.



    We have changed the cables but the problem persists.



    I have also checked the cloud options and the Enable Cloud Data Upload is disabled (was never enabled), so it looks in our case this is not the cause.










  • AdministratorAdministrator
    twaa,



    do you have a log of the SNMP communication? When a request is made via SNMP, the base unit connects to the sensor to retrieve the value. It may be that your SNMP application doesn't wait for the reply (due to UDP protocol) and as such times out.


  • twaatwaa
    I took a look at what the monitoring tool does exactly.



    It runs an snmpwalk on .1.3.6.1.4.1 and parses this output to retrieve the values for the different sensors.



    This snmpwalk has a timeout value of 45 seconds, and so far the monitoring has never received 'timeout' as a response.
  • twaatwaa
    The issue has nothing to do with timeouts. Sensor data also goes missing from the web interface and from the physical display on the sensor gateway.



    Here are two examples of SNMPwalks, they were run with only a few seconds inverval.



    In the first walk we are missing some information:



    # snmpwalk -v2c -c public 172.19.0.19 .1.3.6.1.4.1

    SNMPv2-SMI::enterprises.17095.1.1.0 = STRING: "Temperature & Sensor Gateway"

    SNMPv2-SMI::enterprises.17095.1.2.0 = STRING: "Release 5.07"

    SNMPv2-SMI::enterprises.17095.1.3.0 = STRING: "Jul 3 2014"

    SNMPv2-SMI::enterprises.17095.1.4.0 = STRING: "sensor_zeutestraat"

    SNMPv2-SMI::enterprises.17095.1.5.0 = STRING: "zeutestraat"

    SNMPv2-SMI::enterprises.17095.1.6.0 = IpAddress: 172.19.0.19

    SNMPv2-SMI::enterprises.17095.1.7.0 = IpAddress: 172.19.0.1

    SNMPv2-SMI::enterprises.17095.1.8.0 = IpAddress: 10.32.62.10

    SNMPv2-SMI::enterprises.17095.1.9.0 = IpAddress: 10.32.24.10

    SNMPv2-SMI::enterprises.17095.3.1.0 = STRING: "Temp naast telecom switches"

    SNMPv2-SMI::enterprises.17095.3.2.0 = STRING: "18.89"

    SNMPv2-SMI::enterprises.17095.3.3.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.4.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.5.0 = STRING: "Water Detect"

    SNMPv2-SMI::enterprises.17095.3.6.0 = STRING: "DRY"

    SNMPv2-SMI::enterprises.17095.3.7.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.8.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.9.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.10.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.11.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.12.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.13.0 = STRING: "-"





    And the second walk a few seconds later found all of the sensors:

    # snmpwalk -v2c -c public 172.19.0.19 .1.3.6.1.4.1

    SNMPv2-SMI::enterprises.17095.1.1.0 = STRING: "Temperature & Sensor Gateway"

    SNMPv2-SMI::enterprises.17095.1.2.0 = STRING: "Release 5.07"

    SNMPv2-SMI::enterprises.17095.1.3.0 = STRING: "Jul 3 2014"

    SNMPv2-SMI::enterprises.17095.1.4.0 = STRING: "sensor_zeutestraat"

    SNMPv2-SMI::enterprises.17095.1.5.0 = STRING: "zeutestraat"

    SNMPv2-SMI::enterprises.17095.1.6.0 = IpAddress: 172.19.0.19

    SNMPv2-SMI::enterprises.17095.1.7.0 = IpAddress: 172.19.0.1

    SNMPv2-SMI::enterprises.17095.1.8.0 = IpAddress: 10.32.62.10

    SNMPv2-SMI::enterprises.17095.1.9.0 = IpAddress: 10.32.24.10

    SNMPv2-SMI::enterprises.17095.3.1.0 = STRING: "Temp naast telecom switches"

    SNMPv2-SMI::enterprises.17095.3.2.0 = STRING: "18.94"

    SNMPv2-SMI::enterprises.17095.3.3.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.4.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.5.0 = STRING: "Ext. Temp"

    SNMPv2-SMI::enterprises.17095.3.6.0 = STRING: "21.31"

    SNMPv2-SMI::enterprises.17095.3.7.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.8.0 = STRING: "-"

    SNMPv2-SMI::enterprises.17095.3.9.0 = STRING: "Humidity"

    SNMPv2-SMI::enterprises.17095.3.10.0 = STRING: "36.82"

    SNMPv2-SMI::enterprises.17095.3.11.0 = STRING: "DOWN"

    SNMPv2-SMI::enterprises.17095.3.12.0 = STRING: "13 April 2015,15:44:05"

    SNMPv2-SMI::enterprises.17095.3.13.0 = STRING: "Dew Point"

    SNMPv2-SMI::enterprises.17095.3.14.0 = STRING: "8.68"

    SNMPv2-SMI::enterprises.17095.3.15.0 = STRING: "DOWN"

    SNMPv2-SMI::enterprises.17095.3.16.0 = STRING: "13 April 2015,15:44:06"

    SNMPv2-SMI::enterprises.17095.3.17.0 = STRING: "Water Detect"

    SNMPv2-SMI::enterprises.17095.3.18.0 = STRING: "DRY"
  • BernBern
    I see this too on all version 4 onwards

    does not happen on v3.06
  • twaatwaa
    Can servercheck confirm that v3.06 does not have this issue?



    If so can I still download firmware v3.06 as a temporary fix?
  • AdministratorAdministrator
    3.06 is available from this url:

    http://downloads.serverscheck.com/sensors/FACTORY_HWver5_Fw_Release_3_06.bin
Sign In or Register to comment.