Поделиться через

Understanding SCOM Resource Pools

  • Статья

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    November 22, 2016
    Thank you for the info :) Very useful
  • Anonymous
    November 22, 2016
    Gr8 Article.!!Thx for the post!
  • Anonymous
    November 23, 2016
    Hi,I used the following command to create resource pool in a new SCOM 2016 installation:New-SCOMResourcePool -DisplayName "Displayname of the pool" -Member (Get.SCOMManagementServer | ? {expression}) -Description "Description of the pool"I checked both of them and the $_.UseDefaultObserver value is "False" by default. I did not change it. Maybe this is true for SCOM 2016 only?BTW, this is a good article as we got used to it from Kevin. Thank you for it again.Sandor
    • Anonymous
      November 24, 2016
      Thanks for the catch. Pools created in powershell are apparently different than pools created in the UI. I will update this.
  • Anonymous
    November 23, 2016
    Hi Kevin,When you say "Pool Suicides" (when less then 50% members are available) do you mean that, all agents will loss communication to the resource pool and turns as greyedout agents?Ravi
    • Anonymous
      November 24, 2016
      No - i don't mean that at all. Agent communication has NOTHING to do with resource pools. NOTHING. Resource pools are for workflows. Agents communicate directly to management servers, and have their own mechanism for failover, which has not changed from the SCOM 2007 design. Customers often get confused and think that resource pools handle agent failover. They do not, and there is no relation.When a pool suicides, this means the pool unloads itself from all members, and all workflows that were hosted by the pool are not initialized, and therefore do not run.
      • Anonymous
        February 15, 2017
        Hi Kevin,Do I understand correctly there are no any relationships between “Pool Suicides” and the SCOM alert "The resource pool failed to heartbeat" and it's two different problems with two different causes?
        • Anonymous
          February 15, 2017
          Those are related. A resource pool failing to heartbeat means the pool isnt healthy and stable. This could be due to pool suicides, database connectivity, database blocking, load, bad workflows, all kinds of reasons. If this is common, you start looking at what you have placed on the pool, and what other events are being logged on the management server OpsMgr event leg.
  • Anonymous
    November 24, 2016
    Awesome post. Just a quick note on a scenario where we use the Observer role.We monitor different SNMP enabled devices (getting traps) as Network Devices in SCOM via a resource pool that consists of two gateway servers. Some of these network devices only allows for two trap destinations. As we want the redundancy, but cannot use more than two servers in the pool (for the reason explained above) we use a SCOM agent as observer for the pool.
    • Anonymous
      November 24, 2016
      The comment has been removed
      • Anonymous
        December 19, 2017
        I'd add to this that Unix/Linux Resource Pools are a good candidate for an observer as well. The same failover mechanisms don't apply to Unix/Linux agents as to Windows Agents, and management of certs on gateways is complicated enough without trying to cross-import them across three RP members.
  • Anonymous
    December 05, 2016
    Kevin, hi.As always a great and very helpful post. Thanks to you and Mihai.I created two ps1 that might help to show the config and to set the observers accordingly:https://gallery.technet.microsoft.com/PoSh-Show-Resource-Pool-40d9b18fhttps://gallery.technet.microsoft.com/PoSh-Set-Resource-Pool-aea4e7beBest regards,Patrick
    • Anonymous
      February 01, 2018
      Patrick thats not accurate.If your ressource pool has the default observer, and consists of 2 MS, then it IS higly available.
  • Anonymous
    December 22, 2016
    Kevin, I am having an issue with a customer, which uses a 2 MS + 1 OBS (Failover SQL Cluster DB). Fairly frequently, we are experiencing issues with the resource pools(All management servers resource pool unavailable) , which almost always occurs at night. As read in your post, you would advise to use an uneven amount of management servers. However this customer has 2 datacenters, ideally I would have an even amount of management servers on both sides to cover the load. Would it be advisable to move the DO to another server in this case?
    • Anonymous
      December 22, 2016
      Forgot to mention, the DB is under a significant load at night due to backups and maintenance.
      • Anonymous
        December 22, 2016
        The comment has been removed
        • Anonymous
          January 23, 2017
          Hey Kevin,The management servers reside in the same datacenter, but they do reside in two different physical rooms. So latency is not an issue. The problem I seem to be having is that the pool seems to be under heavy load at night due to backups and SQL maintenance, which I assume causes pool instability.Would it be better to use an agent as an observer in this case, and remove the DO from the SQL server?
          • Anonymous
            January 23, 2017
            If this is happening at night - and you think it is backup related - then it is much more likely that the pool failures are caused by DB connectivity issues, not the DO. If the DO fails - this won't cause pool instability, because the two MS in the pool will work just fine. I'd look at your disk I/O on the SQL server, and for other events in the MS event logs around this time for clues. So to answer you question, no, I would not recommend moving the DO to an agent, and I would recommend leaving the DO in the pool as the database with a size like that. I'd focus on the root cause of pool failure, which is likely SQL connectivity.
          • Anonymous
            January 24, 2017
            Hey Kevin,The system backup of the SQL server seems to be correlating with the pool issues. Have disabled the system backup for now. Thanks for the advice.
  • Anonymous
    January 04, 2017
    The comment has been removed
  • Anonymous
    January 24, 2017
    Hi Kevin,I need your advice about the application polls related to this forum discuss:https://social.technet.microsoft.com/Forums/en-US/a9e94d5d-ec31-4f71-999d-73e3befb796d/sql-server-reporting-services-and-scom-report-server-confusing?forum=operationsmanagerdeploymentBest RegardsBirdal
  • Anonymous
    April 13, 2017
    Hi Kevin,Agents reports to gateways and it doesn't have anything to do with the resource pools.We have a scenario where two resource pools are configured in two data centers and both resource pools have single gateway server.Since both gateways are part of different resource pools so can we do agent failover between these two gateway servers??ThanksAshish
    • Anonymous
      April 13, 2017
      Agent assignment has no relationship to Resource pools, so leaving Resource pool out of the Agent Assignment question would be best.Can you reform the question?
  • Anonymous
    April 21, 2017
    Hi Kevin, How do I reference a resource pool that has being created through powershell? The source of the pool is 'administrator' instead of Management Pack. So how I use it here Target="SC!Microsoft.SystemCenter.AllManagementServersPool" ?
  • Anonymous
    May 07, 2017
    Thanks for the valuable information.
  • Anonymous
    December 19, 2018
    How can you get the name of any currently configured Observer when it is not the default observer via PoSh?