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

Adding support for Antenna & Dry Contacts mapping #1324

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

Originally created by @AnythingOverIP on GitHub (Oct 18, 2017).

Issue type

[ X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: Example: 3.5.4
  • NetBox version: 2.2.1

Description

Please consider adding the following:

  • Tracking of Antennas, the same way a network port or power is tracked.
  • Tracking of Dry Contacts, the same way a network port or power is tracked.

These 2 new items would be mostly used by people in the Telco world.

Antennas: Being able to track device to Antenna path would be beneficial. This could be used to track a GPS antenna of an NTP server or a transmit antenna from a Radio repeater. In both case, the device is hooked on the network and powered, it's just a matter of adding another level of granularity.

Dry Contacts: The same way other connections are tracked, allow the tracking of dry contacts connections (ie: Alarm board on a server hooked to a monitoring device).

Originally created by @AnythingOverIP on GitHub (Oct 18, 2017). ### Issue type [ X ] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: Example: 3.5.4 * NetBox version: 2.2.1 ### Description Please consider adding the following: * Tracking of Antennas, the same way a network port or power is tracked. * Tracking of Dry Contacts, the same way a network port or power is tracked. These 2 new items would be mostly used by people in the Telco world. Antennas: Being able to track device to Antenna path would be beneficial. This could be used to track a GPS antenna of an NTP server or a transmit antenna from a Radio repeater. In both case, the device is hooked on the network and powered, it's just a matter of adding another level of granularity. Dry Contacts: The same way other connections are tracked, allow the tracking of dry contacts connections (ie: Alarm board on a server hooked to a monitoring device).
adam closed this issue 2025-12-29 16:31:29 +01:00
adam commented 2025-12-29 16:31:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 18, 2017):

This would be covered by #968

@jeremystretch commented on GitHub (Oct 18, 2017): This would be covered by #968
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#1324
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?