IPs on slave virtual interface inside VM

[smasharov]

I have a lot of VMs with only one network adapter from the Hypervisor. VLANs are tagged and inside VM I have several sub-interfaces.
I have tried to re-assign IP assigned by this tool to the proper sub-interface, but after fresh run IP was removed from the sub-interface and assigned to the parent again. Is it possible to skip re-assigning of the IP if it is already assigned to one of the slave interfaces?

Also I want to name interfaces as they named inside the OS, but this tool rename them again to something like "vNIC 1 ({switch name})"

[bb-Ricardo]

Hi,

Not sure if this is possible as it depends on the VMWare tools and how they expose the IPs and the sub-interfaces over the vCenter API.

Can you run it in DEBUG3 mode and post the output of an example VM here?

Thank you.

[bb-Ricardo]

any updates?

[bb-Ricardo]

closing this issue due to missing response.

[smasharov]

2023-06-29 15:02:29,400 - DEBUG2: Trying to find prefix for IP: 10.165.160.93/28
2023-06-29 15:02:29,504 - DEBUG2: Found IP '10.165.160.93/28' matches global prefix '10.165.160.80/28'
2023-06-29 15:02:29,528 - DEBUG2: Found existing NetBox IP address object: 10.165.160.93/28
2023-06-29 15:02:29,529 - DEBUG2: Parsing 'IP address' data structure: 10.165.160.93/28
2023-06-29 15:02:29,529 - INFO: Ip address '10.165.160.93/28' attribute 'assigned_object_id' changed from 'eth0.50 (isc-dhcp2)' to 'vNIC 1 (VM-DHCP2-DS) (isc-dhcp2)'
2023-06-29 15:02:29,529 - DEBUG: Updated IP address object: 10.165.160.93/28
2023-06-29 15:12:22,400 - INFO: Updating NetBox 'IP address' object '10.165.160.93/28' with data: {'assigned_object_type': 'virtualization.vminterface', 'assigned_object_id': 2978}

[smasharov]

"vNIC 1 (VM-DHCP2-DS)" is marked as parent for "eth0.50"

[bb-Ricardo]

Hi, I would need the output of the DEBUG3 data.

[smasharov]

it was DEBUG3

[smasharov]

The problem still exist should I open a new request, or we can re-open this one?

[bb-Ricardo]

Hi,

are you still using this project? Would you be able to provide the the whole log file if run with -l DEBUG3?