Hosts that form VMWare cluster that get synchroniyed as Devices are "merged" into one Device
See original GitHub issueHi, I’m very pleased that this tool exists and I’m using it to synchronize virtual machines of my VMWare cluster with NetBox. Besides VirtualMachine objects, I noticed an object of type Device which holds a name of one of 3 physical machines that form the VMWare cluster. I noticed that whenever I run the synchronization, netbox-sync tries to “squeeze” the data of 3 machines into one entry of type Device, overwriting what it had just written:
2022-04-25 09:50:36,341 - INFO: Starting NetBox Sync v1.2.3 (2022-04-09)
2022-04-25 09:50:37,489 - INFO: Successfully connected to NetBox 'netbox.integralis.si'
2022-04-25 09:50:37,489 - INFO: Initializing sources
2022-04-25 09:50:37,556 - INFO: Successfully connected to vCenter SDK 'vc1.marand.si'
2022-04-25 09:50:37,556 - INFO: Querying necessary objects from NetBox. This might take a while.
2022-04-25 09:50:40,700 - INFO: Finished querying necessary objects from NetBox
2022-04-25 09:50:40,717 - INFO: Query data from vCenter: 'vc1.marand.si'
2022-04-25 09:50:42,970 - INFO: Device 'esx5.marand.si' attribute 'name' changed from 'esx6.marand.si' to 'esx5.marand.si'
2022-04-25 09:50:42,970 - INFO: Device 'esx5.marand.si' attribute 'serial' changed from 'YMLU009510' to 'YMLU009509'
2022-04-25 09:50:42,972 - INFO: Interface 'vmnic0 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:26:0D' to '4C:52:62:48:23:70'
2022-04-25 09:50:42,972 - INFO: Interface 'vmnic1 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:26:0E' to '4C:52:62:48:23:71'
2022-04-25 09:50:42,972 - INFO: Interface 'vmnic2 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8A:69' to '4C:52:62:4A:8C:01'
2022-04-25 09:50:42,973 - INFO: Interface 'vmnic2 (esx5.marand.si)' attribute 'description' changed from 'pNIC' to ' pNIC'
2022-04-25 09:50:42,973 - INFO: Interface 'vmnic3 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8A:6A' to '4C:52:62:4A:8C:02'
2022-04-25 09:50:42,973 - INFO: Interface 'vmnic3 (esx5.marand.si)' attribute 'description' changed from 'pNIC' to ' pNIC'
2022-04-25 09:50:42,974 - INFO: Interface 'vmnic4 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8A:6B' to '4C:52:62:4A:8C:03'
2022-04-25 09:50:42,974 - INFO: Interface 'vmnic4 (esx5.marand.si)' attribute 'description' changed from 'pNIC' to ' pNIC'
2022-04-25 09:50:42,974 - INFO: Interface 'vmnic5 (esx5.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8A:6C' to '4C:52:62:4A:8C:04'
2022-04-25 09:50:42,974 - INFO: Interface 'vmnic5 (esx5.marand.si)' attribute 'description' changed from 'pNIC' to ' pNIC'
2022-04-25 09:50:42,975 - INFO: Interface 'vmnic6 (esx5.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A4:74' to 'B4:96:91:78:A0:D8'
2022-04-25 09:50:42,975 - INFO: Interface 'vmnic6 (esx5.marand.si)' attribute 'type' changed from '10gbase-t' to '10gbase-x-sfpp'
2022-04-25 09:50:42,975 - INFO: Interface 'vmnic7 (esx5.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A4:75' to 'B4:96:91:78:A0:D9'
2022-04-25 09:50:42,975 - INFO: Interface 'vmnic7 (esx5.marand.si)' attribute 'type' changed from '10gbase-t' to '10gbase-x-sfpp'
2022-04-25 09:50:42,976 - INFO: Interface 'vmnic8 (esx5.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:99:C8' to 'B4:96:91:78:99:40'
2022-04-25 09:50:42,976 - INFO: Interface 'vmnic8 (esx5.marand.si)' attribute 'type' changed from '10gbase-t' to '10gbase-x-sfpp'
2022-04-25 09:50:42,976 - INFO: Interface 'vmnic9 (esx5.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:99:C9' to 'B4:96:91:78:99:41'
2022-04-25 09:50:42,976 - INFO: Interface 'vmnic9 (esx5.marand.si)' attribute 'type' changed from '10gbase-t' to '10gbase-x-sfpp'
2022-04-25 09:50:42,977 - INFO: Interface 'vmk0 (esx5.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A4:74' to 'B4:96:91:78:A0:D8'
2022-04-25 09:50:42,979 - INFO: Interface 'vmk5 (esx5.marand.si)' attribute 'mac_address' changed from '00:50:56:61:F1:4A' to '00:50:56:69:59:44'
2022-04-25 09:50:42,981 - INFO: Interface 'vmk1 (esx5.marand.si)' attribute 'mac_address' changed from '00:50:56:65:89:AA' to '00:50:56:61:1B:65'
2022-04-25 09:50:42,983 - INFO: Interface 'vmk2 (esx5.marand.si)' attribute 'mac_address' changed from '00:50:56:66:74:F1' to '00:50:56:67:C0:AE'
2022-04-25 09:50:42,985 - INFO: Interface 'vmk3 (esx5.marand.si)' attribute 'mac_address' changed from '00:50:56:6A:06:D4' to '00:50:56:6C:70:E5'
2022-04-25 09:50:42,987 - INFO: Interface 'vmk4 (esx5.marand.si)' attribute 'mac_address' changed from '00:50:56:6D:61:BE' to '00:50:56:64:2F:92'
2022-04-25 09:50:45,081 - INFO: Device 'esx7.marand.si' attribute 'name' changed from 'esx5.marand.si' to 'esx7.marand.si'
2022-04-25 09:50:45,081 - INFO: Device 'esx7.marand.si' attribute 'serial' changed from 'YMLU009509' to 'YMLU009508'
2022-04-25 09:50:45,083 - INFO: Interface 'vmnic0 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:23:70' to '4C:52:62:48:23:7F'
2022-04-25 09:50:45,083 - INFO: Interface 'vmnic1 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:23:71' to '4C:52:62:48:23:80'
2022-04-25 09:50:45,084 - INFO: Interface 'vmnic2 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8C:01' to '4C:52:62:4A:8B:F9'
2022-04-25 09:50:45,084 - INFO: Interface 'vmnic3 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8C:02' to '4C:52:62:4A:8B:FA'
2022-04-25 09:50:45,085 - INFO: Interface 'vmnic4 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8C:03' to '4C:52:62:4A:8B:FB'
2022-04-25 09:50:45,085 - INFO: Interface 'vmnic5 (esx7.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8C:04' to '4C:52:62:4A:8B:FC'
2022-04-25 09:50:45,086 - INFO: Interface 'vmnic6 (esx7.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A0:D8' to 'B4:96:91:78:A5:8C'
2022-04-25 09:50:45,086 - INFO: Interface 'vmnic7 (esx7.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A0:D9' to 'B4:96:91:78:A5:8D'
2022-04-25 09:50:45,087 - INFO: Interface 'vmnic8 (esx7.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:99:40' to 'B4:96:91:78:A5:F4'
2022-04-25 09:50:45,087 - INFO: Interface 'vmnic9 (esx7.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:99:41' to 'B4:96:91:78:A5:F5'
2022-04-25 09:50:45,087 - INFO: Interface 'vmk0 (esx7.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A0:D8' to 'B4:96:91:78:A5:8C'
2022-04-25 09:50:45,089 - INFO: Interface 'vmk5 (esx7.marand.si)' attribute 'mac_address' changed from '00:50:56:69:59:44' to '00:50:56:69:94:D4'
2022-04-25 09:50:45,091 - INFO: Interface 'vmk1 (esx7.marand.si)' attribute 'mac_address' changed from '00:50:56:61:1B:65' to '00:50:56:62:F8:53'
2022-04-25 09:50:45,093 - INFO: Interface 'vmk2 (esx7.marand.si)' attribute 'mac_address' changed from '00:50:56:67:C0:AE' to '00:50:56:66:A1:C3'
2022-04-25 09:50:45,096 - INFO: Interface 'vmk3 (esx7.marand.si)' attribute 'mac_address' changed from '00:50:56:6C:70:E5' to '00:50:56:62:0A:04'
2022-04-25 09:50:45,098 - INFO: Interface 'vmk4 (esx7.marand.si)' attribute 'mac_address' changed from '00:50:56:64:2F:92' to '00:50:56:64:01:D0'
2022-04-25 09:50:47,287 - INFO: Device 'esx6.marand.si' attribute 'name' changed from 'esx7.marand.si' to 'esx6.marand.si'
2022-04-25 09:50:47,287 - INFO: Device 'esx6.marand.si' attribute 'serial' changed from 'YMLU009508' to 'YMLU009510'
2022-04-25 09:50:47,288 - INFO: Interface 'vmnic0 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:23:7F' to '4C:52:62:48:26:0D'
2022-04-25 09:50:47,289 - INFO: Interface 'vmnic1 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:48:23:80' to '4C:52:62:48:26:0E'
2022-04-25 09:50:47,289 - INFO: Interface 'vmnic2 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8B:F9' to '4C:52:62:4A:8A:69'
2022-04-25 09:50:47,290 - INFO: Interface 'vmnic3 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8B:FA' to '4C:52:62:4A:8A:6A'
2022-04-25 09:50:47,290 - INFO: Interface 'vmnic4 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8B:FB' to '4C:52:62:4A:8A:6B'
2022-04-25 09:50:47,291 - INFO: Interface 'vmnic5 (esx6.marand.si)' attribute 'mac_address' changed from '4C:52:62:4A:8B:FC' to '4C:52:62:4A:8A:6C'
2022-04-25 09:50:47,291 - INFO: Interface 'vmnic6 (esx6.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A5:8C' to 'B4:96:91:78:A4:74'
2022-04-25 09:50:47,292 - INFO: Interface 'vmnic7 (esx6.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A5:8D' to 'B4:96:91:78:A4:75'
2022-04-25 09:50:47,292 - INFO: Interface 'vmnic8 (esx6.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A5:F4' to 'B4:96:91:78:99:C8'
2022-04-25 09:50:47,293 - INFO: Interface 'vmnic9 (esx6.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A5:F5' to 'B4:96:91:78:99:C9'
2022-04-25 09:50:47,293 - INFO: Interface 'vmk0 (esx6.marand.si)' attribute 'mac_address' changed from 'B4:96:91:78:A5:8C' to 'B4:96:91:78:A4:74'
2022-04-25 09:50:47,295 - INFO: Interface 'vmk5 (esx6.marand.si)' attribute 'mac_address' changed from '00:50:56:69:94:D4' to '00:50:56:61:F1:4A'
2022-04-25 09:50:47,297 - INFO: Interface 'vmk1 (esx6.marand.si)' attribute 'mac_address' changed from '00:50:56:62:F8:53' to '00:50:56:65:89:AA'
2022-04-25 09:50:47,299 - INFO: Interface 'vmk2 (esx6.marand.si)' attribute 'mac_address' changed from '00:50:56:66:A1:C3' to '00:50:56:66:74:F1'
2022-04-25 09:50:47,301 - INFO: Interface 'vmk3 (esx6.marand.si)' attribute 'mac_address' changed from '00:50:56:62:0A:04' to '00:50:56:6A:06:D4'
2022-04-25 09:50:47,304 - INFO: Interface 'vmk4 (esx6.marand.si)' attribute 'mac_address' changed from '00:50:56:64:01:D0' to '00:50:56:6D:61:BE'
...
It looks like the “key” of that Device object is the same for all 3 machines. Can I do something to my VMWare cluster so that I get 3 separate Device objects in NetBox?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Managing Host and Cluster Lifecycle - VMware vSphere 7.0
vSphere Lifecycle Manager to manage the ESXi hosts and clusters in your environment. Managing Host and Cluster Lifecycle provides ...
Read more >Automating High Availability (HA) Services with VMware HA
VMware Infrastructure introduces two new concepts: • Clusters that aggregate and manage the combined resources of multiple hosts as a single collection.
Read more >vCenter Server and Host Management - VMware vSphere 7.0
vSphere Client components, configure and manage hosts, migrate virtual machines, and manage licenses in your. vCenter Server environment.
Read more >vSAN Monitoring and Troubleshooting - VMware vSphere 6.7
You can monitor hosts, cache devices, and capacity devices used in the vSAN cluster. Procedure. 1. Navigate to the vSAN cluster. 2 Click...
Read more >Add а Host to a Cluster - VMware Docs
In the vSphere Client, navigate to a cluster within a data center. · On the Configure tab, select Configuration > Quickstart. · Click...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It worked. I now have 3 devices.
An asset Tag is meant to be unique, like a serial number. Not sure who (VMWare or Fujitsu) causes this problem here. If you can live without the tag automatically synced then you’re ready to go.