• About Hyper-V.nu
  • Azure Pack Wiki
  • Azure Stack Wiki
  • WS2012R2 Hotfixes
  • Home
  • Tag: SCOM

Posts tagged SCOM

WAP/SPF UR10 cannot retrieve Usage records from SCOM DataWarehouse database

August 17, 2016 Leave a Comment Hans VredevoortWritten by Hans Vredevoort

[Update: Here is the SPF UR11, that has the fix:
https://support.microsoft.com/en-us/kb/3184834 which updates SPF to 7.2.2386.0 and has been verified to keep Usage operational]

We received a signal from one of our service provider customers in the Netherlands, that they were unable to get Azure Pack to see any usage records.

If you have ever configured Usage, you probably recall that the Azure Pack Usage Collector service runs every 3 minutes for every resource provider to collect usage data from the OperationsManagerDW database. However, the WAP Usage Collector actually depends on Service Provider Foundation (SPF) to connect to the database and run an SQL query against the OperationsManagerDW database.

The WAP usage framework is quite a complex chain of interacting components with several different actors: VMM, SCOM, SPF, WAP and usage consumers such as Cloud Cruiser. It takes a very good understanding of the interaction of these components to troubleshoot WAP Usage and several great blogs have been published to troubleshoot Usage. If you take a look at the Usage section of my Azure Pack Wiki, you’ll quickly find them.

In this case, two WAP specialists at the service provider, had already gone through all the troubleshooting steps and were quite confident their configuration was correct. So that’s where I joined the party, and to tripple check, I again went through an analysis of the Usage configuration. For analysis of a WAP Usage problem, I always use the slide below, which I prepared for a talk to the Houston System Center User Group, several years ago. It helps you understand the order in which you can analyze a WAP Usage problem.

WAP Usage Architecture

So I started checking if VMM agents were able to collect performance data (1), if the integration between VMM and SCOM was operational (2), if performance data was moved from the SCOM Operational Database to the SCOM DataWarehouse database (3), if SPF could connect to SCOM (4), if there was any usage data in the SPF usage table (5), if there was usage data for all existing resource providers (6), if the WAP Usage Collector was querying SPF for usage data every 3 minutes (7), if usage data was transferred from temporary SPF usage table to WAP Usage Database (8), if for instance Cloud Cruiser was able to connect to the Usage Service API and receive json file from WAP (9) and that data properly ended up in the Cloud Cruiser database (10).

All-in-all quite a complex chain, but if you understand this chain, it is obvious where to start.

I quickly concluded that VMM to SCOM was configured correctly and produced the correct results. The problem had to be in SPF and after I checked that the SPF was correctly configured to know how to connect to SCOM, I had to conclude I was dealing with a bug in SPF UR10.

There are two scenario’s that you can run into this issue:

  1. You install a fresh copy of SPF and directly upgrade to UR10 and then configure Usage
  2. You have already installed SPF with UR9, upgrade to UR10 and then configure Usage

I assume that if you already had a working Usage configuration and then upgrade to UR10, you should have no problems.

In this case there was a third possible culprit: SCOM 2016. As part of the WSSC 2016 TAP, the service provider had received approval from Microsoft to upgrade SCOM 2012 R2 to SCOM 2016 TP5. Because WAP Usage had not been configured up to then, this should not cause any problems … but it did. It was easy to blame an unsupported combination of WAP 2013 and SCOM 2016 for breaking Usage … but it didn’t. Read More »

Hans Vredevoort
OperationsManagerDW, private fix, SCOM 2016, Service Provider Foundation, SPF, UR10, UR11, Usage, WAP

Vital Signs for Hyper-V Server (part 2)

May 19, 2011 Leave a Comment Hans VredevoortWritten by Hans Vredevoort

After my previous blog post announcing Vital Signs for Hyper-V server by Savision, I received some additional information (including an opportunity for MVP’s to request an NFR license).

Vital Signs for Hyper-V provides a real-time performance monitoring and troubleshooting capability for Windows Hyper-V Server. The agentless dashboard deploys in minutes and allows System Administrators to immediately see dozens of key performance graphs and configuration for Hyper-V Host (CPU, Memory, Disk, Network) and Virtual Guest.

image

 

Stop Waiting, Start Fixing Dynamic Hyper-V Problems

Stop waiting up to 15 minutes for the next polling cycle or remoting into a machine to see its current performance. Get everything you need to troubleshoot every alert or incident in seconds.

One Dashboard, Over 100 Real-time Metrics

Immediately collect all the foundational troubleshooting information to zero in on the root cause faster to ensure hyper-v fabric is functioning well.

Snapshots, Storage, and V-Systems

Instantly track snapshots paths, storage configuration and storage throughput in real-time. Drill into the Virtual Guest OS to understand its performance characteristics. Troubleshoot the most difficult performance problems faster.

Eliminate Capacity Guesswork

Automatically calibrate and quickly tune performance in your environment to understand virtual guest to hyper-v host usage.

Real-time for Microsoft’s Private Cloud (System Center + Hyper-V)

See SCOM Alerts and SCSM incidents, problems and changes, correlated and placed directly to the real-time performance charts.

If you have any additional questions or would like access to our internet-accessible demo environment, please contact: Dan Merritts @ dan.merritts@savision.com; +1-415-480-0366.

Learn more at: http://www.savision.com/hyper-v

For MVP’s:
Contact Dan Merritts for your MVP NFR License Key: dan.merritts@savision.com; +1-415-480-0366.

Hans Vredevoort, Hyper-v, System Management
Hyper-V, Performance, SCSM, System Center, Troubleshooting, Vital Signs

Powered by



Archives

  • November 2017 (1)
  • November 2016 (2)
  • October 2016 (8)
  • September 2016 (10)
  • August 2016 (3)
  • June 2016 (2)
  • January 2016 (2)
  • October 2015 (1)
  • September 2015 (1)
  • August 2015 (1)
  • July 2015 (2)
  • June 2015 (2)
  • May 2015 (7)
  • April 2015 (5)
  • March 2015 (4)
  • February 2015 (15)
  • January 2015 (3)
  • December 2014 (8)
  • October 2014 (1)
  • September 2014 (3)
  • August 2014 (6)
  • July 2014 (4)
  • June 2014 (9)
  • May 2014 (5)
  • April 2014 (7)
  • March 2014 (8)
  • February 2014 (8)
  • January 2014 (5)
  • December 2013 (9)
  • November 2013 (8)
  • October 2013 (2)
  • September 2013 (4)
  • August 2013 (3)
  • July 2013 (9)
  • June 2013 (9)
  • May 2013 (2)
  • April 2013 (2)
  • March 2013 (12)
  • February 2013 (11)
  • January 2013 (9)
  • December 2012 (5)
  • November 2012 (2)
  • October 2012 (5)
  • September 2012 (8)
  • August 2012 (4)
  • July 2012 (1)
  • June 2012 (5)
  • May 2012 (7)
  • April 2012 (9)
  • March 2012 (4)
  • February 2012 (1)
  • January 2012 (7)
  • December 2011 (3)
  • November 2011 (7)
  • October 2011 (4)
  • September 2011 (11)
  • August 2011 (10)
  • July 2011 (5)
  • June 2011 (15)
  • May 2011 (17)
  • April 2011 (16)
  • March 2011 (15)
  • February 2011 (11)
  • January 2011 (7)
  • December 2010 (2)
  • November 2010 (1)
  • October 2010 (10)
  • September 2010 (9)
  • August 2010 (1)
  • July 2010 (7)
  • June 2010 (10)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (4)
  • February 2010 (6)
  • January 2010 (4)
  • November 2009 (26)
  • August 2009 (1)

Categories

  • Azure Pack Wiki (6)
  • Azure Stack (6)
  • Ben Gelens (20)
  • Containers (1)
  • Darryl van der Peijl (16)
  • Events (43)
  • Hans Vredevoort (315)
  • Hyper-v (233)
  • Ivo Hoefakker (1)
  • Marc van Eijk (52)
  • Mark Scholman (10)
  • Microsoft Ignite (5)
  • Peter Noorderijk (56)
  • Support (4)
  • System Management (91)
  • Tom Klaver (1)
  • Uncategorized (4)
  • Vendor (2)
  • Windows Server 2016 (1)

evolve theme by Theme4Press  •  Powered by WordPress