2 Replies Latest reply on May 28, 2013 4:50 AM by MattGagliardi

    Struggling with VIN 2.0 test

    MattGagliardi Enthusiast

      Small 5.1 (vCSA and hosts) test environment running several Server 2008 R2 Standard guests.  I pulled down the OVA for VIN and I am struggling mightily over 3+ days to get it to work.  Most logging looks very solid, only the activediscovery log shows any issue.  I keep getting authorization problems when attemping to discover the guests.

       

      1. VIN is correctly configured in vCenter and is "discovering" objects.

      2. When I manually run single.sh the process appears to authenticate to vCenter correctly but then dies on trying to access the guest.

      3. It looks to me like I've got all ports necessary open.

      4. DNS is resolving forward/backware and I've configured hosts files...pinging back/forth from VIN to guests, vCenter, etc. is all fine.

      5. On installing VIN it sure looks to me like the VMware Tools in each machine were reconfigured (based on the Events tab).

      6. In one log file I see the message "Server certificate chain not trusted but thumbprint matches"...any thoughts on that being the culprit?

       

      This is driving me insane. An example of what I see in the console when I force a manual discover:

       

      Running on VM srv-vvims6401...

      2013-05-22 13:38:05,149 [main] INFO  c.v.v.a.testutils.ActiveProbeRunner - Current host ref count on host-31 is 100.

      2013-05-22 13:38:05,150 [main] INFO  c.v.v.a.testutils.ActiveProbeRunner - Since  ref count is > 0, no need to increase it...

      2013-05-22 13:38:06,985 [main] INFO  c.v.v.a.controller.CacheWrapper - Initializing processes cache

      2013-05-22 13:38:07,077 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | Running...  | OpenSession                             |       |

      2013-05-22 13:38:07,077 [main] INFO  c.v.v.a.s.VmwareVixImplSession - Connecting to host: 172.29.6.50

      2013-05-22 13:38:07,152 [main] INFO  com.vmware.vix.VixUtils - VIX timeout is not enabled

      2013-05-22 13:38:07,359 [main] INFO  c.v.v.a.s.VmwareVixImplSession - Connecting to VM srv-vvims6401 using MOID vm-109

      2013-05-22 13:38:07,474 [main] ERROR c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | VIX error code is: 14010, VIX error message is: There was an error  in communication

      2013-05-22 13:38:07,474 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | Running...  | CloseSession                            |       |

      2013-05-22 13:38:07,475 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | SUCCESS     | CloseSession                            | 1     |

      2013-05-22 13:38:07,475 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | Running...  | AddSupportMatrix                        |       |

      2013-05-22 13:38:07,475 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | IRRELEVANT  | AddSupportMatrix                        | 0     |

      2013-05-22 13:38:07,476 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | Running...  | RemoveServicesWithoutPorts              |       |

      2013-05-22 13:38:07,476 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | SUCCESS     | RemoveServicesWithoutPorts              | 0     |

      2013-05-22 13:38:07,476 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | Running...  | RemoveDuplicateServices                 |       |

      2013-05-22 13:38:07,476 [main] INFO  c.v.v.a.c.DiscoveryTaskRunner - srv-vvims6401 | vm-109 | SUCCESS     | RemoveDuplicateServices                 | 0     |

      2013-05-22 13:38:07,476 [main] INFO  c.v.v.a.testutils.ActiveProbeRunner - Perform un-shuffle on vm with moid: vm-109 with uuid: 422792a4-e6ad-58ee-21e2354daaa3baf7 with vm name: srv-vvims6401

      **************************

      Result status: A communication error occurred while authenticating against the target.

      *** Error: Access failed. An unknown discovery error has occurred.

      2013-05-22 13:38:09,214 [main] INFO  c.v.v.a.testutils.ActiveProbeRunner - Creating a support package file for guest OS srv-vvims6401

      2013-05-22 13:38:09,216 [main] INFO  c.v.v.a.testutils.ActiveProbeRunner - Support package file name for guest OS srv-vvims6401 is: srv-vvims6401_2013-May-22_13 .38.09_package.zip

      Support package was created at /opt/vadm-activecollector/bin/./srv-vvims6401_2013-May-22_13.38.09_package.zip on 127.0.0.1 (vin.techserv.vit)

      Run took 8 seconds.

      Memory consumption delta (before vs. after): 44 MB

      Result serialized size is 967 Bytes

       

       

      ***EDIT***

       

      If it helps at all, here's some more log info:

       

      2013-05-22 13:38:07,472 [main] DEBUG c.v.v.b.k.p.s.OpenSessionProbe - Error when trying to connect to vm: vm-109

      com.vmware.vadm.basic.kbapi.sessions.SessionException: A communication error occurred while authenticating against the target.

      at com.vmware.vadm.activeprobe.sessions.VmwareVixImplSession.open(VmwareVixImplSession.java:193) ~[vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.basic.kb.probes.sessions.OpenSessionProbe.openSession(OpenSessionProbe.java:61) [vadm-kb-2.0.0.jar:na]

      at com.vmware.vadm.basic.kb.probes.sessions.OpenSessionProbe.run(OpenSessionProbe.java:39) [vadm-kb-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.controller.DiscoveryTaskRunner.runNetworkProbes(DiscoveryTaskRunner.java:167) [vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.controller.DiscoveryTaskRunner.runTask(DiscoveryTaskRunner.java:114) [vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.testutils.ActiveProbeRunner.runTask(ActiveProbeRunner.java:391) [vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.testutils.ActiveProbeRunner.initializeAndRunTask(ActiveProbeRunner.java:232) [vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.testutils.ActiveProbeRunner.run(ActiveProbeRunner.java:168) [vadm-active-probe-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.testutils.ActiveProbeRunner.main(ActiveProbeRunner.java:149) [vadm-active-probe-2.0.0.jar:na]

      Caused by: com.vmware.vix.VixException: There was an error in communication

      at com.vmware.vix.VixUtils.checkError(VixUtils.java:241) ~[vadm-vixjava-2.0.0.jar:na]

      at com.vmware.vix.VixUtils.syncWait(VixUtils.java:127) ~[vadm-vixjava-2.0.0.jar:na]

      at com.vmware.vix.VixUtils.waitForJob(VixUtils.java:115) ~[vadm-vixjava-2.0.0.jar:na]

      at com.vmware.vix.VixUtils.getResultHandleFromJob(VixUtils.java:164) ~[vadm-vixjava-2.0.0.jar:na]

      at com.vmware.vix.VixHostHandle.openVm(VixHostHandle.java:244) ~[vadm-vixjava-2.0.0.jar:na]

      at com.vmware.vadm.activeprobe.sessions.VmwareVixImplSession.open(VmwareVixImplSession.java:187) ~[vadm-active-probe-2.0.0.jar:na]

      ... 8 common frames omitted

      Thanks for any help you can give!

        • 1. Re: Struggling with VIN 2.0 test
          Enthusiast

          Hi Matt,

           

          The error you are describing may be related to opened ports - 14010 – VIX_E_HOST_TCP_SOCKET_ERROR; can you please verify that all required ports are opened, as listed in the Admin guide?

           


          Let me know how this works for you,

          Thanks,
          Nir

          • 2. Re: Struggling with VIN 2.0 test
            MattGagliardi Enthusiast

            Everything certainly appeared to be open Nir, I was able to see the proper ports listening on all ends when I ran "netstat -nl" and the rest of my infrastructure is running just fine.  I think the issue *might* have been the Inventory Service (on vCSA) appearing to be bound to the IPv6 address (:::10109) and the VIN appliance not dealing with IPv6.  Regardless, I've abandoned my attempt to try Infrastructure Navigator...I don't have time to struggle with it (I know my way around this stuff and if I've got to ssh into appliances and run shell scripts, etc. to try to figure out why things aren't working then I'm just going to move on).