Ad Widget

Collapse

Detected VM in the VMWare intergration doesnt choose de correct IP Address

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Lash7653
    Junior Member
    • Apr 2023
    • 10

    #1

    Detected VM in the VMWare intergration doesnt choose de correct IP Address

    Hello everyone,

    To be honnest I don't know in which topic i should talk about this, anyway here is the thing.

    In our project we have 2 ESXi hypervisors with some VMs on them and I have installed the VMWare integration on my Zabbix server. I've configured the hypervisors hosts to detect all the VMs present and it works perfectly.

    However i have 1 problem with 1 VM. It looks like the integration select the very first IP address in the general informations about the VM, but this IP address is a "cluster address" and it is not possible for me to interract with it. The zabbix agent and server cannot communicate with each other neither.
    This is not a network problem, I just want the selected ip address to be X.X.8.22 but the field is grayed out and I can't change it. I know I can create the host on my own, but I wonder if we can trick it? Let me know what you think.

    Personally, I believe it is linked to the order of the network cards directly on the machine, but I wonder if there's a hidden option in the VMWare integration (because i can fix it on windows but this is not why i make this topic).
    Thanks for your time and here are a few screenshots to illustrate what I'm saying, have a nice day!


    ​​​Click image for larger version

Name:	image.png
Views:	685
Size:	57.9 KB
ID:	470363Click image for larger version

Name:	image.png
Views:	608
Size:	36.5 KB
ID:	470364Click image for larger version

Name:	image.png
Views:	611
Size:	64.1 KB
ID:	470365​​​
  • Con1821
    Junior Member
    • Sep 2023
    • 1

    #2
    Hello,
    I am facing the same issue, i tried some modifications on vmware tools but with no results. If you find a solution please let us know
    Thanks

    Comment

    • vijayk
      Senior Member
      • May 2023
      • 305

      #3
      Hi,
      Is your network IPv6 enabled? If not then make it disable in ESXi network. It will solve your issue.​

      Comment

      • cyber
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Dec 2006
        • 4807

        #4
        Originally posted by vijayk
        Hi,
        Is your network IPv6 enabled? If not then make it disable in ESXi network. It will solve your issue.​
        No it does not, as you see first v4 address is taken (...99.2), no v6 address is used...

        But how to solve your issue I do not know...

        Comment

        • vijayk
          Senior Member
          • May 2023
          • 305

          #5
          Yes I know but I'm asking about ESXi network not for Windows host.

          Comment

          • cyber
            Senior Member
            Zabbix Certified SpecialistZabbix Certified Professional
            • Dec 2006
            • 4807

            #6
            Originally posted by vijayk
            Yes I know but I'm asking about ESXi network not for Windows host.
            But it is irrelevant.. As you see from pics, vmware discovery chooses the first ipv4 address (nr 2 in list) in that list to be used, but "should" use second one (nr 4 in list) ... and nothing changes if your ESX is v6 enabled or not... You might lose those 2 ipv6 addresses from list, but it still wont move that needed IP to the top of list... I am pretty sure, that vmware discovery is not pulling that list, only takes first one... And my gut feeling says, it is ignoring v6 addresses anyway ..
            Unfortunately I have no direct experience with those vmware templates...​

            Comment

            • vijayk
              Senior Member
              • May 2023
              • 305

              #7


              Refer this link.

              Comment

              Working...