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

Add PPS (COAX) port type #10016

New Issue
Closed
opened 2025-12-29 21:25:45 +01:00 by adam · 11 comments
adam commented 2025-12-29 21:25:45 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Jul 26, 2024).

NetBox version

v4.0.7

Feature type

Change to existing functionality

Proposed functionality

Update netbox/dcim/choices.py to include a new Coaxial type called PPS.

Use case

Wikipedia references this page about it http://pos.mgb-tech.com/insightpps/.

Arista and others have devices with PPS interfaces like the 7130 series https://www.arista.com/assets/data/pdf/Datasheets/7135LB-Datasheet.pdf

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Jul 26, 2024). ### NetBox version v4.0.7 ### Feature type Change to existing functionality ### Proposed functionality Update netbox/dcim/choices.py to include a new Coaxial type called PPS. ### Use case Wikipedia references this page about it http://pos.mgb-tech.com/insightpps/. Arista and others have devices with PPS interfaces like the 7130 series https://www.arista.com/assets/data/pdf/Datasheets/7135LB-Datasheet.pdf ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 21:25:45 +01:00
adam closed this issue 2025-12-29 21:25:45 +01:00
adam commented 2025-12-29 21:25:46 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 29, 2024):

@ryanmerolle it looks like you have this in your codebase already, so assigning to you.

@arthanson commented on GitHub (Jul 29, 2024): @ryanmerolle it looks like you have this in your codebase already, so assigning to you.
adam commented 2025-12-29 21:25:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 2, 2024):

My understanding is that PPS is a type of clocking signal, not a network interface. Is that incorrect?

@jeremystretch commented on GitHub (Aug 2, 2024): My understanding is that [PPS](https://en.wikipedia.org/wiki/Pulse-per-second_signal) is a type of clocking signal, not a network interface. Is that incorrect?
adam commented 2025-12-29 21:25:46 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Aug 10, 2024):

That’s fair, but the only coax connector in netbox was docsis. It’s definitely not that connector type.

Cisco, Arista, and several of the time sync appliance makers all have a coax connector they label as pps. I’m happy to call it coax or any other name.

@ryanmerolle commented on GitHub (Aug 10, 2024): That’s fair, but the only coax connector in netbox was docsis. It’s definitely not that connector type. Cisco, Arista, and several of the time sync appliance makers all have a coax connector they label as pps. I’m happy to call it coax or any other name.
adam commented 2025-12-29 21:25:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2024):

It's not a network interface at all, so adding it as one would not make sense.

@jeremystretch commented on GitHub (Aug 10, 2024): It's not a network interface at all, so adding it as one would not make sense.
adam commented 2025-12-29 21:25:47 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Aug 12, 2024):

Isn't this duplicate of #16334 which has more detail about the physical interface?

@bluikko commented on GitHub (Aug 12, 2024): Isn't this duplicate of #16334 which has more detail about the physical interface?
adam commented 2025-12-29 21:25:47 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Aug 12, 2024):

Yep but I have a PR ready. I do not see a PR linked for that issue.

@ryanmerolle commented on GitHub (Aug 12, 2024): Yep but I have a PR ready. I do not see a PR linked for that issue.
adam commented 2025-12-29 21:25:47 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Aug 13, 2024):

Interesting, very interesting.

Edit: "PPS" is not any kind of standard interface, by the way. See the previously linked issue for actual standardized connector names.

@bluikko commented on GitHub (Aug 13, 2024): Interesting, very interesting. Edit: "PPS" is not any kind of standard interface, by the way. See the previously linked issue for *actual* standardized connector names.
adam commented 2025-12-29 21:25:47 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Aug 13, 2024):

@bluikko can you explicitly state what port names need to be added in the linked issue so I can update the or? Ie add the follow port names:

  • port name 1
  • Port name 2
@ryanmerolle commented on GitHub (Aug 13, 2024): @bluikko can you explicitly state what port names need to be added in the linked issue so I can update the or? Ie add the follow port names: - port name 1 - Port name 2
adam commented 2025-12-29 21:25:48 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Aug 14, 2024):

@bluikko can you explicitly state what port names need to be added in the linked issue so I can update the or? Ie add the follow port names:

Sure, here's some data on the physical interfaces:

I do not know if it is better to add these using the acronym or the full name. I assume it's a judgement call based on how interfaces are listed currently in NetBox.

Datasheet example of both from a well-known connector vendor: https://web.archive.org/web/20100331083020/http://www.amphenolrf.com/products/CatalogPages/SMA.pdf

The earlier issue called them "SMA connector types" but I believe that is a bit wrong (nitpicking), the two interfaces are not types of "SMA" but types of "SM" (subminiature).

There is also "SMC" but I do not know how prevalent that is; wiki also lists several other SM versions. I could not find mainstream network devices using SMC while SMA/SMB are common AFAIK.
From what I can tell the PPS interfaces on Juniper, Cisco at least are either SMA or SMB.

@bluikko commented on GitHub (Aug 14, 2024): > @bluikko can you explicitly state what port names need to be added in the linked issue so I can update the or? Ie add the follow port names: Sure, here's some data on the physical interfaces: - **SMA**: "SubMiniature version A", reference https://en.wikipedia.org/wiki/SMA_connector - **SMB**: "SubMiniature version B", reference https://en.wikipedia.org/wiki/SMB_connector I do not know if it is better to add these using the acronym or the full name. I assume it's a judgement call based on how interfaces are listed currently in NetBox. Datasheet example of both from a well-known connector vendor: https://web.archive.org/web/20100331083020/http://www.amphenolrf.com/products/CatalogPages/SMA.pdf The earlier issue called them "SMA connector types" but I believe that is a bit wrong (nitpicking), the two interfaces are not types of "SMA" but types of "SM" (subminiature). There is also "SMC" but I do not know how prevalent that is; wiki also lists several other SM versions. I could not find mainstream network devices using SMC while SMA/SMB are common AFAIK. From what I can tell the PPS interfaces on Juniper, Cisco at least are either SMA or SMB.
adam commented 2025-12-29 21:25:48 +01:00
Author
Owner
Copy Link

@pobk commented on GitHub (Aug 14, 2024):

The "mostly standard but some manufacturers want to be SPESHUL" standard is SMA for things like GNSS receivers et al. Timing interfaces are a bit of a quirky thing. 1PPS has implementations in RJ-11, RJ-45, SMA, and I've seen older kit using standard N-type or F-type connectors too. It seems to be a coaxial thing...

I believe the ITU or IEEE might have said something on it, at some point, but I'm attempting to stay away from that rabbithole of woe and information overload at the moment.

Also, as I've said elsewhere, just because it's not running IP, doesn't mean it's not a network... PTP and other networks exist.

Specifically, in this case, I think I can personally agree that this should not be an "interface" in the context of netbox but instead a front-port.

SMA is the understood definition of the connector type. If you throw that in an email to me, I will immediately comprehend what level of pain I'm going to suffer that day.

Actually, having spent the morning thinking about this. A front-port implies a passive connection to a rear-port. This is not the case. This should be an interface. It is the external connectvity (interface) to a targetted function within the device. It is no different from an ethernet port, SFP+ cage or a console port. Each of these are external connectivity for a targetted function within the device.

@pobk commented on GitHub (Aug 14, 2024): The "mostly standard but some manufacturers want to be SPESHUL" standard is SMA for things like GNSS receivers et al. Timing interfaces are a bit of a quirky thing. 1PPS has implementations in RJ-11, RJ-45, SMA, and I've seen older kit using standard N-type or F-type connectors too. It seems to be a coaxial thing... I believe the ITU or IEEE might have said something on it, at some point, but I'm attempting to stay away from that rabbithole of woe and information overload at the moment. Also, as I've said elsewhere, just because it's not running IP, doesn't mean it's not a network... PTP and other networks exist. ~~Specifically, in this case, I think I can personally agree that this should not be an "interface" in the context of netbox but instead a front-port~~. SMA is the understood definition of the connector type. If you throw that in an email to me, I will immediately comprehend what level of pain I'm going to suffer that day. Actually, having spent the morning thinking about this. A front-port implies a passive connection to a rear-port. This is not the case. This should be an interface. It is the external connectvity (interface) to a targetted function within the device. It is no different from an ethernet port, SFP+ cage or a console port. Each of these are external connectivity for a targetted function within the device.
adam commented 2025-12-29 21:25:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 16, 2024):

I'm going to close this for two reasons:

  • "PPS" is not any type of physical connector at all. Rather, it is a signaling specification.
  • PPS is not used to transmit network data, and its termination would not be qualified as a network interface.
  • It seems that some form of this has already been proposed in #16334. Please continue any further discussion in that issue.
@jeremystretch commented on GitHub (Aug 16, 2024): I'm going to close this for two reasons: * "PPS" is not any type of physical connector at all. Rather, it is a [signaling specification](https://en.wikipedia.org/wiki/Pulse-per-second_signal). * PPS is not used to transmit network data, and its termination would not be qualified as a network interface. * It seems that some form of this has already been proposed in #16334. Please continue any further discussion in that issue.
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 status: duplicate type: feature
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#10016
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?