MPO Connector Type Improvement #8458

Closed
opened 2025-12-29 20:37:01 +01:00 by adam · 7 comments
Owner

Originally created by @JoeIzzard on GitHub (Aug 11, 2023).

NetBox version

v3.2.1

Feature type

Change to existing functionality

Proposed functionality

Expand the MPO connector types to be more detailed. Currently it only lists MPO, however the number of fibre's within the MPO connector are an important aspect. As such we should add:

  • MPO12
  • MPO16
  • MPO24
  • MPO36
  • MPO48

I would suggest we leave MPO in place so we don't break anyones existing data, and just add the new ones to allow you to be more precise if you want to.

Use case

Better documentation, especially in connection with #13375

We mostly use MPO12 however have on occasion found other versions which we only realise at the last minute. Having this documented would be a big improvement.

Database changes

None, only requires adding more hardcoded connector types.

External dependencies

None

Originally created by @JoeIzzard on GitHub (Aug 11, 2023). ### NetBox version v3.2.1 ### Feature type Change to existing functionality ### Proposed functionality Expand the MPO connector types to be more detailed. Currently it only lists MPO, however the number of fibre's within the MPO connector are an important aspect. As such we should add: - MPO12 - MPO16 - MPO24 - MPO36 - MPO48 I would suggest we leave MPO in place so we don't break anyones existing data, and just add the new ones to allow you to be more precise if you want to. ### Use case Better documentation, especially in connection with #13375 We mostly use MPO12 however have on occasion found other versions which we only realise at the last minute. Having this documented would be a big improvement. ### Database changes None, only requires adding more hardcoded connector types. ### External dependencies None
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 20:37:01 +01:00
adam closed this issue 2025-12-29 20:37:01 +01:00
Author
Owner

@DanSheps commented on GitHub (Aug 11, 2023):

I haven't seen 32 and 48 connectors, but apparently they are out there. IMO I would omit them until someone asks for it.

That said, I would perhaps add 4 and 8.

@DanSheps commented on GitHub (Aug 11, 2023): I haven't seen 32 and 48 connectors, but apparently they are out there. IMO I would omit them until someone asks for it. That said, I would perhaps add 4 and 8.
Author
Owner

@JoeIzzard commented on GitHub (Aug 11, 2023):

I have seen them as an option when purchasing a few times, and MPO48 would be related to OpticalCON Connectors used in Entertainment (#12534). As these are usually a pass-through having the official MPO variant would be useful for anyone using them. I have seen 36 less so would be happy dropping that from the request for now.

I do agree we should add 4 & 8 too.

@JoeIzzard commented on GitHub (Aug 11, 2023): I have seen them as an option when purchasing a few times, and MPO48 would be related to OpticalCON Connectors used in Entertainment (#12534). As these are usually a pass-through having the official MPO variant would be useful for anyone using them. I have seen 36 less so would be happy dropping that from the request for now. I do agree we should add 4 & 8 too.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 10, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 10, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@JoeIzzard commented on GitHub (Nov 12, 2023):

I am happy to take this work on if I can get approval to do so.

@JoeIzzard commented on GitHub (Nov 12, 2023): I am happy to take this work on if I can get approval to do so.
Author
Owner

@DanSheps commented on GitHub (Nov 13, 2023):

Assigned to you @JoeIzzard

@DanSheps commented on GitHub (Nov 13, 2023): Assigned to you @JoeIzzard
Author
Owner

@github-actions[bot] commented on GitHub (Aug 23, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 23, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 23, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8458