Does Third party PDUs (Single IP with multiple sensors) can be associate with DCO basic rack pdus?

[DCIM_Support]

Hi

Please clarrify 3rd party PDU / Line meters which have single ip connected with multiple Basic rack PDUs. How to associate the Power and Temperature sensors in DCO basic pdus?

The example products are mentioned below:

Chatworts Product (CPI) – Diasy Chain Connection upto 20 PDUs in a single IP 

- Panduit- Unite CL Amp – where I can use Eagle-I (having single IP) with multiple Clamp Meters or PDUs or sensors

RacKMS - Single IP with multiple Clamp meters for Basic PDU measurement.

(CID:89064339)

[DCIM_Support]

Hi Venkat,

You will get as many sensors you have in DC Expert for the discovered devices. Please share the snaps from DCE & DCO- Device Associations. If you are able to see the sensors & all their sub-sensors in device association, only then you will be able to associate them.

(CID:89064349)

[DCIM_Support]

Thanks Aniruddh,

I didn't see the sensors & all their sub-sensors in DCO device association for this product. Please find herewith the RacKMS and DCE Snapshots for your reference.

Is there any work around / road map to add these kind of products single IP with multiple sensors for Basic Rackpdu DCO association?

(CID:89064375)

[DCIM_Support]

Hi Venkat,

As per your observations, you see common sensors discovered in DCO for power & environment so you cannot have them segregated & mapped against the actual physical location of the device. To achieve this you need to have them discovered separately. Well, here we are solely dependent on the way the third party devices make the data available to DCO after their discovery. You can map the only device discovered in DCO & let it report all the data. Thanks. 

(CID:89064425)

[DCIM_Support]

Hi Venkat,

Specific case = custom solution 😀 

Take a look at our ETL integration possibilities. I have solved recently a similar problem by building a custom integration between DCE and DCO, pushing to DCO the different sensors independently (each power sensor = one device), so you can associate them to the rackPDU you want to. We end-up with a very similar behaviour than the standard integration DCE/DCO: peak and average values, KPIs generation...etc

(CID:89555647)

[DCIM_Support]

Hi Vigneron, can you compile the same into a information presentation with snapshots showcasing the way you did it so that we can work on similar patterns as well. I believe when you say pushing each power sensor as one device , did you modify the MIB and DDF to report the parameters in such way?

(CID:89556790)

[DCIM_Support]

Hi Vineet, I did not modify the way DCE recognise the devices and sensors, so I didn't touch to MIB and/or DDF. I created an ETL integration that request to DCE (via web-services) the list of the concerned devices, based on the result I request then the list and values of the sensors in these devices. I pushed the information to DCO in the following form: each sensor is a device with one power measurement. The end result in DCO is a list of devices (each one representing one power measurement) that I can associate one by one to my modelled rackPDUs. This require knowledge on DCE web-services and ETL and must not be considered as a plug and play solution. It's a professional service that require some time for: -understanding the exact situation -developing the ETL process -deeply testing the solution We can help you guys if you face that sort of situation, feel free to contact us.

(CID:89556799)

[DCIM_Support · Accepted solution]

Hi Venkat,

An option that has worked for us with Unite / Eagle-i is to create a virtual sensor in DC Expert for each active power point.

Associate that virtual sensor to the Rack PDU upstream distribution PDU, then use branch circuit mapping to map the virtual sensor to the circuit outlet that corresponds to the Rack PDU.

This if for DCO 7.4, not sure if this works in prior versions

(CID:90243188)

[DCIM_Support]

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