Hello,
We have two collector servers and one management server in different locations and we are using SCOM SP1.
Lately we have been getting loads of VC200 alerts from one of the collector servers. Nothing has been changed in our environment, but from this one collector we are getting email alerts every 10-15 minutes. And they close in a minute or two.
Alert: nworks Collector: VC-API Event Link Connection Status
VC200 Exception connecting to vCenter server <VC Cluster >[443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
We even increased the memory on the collector server, and decreased the esx servers being monitored. But we still get quite a number of these alerts.
Any ideas why we are getting these?
Thanks in advance
-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Sep 30, 2009 2:42 pm
- Full Name: Sameer Dave
- Contact:
-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Sep 30, 2009 2:42 pm
- Full Name: Sameer Dave
- Contact:
Re: VC200 Alerts
And to add to this, for every one "New Alert" we receive, we get two "Closed Alerts" .
New Alert -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: System
Last modified time: 3/31/2010 9:51:14 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER>[443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
Closed Alert 1 -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: System
Last modified time: 3/31/2010 9:52:51 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER> [443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
Closed Alert 2 -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: domain\userid. Last modified time: 3/31/2010 9:53:03 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER>[443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
New Alert -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: System
Last modified time: 3/31/2010 9:51:14 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER>[443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
Closed Alert 1 -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: System
Last modified time: 3/31/2010 9:52:51 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER> [443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
Closed Alert 2 -
Alert: nworks Collector: VC-API Event Link Connection Status
Source: <VC CLUSTER> [443]
Path: xxxxxx
Last modified by: domain\userid. Last modified time: 3/31/2010 9:53:03 PM Alert Description: VC200 Exception connecting to vCenter server <VC CLUSTER>[443], Exception: retrieveEvents: wait task is stalled. Aborting & reconnecting. VC events will no longer be captured from this system.
-
- Expert
- Posts: 181
- Liked: 13 times
- Joined: Jan 13, 2010 6:08 pm
- Full Name: Brian Pavnick
- Contact:
Re: VC200 Alerts
Hello Dave,
I would recommend opening up a support case (e-mail to: support@veeam.com) so this issue can be looked into with a bit more urgency. This is incase you are actually losing data being collected from the VC. In your e-mail please include a description of both your VMware Infrastructure and nworks Infrastructure (example: where is your nworks Collectors and Management Center in relationship to your vCenter, etc.).
Thanks!
-Brian
I would recommend opening up a support case (e-mail to: support@veeam.com) so this issue can be looked into with a bit more urgency. This is incase you are actually losing data being collected from the VC. In your e-mail please include a description of both your VMware Infrastructure and nworks Infrastructure (example: where is your nworks Collectors and Management Center in relationship to your vCenter, etc.).
Thanks!
-Brian
Brian Pavnick | Cireson| Solutions Architect
- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com
- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com
Who is online
Users browsing this forum: No registered users and 1 guest