Nworks 5.5 : Virtual Center deconnection / VC200 Exception

[Christopher Keyaert]

Dear Team,

Yesterday, I upgraded our Acceptance environment with the version 5.5 of Nworks SCOM MP. And since this upgrade, I have every 5 minutes a disconnection from our Virtual Center servers.

Event Type: Information
Event Source: nworksSource
Event Type: Error
Event Source: nworksSource
Event Category: None
Event ID: 61
Date: 7/15/2010
Time: 9:38:24 AM
User: N/A
Computer: CENMOMCON701
Description:
VC200 Exception connecting to vCenter server bravmvcap001.dir.ucb-group.com, Exception: The operation has timed out. VC events will no longer be captured from this system.

This event generated by the nworks collector
For more information see http://veeam.com/support/events.aspx?EvtID=61


Event Type: Information
Event Source: nworksSource
Event Category: None
Event ID: 62
Date: 7/15/2010
Time: 9:39:25 AM
User: N/A
Computer: CENMOMCON701
Description:
VC201 Connection restored to vCenter server bravmvcap001.dir.ucb-group.com. VC event capture from this system will resume.

This event generated by the nworks collector
For more information see http://veeam.com/support/events.aspx?EvtID=62

Our environment is composed of two virtual center in linked mode, 66 ESX Hosts, around 700 VMs and Two collectors servers (Bi-Processors / 2Gb Ram).
Concerning SCOM, we are using the R2 with the CU2 installed and we don’t have this issue when we were in version 5.0.3 of Nworks.

The disconnections occur on the both Virtual Center.

Thank you
Bests Regards

Christopher KEYAERT

[Vitaliy S.]

Hello Christopher,

I'm not sure there were significant changes between those releases regarding monitoring vCenter connections, so it would be best if you could open a support case with our techical team and provide all the logs for investigation. By the way do you see any events on the vCenters that could be connected to those issues?

Thank you!

[Christopher Keyaert]

Hello,

A ticket is already opened at the support ID#528321.
I'll check the logs of VC and keep you posted.

Thank you
Christopher

[Christopher Keyaert]

Hello

When the event id 61 appears in the event viewer of the collector server, the connection is still mark as active in VC.
And some minutes later, when the event id 62 comes, a new connection appears in VC…I’ve got two connections, and some times more, and a few minutes later, all connections have an idle status, except one which is active.

Thank you

Regards
Christopher

[Vitaliy S.]

Christopher,

Thank you for this info, it would be helpful for our technical support team while they are reviewing all your log files.

Thanks!

[Christopher Keyaert]

Christopher,

Thank you for this info, it would be helpful for our technical support team while they are reviewing all your log files.

Thanks!

Here an example of what I've got

[Christopher Keyaert]

The solution proposed by the support :

The issue has something to do with the VC creating an event filter.
For fixing it, locate files named “vcEvents.xml” on each collector (the default location is C:\Program Files\nworks\VIC\Collector\Resources). Back up these files, because it will be necessary to make changes to them.
Open the files with Notepad,
replace
severity=”verbose”
to
severity=”info”

for all events with “verbose” severity. Restart the collector after that, normally the issue is fixed.

For me, it works Thank you very much to the support !

[Vitaliy S.]

Christopher,

Thank you for updating the thread with the resolution, glad that you're up and running now!