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

Management interface not listed in list box for device type #1019

New Issue
Closed
opened 2025-12-29 16:27:58 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:27:58 +01:00
Owner
Copy Link

Originally created by @mattdharris on GitHub (Jun 10, 2017).

Python version: 3.4.5
NetBox version: 2.0.5

I've created two "management interfaces" on a "Console Server" type device. The first one shows up in the list, called "Network 1" but the second which is called "Network 2" does not. If I attempt to create "Network 2" again, I get "Network 2: Interface template with this Device type and Name already exists." This indicates that it's there, just not showing up in the list box on the device type page.

Originally created by @mattdharris on GitHub (Jun 10, 2017). **Python version:** 3.4.5 **NetBox version:** 2.0.5 I've created two "management interfaces" on a "Console Server" type device. The first one shows up in the list, called "Network 1" but the second which is called "Network 2" does not. If I attempt to create "Network 2" again, I get "Network 2: Interface template with this Device type and Name already exists." This indicates that it's there, just not showing up in the list box on the device type page.
adam closed this issue 2025-12-29 16:27:58 +01:00
adam commented 2025-12-29 16:27:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 11, 2017):

Does "Network 2" show up in the interfaces list? It's possible that it was created without being designated as a management interface.

@jeremystretch commented on GitHub (Jun 11, 2017): Does "Network 2" show up in the interfaces list? It's possible that it was created without being designated as a management interface.
adam commented 2025-12-29 16:27:59 +01:00
Author
Owner
Copy Link

@mattdharris commented on GitHub (Jun 12, 2017):

Yepp, indeed it was. Which was odd because it was a serial console so it had all the serial ports over there and I hadn't noticed it. It was created the same way as the other mgmt interface though and that one had mgmt interface set.
I edited it to check the 'oob mgmt' box and that put it where it belonged. Not sure why that wasn't done right from the get go though, so still a minor bug.

@mattdharris commented on GitHub (Jun 12, 2017): Yepp, indeed it was. Which was odd because it was a serial console so it had all the serial ports over there and I hadn't noticed it. It was created the same way as the other mgmt interface though and that one had mgmt interface set. I edited it to check the 'oob mgmt' box and that put it where it belonged. Not sure why that wasn't done right from the get go though, so still a minor bug.
adam commented 2025-12-29 16:28:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 12, 2017):

Interfaces are designed as management-only by default if you click the "add interfaces" button in the "critical connections panel" (note the ?mgmt_only=1 in the URL). Otherwise, it has to be toggled manually.

@jeremystretch commented on GitHub (Jun 12, 2017): Interfaces are designed as management-only by default if you click the "add interfaces" button in the "critical connections panel" (note the `?mgmt_only=1` in the URL). Otherwise, it has to be toggled manually.
adam commented 2025-12-29 16:28:00 +01:00
Author
Owner
Copy Link

@mattdharris commented on GitHub (Jun 12, 2017):

I just figured out what the issue was here after playing around with reproducing this to make sure I'm not just crazy. I had created this via the "device type" screen, not a specific device. It was a serial console type and not network device type, so it didn't have network ports section on the right by default. So I clicked "create mgmt interface" from that page, and then added "Network 1", the OOB mgmt box was chcked. I then clicked "create and add another" and it created it then on the screen to create "Network 2", it did not have that box checked. Thus "Network 2" was created without the OOB mgmt flag set.

When it returned to the device type definition screen, "Network 2" was nowhere to be found because the network ports on the right side didn't exist. Going back to that screen after the fact, it appeared with "Network 2" in it.

So this isn't really a bug then, but just something a bit counter-intuitive insofar as "create and add another" when creating a mgmt interface does not keep that box checked by default on the second and latter submissions.

@mattdharris commented on GitHub (Jun 12, 2017): I just figured out what the issue was here after playing around with reproducing this to make sure I'm not just crazy. I had created this via the "device type" screen, not a specific device. It was a serial console type and not network device type, so it didn't have network ports section on the right by default. So I clicked "create mgmt interface" from that page, and then added "Network 1", the OOB mgmt box was chcked. I then clicked "create and add another" and it created it then on the screen to create "Network 2", it did not have that box checked. Thus "Network 2" was created without the OOB mgmt flag set. When it returned to the device type definition screen, "Network 2" was nowhere to be found because the network ports on the right side didn't exist. Going back to that screen after the fact, it appeared with "Network 2" in it. So this isn't really a bug then, but just something a bit counter-intuitive insofar as "create and add another" when creating a mgmt interface does not keep that box checked by default on the second and latter submissions.
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#1019
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?