OOB Management Interfaces being grouped with normal Interfaces

[aaronkrzywicki]

Issue type

[x] Bug report

Environment

• NetBox version: 14a2f0c015ab (v2.2.2)
  

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.

[aaronkrzywicki]

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

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.

[jeremystretch]

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.