Grayed out items in SCOM?

[felyjos]

Hello,

I am using nWorks for the interface between the vCenter and SCOM. I have some ESX servers and some VMs which are grauyed out in SCOM.
It is not always VMs on a Grayed out ESX which are grayed out themselves.... Some VMs on a Grayed Out ESX are Healthy !!!, Some VMs on a Healthy ESX are Grayed out...

How do you explain this?
Thanks,
Dom

[Alec King]

Hi Dom,

This can happen when the SCOM Configuration Service gets 'out of sync' with our VMware objects.

The solution is to restart the SCOM Configuration Service on the RMS - however, I'd advise scheduling this outside business hours, as the RMS has to rebuild it's in-memory configuration for the whole environment. It does not cause a monitoring outage, however depending on the size of your monitored infrastructure it can put a load on the RMS, so it's best done outside normal business.

Note that improvements in the SCOM Configuration service in SCOM 2012 have resolved this issue

Cheers
Alec

[felyjos]

Hi Alec,

Thanks, I just applied CU5 ... and I am planning for SCOM 2012 but not right away...
I will schedule this restart as still today (6 days later) I have several Cluster Grayed out , All ESX are okay none grayed out, about 200 VMs grayed out...

Thanks,
DOm

[felyjos]

Hi Alec,

No luck...
I restarted the OSMFG Service but still no progress, most of the ESX are grayed out, a lot of VMs even several clusters now.
I then rebooted the servers:
RMS/ MS / nWOrks/ Collectors and still the same issue.

Any way to have some clue? somwhere? a server failing in the path?

Thanks,
DOm

[felyjos]

If you follow Step 7: Run “configure opsmgr agent” task within the Veeam MP Installation Guide, it explains we have a nworks Collector task that automatically configures these registry settings. We bump the values up significantly.

Persistence Version Store Maximum = 12800
State Queue Items = 20480
MaximumQueueSizeKB = 204800

The nworks.VMware.2007R2RequiredOverrides.xml MP that comes along with our MP_Resource_Kit_5_7 has the necessary overrides to allow these settings to be changed in your environment for Veeam Collectors (see Step 8: Apply required Overrides )

Hope this helps!

Thanks Brian

[vBPav]

No, thank you Dom

[felyjos]

Hello,

I have several machines which looks fine in the vCenter but are grayed out in the nWorks Views in SCOm.
How to troubleshoot this issue?
The collectors are okay
Other machines on the same Host, ESX, Collector are fine also.

Thanks,
Dom

[Vitaliy S.]

Hi Dom, is this the same issue as you've had before?

[felyjos]

Hello Sergey,
I will cross check the settings, I hope they have not been changed add the issue seems to be more localized than before as only few servers are gray no ESX, no Cluster, No Hosts,... let me see the settings.

Thanks,
Dom

[sergey.g]

Hi Dom,

I would also recommedn to check Operations Manager log for configuration service errors. If you see issues with delta synchronizations, that's a known issue in SCOM 2012. Microsoft recently publiched the corresponding KB article

http://blogs.technet.com/b/momteam/archive/2013/01/29/support-tip-config-service-deltasynchronization-process-fails-with-timeout-exception.aspx

Thanks.

[felyjos]

Hello,
1. The settings are correct against what is expected,
2. now I will plan the restart of the OMCFG Service
3. I will check the delta sync after the first two steps

Thanks,
Dom

[felyjos]

it is okay after restarting the OMCFG