Collector issue

Unleash the power of System Center for vSphere and Hyper-V | Veeam Task Manager for Hyper-V

Collector issue

Veeam Logoby vrm » Wed Aug 04, 2010 5:42 am

We've installed a extra VIC(5.5.1.493) on a seperate Windows Server 2008 R2

The VI-api-link(in _VIC State) is not healthy(blank) in scom. The VIC Service is running with an AD account thats is local admin on the VIC en VEM server. We've run the nWorks Collector taks "configure opsmgr agent"

The nessecary tcp/udp ports are opened in the Windows Server 2008 R2 Firewall.

The registry of the new VIC contains the correct information of the added vCenter Servers to the new VIC.

When we look in SCOM at the nWorks Collector properties of nWorks Virtual Infrastructure Collector. As VEM server is the new VIC displayed while it's not a VEM server. During the installation of the new VIC we defined the VEM server.

We installed the VIC as described in Veeam MP for VMware version installation guide may 2010.

Someone any idea?
vrm
Influencer
 
Posts: 18
Liked: never
Joined: Thu Feb 18, 2010 7:51 am
Full Name: Vincent

Re: Collector issue

Veeam Logoby Irina Simkina » Fri Aug 06, 2010 1:08 pm

Just to inform:
this issue was resolved by enabling proxying on the ops manager agent on the VEM servers.
Irina Simkina
Enthusiast
 
Posts: 51
Liked: never
Joined: Tue Apr 20, 2010 9:00 am
Full Name: Irina Simkina


Return to Veeam Management Pack for Microsoft System Center



Who is online

Users browsing this forum: No registered users and 2 guests