Closed sliddjur closed 2 years ago
Hi,
Good point. Maybe the missing network is the issue here. Will check if I can add these interfaces as well.
Hi,
I finally got time and was about adding this info.
The issue here is that there is no interface name exposed. I could make up interface names out of the MC address last few octets.
macAddress = '76:3e:00:c9:3c:d9',
-> "dummy-3cd9"
What do you think?
Yes, this sounds like a good idea.
Hi,
I just added a ne config option sync_vm_dummy_interfaces
to the project. Can you pull the latest development
branch and test it out?
Tank you
@bb-Ricardo it seems to work - however I noticed some VM's adds an extra interface without an actual IP-address on them.
@sliddjur: That is correct. because these interfaces are populated but have no IP address assigned.
Is there any use for dummy interfaces without IP addresses to be synced?
Otherwise we could just skip these ones.
well, I just added it.
I think we should skip those interfaces. Thanks for your awesome work! :)
did you test the latest "development" commit?
Yes - it seems to work as expected.
I have some VyOS VM's that uses the
dummy
linux type of interfaces. These VMs uses Debian Buster as base OS.The IP's are exposed on vmware tools, but doing some debugging, I see that they don't have a
Device
nor aNetworkName
property.I want these IP's to be synced to netbox, as they are used globally. When I do a
netbox-sync
I don't see the IP's are ever listed in the debug output.I included a second interface that does work as intended for comparison.
Using PowerCLI tools:
And on the VM, the IP addresses are shown like this
Lastly, this is the output from
netbox-sync -l DEBUG3
, with what I think might be the relevant info.