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

OOB Management Interfaces being grouped with normal Interfaces #1358

New Issue
Closed
opened 2025-12-29 16:31:45 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:31:45 +01:00
Owner
Copy Link

Originally created by @aaronkrzywicki on GitHub (Oct 27, 2017).

Issue type

[x] Bug report

Environment

  • NetBox version: 14a2f0c015ab (v2.2.2)
    screenshot from 2017-10-27 10-58-33

Description

OOB Management Interface functionality not working as expected. When OOB Management radio button is selected for a new interface it shows in the group of normal interfaces.

This behavior is unexpected as far as I can tell. Expected behavior would be interfaces created with the OOB Management radio button checked should be grouped in their own Management Interfaces group independent of the main interfaces.

Originally created by @aaronkrzywicki on GitHub (Oct 27, 2017). ### Issue type [x] Bug report <!-- Reporting unexpected or erroneous behavior --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * NetBox version: 14a2f0c015ab (v2.2.2) ![screenshot from 2017-10-27 10-58-33](https://user-images.githubusercontent.com/12716923/32113829-28b2ae84-bb07-11e7-9e48-e2368192e8a5.png) ### Description OOB Management Interface functionality not working as expected. When OOB Management radio button is selected for a new interface it shows in the group of normal interfaces. This behavior is unexpected as far as I can tell. Expected behavior would be interfaces created with the OOB Management radio button checked should be grouped in their own Management Interfaces group independent of the main interfaces.
adam added the type: bug label 2025-12-29 16:31:45 +01:00
adam closed this issue 2025-12-29 16:31:45 +01:00
adam commented 2025-12-29 16:31:46 +01:00
Author
Owner
Copy Link

@aaronkrzywicki commented on GitHub (Oct 27, 2017):

It's also not possible to add a management interface to a PDU or console server without also marking the device as a network device. especially when that check box specifically says "This device has NON-MANAGEMENT network interfaces".

However
upload 4
you can designate a PDU or console server as a network device, add the management interface, then remove the network device designation and the management interface stays.

@aaronkrzywicki commented on GitHub (Oct 27, 2017): It's also not possible to add a management interface to a PDU or console server without also marking the device as a network device. especially when that check box specifically says "This device has NON-MANAGEMENT network interfaces". However <img width="245" alt="upload 4" src="https://user-images.githubusercontent.com/12716923/32114849-3ea56d00-bb0a-11e7-8821-6e6979c89080.png"> you can designate a PDU or console server as a network device, add the management interface, then remove the network device designation and the management interface stays.
adam commented 2025-12-29 16:31:46 +01:00
Author
Owner
Copy Link

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

OOB Management Interface functionality not working as expected. When OOB Management radio button is selected for a new interface it shows in the group of normal interfaces.

This is intended behavior. Management interfaces used to be grouped separately but were merged with normal interfaces a while back to simplify the UI.

It's also not possible to add a management interface to a PDU or console server without also marking the device as a network device. especially when that check box specifically says "This device has NON-MANAGEMENT network interfaces".

This wording is outdated and should be fixed. Anything with a network interface is considered a network device.

However you can designate a PDU or console server as a network device, add the management interface, then remove the network device designation and the management interface stays.

This is intended behavior. Modifying a device type does not retroactively alter any associated devices.

@jeremystretch commented on GitHub (Oct 30, 2017): > OOB Management Interface functionality not working as expected. When OOB Management radio button is selected for a new interface it shows in the group of normal interfaces. This is intended behavior. Management interfaces used to be grouped separately but were merged with normal interfaces a while back to simplify the UI. > It's also not possible to add a management interface to a PDU or console server without also marking the device as a network device. especially when that check box specifically says "This device has NON-MANAGEMENT network interfaces". This wording is outdated and should be fixed. Anything with a network interface is considered a network device. > However you can designate a PDU or console server as a network device, add the management interface, then remove the network device designation and the management interface stays. This is intended behavior. Modifying a device type does not retroactively alter any associated devices.
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 type: bug
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#1358
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?