Wednesday, February 29, 2012

OM12 Dashboards fail after upgrade to RC

You upgraded (or think about to upgrade) your SCOM 2007 R2 environment to SCOM 2012 RC?

Well, if you installed the SCOM databases using the DBCreateWizard tool (for instance because based on SQL 2008 R2) you might run into the issue, where every access to the DWH will fail. Unfortunately the new OM12 dashboards provided in the Network Montoring views (and others as well) will be concerned.

Reports are still available (or at least should be) because accessing the DWH through SRS.

At the moment there is no workaround available but PG is working on that issue.

Update: there is a workaround available now. You can open an issue in the Connect portal and refer to the following issue:

RC- Network Node Dashboard contains no data

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

Read Full Post...

Tuesday, February 28, 2012

Network Devices not discovered?

Today a customer of mine run into an issue when he wanted to discover network devices with SCOM 2012. So he added the devices to the explicit discovery rule and started the discovery process immediately.

After a while he checked for the new devices in the Network Devices view (Administration, Network Management, Network Devices) and was not able to see them in this view.

So he double checked the devices in the discovery rule and started again – same problem.

As it seems, the devices are excluded from the discovery. To check that we had to export the Network Discovery Internal MP (unsealed). After that we opened it with a XML or Text editor and went <ExcludeIP> tag and usually the IPs are listed there. (Be aware that there might be several rules and each has its own exclude- list!)

We simply removed the whole line with the device IP, increment the MP version number and import the MP again.

Now we ran the discovery rule again and after a while the devices occur in the view as mentioned above.

At this time we where not able to reproduce the matter for this behavior but I assume that the devices had been deleted manually in SCOM during the testing phase what will put them into the exclude list (to be sure that they won’t be discovered again by accident).

Note: for easier following the discovery process you can filter the Operations Manager log for source OpsMgr Network Discovery. Event ID 12008 includes a summary and there you can check for the number of discovered devices as well as for the amount of excluded ones.

Update: when using Recursive Discovery (= auto-discover) you can remove those devices in the wizard of the discovery rule as well. Find them in the Exclude Filters page within the discovery rule properties.

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

Read Full Post...

Thursday, February 2, 2012

SCVMM 2012 RC: high CPU load

Today I run in an issue with SCVMM 2012 RC: I experienced high CPU load on my VMM machine. The task manager showed me that the vmmservice.exe consumed all CPU time.

After disabling the CEIP (VMM Console, Settings, General, Customer Experience Improvement Program Settings) the problem was solved.

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

Read Full Post...