Scom 2012 knowledge sharing-2: Understanding the Management Server

(1) Management Server

The Management Server is mainly used:

Manages the entire management group and communicates with the database;

Provides configuration data for the agent;

All agents submit health data and performance data to the management server, and then the management server writes the data to the database. The agent does not directly deal with databases;

The Management Server is the focus of managing the management group and communicating with the database. When you open the operation console and connect to the Management Group, you will be connected to the management server of the Management Group. Based on the size of the computing environment, the Management Group can contain a single management server or multiple management servers.

(2) resource pool

After two or more management servers are added to the Management Group, the Management Server becomes part of the resource pool and shares the work among the pool members. If a member in the resource pool fails, other members in the resource pool obtain the workload of the member. After a new management server is added, the new management server automatically obtains some work from existing members in the resource pool. All members in the resource pool will manage different sets of remote objects. At any given time, two members in the same pool will not manage the same object at the same time.

In scom2007, the Management Server is divided into two types: Root Manager server and Manager server, which cannot be used for load balancing. Scom2012 introduces the concept of resource pool. Resource Pool allocation reduces resource requirements and supports multiple Server Load balancer instances for high availability and scalability. The scom2007 management group must have a root management server, which can be used for root management clusters. spof exists. Otherwise, problems may occur. Therefore, the concept of resources pool is introduced in 2012. The server is put into the pool and each server is equal to each other to achieve high availability load. Similar to the voting mechanism, at least three servers are required. If there are only two manage servers, therefore, high availability cannot be achieved.

650) This. width = 650; "Title =" 03 "style =" border-top: 0px; border-Right: 0px; Background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; padding-Right: 0px; "Border =" 0 "alt =" 03 "src =" http://img1.51cto.com/attachment/201407/17/639838_1405595797k0LP.png "Height =" 410 "/>

There are two types of resource pool membership: automatic and manual. There are three built-in resource pools:

1. All Management Servers resource pools)

2. Ad assignment resource pool)

3. Notification resource pool)

Custom resources pool can only be used to manage Linux/Unix proxies, but cannot manage windows proxies

By default, resources pool does not need to be manually specified for Windows proxy. The management server automatically selects the appropriate default resource pool.

If ad integration is not available, you can use the default all Management Servers resources pool, which is responsible

If it is integrated with AD, you can use the default ad assignment resources pool (the integrated function is mainly used to switch the agent to a good management server through the workflow if the server breaks down)

Send notifications using the notification resource pool (generally, this resource pool is automatically switched to a manual one to determine which administrators will send notifications)

The membership can be changed from automatic to manual, but not from manual to automatic

(3) Health Service

The agent on the client will pull all the MP packages that have been imported to scom to the local machine. Then, Health Service uses a series of scripts to determine which MP packages are suitable for local installation. The appropriate ones are local installation, if it is not suitable, ignore it.

Health service: executes monitoring rules. This service is available on both servers and clients.

(4) Configuration Service

Configuration service runs on all management servers and is responsible for the configuration information of all management servers. scom2007 exists on IMS, and scom2012 cancels IMS and stores it in a table in the database, all Management Servers take configurations from the table to ensure that the configurations can be synchronized.

2007 the platform sometimes cannot Update client configuration information in time because of the RMS problem.

2012 the Configuration Service ensures that all configurations of a management group are synchronized. Distribute new configurations. Calculate the members of the dynamic pool.

Multiple scom 2012 servers have multiple configuration services. Therefore, the concept of virtual data storage is introduced. There are several tables in the scom database to ensure configuration uniqueness.

Configuration example: override is a parameter. Ms may have many machines, but the configuration may be generated by one machine. Because it has been pooled, multiple Ms notifications are synchronized and then distributed to the client.

(5) Data Access Service

It is very important to deal with database services. After scom2012 is pooled, every MS will establish a connection with SQL.

On the 2007 platform, RMS is used for operation control. On the 2012 platform, improvement can be made to any management server.

The DAS is used to control access to the database. It can be used through the console, powershell, connector, and custom APIs. Any management server can retain an SDK connection.

650) This. width = 650; "Title =" 04 "style =" border-top: 0px; border-Right: 0px; Background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; padding-Right: 0px; "Border =" 0 "alt =" 04 "src =" http://img1.51cto.com/attachment/201407/17/639838_1405595812HB5l.png "Height =" 280 "/>

(6) Simulator role

Simulator role: the role can be moved by running the powershell command. If one MS is broken, it can be moved to another Ms. If the package is not managed, it can be removed if it is not used.

This role will be gradually eliminated in future management packages.

By default, the first management server is the RMS emulator.

For example, the MP of Exchange 2007 server and Exchange Server 2010 depends on RMS. Because scom did not have an RMS server in 2012, one management server assigned the RMS simulator role to provide compatibility with these MPs servers.

(7) Communication Mechanism

Data Flow: The agent does not communicate with SQL and only communicates with Ms. If no priority is specified for multiple Ms instances, the agent randomly points to one.

Data warehouse stores historical data; workflow must be performed on rms;

========================================================== ==================================

This article is from the blog "Zeng luxin's technical column" and will not be reposted!