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

manually set IP address will be overwritten #378

Open
BastiAtWork opened this issue Mar 20, 2024 · 3 comments
Open

manually set IP address will be overwritten #378

BastiAtWork opened this issue Mar 20, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@BastiAtWork
Copy link

Hello,

Some of our VMs are synchronized without an IP address because they do not have VM Guest Tools installed. If we set the IP address manually in Netbox, it will be set to "none" again at the next sync. Is it possible to deactivate the overwriting of the primary IP?

I had already tried to prevent this with the option:
set_primary_ip: never

But unfortunately the primary IP is still removed.

Thank you for this great project!!

@bb-Ricardo
Copy link
Owner

Thank you, will have a look at it.

@bb-Ricardo bb-Ricardo added the bug Something isn't working label May 14, 2024
@alainseys
Copy link

@BastiAtWork seems like intended so netbox should act as single source of truth so if you manualy change the ip.
The sync will get back to the vmware api and try to get the ipadres if nothing is found this wil report back (everything in your source dataset is the truth).

you can use exclude vm to allow to be excluded so the sync will not process this vm no longer. (i should place a tag on that vm so you can filter on the non sync vms / devices).

i have the same issue with contact that i had linked to a vm , i added custom fields on vcenter to sync this

@smasharov
Copy link

Wi have a similar, but slightly different situation, described in #302

VM have a trunk interface, and several IP addresses. each vlan have own IP
vm-tools reports all IPs, but without vlan information.

slave interfaces created in netbox, but after the sync all IP adresses from them will be re-assigned to the parent interface.

I think in such situations IP re-assignment must be skipped if the IP already assigned to the slave interface inside vm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants