Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V in a single System Center Operations Manager Console
Post Reply
Christopher Keyaert
Enthusiast
Posts: 30
Liked: never
Joined: Jul 15, 2010 9:33 am
Full Name: Christopher Keyaert
Contact:

nworks Collector: VC-API Performance Link Connection Status

Post by Christopher Keyaert »

Hi Everyone,

So, I've got a little, with one located in Atlanta (our primary site is in Belgium).

When I check my collector everything seems to work fine, this collector monitor 2000 objects, but I receive a lot of alerts like the ones below, around 80 alerts per 24hours.
These alerts auto-close in less than 10 min, but that generates a lot of incidents in our Servers Team queue.

Do you have any advise ? Which threshold may I increase ?

Thank you
Bests Regards
Christopher
VP210 Datacomm connection lost to VC target atlvc001.dir.ucb-group.com. The VMware API error returned was 'The underlying connection was closed: A connection that was expected to be kept alive was closed by the server., Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. at nworksCollector.Collectors.EsxPerfCollector40.performanceDaemon()'. No performance data will be obtained from this source until connection can be restored.


This event generated by the nworks collector
For more information see http://veeam.com/support/events.aspx?EvtID=96
VP210 Datacomm connection lost to VC target atlvc001.dir.ucb-group.com. The VMware API error returned was 'The operation has timed out at nworksCollector.Collectors.EsxPerfCollector40.performanceDaemon()'. No performance data will be obtained from this source until connection can be restored.


This event generated by the nworks collector
For more information see http://veeam.com/support/events.aspx?EvtID=96
Alec King
VP, Product Management
Posts: 1445
Liked: 362 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: nworks Collector: VC-API Performance Link Connection Sta

Post by Alec King »

Hi Christopher,

Well, if you are monitoring over the WAN, you could have latency or delays in the network causing a timeout.

If so, then the timeout setting for all Collectors is in Enterprise Manager.

In our UI, go to Enterprise Manager tab, and select Enterprise Manager node. Click Advanced Settings button and you will find 'Net Timeout'.

Default is 210 seconds, you can try increasing to 300, or 400.

However - I'd always advise opening a support case. Increasing the timeout might not be dealing with some root cause configuration issue.

Let me know how it goes!

Thanks,
Alec
Alec King
Vice President, Product Management
Veeam Software
Christopher Keyaert
Enthusiast
Posts: 30
Liked: never
Joined: Jul 15, 2010 9:33 am
Full Name: Christopher Keyaert
Contact:

Re: nworks Collector: VC-API Performance Link Connection Sta

Post by Christopher Keyaert »

Alec King wrote:Hi Christopher,

Well, if you are monitoring over the WAN, you could have latency or delays in the network causing a timeout.

If so, then the timeout setting for all Collectors is in Enterprise Manager.

In our UI, go to Enterprise Manager tab, and select Enterprise Manager node. Click Advanced Settings button and you will find 'Net Timeout'.

Default is 210 seconds, you can try increasing to 300, or 400.

However - I'd always advise opening a support case. Increasing the timeout might not be dealing with some root cause configuration issue.

Let me know how it goes!

Thanks,
Alec
Thank you Alec, I just checked and the value was set to 120, this value was may be the one by default from a previous release ? I did a upgrade from 5.5 to 5.6.
I reset it to the default value, 210, and I will see now, if i still have the alert.

Thank you
Christopher Keyaert
Enthusiast
Posts: 30
Liked: never
Joined: Jul 15, 2010 9:33 am
Full Name: Christopher Keyaert
Contact:

Re: nworks Collector: VC-API Performance Link Connection Sta

Post by Christopher Keyaert »

I confirm that's working perfectly now. I really don't know why I was not using the default value ;-)

Thank you.
Alec King
VP, Product Management
Posts: 1445
Liked: 362 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: nworks Collector: VC-API Performance Link Connection Sta

Post by Alec King »

excellent news Christopher, thanks! :)
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests