Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make MAC an available column on dcim/interfaces #4899

Closed
lps-rocks opened this issue Jul 24, 2020 · 1 comment
Closed

Make MAC an available column on dcim/interfaces #4899

lps-rocks opened this issue Jul 24, 2020 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@lps-rocks
Copy link

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

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application and removed status: accepted This issue has been accepted for implementation labels Jul 24, 2020
@jeremystretch jeremystretch self-assigned this Jul 24, 2020
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jul 24, 2020
@jawyoonis
Copy link

jawyoonis commented 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

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants