Hi!
I'm back again with another problem: I have a machine connected to a segment with IP address 176.16.30.50. However, when I add this machine to a group, it sees its IP address as 176.16.10.70. This makes my dfw rules apparently not working, since it doesn't match anymore. I've readded the machine to the group as well. Also, vSphere says it has the proper address. See underlying images for the address vsphere sees and the address nsx-t sees. Other machines are recognized properly.
Any help would be highly appreciated!
Hi, I completely reinstalled the machine and gave it a different IP, and now it seems to work. Thanks for the help tho!
This is because of the segment profile which has the TOFU enabled. Either you can create new segment profile with TOFU disabled and attach to the segment. Or simply go to the vm port from the nsx-t UI and goto realised bindings, select the old ip and select ignore binding. This will remove the old ip from the realised bindings and the group shuld be ok with the new ip.
Hi,
Can you show us the group definition ? and the who what segment the vm is connected to ?
Hi P0wertje,
Here is the group and the segment:
Hi,
Sorry. I mean the complete group definition. i.e.:
The group definition:
Do you have another machine that does have the ip 176.16.10.70 ?
Or did the machine in question had 176.16.10.70 before ?
No there hasn't been any machine with that address. That made it even more confusing.
Can you try creating a new group. with the vm as member and see if the info is correct ?
I was just doing that, created a whole new group with different name and still the wrong IP shows up. I guess I'll try to make a new VM with the same purpose as that machine.
Could you take a look at
Inventory tab, then Virtual Machines. find the VM and click view details ?
Does it show the wrong or correct info ?
And does System->Fabric->Compute managers also shows everything ok?
Hi, I completely reinstalled the machine and gave it a different IP, and now it seems to work. Thanks for the help tho!
Same issue as OP. After manually changing VMs IP address NSX-T inventory doesn't reflect that and still shows old IP, and so firewall rules no longer work. What gives? NSX-T 3.1.3.7 vcenter 7 update 3.
This is because of the segment profile which has the TOFU enabled. Either you can create new segment profile with TOFU disabled and attach to the segment. Or simply go to the vm port from the nsx-t UI and goto realised bindings, select the old ip and select ignore binding. This will remove the old ip from the realised bindings and the group shuld be ok with the new ip.
Yea, never liked soybean curds, and it's not really good for you.
😄TOFU - Trust On First Use
Thanks. I will keep this in mind!