Host monitoring agent mutual discovery method based on complex IT cloud resource pool network

Abstract

The host monitoring Agent mutual discovery method based on a complex IT cloud resource pool network can improve the ability and efficiency of discovering an Agent management service end through a manual or image installation Agent in a complex IT cloud resource pool network environment, can complete Agent registration to the management service end through the Agent mutual discovery mechanism, can discover a network abnormal Agent and forward the data reporting capability of the network abnormal Agent through a network normal Agent, and is characterized in that the Agent mutual discovery algorithm is included, wherein an Agent in network intercommunication with an Agent management service end can detect and discover an Agent in the same network segment that does not intercommunicate with the Agent management service end, and report the discovery result.

Description

Technical Field

[0001] This invention relates to the field of IT cloud resource pool network management and monitoring technology, and in particular to a method for mutual discovery of host monitoring agents based on complex IT cloud resource pool networks. Background Technology

[0002] With the rapid development of networks, the scale and network structure of IT cloud resource pools are becoming increasingly complex and massive. Monitoring the vast number of hosts within these pools has become fundamental to their construction. Currently, monitoring of physical and cloud hosts within an IT cloud resource pool mainly comprises two parts: one is acquiring sensor data from the physical host via its IPMI (Intelligent Platform Management Interface) interface to monitor parameters such as fans, temperature, and power consumption; the other part involves installing monitoring agent programs within the operating systems of the physical and cloud hosts to obtain data including CPU, memory, processes, applications, and disk usage. This invention primarily focuses on the latter scenario.

[0003] Due to the massive number of hosts in an IT cloud resource pool, especially with the introduction of virtualization technology, installing host monitoring agents on physical and cloud hosts is a huge workload. Therefore, IT cloud resource pool operations and maintenance personnel typically pre-install the host monitoring agent into the operating system image. This way, after the operating system is installed on the physical or cloud host, the host monitoring agent will be automatically installed, reducing installation costs. However, as the scale of IT cloud resource pool devices continues to grow and the network environment becomes increasingly complex, how to discover the agent management server after installation from the operating system image becomes a major challenge. Of course, manually installing Anget on the server may also present similar problems.

[0004] Existing technical solutions mainly fall into the following categories:

[0005] 1. While existing vendors' IT cloud resource pool monitoring systems have implemented agent discovery capabilities, these capabilities are only applicable to simple network structures. Specifically, the network of the server hosting the agent is directly connected to the network of the agent management server. When the networks of the agent's server and the agent management server are disconnected, the agent cannot be discovered. For example... Figure 1 As shown, Agent B cannot be discovered by the Agent Management server.

[0006] 2. Initiate a network probe from the Agent management server, scanning all IP addresses on specified ports within its network segment to discover Agents. For example... Figure 2As shown, the IP addresses involved include 192.168.1.1; 192.168.1.2; 192.168.1.3; 192.168.1.4; ... 192.168.1.12, etc.

[0007] 3. Agent discovery is achieved by configuring a fixed Agent management service address in the Agent configuration packaged into the operating system image. Specific examples include... Figure 3 As shown.

[0008] 4. Access the domain name server via an agent. Configure management server information in the domain name server beforehand to discover the agent. Specific scenarios are as follows: Figure 4 As shown.

[0009] The current installation status of IT cloud resource pool host monitoring agents, in order to meet the requirement of timely detection by the agents, has the following problems and shortcomings:

[0010] 1. Figure 1 In this scenario, Agent A and the Agent Management server are connected via the network, thus Agent A can be discovered; however, Agent B cannot be connected via the network, so Agent B cannot be discovered. Therefore, this solution has certain limitations.

[0011] 2. Figure 2 In this approach, the server needs to repeatedly scan all IP addresses in the network segment one by one. Excessive scanning concurrency and frequency may cause network congestion, while insufficient scanning frequency may result in agents not being detected online in a timely manner. Therefore, this solution has certain limitations.

[0012] 3. Figure 3 In this approach, when the management server's IP address and port number change, the Agent cannot discover the management server. It's necessary to promptly log in to the server hosting each Agent, modify the server's IP address, and repackage the Agent configuration in the operating system image to prevent subsequent Agent installations from failing to register with the management server; therefore, this solution has certain limitations.

[0013] 4. Figure 4 However, this solution cannot be completed if the cloud resource pool does not have a domain name server. In most current cloud resource pool management systems, there is no domain name server; therefore, this solution has certain limitations. Summary of the Invention

[0014] This invention addresses the shortcomings of existing technologies by providing a method for mutual discovery of host monitoring agents based on complex IT cloud resource pool networks. This method can improve the ability and efficiency of agents discovered by manual or image-installed agents in complex IT cloud resource pool network environments. It can complete agent registration with the management server through the mutual discovery mechanism of agents, and can discover abnormal network agents and forward the data reporting capabilities of abnormal network agents through normal network agents.

[0015] The technical solution of the present invention is as follows:

[0016] A host monitoring agent mutual discovery method based on a complex IT cloud resource pool network is characterized by including an agent mutual discovery algorithm, in which an agent that is interconnected with the agent management server network can detect and discover that there are no agents interconnected with the agent management server in the same network segment, and report the discovery result.

[0017] The Agent mutual discovery algorithm includes the following steps:

[0018] Step 1: After the Agent is deployed, the Agent that has been registered with the Agent Management Center obtains its own IP address;

[0019] Step 2: This Agent scans the specified port range of all IP addresses in the network segment where this Agent is located;

[0020] Step 3: Determine if this is the last IP address. If yes, proceed to step 13; otherwise, proceed to step 4.

[0021] Step 4: Does this IP have a registered agent? If so, return to step 2 to scan the next IP; otherwise, proceed to step 5.

[0022] Step 5: Is the port open? If not, record the IP status and return to step 2 to scan the next IP after no agent was found. If yes, proceed to step 6.

[0023] Step 6: Send a command to obtain the Agent registration status;

[0024] Step 7: Determine if the request is responded to. If not, record the IP status as "No Agent Found" and return to Step 2 to scan the next IP. If yes, proceed to Step 8.

[0025] Step 8: Determine the Agent registration status. If it is registered, record the IP status and return to Step 2 to scan the next IP. If it is not registered, proceed to Step 9.

[0026] Step 9: Determine if the registration center address is known. If not, proceed to step 11; if known, proceed to step 10.

[0027] Step 10: Compare the management center address. If they match, record the IP status. If the Agent cannot reach the management center network, return to step 2 to scan the next IP. However, if they do not match, proceed to step 11.

[0028] Step 11, send the management center address;

[0029] Step 12: Obtain the Agent registration result. If the registration is successful, record the IP status. After the Agent detects the success, return to Step 2 to scan the next IP. If the registration fails, record the IP status. After the Agent cannot reach the management center network, return to Step 2 to scan the next IP.

[0030] Step 13: Analyze the scan results;

[0031] Step 14: Report the Agent scan results to the Agent server;

[0032] Step 15, wait for the next scan cycle.

[0033] This includes algorithms that allow the Agent to forward business data to the Agent management server through a proxy Agent, in order to ensure the availability of Agent services.

[0034] The algorithm by which the Agent forwards business data to the Agent management server through the proxy Agent includes the following steps:

[0035] Step A1: The Agent cannot register with the management server;

[0036] Step A2: The Agent requests the forwarding of business data from the Agent Agent.

[0037] Step A3: The agent requests the management server to forward the agent's business data;

[0038] Step A4: The management server returns a result indicating whether it agrees to forward the message based on the configuration. If it disagrees, the process ends; if it agrees, the process proceeds to step A5.

[0039] Step A5: Return an agreement to forward the request to the requesting Agent;

[0040] Step A6: The Agent receives a request to agree to forward the request.

[0041] Step A7: The Agent prepares business data for the Agent agent;

[0042] Step A8: After forwarding the data packets, the agent reports the data to the agent management server.

[0043] Step A9: The Agent management server records business data.

[0044] The technical advantages of this invention are as follows: This invention, based on a host monitoring agent mutual discovery method for complex IT cloud resource pool networks, solves the problem that even in complex network environments where agents cannot reach the management server within a network segment, other agents can still detect and report the discovery results. Compared to other existing technologies, the mutual discovery algorithm significantly improves the ability and efficiency of agent discovery in complex network environments. This invention also solves the problem of agents being unable to report business data when the network connection to the management server is lost, greatly enhancing the availability and ease of use of the entire agent monitoring system. Attached Figure Description

[0045] Figure 1 This is a schematic diagram of the network structure of the Agent management server and the Agent in the existing technology. Figure 1 The Agent (intelligent agent or agent) includes Agent A and Agent B. Agent A can communicate with the Agent Management server network, so Agent A can be discovered; Agent B cannot communicate with the Agent Management server network, so Agent B cannot be discovered.

[0046] Figure 2 This is a schematic diagram of a network probe initiated by an Agent management server on an Agent in existing technology. Figure 2 The Agent management server (192.168.1.1) obtains server A (192.168.1.2), i.e. Agent A, by scanning all IP addresses in this network segment one by one; no device (192.168.1.3); server B (192.168.1.4), i.e. Agent B; and switch A (192.168.1.12).

[0047] Figure 3 This is a diagram illustrating how existing technologies discover agents by configuring a fixed agent management service address within the agent configuration packaged into the operating system image. Figure 3This includes the Agent Management Server (192.168.1.1), Server A: 192.168.1.2 (Agent A Server: 192.168.1.1), and Server B: 192.168.1.4 (Agent B Server: 192.168.1.1).

[0048] Figure 4 This diagram illustrates how existing technologies discover agents by accessing domain name servers through agents and configuring management server information in the domain name servers in advance. Figure 4 This includes the Agent management server (192.168.1.1), the domain name server (domain name / 192.168.1.1), server A: 192.168.1.2 (Agent A server: domain name), and server B: 192.168.1.4 (Agent B server: domain name).

[0049] Figure 5 This is a schematic diagram illustrating the process of implementing the host monitoring agent mutual discovery method based on a complex IT cloud resource pool network according to the present invention. Figure 5The process includes the following steps: Step 1: Obtain the IP address of this Agent; Step 2: Analyze all network segments of this IP address and scan the specified port range one by one; Step 3: Determine if this is the last IP address. If yes, proceed to Step 13; otherwise, proceed to Step 4; Step 4: Check if this IP has a registered Agent. If yes, return to Step 2 to scan the next IP; otherwise, proceed to Step 5; Step 5: Check if the port is open. If no, record the IP status "No Agent Found" and return to Step 2 to scan the next IP; if yes, proceed to Step 6; Step 6: Send a command to obtain the Agent registration status; Step 7: Determine if the request is responded to. If no, record the IP status "No Agent Found" and return to Step 2 to scan the next IP; if yes, proceed to Step 8; Step 8: Determine the Agent registration status. If already registered, record the IP status "Registered Agent". After the agent registers, return to step 2 to scan the next IP. If the agent is not registered, proceed to step 9. Step 9: Determine if the registration center address is known. If not, proceed to step 11; if known, proceed to step 10. Step 10: Compare the management center address. If they match, record the IP status. If the agent cannot reach the management center network, return to step 2 to scan the next IP. If they do not match, proceed to step 11. Step 11: Send the management center address. Step 12: Obtain the agent registration result. If registration is successful, record the IP status. If the agent finds success, return to step 2 to scan the next IP. If registration fails, record the IP status. If the agent cannot reach the management center network, return to step 2 to scan the next IP. Step 13: Calculate the scan results. Step 14: Report the agent scan results to the agent server. Step 15: Wait for the next scan cycle.

[0050] Figure 6 This is a schematic diagram of the algorithm flow in this invention for cases where the detected Agent cannot register with the management center and business data is forwarded by other Agents. Figure 6 The process includes the following steps: Step 1, the Agent fails to register with the management server; Step 2, the Agent requests the forwarding of business data from the proxy Agent; Step 3, the proxy Agent requests the forwarding of Agent's business data from the management server; Step 4, the management server returns a result indicating whether it agrees to the forwarding based on the configuration. If it disagrees, the process ends; if it agrees, it proceeds to Step 5; Step 5, the management server returns an agreement to forward the data to the requesting Agent; Step 6, the Agent receives the agreement to forward the data; Step 7, the Agent prepares the business data for the proxy Agent; Step 8, the proxy Agent forwards the data and reports it to the Agent management server; Step 9, the Agent management server records the business data.

[0051] Figure 7This is a schematic diagram of the network structure between the Agent management server and the Agent in this invention. Figure 7 The Agent (intelligent agent or agent) includes Agent A and Agent B. Agent A and Agent Management Server are interconnected on the network, and Agent A and Agent B are interconnected on the network, but Agent B is not interconnected on the network with Agent Management Server. Detailed Implementation

[0052] The following is in conjunction with the attached diagram ( Figures 5-7 The invention will be described in the following sections and examples.

[0053] Figure 5 This is a schematic diagram illustrating the process of implementing the host monitoring agent mutual discovery method based on a complex IT cloud resource pool network according to the present invention. Figure 6 This is a schematic diagram of the algorithm flow in this invention for cases where the detected Agent cannot register with the management center and business data is forwarded by other Agents. Figure 7 This is a schematic diagram of the network structure between the Agent management server and the Agent in this invention. (Reference) Figures 5 to 7 As shown, a host monitoring agent mutual discovery method based on a complex IT cloud resource pool network is characterized by including an agent mutual discovery algorithm. In the agent mutual discovery algorithm, an agent that is interconnected with the agent management server network can detect and discover that there is no agent interconnected with the agent management server in the same network segment, and report the discovery result.

[0054] The Agent mutual discovery algorithm includes the following steps: Step 1, after Agent deployment is complete, Agents registered with the Agent management center obtain their own IP address; Step 2, each Agent scans the specified port range of all IP addresses in its network segment; Step 3, determines if it is the last IP address; if yes, proceed to Step 13; otherwise, proceed to Step 4; Step 4, checks if this IP has discovered a registered Agent; if yes, returns to Step 2 to scan the next IP; otherwise, proceed to Step 5; Step 5, checks if the port is open; if no, records the IP status as "No Agent Discovered" and returns to Step 2 to scan the next IP; if yes, proceed to Step 6; Step 6, sends a command to obtain Agent registration status; Step 7, determines if the request is responded to; if no, records the IP status as "No Agent Discovered" and returns to Step 2 to scan the next IP; if yes, proceed to Step 8; Step 8... Determine the Agent registration status. If registered, record the IP status and return to step 2 to scan the next IP. If not registered, proceed to step 9. Step 9: Determine if the registration center address is known. If unknown, proceed to step 11; if known, proceed to step 10. Step 10: Compare the management center address. If they match, record the IP status and return to step 2 to scan the next IP. If they do not match, proceed to step 11. Step 11: Send the management center address. Step 12: Obtain the Agent registration result. If registration is successful, record the IP status and return to step 2 to scan the next IP. If registration fails, record the IP status and return to step 2 to scan the next IP. Step 13: Calculate the scan results. Step 14: Report the Agent scan results to the Agent server. Step 15: Wait for the next scan cycle.

[0055] This includes an algorithm for an Agent to forward business data to an Agent management server via a proxy Agent, ensuring the availability of Agent services. The algorithm comprises the following steps: Step A1, the Agent cannot register with the management server; Step A2, the Agent requests the proxy Agent to forward business data; Step A3, the proxy Agent requests the management server to forward the Agent's business data; Step A4, the management server returns a decision on whether to approve the forwarding based on its configuration. If not, the process ends; if approved, proceed to Step A5; Step A5, an approval response is returned to the requesting Agent; Step A6, the Agent receives the approval request; Step A7, the Agent prepares business data for the proxy Agent; Step A8, the proxy Agent forwards the data and reports it to the Agent management server; Step A9, the Agent management server records the business data.

[0056] This invention aims to improve the ability and efficiency of agent management server discovery through manual or image installation in complex IT cloud resource pool network environments. It can complete agent registration with the management server through agent mutual discovery mechanism, and discover abnormal network agents and forward the data reporting capability of abnormal network agents through normal network agents.

[0057] This invention provides a method for mutual discovery of host monitoring agents based on a complex IT cloud resource pool network, implemented as follows: The discovery process is as follows... Figure 5 :

[0058] Once the Agent is deployed, Agents registered with the Agent Management Center will scan the specified port range of all IP addresses in the network segment where the Agent is located.

[0059] When the network is not accessible for an IP address or port range, record this IP as an Agent not found.

[0060] When the IP address is within the valid port range and there is network access on a port, send a command to obtain the Agent registration status.

[0061] If the scanned port does not respond, record this IP as having an undiscovered agent status.

[0062] When the scanned agent returns an Agent registration status of "registered", this IP is recorded as a discovered registered Agent.

[0063] When the scanned Agent returns an Agent registration status of "unregistered" and a known management center address status, the consistency between the returned management center address and the management center address of this Agent is verified.

[0064] When the address returned by the scanned Agent to the management center matches the address registered by this Agent to the management center, record this IP as indicating that the Agent cannot reach the management server via the network.

[0065] When the address of the management center returned by the scanned agent is inconsistent with the address of the registration management center of this agent, send the address of the registration management center of this agent.

[0066] Waiting for the scanned agent to return the registration result.

[0067] When the scanned agent returns a registered status, record this IP as a registered agent.

[0068] When the scanned Agent returns an unregistered status, record this IP as indicating that the Agent's network connection to the management server is unreachable.

[0069] After the Agent has scanned all IP addresses in the IP range, it integrates the scan results and reports them to the Agent management server.

[0070] The agent management server records the agent scan results.

[0071] When the probed agent is unable to register with the registry center due to network or other reasons, the probe agent can act as an intermediary to forward or distribute business data, thereby maximizing the availability of agent services. The process is as follows: Figure 6 :

[0072] When the Agent cannot register to the management center address, the request is forwarded to the agent to report business data.

[0073] The agent requests forwarding permission from the agent management server, which then returns the forwarding permission result based on the forwarding permission policy.

[0074] When the agent receives a response from the management server that data forwarding is not allowed, it notifies the requesting agent that it disagrees with the status, records the status, and does not initiate any more data forwarding requests.

[0075] When the agent receives a data forwarding permission from the management server, it notifies the requesting agent of the status and requests the agent to prepare business data to send to the agent.

[0076] The agent encapsulates the forwarding agent's business data, adds information such as the forwarding agent's IP address, and sends it to the agent management service.

[0077] The features of this invention are as follows:

[0078] An algorithm that analyzes the network segment address where the server is located and probes other agents one by one;

[0079] An algorithm for obtaining the registration status of detected agents;

[0080] An algorithm for the Agent to send the management server address to the discovered Agent;

[0081] An algorithm for identifying the network status of the probed agent to the management server;

[0082] The algorithm for the registered agent of the probe with the agent management server;

[0083] An algorithm that allows the detected Agent to fail to register with the management center and instead forward business data to other Agents.

[0084] The advantages of this invention are as follows:

[0085] The Agent mutual discovery algorithm of this invention, compared with existing technologies, solves the problem that even in complex network environments, where there is a network connection failure between an Agent and the management server within a network segment, other Agents can still detect and report the discovery results. Figure 7 Compared to other existing technologies, the mutual discovery algorithm of agents greatly improves the ability and efficiency of agent discovery in complex network environments. This invention also solves the problem that agent business data cannot be reported when the network between the agent and the management server is not accessible, greatly improving the availability and ease of use of the entire agent monitoring system.

[0086] The agent discovery results detected by the agent play a decisive role in providing a basis for network access in complex network environments and IT cloud environments with a large server management scale.

[0087] This agent mutual discovery algorithm offers significant benefits: In complex network environments, it reduces substantial manpower costs for network status monitoring and troubleshooting; furthermore, the agent mutual forwarding service data algorithm provides service monitoring for specific network situations, such as network security issues or specific business needs where fixed point-to-point networks cannot be established. In-depth analysis and evaluation of the agent mutual discovery results also play a supporting role in the timely and effective identification of potential critical vulnerabilities, mitigating the impact of large-scale failures, and reducing the frequency of such failures.

[0088] Contents not described in detail in this specification are prior art known to those skilled in the art. It is hereby indicated that the above description is intended to help those skilled in the art understand this invention, but does not limit the scope of protection of this invention. Any equivalent substitutions, modifications, improvements, and / or simplifications of the above descriptions that do not depart from the essential content of this invention fall within the scope of protection of this invention.

Claims

1. A method for mutual discovery of host monitoring agents based on complex IT cloud resource pool networks, characterized in that, This includes an Agent mutual discovery algorithm, in which an Agent that is interconnected with the Agent Management Server network can detect and discover that there are no Agents interconnected with the Agent Management Server in the same network segment, and report the discovery result. The Agent mutual discovery algorithm includes the following steps: Step 1: After the Agent is deployed, the Agent that has been registered with the Agent management server obtains its own IP address; Step 2: This Agent scans the specified port range of all IP addresses in the network segment where this Agent is located; Step 3: Determine if this is the last IP address. If yes, proceed to step 13; otherwise, proceed to step 4. Step 4: Does this IP have a registered agent? If so, return to step 2 to scan the next IP; otherwise, proceed to step 5. Step 5: Is the port open? If not, record the IP status and return to step 2 to scan the next IP after no agent was found. If yes, proceed to step 6. Step 6: Send a command to obtain the Agent registration status; Step 7: Determine if the request is responded to. If not, record the IP status as "No Agent Found" and return to Step 2 to scan the next IP. If yes, proceed to Step 8. Step 8: Determine the Agent registration status. If it is registered, record the IP status and return to Step 2 to scan the next IP. If it is not registered, proceed to Step 9. Step 9: Determine if the address of the registration agent management server is known. If not, proceed to step 11; if known, proceed to step 10. Step 10: Compare the Agent management server address. If they match, record the IP status. If the network between Agent and Agent management server is not connected, return to step 2 to scan the next IP. If they do not match, proceed to step 11. Step 11: Send the Agent management server address; Step 12: Obtain the Agent registration result. If the registration is successful, record the IP status. After the Agent detects the success, return to Step 2 to scan the next IP. If the registration fails, record the IP status. After the Agent manages the server, return to Step 2 to scan the next IP. Step 13: Analyze the scan results; Step 14: Report the Agent scan results to the Agent management server; Step 15, wait for the next scan cycle.

2. The method for mutual discovery of host monitoring agents based on a complex IT cloud resource pool network according to claim 1, characterized in that, This includes algorithms that allow the Agent to forward business data to the Agent management server through a proxy Agent, in order to ensure the availability of Agent services.

3. The method for mutual discovery of host monitoring agents based on a complex IT cloud resource pool network according to claim 2, characterized in that, The algorithm by which the Agent forwards business data to the Agent management server through the proxy Agent includes the following steps: Step A1: The Agent cannot register with the Agent management server; Step A2: The Agent requests the forwarding of business data from the Agent Agent. Step A3: The agent requests the forwarding of agent business data from the agent management server; Step A4: The Agent management server returns a result indicating whether it agrees to forwarding based on the configuration. If it disagrees, the process ends; if it agrees, the process proceeds to step A5. Step A5: Return an agreement to forward the request to the requesting Agent; Step A6: The Agent receives a request to agree to forward the request. Step A7: The Agent prepares business data for the proxy Agent; Step A8: After forwarding the data packets, the agent reports the data to the agent management server. Step A9: The Agent management server records business data.

Images