Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
Rittal rPDU (CMC III Processing Unit) Association Issue
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.
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
Solved
Go to Solution
Hi All,
One of our customers has Rittal rPDU (DK 7955.411 & DK 7955.911), In each rack he has one (DK 7955.411) which is smart rPDU and connected to DCE private network and one (DK 7955.911) which is not smart and connected directly to the smart one.
And we got the attached DDF (for your reference) for this device and added it to DCE, The two rPDUs added to DCE as one node and we got the sensors of the two rPDUs on one device in DCE (Refer to attached screenshot).
When we tried to associate these devices to DCO data center item we found that
- We have only one device appeared under the external system, Without separated sensors for the two rPDUs to be associated to Qty: 2 of Rittal rPDU (The used Genome is "Power Distribution/Rack Power Distribution/Rittal Corp/PDU international, managed").
- We can NOT associate the rPDU device coming from the DCE to the selected genome, It appears like it's rack mounted device and refuse to be associated to rPDU genome.
So, Please advice.
Accepted Solutions
Hi Ahmed,
I don't think the described scenario can be fully supported in DCO/ITA - but concerning the device appearance as one device, that is expected. A device is defined as a single IP address in DCO.
Why you are unable to associate, I think in general if the rack pdu has already device association or most likely in this case the DCE device contains some unexpected properties not matching a rack pdu.
However your rack pdu "CMC III" dose not have/cannot provide any power data, so even if you had been able to associate it, it would not have provided any measured data.
To clarify, your rack pdu Properties shows only its External Systems info:
A DCE device/rack pdu that can provide power data, similar to the following image, will show External Systems > Device (that may contain measured data):
I'm not sure what to expect or what the possible power data may look like (in DCO/ITA) - perhaps as one device with peak and average power data, but I think at least from the DCO/ITA side it is expected that the DDF should contain definitions for
Power Sensors:
OUTPUT_POWER_WATTS
OUTPUT_POWER_TOTAL_WATTS
MODULE_OUTPUT_POWER or MODULE_BREAKER_POWER
Amp Sensors:
MODULE_BREAKER_CURRENT
OUTPUT_CURRENT
OUTPUT_CURRENT_TOTAL
INPUT_CURRENT
Kind regards,
Jef
Hi Jef,
Actually, I communicated the DDF team to clarify if it's applicable to get different rPDU components from DCE to can associate each component to different rPDU in DCO.
But it's not applicable as per their reply.
Now I did the association by moving the "unassociated device" pane to the right side window in DCO, found the rack pdu I want to associate it with in the navigation pane and drag and drop it on top.
and the device now is associated to the required rPDU, But without any power data as you explained.
However the used DDF in DCE doesn't contain definitions for the Power Sensors and Amp Sensors that you mentioned, but it is getting the device power data and can be monitored via DCE.
The Conclusion is
- The DDF is getting the power data of the device in DCE.
- Now the device is associated to the required data center item, But only the External Device info are shown in DCO (No power data).
So, What may be the cause of this issue? And How can be resolved?
Thanks,
Ahmed Ashraf
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.