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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
You guys have been great so far, here's another issue I've run into.
I moved our physical DCE server from on rack to another in the data center and it works fine, without having to load anything from our backup. However in DCO when I try to connect it to its new PDUs, I get the following error:
Anyone else run into this or know what can be done? Only the DCE server asset is experiencing this issue. Every other asset (so far) is displaying and allowing for edits as normal.
(CID:107448189)
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 05:10 AM . Last Modified: 2024-04-08 11:25 PM
Good news, the issue has been resolved by migrating to 8.0.
Thanks so much for everyone's help on this mystery!
(CID:107448580)
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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
Hi Austin,
You mentioned the server was moved but also stated:
"without having to load anything from our backup".
Was the server restored and reconfigured? If so, were the devices re-associated with the DCE and it's devices? I believe you may need to do that if the system was restored as a new config means new device IDs on the DCE server and DCO is looking for the old ones.
Steve
(CID:107448194)
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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
Nope, no restore or reconfiguration. Just wanted to specify that it was brought back up from a powered off state without needing to do anything else.
(CID:107448196)
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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
Quick update: I removed the asset from DCO and added it from the Genomes as if it was now. Ran into the same issue. I tried added the power connection before associating as well and the same error message popped up.
(CID:107448197)
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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
Update 2: I restored both the DCE and DCO server to points prior to moving the physical DCE server, but I am still running into the same issue.
(CID:107448293)
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 05:09 AM . Last Modified: 2024-04-08 11:26 PM
This issue is very interesting. You physically moved DCE server. Then you went into DCO and moved DCE from old rack to new rack, correct? Have you done a Test connection on the External System Configuration in DCO?
(CID:107448309)
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 05:10 AM . Last Modified: 2024-04-08 11:26 PM
The external system still works fine and all other devices that are linked to DCE are working properly. Only this asset seems to be affected.
(CID:107448452)
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 05:10 AM . Last Modified: 2024-04-08 11:26 PM
I assume there is something strange on the power tab or other tabs for the DCE genome that is causing this. Can you include a screenshot of the power tab for that server? When you try to connect it to power, are you seeing any error messages at the top of the DCE server properties window before you click ok? I remember older versions used to have include both power inlets/outlets (not that it should matter, just strange). Also which version of DCO are you running?
As a work around, you could either use the generic server genome or the equivalent Dell server (R200, R610, R710, etc) genome for your DCE server instead of the DCE server we have in the genome library.
(CID:107448428)
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 05:10 AM . Last Modified: 2024-04-08 11:26 PM
I am currently running DCO 7.5. You can see on the attached that if I hit the 'Power' tab, I get the error right away and cannot actually see anything under the tab. If I click another tab and then go back to 'Power', I just see an empty space but do not get the error message again.
(CID:107448449)
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 05:10 AM . Last Modified: 2024-04-08 11:26 PM
There is most likely something wrong that specific genome then...I've seen similar things with Cooling devices in previous versions. If you're under a current support contract, you can contact your local tech support and get either Service Pack 5 for DCO 7.5 or the 8.0 release (note due to an OS change, 8.0 requires a server migration), both of these contain a genome library update. Alternatively you follow my previous suggestion and use a generic server or Dell server that matches your DCE server (you can find the dell service tag for the DCE server somewhere on it). There is nothing special about that specific DCE genome other than it currently doesn't seem to be working correctly.
(CID:107448501)
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 05:10 AM . Last Modified: 2024-04-08 11:26 PM
Hi Austin,
The error message/notification is complaining about the setup/configuration containing "invalid values" (such as mis-configured power settings). Right click on device/server -> Properties > Power, and see if the device and the rack pdu power settings are "valid" (meaning that the rack pdu power settings can support being connected to the device/server).
Hope this helps,
Kind regards
(CID:107448432)
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 05:10 AM . Last Modified: 2024-04-08 11:25 PM
Unfortunately under the 'Power' tab there is nothing to see or change.
(CID:107448454)
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 05:10 AM . Last Modified: 2024-04-08 11:25 PM
Hi Austin, Thanks for sharing the screen capture, it seems that might be the main issue. In the "Genomes" if you right click (on the device that have been used) > Properties, what do you see under the 'power' tab? Do you know which "Genome Library" item have been used? screen capture(s) would be great. If there is bug in the Genome Library, we need to locate and fix it. The device properties 'power' tab must contain some voltage information, otherwise cannot be connected to a rpdu. In the mean time I would suggest using another item from the Genome Library. Kind regards
(CID:107448513)
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 05:10 AM . Last Modified: 2024-04-08 11:25 PM
Good news, the issue has been resolved by migrating to 8.0.
Thanks so much for everyone's help on this mystery!
(CID:107448580)
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 05:10 AM . Last Modified: 2023-10-31 10:56 PM
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.