EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:05 PM . Last Modified: 2024-04-08 12:45 AM
Hi all!
After upgrading from DCE-7.4.2 to DCE-7.4.3, I found the following possible bug.
The DCE-7.4.2 was setup multiple virtual sensors containing UPS Symmetra PX 96/128 power sensors. After upgrading to DCE-7.4.3, the above-mentioned Symmetra PX 96/128 UPS power sensors are switched to the Unplugged state. As a result, virtual sensors have also switched to the Unplugged state.
After that, when I try to edit these Unplugged virtual sensors, I get a message about the lack of rights 😕 as can be seen in the screenshot:
I will say, that my DCE-server account has the rights of the server administrator and all devices without exceptions. This bug applies only to Unplugged virtual sensors, which contain only Symmetra PX 96/128 UPS Unplugged power sensors (3-phase UPSs).
Very thanks for the support.
(CID:118621910)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:05 PM . Last Modified: 2024-04-08 12:45 AM
Hi spezialist. So I don't have a 96/128 UPS to test with but I have a DCE 7.4.2 system with (2) 40k PX units and a PX250. I am in the system as a server administrator. I created 2 virtual sensors in hopes that I could get something to list unplugged after upgrade. One sensor was kw and the other watts.
I upgraded to 7.4.3 and many of the sensors report unplugged. I went in to edit the first virtual sensor and see:
I edited the second virtual sensor and see:
The main difference I am seeing is that your virtual sensors report unplugged while mine report normal. It may simply take some time:
I am also able to add/remove sensors from these virtual sensors.
You stated that "my DCE-server account has the rights of the server administrator and all devices without exceptions". Do you have administrative rights to the groups or is your user specifically a server admin (actually in that group)?
I can check these sensors tomorrow to see if they change state. How long ago did you upgrade? What was the full upgrade path for this server (ie did you start at 7.0 and have been upgrading ever since)? Do you know at what point the virtual sensors were added? (7.2, 7.3, etc)?
If I'm going to replicate this, we need to figure out why I'm not seeing the same results as are you.
Steve
(CID:118622173)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:05 PM . Last Modified: 2024-04-08 12:45 AM
Hi Steven Marchetti,
Today I found the same problem on two more DCE-servers. And on one of these DCE-servers the problem virtual sensor (total power Watt) was in a normal state, i.e. not Unplugged (but virtual sensor is also not editable for me).
Regarding the rights of my local DCE-account: I have both User Roles: SxW DCE Administrator and SxW DCE Proxy. In addition, I am a member of a local DCE-group Server Administrators with role SxW DCE Administrator.
On all three DCE-servers, the above problematic uneditable virtual sensors (total power Watt) were created with the version of DCE-7.3.1. All three DCE-servers have consistently passed the upgdate 7.3.1 -> 7.4.0 -> 7.4.1 -> 7.4.2 -> 7.4.3. And in the version of DCE-7.4.1 the virtual sensors (total power Watt) were still editable.
And one more thing: on one of the DCE-servers I solved the above mentioned problem by simply removing the problematic uneditable virtual sensor (total power Watt) and recreating it exactly.
It may require further any additional information to recreate this bug?
Very thanks for the support.
(CID:118622633)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:05 PM . Last Modified: 2024-04-08 12:45 AM
Hi Spezialist.
I did more testing over the past few days and numerous upgrades. Here's the sum of my testing and configuration:
Fresh image of 7.3.1 on a hardware server
Added 40K, PX250, and an LX
Created w or kw virtual sensors individually for each unit
Created a threshold for each virtual sensor
Upgraded to 7.4.0
Created w or kw virtual sensors individually for each unit
Created a threshold for each virtual sensor
verified editability to sensors and thresholds
Upgraded to 7.4.1
Created w or kw virtual sensors individually for each unit
Created a threshold for each virtual sensor
verified editability to sensors and thresholds
Upgraded to 7.4.2
Verified there are some unplugged sensors in each device.
Created w or kw virtual sensors individually for each unit
Created a threshold for each virtual sensor
only 7.4.2 virtual sensors remainin a state showing values, all previous report unplugged.(all remain editable)
thresholds are editable.
Added a NetBotz appliance and created an average virtual temp sensor and threshold. Just to add to the test
Upgraded to 7.4.3
Some v-sensors report unplugged but the values within them for the most part report fine.
I edited some that I created back in 7.3.1 without issue. The rest appear to be editable.
I did not replace any sensors, just clicked edit and / or changed the v-sensor name.
One of the sensors that I edited the name for was marked unplugged but shown a value after changing it's name.
Steve
(CID:119050073)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:06 PM . Last Modified: 2024-04-08 12:45 AM
Hi Steven Marchetti,
Thank you for the work done.
I also did some research on the above mentioned bug and now I can say with a high probability the following. All problematic virtual sensors (I have the sum of the total output powers of several Symmetra 160K) have device sensors, that do not exist anymore (note: I did not delete them manually).
For example, I have a virtual power sum sensor, that has the "Total Output Active Power" device sensors of two Symmetra 160K. And one of these UPSs is now offline and is not available for the DCE-server. In this case, the available online UPS has a "Total Output Active Power" device sensor, for example, as in the screenshot:
But the other offline UPS, that is not currently available does not have a "Total Output Active Power" device sensor, for example, as in the screenshot:
This is the reason for the bug.
Now I'll tell you how it happened.
In the second half of January 2017, the device sensor "Total Output Active Power" of the new Symmetra 160K (192.168.1.20) was added to the existing virtual power sum sensor. As a result, the virtual power sum sensor contained two "Total Output Active Power" device sensors: one old Symmetra 160K (192.168.1.21) and one new Symmetra 160K (192.168.1.20). The DCE-server had version 7.4.2. Then the new Symmetra 160K (192.168.1.20) was shutdown for technical reasons and is still in the offline state to this day. And at the end of April 2017 the DCE-server was updated to version 7.4.3, after which the above bug was detected.
The solution to this problem I posted earlier: it is necessary to remove the problematic virtual sensor and recreate it using the available device sensors required devices.
Best regards and thank you for your support.
(CID:119050078)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-03 04:06 PM . Last Modified: 2023-10-20 04:59 AM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.