Customized DDF for Network Port Sharing PDUs for proper DCE discovery & ITA Mapping

[sesa241642]

While we do not support Network Port Sharing as of today in DCE. Is it possible to create a custom DDF to be able to support the same, and also to enable proper device association in ITA?

[Jef]

Hi Aniruddha,

Network port sharing is not fully supported in DCE (or ITA). This is not DDF related. Currently discovered devices in DCE are tied to device IP address, eg. one unique IP = one device. Daisy chained rack pdu's might show up as a single device in DCE and might also be reported as a single device in ITA. 

Kind regards,

Jef

[sesa241642]

Thanks Jef,

May I ask if this behaves same for BCPM?

A different scenario though, One of our customers has added BCPM to DCE, via automation server, and now they want to see the Rack PDU level power mapping done in ITA. Can the original DDF be customized to split the independent BCMP-circuits to map them at the rack PDU level.

[ATrabert]

Although i haven't looked at it recently, i'm pretty sure network port sharing for APC rpdus works in DCE and you are able to some power information from all rpdus daisy chained together.  This also works on some 3rd party rpdus if the DDF is programed for it. I can double check if needed

Regarding BCPM and ITA, the customer should configure branch circuit monitoring using device association and sensor mapping https://helpcenter.ecostruxureit.com/hc/en-us/articles/360036207934-Configuring-branch-circuit-monit... 

this would be easier than trying to automate it with a DDF.

[sesa241642]

@ATrabert 

Many thanks for your response. Indeed, it would be great if this can be managed at DDF level.

So, to summarize the situation- Cascaded PDUs are seen as 1 single sensor in DCE. When it comes to ITA mapping (which is the end goal), we still see single sensor to associate. Hence we cannot associate the cascaded PDUs at all.

Expectation is to find a way to segregate the sensor data from the cascaded IP, so as to be seen as multiple rPDUs, cascade originally (with respective sensors tagged with resp. ePDUs), and to be able to associate in ITA individually at each corresponding  rPDU modelled.

This is required to be done for one of our big customers & partner in Sri Lanka which are at presenting facing this situation, and should be a good solution for many more customers, who leveraged cascading but not enough to extend the benefit in ITA.

Customer- Orion City

Partner- n*able

Thanks for commenting on the BCPM part as well, will validate and come back for any queries.

[Elvira231]

---

@sesa241642 mymilestonecard wrote:

While we do not support Network Port Sharing as of today in DCE. Is it possible to create a custom DDF to be able to support the same, and also to enable proper device association in ITA?

---

One of our customers has added BCPM to DCE, via automation server, and now they want to see the Rack PDU level power mapping done in ITA. 

[Anonymous user]

I faced similar kind of issue last time, I am still searching for some proper solution. MyMileStone Card

[ATrabert]

One of our customers has added BCPM to DCE, via automation server, and now they want to see the Rack PDU level power mapping done in ITA. 

Regarding BCPM and ITA, the customer should configure branch circuit monitoring using device association and sensor mapping https://helpcenter.ecostruxureit.com/hc/en-us/articles/360036207934-Configuring-branch-circuit-monit... 

they would associate the BCPM with the upstream RPP or Floor PDU, right click the device, click sensor mapping, then map each current and/or watt sensor to each circuit.

[Anonymous user]

 I am trying to Integrate a NetBotz 455 into DCE v7.6.0 however when I run the Device Discovery, its not running.

I had this NetBotz on DCE before but I deleted it and now I want to add it back onto DCE. I ran the previous saved discovery for this device but it wont run. I also created a new entry to Add the NetBotz but it won't Run either. I still have enough Licences.