Pass-through ports missing from "add components" on device list #2534

Closed
opened 2025-12-29 18:19:44 +01:00 by adam · 2 comments
Owner

Originally created by @jeremystretch on GitHub (Apr 19, 2019).

Environment

  • Python version: 3.5.6
  • NetBox version: 2.5.10

Steps to Reproduce

  1. Navigate to the devices list
  2. At the bottom of the page, click the "Add components" button

Expected Behavior

Front ports and rear ports should be included in the list of available components

Observed Behavior

They are absent

Originally created by @jeremystretch on GitHub (Apr 19, 2019). ### Environment * Python version: 3.5.6 * NetBox version: 2.5.10 ### Steps to Reproduce 1. Navigate to the devices list 2. At the bottom of the page, click the "Add components" button ### Expected Behavior Front ports and rear ports should be included in the list of available components ### Observed Behavior They are absent
adam closed this issue 2025-12-29 18:19:44 +01:00
Author
Owner

@jeremystretch commented on GitHub (Apr 19, 2019):

IIRC these were skipped originally due to the difficulty in mapping front ports to rear ports across multiple devices simultaneously.

@jeremystretch commented on GitHub (Apr 19, 2019): IIRC these were skipped originally due to the difficulty in mapping front ports to rear ports across multiple devices simultaneously.
Author
Owner

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

I'm going to reject this one as there's no sane way to add front ports in bulk to multiple devices simultaneously. (Each front port must be mapped to a rear port belonging to its respective device.) As pass-through ports are static physical entities that can be defined on the DeviceType model, this shouldn't present much of an inconvenience.

@jeremystretch commented on GitHub (Dec 6, 2019): I'm going to reject this one as there's no sane way to add front ports in bulk to multiple devices simultaneously. (Each front port must be mapped to a rear port belonging to its respective device.) As pass-through ports are static physical entities that can be defined on the DeviceType model, this shouldn't present much of an inconvenience.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2534