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

Skip virtual interfaces overwriting physical interfaces #406

Open
alexpusca opened this issue Aug 6, 2024 · 2 comments
Open

Skip virtual interfaces overwriting physical interfaces #406

alexpusca opened this issue Aug 6, 2024 · 2 comments

Comments

@alexpusca
Copy link

alexpusca commented Aug 6, 2024

I have a new Netbox installation, in which I have already documented the servers (site/location/rack/modules) and cables.
When running the vCenter sync, the virtual bonds (vmk0...x) overwrite and alter the existing physical configuration of the server. Is there a way in which:
a. virtual bonds should be created as virtual interfaces and only vmnic0....x should overwrite the physical interface parameters?
b. a user could totally skip the population of the virtual bonds?

I have read the documentation and tried to find a solution in the configuration file, but I couldn't find a solution. We are running a standalone Netbox 3.7.6

@alexpusca
Copy link
Author

To make the issue a little more clear, below an example of a dry run for a node:
2024-08-06 08:49:00,666 - DEBUG2: Matching 'vmk0' to NetBox Interface 'FlexLOMP1 (node2)'
2024-08-06 08:49:00,666 - DEBUG2: Matching 'vmk1' to NetBox Interface 'FlexLOMP2 (node2)'
2024-08-06 08:49:00,666 - DEBUG2: Matching 'vmnic0' to NetBox Interface 'FlexLOMP3 (node2)'
2024-08-06 08:49:00,666 - DEBUG2: Matching 'vmnic1' to NetBox Interface 'FlexLOMP4 (node2)'
2024-08-06 08:49:00,667 - DEBUG2: Matching 'vmnic10' to NetBox Interface 'Gig-E 1 (node2)'
2024-08-06 08:49:00,667 - DEBUG2: Matching 'vmnic11' to NetBox Interface 'Gig-E 2 (node2)'
2024-08-06 08:49:00,667 - DEBUG2: Matching 'vmnic12' to NetBox Interface 'Gig-E 3 (node2)'
2024-08-06 08:49:00,667 - DEBUG2: Matching 'vmnic13' to NetBox Interface 'Gig-E 4 (node2)'
2024-08-06 08:49:00,668 - DEBUG2: Matching 'vmnic2' to NetBox Interface 'PCIe1P1 (node2)'
2024-08-06 08:49:00,668 - DEBUG2: Matching 'vmnic3' to NetBox Interface 'PCIe1P2 (node2)'
2024-08-06 08:49:00,668 - DEBUG2: Matching 'vmnic4' to NetBox Interface 'PCIe3P1 (node2)'
2024-08-06 08:49:00,668 - DEBUG2: Matching 'vmnic5' to NetBox Interface 'PCIe3P2 (node2)'
2024-08-06 08:49:00,668 - DEBUG2: Matching 'vmnic6' to NetBox Interface 'PCIe4P1 (node2)'
2024-08-06 08:49:00,669 - DEBUG2: Matching 'vmnic7' to NetBox Interface 'PCIe4P2 (node2)'
2024-08-06 08:49:00,669 - DEBUG2: Matching 'vmnic8' to NetBox Interface 'PCIe5P1 (node2)'
2024-08-06 08:49:00,669 - DEBUG2: Matching 'vmnic9' to NetBox Interface 'PCIe5P2 (node2)'

If the first two lines (vmk0 and vmk1) would be omitted, then mapping would be correct (the interfaces are not physical, but virtual VMkernel adapters)

@bb-Ricardo
Copy link
Owner

Hi, good point. Usually it matches by MAC address. But I guess your current NetBox config does not contain the MAC addresses and that's why the script try to do a 1:1 match

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants