Connectivity issues

[AlexanderDonov]

I have installed the Monitor 3.0.2 free version. When I add the VC or ESX it errors out with (connection problems)(disconnected). I am running VC 2.5 U3 and ESX 3.5 U3
Pls help.
Thanks

[Gostev]

Can you ping the VC or ESX servers you have added from your console using the names you have specified in Veeam Monitor? If yes, check the log files (you can access them through the Veeam Monitor Settings app), look for the VC/ESX server name you have specified - usually error text there is pretty self-explanatory when it comes to connectivity issues.

If you can find anything, you can send all logs to our support email address along with link to this topic, and our support will investigate this.

[kiddx]

Testing out the new 3.02 monitor app. I have 4 esxi standalone servers. they are all brand new installs, however one of my servers will not show up in the program it just keeps saying connection problem.

When I goto the log it tells me a new server has been added with the IP I put in, but doesnt have any more information. I try hostname and ip and get the same issue.

I can open vic, and i can goto the https://site and get the vmware info page. All the other servers came right up so not sure whats different about this one.

Thanks

[Cashman]

Originally posted by kiddx

Testing out the new 3.02 monitor app. I have 4 esxi standalone servers. they are all brand new installs, however one of my servers will not show up in the program it just keeps saying connection problem.

When I goto the log it tells me a new server has been added with the IP I put in, but doesnt have any more information. I try hostname and ip and get the same issue.

I can open vic, and i can goto the https://site and get the vmware info page. All the other servers came right up so not sure whats different about this one.

Thanks

12/26/08 08:57:33 Inform 0x00000BF8 "Collecting thread starts, hostID: #2 (esxi2)."
12/26/08 08:57:33 Inform 0x00000BF8 "Connecting to DB Monitor at amd\veeam. Local host is AMD."
12/26/08 08:57:33 Inform 0x00001708 "Detect Alarm: 0.015
"
12/26/08 08:57:33 Inform 0x00000BF8 "Connecting to host #2 (esxi2)"
12/26/08 08:57:36 Error 0x00000BF8 "Connect failed for host #2 (esxi2)"
12/26/08 08:57:36 Error 0x00000BF8 "Unknown error 0x80131500 (Code: 0x80131500, Source: PerfHelper, Description: Login failed due to a bad username or password.)"
12/26/08 08:57:36 Warning 0x00000BF8 "Collecting thread will exit, hostID: #2 (esxi2)."
12/26/08 08:57:36 Inform 0x00000BF8 "Collecting thread exits, hostID: #2 (esxi2)."
12/26/08 08:57:53 Inform 0x00001708 "Detect Alarm: 0.000
"
12/26/08 08:58:10 Error 0x00000E3C "Connect failed for host #3 (esxi.domain.ru)"
12/26/08 08:58:10 Error 0x00000E3C "Unknown error 0x80131500 (Code: 0x80131500, Source: PerfHelper, Description: Ã

[Gostev]

Cashman, for esxi2 you have bad credentials provided, as the error description says.
For esxi3, I would like to hear a comment from our developers - Alexander, what could be causing this issue?

[Gostev]

kiddx, could you please also post the corresponding piece of the log file here, so our devs could take a look?

[Gostev]

Cashman, according to developers this error is due to connection being closed (not by our application). They have seen this before a few times, and they believe this was due to firewalls. Stanislav, do you have more details on this error from similar support cases, and what exactly were causing those errors?

[AlexanderDonov]

Sorry - I have been out on vacation.
Thanks for the responses.

I do not have any firewalls that could cause this issue.
And I can ping the vc and esx hosts with their names.

Thanks,
vmsf

[ssimakov]

Hello,

Could you please send the logs of the product to support@veeam.com? We have found a possible cause for such a behaviour and would like to check if the fix is applicable to your case.

[VMFAN]

Hi ssimakov ,
i am also having the similare issue can you please share the fix that you have found.

Many Thanks
Sun

[AlexanderDonov]

The time was not in sync on the ESX servers. Once I pointed to an external source, the issues were resolved.

Hope this helps.

[Ben Milligan]

Thanks VMSF - The majority of connectivity problems have been related to time disparities between the Monitor Server and ESX host.

As you had stated, configuring the time (Which is tremendously simple with our Configurator product) on the ESX host will correct this.

[VMFAN]

Thanks Ben and VMSF ,
Issue was with NTP configuration, once configured the NTP source i am able to monitor the ESXi server.

Regards
Sun

[sixth]

Just wanted to post I had this same problem today adding a server, NTP wasn't configured on it. I configured it and it worked fine!