Add Form Factor to power outlet/port #624

@jeremystretch commented on GitHub (Jan 17, 2017):

This is something I've had on the back burner for a while, but there's a lot more that needs to be added along with this (circuit amperage, voltage, phase, etc.), so I'm going to mark it as a major feature.

@jeremystretch commented on GitHub (Jan 17, 2017): This is something I've had on the back burner for a while, but there's a lot more that needs to be added along with this (circuit amperage, voltage, phase, etc.), so I'm going to mark it as a major feature.

adam commented

@rc5hack commented on GitHub (Feb 6, 2017):

adding also an optional "color" option for each outlet sounds like a good addition here (some PDU could have different colors outlets of the same type, e.g. black outlet is normal, and red outlet is UPS-backuped)

@rc5hack commented on GitHub (Feb 6, 2017): adding also an optional "color" option for each outlet sounds like a good addition here (some PDU could have different colors outlets of the same type, e.g. black outlet is normal, and red outlet is UPS-backuped)

adam commented

@jsenecal commented on GitHub (Feb 6, 2017):

We also got rack PDUs with a color per phase. black-gray-white

On Mon, Feb 6, 2017, 03:14 Antonio Kless, notifications@github.com wrote:

adding also an optional "color" option for each outlet sounds like a good
addition here (some PDU could have different colors outlets of the same
type, e.g. black outlet is normal, and red outlet is UPS-backuped)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/792#issuecomment-277611167,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfg5hwVGabC4w5NID4oOxJl4AmEgWf1ks5rZtaAgaJpZM4LhorG
.

@jsenecal commented on GitHub (Feb 6, 2017): We also got rack PDUs with a color per phase. black-gray-white On Mon, Feb 6, 2017, 03:14 Antonio Kless, <notifications@github.com> wrote: > adding also an optional "color" option for each outlet sounds like a good > addition here (some PDU could have different colors outlets of the same > type, e.g. black outlet is normal, and red outlet is UPS-backuped) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/792#issuecomment-277611167>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABfg5hwVGabC4w5NID4oOxJl4AmEgWf1ks5rZtaAgaJpZM4LhorG> > . >

adam commented

@bmsmithvb commented on GitHub (Mar 16, 2017):

Is it possible to obtain 0U rack PDUs?

@bmsmithvb commented on GitHub (Mar 16, 2017): Is it possible to obtain 0U rack PDUs?

adam commented

@jeremystretch commented on GitHub (Mar 16, 2017):

@bmsmithvb Yes, very easily. Just set the device type's height to 0U.

@jeremystretch commented on GitHub (Mar 16, 2017): @bmsmithvb Yes, very easily. Just set the device type's height to 0U.

adam commented

@puck commented on GitHub (Aug 3, 2017):

If colours per phase are implemented, then they'll need to be customisable. We use different colours in NZ.

@puck commented on GitHub (Aug 3, 2017): If colours per phase are implemented, then they'll need to be customisable. We use different colours in NZ.

adam commented

@jasonguy commented on GitHub (Dec 7, 2017):

It is common practice in many DCs to mount the long PDUs (like a 24-port APC), vertically on the back of a rack. I set it as an unracked device currently, however it would be cool to add something to the graphical rack view, showing the vertically mounted PDU. This could also simply be displayed on the PDU detail page, along with information from the smart PDU.

@jasonguy commented on GitHub (Dec 7, 2017): It is common practice in many DCs to mount the long PDUs (like a 24-port APC), vertically on the back of a rack. I set it as an unracked device currently, however it would be cool to add something to the graphical rack view, showing the vertically mounted PDU. This could also simply be displayed on the PDU detail page, along with information from the smart PDU.

adam commented

@wrouesnel commented on GitHub (Apr 30, 2018):

Technically then you'd like to also mark a vertical PDU by what side of the housing its on (important if you were trying to tell someone which phase to unplug / replug).

@wrouesnel commented on GitHub (Apr 30, 2018): Technically then you'd like to also mark a vertical PDU by what side of the housing its on (important if you were trying to tell someone which phase to unplug / replug).

adam commented

@fischa commented on GitHub (Feb 7, 2019):

We use PDUs that have all or some switchable power outlets. Would be nice to have that as Boolean or yes/no field available (per power outlet) too.

@fischa commented on GitHub (Feb 7, 2019): We use PDUs that have all or some switchable power outlets. Would be nice to have that as Boolean or yes/no field available (per power outlet) too.

adam commented

@falz commented on GitHub (May 8, 2019):

Also give consideration to DC power. We recently begun testing Netbox and added some DC fuse panels as power connections.

Here are a few examples of DC panels that we, and likely others use. Between these two, there are 3 different fuse types. There are certainly many others as well:

http://www.trimminc.com/download/8271001001.pdf - 4x4 TPA + 5x5 GMT
http://www.trimminc.com/download/7272101001.pdf - 8x8 TPM

.. each fuse type can have different amperage (1, 3, 5, 10... etc). In our case everything worked just fine as-is, we labeled the power outlets as "TPA A[1-4] and "TPA B[1-4]".

The only important piece we were unable to document was fuse size (amps) and DC voltage (-48v). Voltage, at least in our case, is always static as we've standardized on -48v DC.

@falz commented on GitHub (May 8, 2019): Also give consideration to DC power. We recently begun testing Netbox and added some DC fuse panels as power connections. Here are a few examples of DC panels that we, and likely others use. Between these two, there are 3 different fuse types. There are certainly many others as well: http://www.trimminc.com/download/8271001001.pdf - 4x4 TPA + 5x5 GMT http://www.trimminc.com/download/7272101001.pdf - 8x8 TPM .. each fuse type can have different amperage (1, 3, 5, 10... etc). In our case everything worked just fine as-is, we labeled the power outlets as "TPA A[1-4] and "TPA B[1-4]". The only important piece we were unable to document was fuse size (amps) and DC voltage (-48v). Voltage, at least in our case, is always static as we've standardized on -48v DC.

adam commented

@DocCox commented on GitHub (May 24, 2019):

My team primarily works in DC environments - and power mapping is what keeps us considering different DCIM tools. We ended up with a home rolled flask solution but there's just not enough time to maintain it so Netbox is up for consideration

For DC power on the internal tool we used the following
Cable gauge
Cable color (helpful - different standards are everywhere)
Cable length
Cable battery/return
A/Z side terminations (Lug type/length/spacing/holes)

Fuse panels typically support 1 or more type of fuses/breakers now. Fuses had
Amperage
Form factor
Losses

Panels themselves had
Inputs/outputs with the above A/Z termination points
Internal Busses

The buses had
Compatible form factor(s)
Qty of connectors
Maximum amperage (By bus and form factor)
(Ex: In those 4x5 TPA/GMT panels its not uncommon to see 100-200A rating for the TPA bus and a 60A rating on the GMT bus. I see guys loading 60A GMT buses to 80A+ pretty frequently, or throwing 20A GMT fuses in a bus rated for 15A fuses.)

Just glancing over the version of netbox I have locally everything looks pretty close to whats needed
Fuse panels could be treated as chassis, busses would more or less be cards/modules, and the power runs over the existing port setup. Power could calculate fairly accurately from the top most device in the chain with this sort of setup - in some of our locations we own the whole shebang and in other vendors are providing us power to our BDFBs/inverters or straight to fuse panels

@DocCox commented on GitHub (May 24, 2019): My team primarily works in DC environments - and power mapping is what keeps us considering different DCIM tools. We ended up with a home rolled flask solution but there's just not enough time to maintain it so Netbox is up for consideration For DC power on the internal tool we used the following Cable gauge Cable color (helpful - different standards are everywhere) Cable length Cable battery/return A/Z side terminations (Lug type/length/spacing/holes) Fuse panels typically support 1 or more type of fuses/breakers now. Fuses had Amperage Form factor Losses Panels themselves had Inputs/outputs with the above A/Z termination points Internal Busses The buses had Compatible form factor(s) Qty of connectors Maximum amperage (By bus and form factor) (Ex: In those 4x5 TPA/GMT panels its not uncommon to see 100-200A rating for the TPA bus and a 60A rating on the GMT bus. I see guys loading 60A GMT buses to 80A+ pretty frequently, or throwing 20A GMT fuses in a bus rated for 15A fuses.) Just glancing over the version of netbox I have locally everything looks pretty close to whats needed Fuse panels could be treated as chassis, busses would more or less be cards/modules, and the power runs over the existing port setup. Power could calculate fairly accurately from the top most device in the chain with this sort of setup - in some of our locations we own the whole shebang and in other vendors are providing us power to our BDFBs/inverters or straight to fuse panels

adam commented

@bluikko commented on GitHub (Jun 11, 2019):

I would like to add my 2 cents in this feature request: if 0U vertical devices (my use case is large PDUs) are somehow rendered in rack views, please allow at least 3 of them horizontally and/or on the "depth axis".

@bluikko commented on GitHub (Jun 11, 2019): I would like to add my 2 cents in this feature request: if 0U vertical devices (my use case is large PDUs) are somehow rendered in rack views, please allow at least 3 of them horizontally and/or on the "depth axis".

adam commented

@jeremystretch commented on GitHub (Oct 30, 2019):

Adding this as reference material: https://twitter.com/network_phil/status/1181563103034724352

Also this excellent cheat sheet: http://blog.packetsar.com/wp-content/uploads/Power_and_Cooling_Cheat_Sheet.pdf

@jeremystretch commented on GitHub (Oct 30, 2019): Adding this as reference material: https://twitter.com/network_phil/status/1181563103034724352 Also this excellent cheat sheet: http://blog.packetsar.com/wp-content/uploads/Power_and_Cooling_Cheat_Sheet.pdf

adam commented

@pyro3d commented on GitHub (Nov 5, 2019):

+1 for more DC support. Have a number of devices off rectifiers+battery strings or off a PDU in a CO where it's needed. Copper grounding bars would also be nice.

@pyro3d commented on GitHub (Nov 5, 2019): +1 for more DC support. Have a number of devices off rectifiers+battery strings or off a PDU in a CO where it's needed. Copper grounding bars would also be nice.

adam commented

@jeremystretch commented on GitHub (Nov 6, 2019):

I'm having a difficult time determining what to include for the plug/outlet types. It seems there are several series of standards:

IEC 60320 (the CXX types)
Four (or 12?) different IEC 60309 arrangements
US NEMA
European CEE 7
ITA letter types, which overlap with various international standards

Does it make sense to include the ITA types (A through O) as their own types, even though they technically overlap with other standards? (For example, type A is the same as NEMA 1-15.) If not, we could just list individual country-specific types as their own series.

@jeremystretch commented on GitHub (Nov 6, 2019): I'm having a difficult time determining what to include for the plug/outlet types. It seems there are several series of standards: * [IEC 60320](https://en.wikipedia.org/wiki/IEC_60320) (the CXX types) * Four (or 12?) different [IEC 60309](https://en.wikipedia.org/wiki/IEC_60309) arrangements * US [NEMA](https://en.wikipedia.org/wiki/NEMA_connector) * European [CEE 7](https://en.wikipedia.org/wiki/CEE_7_standard_AC_plugs_and_sockets) * [ITA letter types](https://www.worldstandards.eu/electricity/plugs-and-sockets/), which overlap with various international standards Does it make sense to include the ITA types (A through O) as their own types, even though they technically overlap with other standards? (For example, type A is the same as NEMA 1-15.) If not, we could just list individual country-specific types as their own series.

adam commented

@swerveshot commented on GitHub (Nov 7, 2019):

Hi @jeremystretch! For your information; in the Netherlands we mostly encounter IEC 60320 (C13/14 and C19/C20) in the datacenter. And occasionally a CEE 7 'shuko' type plug.

@swerveshot commented on GitHub (Nov 7, 2019): Hi @jeremystretch! For your information; in the Netherlands we mostly encounter IEC 60320 (C13/14 and C19/C20) in the datacenter. And occasionally a CEE 7 'shuko' type plug.

adam commented

@jeremystretch commented on GitHub (Nov 7, 2019):

This work is mostly done, but leaving the issue open for additional feedback regarding specific types.

@jeremystretch commented on GitHub (Nov 7, 2019): This work is mostly done, but leaving the issue open for additional feedback regarding specific types.

adam commented

@bluikko commented on GitHub (Nov 8, 2019):

Can you confirm that "universal" outlet sockets are supported?

I have to admit that we have a few rack-mount "PDU"s with these for random power bricks. Here is an example of how the sockets look:
https://www.havells.com/content/dam/havells/consumer/switches/Fabio-modular-range/sockets/AHFKUXW133/cover.png

@bluikko commented on GitHub (Nov 8, 2019): Can you confirm that "universal" outlet sockets are supported? I have to admit that we have a few rack-mount "PDU"s with these for random power bricks. Here is an example of how the sockets look: https://www.havells.com/content/dam/havells/consumer/switches/Fabio-modular-range/sockets/AHFKUXW133/cover.png

adam commented

@ThomasADavis commented on GitHub (Nov 21, 2019):

Ok, just found this..

We have racks that have hardwired connections in them - so please add 'hardwired'.
We have systems coming in that will have 150A power feeds. The current feed max is about ~100A - I get:

<class 'django.db.utils.DataError'>

smallint out of range

Getting into the 1200A or better range for feeds can mean I create feeds from the substations all the way to rack. In case your wondering what the high current is used for, it's what a supercomputer cabinet pulls. :)

thanks!
thomas

@ThomasADavis commented on GitHub (Nov 21, 2019): Ok, just found this.. 1) We have racks that have hardwired connections in them - so please add 'hardwired'. 2) We have systems coming in that will have 150A power feeds. The current feed max is about ~100A - I get: ``` <class 'django.db.utils.DataError'> smallint out of range ``` Getting into the 1200A or better range for feeds can mean I create feeds from the substations all the way to rack. In case your wondering what the high current is used for, it's what a supercomputer cabinet pulls. :) thanks! thomas

adam commented