locked
how to configure local site High availibility on scom 2012 r2 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Team,

    Please help me with the deployment guide for configuring  high availibilty on scom 2012 r2 for agent failover in case if one server goes down agent get fail over and we still get alerts and monitoring happens.

    Tuesday, November 24, 2015 11:43 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    In SCOM 2012, agents are automatically configured to fail over any available management server when they loose connection to their primary management server. There is no need for any additional configuration. For more information about securing availability of SCOM, take a look at the following articles:

    Distributed Deployment of Operations Manager

    SCOM 2012 R2 HA options with Server 2012 and SQL 2012

    Gleb.

    • Proposed as answer by Elton_Ji Sunday, December 6, 2015 4:39 PM
    • Marked as answer by Elton_Ji Tuesday, December 8, 2015 2:43 PM
    Tuesday, November 24, 2015 12:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    i think you have problem, which needs solving. There are quite a few causes, which can lead to the discovery not working and to this error message. Some of them are the inability to establish a connection with the SQL server, SQL Browser service not running, issues with the credentials of the SDK service, etc.). I have selected some threads, where you can find all the things to check and the possible causes. Please try to read them through and check all the points suggested there. Somewhere on the path you will find the solution, I'm sure. Here the threads:

    The pool managing the instance is not available or the location monitoring object cannot be found - discovery progress

    Discovery Errors on new SCOM 2012R2 install

    discovery wizard: LocationObjectNotFoundException

    Additional tip:

    Check the event logs (Operations Manager) on your management servers and make sure you have no errors, related to the health of your management group.

    Regards,

    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!)

    • Proposed as answer by Elton_Ji Sunday, December 6, 2015 4:39 PM
    • Marked as answer by Elton_Ji Tuesday, December 8, 2015 2:43 PM
    Tuesday, November 24, 2015 2:12 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    In SCOM 2012, agents are automatically configured to fail over any available management server when they loose connection to their primary management server. There is no need for any additional configuration. For more information about securing availability of SCOM, take a look at the following articles:

    Distributed Deployment of Operations Manager

    SCOM 2012 R2 HA options with Server 2012 and SQL 2012

    Gleb.

    • Proposed as answer by Elton_Ji Sunday, December 6, 2015 4:39 PM
    • Marked as answer by Elton_Ji Tuesday, December 8, 2015 2:43 PM
    Tuesday, November 24, 2015 12:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    what Gleb said is true. The failover functionality is built-in in SCOM. There is one consideration though: Like Gleb said the agent will fail over to any available management server. In the most cases people want to control to which management server the failover will happen. This gives certain level of control over the environment. In this case you have two choices:
    1. Active Directory integration
    Please read this article first AD Integration Considerations
    2. PowerShell 
    This is my preferred method for controlling agent fail over.  It is pretty easy and is also not time demanding:

    Set Primary and Failover Management Servers for Agent Managed Computers with Powershell

    Hope this helps. Regards,

    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!)

    Tuesday, November 24, 2015 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

      I am getting error message while discovering servers. 

    Tuesday, November 24, 2015 1:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    i think you have problem, which needs solving. There are quite a few causes, which can lead to the discovery not working and to this error message. Some of them are the inability to establish a connection with the SQL server, SQL Browser service not running, issues with the credentials of the SDK service, etc.). I have selected some threads, where you can find all the things to check and the possible causes. Please try to read them through and check all the points suggested there. Somewhere on the path you will find the solution, I'm sure. Here the threads:

    The pool managing the instance is not available or the location monitoring object cannot be found - discovery progress

    Discovery Errors on new SCOM 2012R2 install

    discovery wizard: LocationObjectNotFoundException

    Additional tip:

    Check the event logs (Operations Manager) on your management servers and make sure you have no errors, related to the health of your management group.

    Regards,

    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!)

    • Proposed as answer by Elton_Ji Sunday, December 6, 2015 4:39 PM
    • Marked as answer by Elton_Ji Tuesday, December 8, 2015 2:43 PM
    Tuesday, November 24, 2015 2:12 PM