Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84484members
353706posts

Sensor becomes UNPLUGGED followed by unreasonable value

EcoStruxure IT forum

A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.

DCIM_Support
Picard
Picard
0 Likes
4
131

Sensor becomes UNPLUGGED followed by unreasonable value

This question was originally posted on DCIM Support by Yang Gao on 2018-12-10


Why a sensor goes to UNPLUGGED momentarily and followed by a unreasonable value? Is it device or DCE problem?

(CID:137109687)

4 Replies 4
DCIM_Support
Picard
Picard
0 Likes
0
131

Re: Sensor becomes UNPLUGGED followed by unreasonable value

This comment was originally posted on DCIM Support by Steven Marchetti on 2018-12-10


Hi Yang,

With the information provided, it is impossible to tell if it is the device or DCE causing this. What do the data logs for the device say? Is there anything about the sensor losing comm with the device? Any strange readings? Is this an APC device or 3rd party? Is this SNMP or modbus? What kind of device? Sensor?

 

How often does this happen? If it is very frequent, perhaps polling with another (snmp or modbus) polling system. Perhaps a packet capture when the issue is happening would show what the device is reporting.Can you recreate the issue at will perhaps with the disconnection or reconnection of the sensor?

 

Steve

(CID:137109734)

DCIM_Support
Picard
Picard
0 Likes
0
131

Re: Sensor becomes UNPLUGGED followed by unreasonable value

This answer was originally posted on DCIM Support by spezialist on 2018-12-10


Dear Yang Gao,

I suspect ~99% that this is not the problem of your DCE-server, this is the problem of the UPS and the network (via the SNMP protocol, right?).

Why this happens: for unknown reasons, the SNMP OID sensor Total Output Load becomes non-existent, or its existing incorrect value is masked by the DDF-file used by you (this is the correct behavior of the DDF-file). After a short time, the above specified SNMP OID sensor appears or its value switches to the value:

2147483647 = 2^31 - 1.

As a rule, this value means that the sensor is NULL or non-existent. After another short time, the SNMP OID sensor takes on a real value, which the DCE software displays.

1. How to solve the problem of incorrect values on the DCE-server side?

It's very simple: you need to make on the Device Support resource for your UPS model the corresponding Request modification. That is, in the DDF-file need to make a masking above the specified incorrect value (2147483647). Thus, you can simply remove the gaps in the tables and graphs of the values of the important sensors of your UPS.

2. How to solve this problem on the UPS side and the network?

This is not a trivial process. I suspect, firstly, you need help from the UPS vendor staff. Secondly, help from NOC staff is required to analyze network traffic at the packet level, and so on.

Hope this helps you.

If you have more questions, please ask.

With respect.

(CID:137109774)

DCIM_Support
Picard
Picard
0 Likes
0
131

Re: Sensor becomes UNPLUGGED followed by unreasonable value

This comment was originally posted on DCIM Support by spezialist on 2019-01-05


Dear Yang Gao,

Please tell us if you could solve your problem or not?

With respect.

(CID:137729878)

DCIM_Support
Picard
Picard
0 Likes
0
131

🔒 Closed

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.