Make MAC an available column on dcim/interfaces #3897

Closed
opened 2025-12-29 18:31:51 +01:00 by adam · 1 comment
Owner

Originally created by @lps-rocks on GitHub (Jul 24, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7.6
  • NetBox version: 2.8.7

Proposed Functionality

Make MAC an available column on dcim/interfaces.

Use Case

This is one of the most common search mechanisms used by networking administrators when tracking down an unknown device or a device that may not be operating properly.

Database Changes

None AFAIK

Originally created by @lps-rocks on GitHub (Jul 24, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.6 * NetBox version: 2.8.7 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Make MAC an available column on dcim/interfaces. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case This is one of the most common search mechanisms used by networking administrators when tracking down an unknown device or a device that may not be operating properly. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None AFAIK
adam added the status: acceptedtype: feature labels 2025-12-29 18:31:51 +01:00
adam closed this issue 2025-12-29 18:31:51 +01:00
Author
Owner

@jawyoonis commented on GitHub (Oct 9, 2020):

Hey guys, is this issue solved . I am having a similar issue in my ansible playbook when try to assign mac address to a device.


['Invalid custom field for dcim | device objects: MAC']}\n",
    "module_stdout": "",

@jeremystretch

@jawyoonis commented on GitHub (Oct 9, 2020): Hey guys, is this issue solved . I am having a similar issue in my ansible playbook when try to assign mac address to a device. ``` ['Invalid custom field for dcim | device objects: MAC']}\n", "module_stdout": "", ``` @jeremystretch
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3897