starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Adding new port type - I/O Port #2702

New Issue
Closed
opened 2025-12-29 18:21:12 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:12 +01:00
Owner
Copy Link

Originally created by @greengorych on GitHub (Jun 27, 2019).

Environment

Python version: 3.6.8
NetBox version: 2.6.1

Proposed Functionality

Please add the option that allows creating a I/O type port for connecting various humidity or temperature sensors.

Use Case

Currently, we are creating a Smart-UPS SRT 3000 device type in the NetBox and specify it as Parent. We add a Device Bay to it, to which we add a UPS Network Management Card 2 device, which is a Child device.
The UPS Network Management Card 2 has two Universal I/O ports to which humidity or temperature sensors will be connected.
If the Universal I/O is specified as a console port you can connect to it only the port of another device, but not the end device.

Adding a new port type - I/O Port - would allow connecting humidity or temperature sensors for various devices.

Originally created by @greengorych on GitHub (Jun 27, 2019). ### Environment Python version: 3.6.8 NetBox version: 2.6.1 ### Proposed Functionality Please add the option that allows creating a I/O type port for connecting various humidity or temperature sensors. ### Use Case Currently, we are creating a Smart-UPS SRT 3000 device type in the NetBox and specify it as Parent. We add a Device Bay to it, to which we add a UPS Network Management Card 2 device, which is a Child device. The UPS Network Management Card 2 has two Universal I/O ports to which humidity or temperature sensors will be connected. If the Universal I/O is specified as a console port you can connect to it only the port of another device, but not the end device. Adding a new port type - I/O Port - would allow connecting humidity or temperature sensors for various devices.
adam closed this issue 2025-12-29 18:21:12 +01:00
adam commented 2025-12-29 18:21:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 27, 2019):

These are not considered network interfaces. Modeling these is out of scope for NetBox.

@jeremystretch commented on GitHub (Jun 27, 2019): These are not considered network interfaces. Modeling these is out of scope for NetBox.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2702
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?