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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
I have couple of rack mount per outlet metered PDU in my environment.
Is there any custom solution how I can create an inventory about which device is connected to which PDU socket?
I think it is not just interesting for outlet metered PDU. On a standard basic
APC PDU the outlets are numbered and it would worth to know which outlet is allocated to which device.
(CID:132651187)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
Hi Mate,
Currently that's not supported, I can capture a feature request for you? Might not be so practical, but perhaps using custom properties could help a little.
Kind regards
(CID:132651245)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
Work around then,manual mapping using custom properties per what Jef said:create 2 custom properties template
1.for rack pdu outlet at rack pdu itself,to track which outlet is being used,or to which server.
2.On the individual server,to track the outlet number of the rack pdu.
Its manual and prone to entry error,still better than not tracking.
I would suggest to name the rack pdu outlet on the rpdu nmc itself,especially if this is switched outlet rpdu, to avoid switching the wrong outlet....
(CID:132651330)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
Thank you both. I think create a future request would worth as I can see the upvotes not just me interested.
I also thought on custom properties but on PDU side it will be huge amount. For example on a PDU where I have 36 outlets I have to create:
Which means 36 custom properties only for a PDU?
(CID:132651349)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
Hi Mate,
I have now registered this as a feature request for you - will send you a direct confirmation as well, thanks.
Kind regards
(CID:132651367)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
On custom property of rack pdu itself,yes unfortunately
Only one cp per server,set the cp template as a list of fixed number,so user can then just select when setting on server.
For rack pdu cp,yes per you said,each cp is for the outlet,to list which server it is connected,or at leat to tell if outlet is in use/available.
p.s did raise similar request previously, for the same reason as you....
(CID:132651378)
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-04 06:45 PM . Last Modified: 2024-04-04 11:26 PM
Hi Mate
As others have suggested, if you do decide to try something, I recommend A) focusing on keeping the device to port mapping in one place only and B) ensuring it can be kept up to date. There's no point starting if you can't pretty much guarantee B. AFAIK there is no automated way to do either so there is risk involved - this only means that your reward must be sufficient to take the risk.
I would keep the detail on the rPDU (agree with Christopherus' comments above) but I would automate the writing to DCO. You could use web service calls to read rPDU names from DCE (assuming its included), SNMP to get port/server info from each rPDU and web service calls to write the rPDU name and outlet number to a custom property on the DCO device.
For giggles, it might work something like this.....
Just thinking out loud. Let me know if you'd like to have a go.
Cheers
Ed
(CID:132651605)
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-04 06:45 PM . Last Modified: 2023-10-22 03:43 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.