Server integrated monitoring system

The server integrated monitoring system addresses the challenges of managing complex IT environments by using the Redfish API for standardized management of multiple servers, predicting failures, and providing proactive alerts, thereby enhancing operational efficiency and reducing costs.

JP2024156643AInactive Publication Date: 2024-11-06GENIAI CO LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2024070586
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-04-24
Filing Date
2024-04-24
Publication Date
2024-11-06
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Complex IT environments with large-capacity servers face frequent failures due to various factors, leading to operational inefficiencies, high costs, and difficulties in managing and responding to server failures, especially in small companies without specialized staff, resulting in significant downtime and losses.

Method used

A server integrated monitoring system that monitors multiple servers, collects and analyzes hardware and software data, predicts failures, and provides proactive alerts and solutions, using the Redfish API for standardized management of x86 servers, including Dell, HP, and Lenovo servers, and supports multi-vendor environments.

Benefits of technology

The system enhances operational efficiency, reduces operational costs, strengthens security, and minimizes server failures by preemptively predicting and addressing issues, enabling efficient management of multiple servers with reduced downtime and improved response times.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156643000001_ABST
    Figure 2024156643000001_ABST
Patent Text Reader

Abstract

To prevent faults that may occur in servers in advance to reduce damages due to the server faults.SOLUTION: A server integrated monitoring system that monitors two or more servers to be monitored includes a management server which monitors and manages a status of each server and provides various server monitoring information including management service statistical data and a management service report related to the monitored and managed status of the servers, to an administrator terminal used by an administrator and a customer terminal that requests the server to be managed.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technique for monitoring a server, and more particularly to a technique for integrated monitoring of a plurality of servers. [Background technology]

[0002] Recently, IT (Information Technology) environments, including servers, storage, and networks, have become more complex, resulting in a lack of available work time. As computer systems become larger and faster, computer problems due to system errors and viruses are becoming more frequent. In particular, in the case of large-capacity servers, problems can frequently occur due to various factors such as the operation of various application programs and the storage, reading, and transfer of data. Therefore, each company assigns separate server administrators to manage these servers and handle problems when they occur.

[0003] However, server management requires specialized skills, and hiring such specialized staff is quite costly. Therefore, especially in small companies, the reality is that rather than hiring specialized engineers to be server administrators, they select suitable people from among the existing staff within the company and assign them as server administrators. In such cases, server management is difficult to carry out smoothly, and it is almost impossible to deal smoothly with server failures.

[0004] In addition, even if a server administrator with specialized skills is employed for server management, if the server administrator is located remotely from the server due to a business trip or other reason, it is difficult to promptly notify the administrator of the server's status when a server failure occurs, making it difficult to deal with the server failure smoothly. Even if the server administrator is notified of the server failure, it is difficult for him or her to respond immediately because he or she is located remotely, which can ultimately result in huge losses such as the server going down.

[0005] In the past, in a server integrated management system that integratedly manages multiple servers, if a failure occurs in a server, the failure is detected and the failure is recovered after the fact. However, such a conventional method of recovering from a failure after the fact has a problem in that the operation of the server is interrupted during the recovery period of the failed server, resulting in losses due to the interruption of use of the server, and the damage is large depending on the manpower and cost required for recovery. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Korean Patent Publication No. 10-2015-0124642 Summary of the Invention [Problem to be solved by the invention]

[0007] The present invention has been devised to solve the above problems, and aims to provide a server integrated monitoring system that can improve operational efficiency, reduce operational costs, and strengthen security by systematizing IT resources and standardizing operations.

[0008] The objects of the present invention are not limited to the above objects, and other objects not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0009] To achieve this objective, the present invention relates to a server integrated monitoring system that monitors two or more managed servers, and includes a database that stores data related to the managed servers, and a management server that collects hardware-related data and software-related data from the managed servers, monitors and manages the current status of each managed server, and provides various server monitoring information including related management service statistical data and management service reports to an administrator terminal used by an administrator and to a customer terminal that has requested the managed servers.

[0010] The management server can monitor the managed servers according to a preset schedule for monitoring the managed servers, and provide monitoring result information to the administrator terminal and the client terminal.

[0011] The management server can provide a schedule setting function that can set a server monitoring period and set data collection values ​​to be collected from the managed servers.

[0012] The management server can use the Redfish API to collect information about the x86 servers in operation, including detailed hardware specifications, OS (Operating system) information, firmware information, and driver information for each managed server, and perform standardized management of x86 servers. Effect of the Invention

[0013] According to the present invention, by monitoring a large number of managed servers, it is possible to preemptively predict server failures, provide warnings, and provide solutions, thereby preventing possible server failures and reducing damage caused by server failures.

[0014] According to the present invention, by systematizing IT resources and standardizing operations, it is possible to improve operational efficiency, reduce operational costs, and strengthen security.

[0015] According to the present invention, it is possible to more conveniently and efficiently manage a large number of servers.

[0016] According to the present invention, by analyzing failure patterns for a client who has requested server management, preemptively associating failures in advance, and providing server management functions, it is possible to process and transmit data suited to the client's needs. [Brief description of the drawings]

[0017] [Figure 1] 1 is a diagram conceptually illustrating an overall configuration of a server integrated monitoring system according to an embodiment of the present invention. [Diagram 2] 2 is a diagram conceptually illustrating an operation process of a server integrated monitoring system according to an embodiment of the present invention. [Diagram 3] 4 is a flowchart illustrating a method for implementing functions in a server integrated monitoring system according to an embodiment of the present invention. [Figure 4] 11 is a screen example showing functions provided by a server integrated monitoring system according to an embodiment of the present invention. [Diagram 5] 11 is a screen example showing functions provided by a server integrated monitoring system according to an embodiment of the present invention. [Figure 6] 11 is a screen example showing functions provided by a server integrated monitoring system according to an embodiment of the present invention. [Figure 7] 11 is a screen example showing functions provided by a server integrated monitoring system according to an embodiment of the present invention. [Figure 8] 11 is a screen example showing functions provided by a server integrated monitoring system according to an embodiment of the present invention. [Figure 9] 1 is a diagram illustrating an example of the configuration of a server integrated monitoring system according to an embodiment of the present invention. [Figure 10]FIG. 1 is an exemplary diagram illustrating a server monitoring function using Redfish events in a server integrated monitoring system according to an embodiment of the present invention. [Figure 11] FIG. 11 is an exemplary diagram illustrating a server configuration job automation function using Redfish in a server integrated monitoring system according to an embodiment of the present invention. [Figure 12] FIG. 1 is an exemplary diagram illustrating a server configuration automation function using Redfish in a server integrated monitoring system according to an embodiment of the present invention. [Figure 13] 1 is a flowchart illustrating a method for managing servers by supporting multiple vendors in a server integrated monitoring system according to an embodiment of the present invention. [Figure 14] 4 is a flowchart illustrating a method for preventing failures in advance by analyzing failure logs and patterns in a server integrated monitoring system according to an embodiment of the present invention. [Figure 15] 1 illustrates an operational model for supporting multi-vendors using Redfish API in a server integrated monitoring system according to an embodiment of the present invention. [Figure 16] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 17] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 18] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 19] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 20] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 21] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 22]1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Diagram 23] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 24] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Diagram 25] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 26] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 27] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 28] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Figure 29] 1 is a diagram showing an example of a screen of a server integrated monitoring system according to an embodiment of the present invention; [Diagram 30] FIG. 2 is a classification diagram of system equipment according to an embodiment of the present invention. [Diagram 31] 1 is a chart illustrating hardware symptoms and their causes according to an embodiment of the present invention. [Diagram 32] 1 is a chart illustrating hardware symptoms and their causes according to an embodiment of the present invention. [Diagram 33] 4 is a flowchart illustrating a method for proactively responding to a fault in a server integrated monitoring system according to an embodiment of the present invention. [Diagram 34] 4 is a flowchart illustrating a method for proactively responding to a fault in a server integrated monitoring system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] While the invention is susceptible to various modifications and embodiments, specific embodiments have been shown in the drawings and will be described in detail.

[0019] It should be understood, however, that this is not intended to limit the invention to the particular embodiments, but to cover all modifications, equivalents and alternatives falling within the spirit and scope of the invention.

[0020] The terms used in this application are merely used to describe particular embodiments and are not intended to limit the present invention.

[0021] The singular expression includes the plural expression unless otherwise clearly indicated in the context.

[0022] In this application, terms such as "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described herein, and it is to be understood that one or more other features does not preclude the presence or possibility of additional numbers, steps, operations, components, parts, or combinations thereof.

[0023] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

[0024] Terms such as those commonly used and predefined should be construed to have a meaning consistent with the contextual meaning of the relevant art, and should not be construed as having an ideal or overly formal meaning unless expressly defined in this application.

[0025] In addition, in the description with reference to the accompanying drawings, the same components are given the same reference numerals and the duplicated description thereof will be omitted.

[0026] In describing the present invention, if it is determined that a detailed description of related prior art may unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

[0027] The present invention relates to a server integrated monitoring system for monitoring two or more managed servers, and includes a database for storing data related to the managed servers, and a management server for collecting hardware-related data and software-related data from the managed servers, monitoring and managing the current status of each managed server, and providing various server monitoring information including related management service statistical data and management service reports to an administrator terminal used by an administrator and to a customer terminal that has requested the managed servers.

[0028] The management server can monitor the managed servers according to a preset schedule for monitoring the managed servers, and provide monitoring result information to the administrator terminal and the client terminal.

[0029] The management server can provide a schedule setting function that can set a server monitoring period and set data collection values ​​to be collected from the managed servers.

[0030] The management server can use the Redfish API to collect information about the x86 servers in operation, including detailed hardware specifications, OS (Operating system) information, firmware information, and driver information for each managed server, and can perform standardized management of the x86 servers.

[0031] FIG. 1 is a diagram conceptually illustrating an overall configuration of a server integrated monitoring system according to an embodiment of the present invention, and FIG. 2 is a diagram conceptually illustrating an operation process of the server integrated monitoring system according to an embodiment of the present invention.

[0032] 1 and 2, the server integrated monitoring system of the present invention includes a management server 110, a database 112, an administrator terminal 120, and a customer terminal .

[0033] The manager terminal 120 is a terminal used by a manager who manages the server integrated monitoring system.

[0034] The client terminal 130 is a terminal used by each client who has requested the managed servers 10, 20, 30, and 40.

[0035] In one embodiment of the present invention, the administrator terminal 120 and the customer terminal 130 can be realized by various terminals capable of wired and wireless communication, such as a desktop computer, a laptop computer, a tablet PC, a mobile phone, a mobile phone, or a smartphone.

[0036] In one embodiment of the present invention, the user terminal is a concept that includes the administrator terminal 120 and the customer terminal 130.

[0037] The database 112 stores data relating to the managed servers 10 , 20 , 30 , 40 .

[0038] The management server 110 collects data from the managed servers 10, 20, 30, 40, and keeps track of the current status of each managed server, including related management service statistics and management service reports.

[0039] It provides various server management information to the administrator terminal 120 and the customer terminal 130.

[0040] The management server 110 can collect and store multi-vendor hardware information from multiple managed servers, and provide the stored information to the administrator terminal 120 and the customer terminal 130 so that the information can be referenced and used.

[0041] The management server 110 can collect and store multi-vendor hardware inventory information from multiple registered managed servers.

[0042] The management server 110 can facilitate firmware updates for all managed servers upon firmware update events, including emergency firmware updates.

[0043] The management server 110 analyzes logs and patterns when a failure occurs in any of the equipment of the managed servers, stores the analyzed data, and when the failure is resolved, classifies equipment similar to the failed equipment and performs pre-failure response processing on the classified similar equipment.

[0044] The management server 110 can use the Redfish API to collect information about the x86 servers in operation, including detailed hardware specifications, OS (Operating system) information, firmware information, and driver information of each managed server, and can perform standardized management of the x86 servers.

[0045] The management server 110 provides a preventive analysis function that analyzes failure patterns of the managed servers 10, 20, 30, and 40 and prevents similar failures from occurring. Through the preventive analysis function, the management server 110 can preemptively send a predicted failure occurrence message to a client terminal that has requested the managed server, warning that a failure may occur due to a predetermined event that occurs in the managed server (10, 20, 30, and 40).

[0046] The management server 110 can provide a history management function for managing the installation, failure, and technical support history of the managed servers 10 , 20 , 30 , and 40 .

[0047] The management server 110 can provide a delivery management function for managing the delivery history of the managed servers 10 , 20 , 30 , and 40 .

[0048] When an equipment-related event occurs in a managed server, the management server 110 classifies the dangerous equipment according to predetermined classification criteria, sends a warning message regarding the dangerous equipment to the administrator terminal 120 and the corresponding customer terminal, and can take pre-emptive troubleshooting measures for the dangerous equipment.

[0049] When an equipment-related event occurs in a managed server, the management server 110 can grasp the fault symptoms of the equipment, analyze the cause according to the fault code corresponding to the fault symptoms, send a report including a fault response plan to the administrator terminal 120 and the corresponding customer terminal, and execute fault response measures for the equipment.

[0050] In the present invention, the management server 110 can provide a data delivery service function for processing and delivering data related to management of the managed servers upon request of the client terminal 130 .

[0051] In addition, the management server 110 can analyze critical failures of the managed servers and propagate the same cases to prevent server failures in advance, and can provide failure statistics of each server to the administrator terminal 120 and the customer terminal 130 on a quarterly basis.

[0052] In the present invention, the management server can manage the history of delivered server-related equipment, provide installation / failure / technical support history management services, and manage problems by part.

[0053] The present invention relates to a server integrated monitoring system that manages a plurality of managed servers 10, 20, 30, 40 at the request of a customer.

[0054] In one embodiment of the present invention, the managed server, which is the server to be managed, may be a variety of servers, such as a Dell® server 10, an HP® server 20, a Lenovo® server 30, or an X86 server 40.

[0055] The managed servers 10, 20, 30, 40 and the management server 110 can communicate with each other via various wired or wireless communication methods, for example, HTTP communication or a POST transfer method in JSON format.

[0056] Additionally, the managed servers 10, 20, 30, 40 can automatically execute scripts according to a defined schedule across various x86 servers in a large scale computing environment.

[0057] The administrator connects to the management server 110 via the administrator terminal 120, executes a batch program according to a schedule defined by the management server 110, and manages the change history by comparing it with existing data.

[0058] The management server 110 automatically collects hardware and software information of the managed servers 10, 20, 30, 40, and based on this, grasps the current state of each server and provides management services according to the request status of each server.

[0059] FIG. 2 is a conceptual diagram illustrating the operational process of a server integrated monitoring system according to one embodiment of the present invention. In FIG. 2, the managed server is a Dell (registered trademark) server 10 to which the iDRAC9 version is applied, and an example of a platform using the Redfish API (Application Programming Interface) is shown.

[0060] Referring to FIG. 2, a Get Module is executed on a user terminal using Flask to collect iDRAC9 formatted data and unformatted data from a Dell (registered trademark) server 10 using Redfish API.

[0061] Then, the collected data is classified and data pre-processing is performed.

[0062] The pre-processed data is then stored in the database 112, and learning is performed on the data stacked in the database through an AI learning data model to reclassify the data and generate data rows.

[0063] Next, the user terminal calls up the page using Flask, and the data analysis module searches the database 112, performs the analysis, performs data visualization, and transmits this to a Flask Response User Web page.

[0064] FIG. 3 is a flowchart showing a method for implementing functions in a server integrated monitoring system according to an embodiment of the present invention.

[0065] The embodiment in Figure 3 is an embodiment using the Redfish API.

[0066] FIG. 3 is a flowchart illustrating a method for implementing a server monitoring function in a server integrated monitoring system according to an embodiment of the present invention.

[0067] Referring to Fig. 3, the management server 110 provides a schedule setting function for implementing a server monitoring function to the terminal (S1010). In the schedule setting function, related items such as setting a server monitoring period and collection value setting for setting data values ​​to be collected from the server can be set (S1020, S1030). When the schedule setting is completed (S1040), the server monitoring function is executed according to the set schedule (S1050, S1060). Then, the management server 110 provides the terminal with information on the results of inspecting the server according to the server monitoring function (S1070). Figs. 4 to 8 are example screens showing functions provided by a server integrated monitoring system according to an embodiment of the present invention.

[0068] Figure 4 is an example of the main dashboard screen.

[0069] Referring to FIG. 4, the management server 110 provides a main dashboard screen that displays important information on a single screen based on resource information collected from the managed servers 10, 20, 30, and 40 and the number of registered performance items.

[0070] The present invention supports deep analysis and continuous monitoring of specific information, and provides various information such as what equipment the user frequently uses, what task is taking up a lot of time, and whether stabilized firmware is applied to each component of the managed server through a dashboard screen, allowing the user to check important managed server information at a glance through the dashboard screen.

[0071] The example screen in Figure 4 displays information on the operation status of servers, storage, and networks, and provides pie charts of the total number of servers in operation and the number by server manufacturer.

[0072] It also provides monthly performance status information, providing bar graphs of work, change and defect performance numbers.

[0073] When displaying information on the stabilization firmware application status, a chart is provided regarding the stabilization application rate, which is the ratio of devices with stabilization firmware applied and devices without stabilization firmware applied, such as BIOS, R / C, NIC, iDRAC, and HBA.

[0074] Figure 5 is an example of a screen displaying the resource management function.

[0075] In the present invention, the management server 110 provides a resource management function that automatically collects and organizes a list of new equipment installations and changes to servers and the like, and provides reliable data in real time.

[0076] The management server 110 can collect information registered from user terminals in the resource management function, or automatically collect resource information of servers in the data center according to a predefined period via a standardized Redfish RESTful API.

[0077] In the example screen of Figure 5, equipment information is displayed, and equipment information such as servers, storage, networks, SAN, backup equipment, and disposal equipment can be registered or inquired.

[0078] In addition, to provide related statistical information, it provides pie charts for equipment status such as operation, idle, pre-service, and disposal, as well as various statistical graphs such as the current status of operation equipment by year and vendor, a list of recently registered equipment, and additional customization methods.

[0079] Figure 6 is an example of a screen displaying the performance management function.

[0080] In the present invention, the management server 110 provides a performance management function for managing scheduled tasks, items changed by the tasks, and the like, as well as a history of failures and improvement results.

[0081] As a result, in the present invention, when the cause of a failure is clear, records can be managed to prevent the same failure from occurring again, a person in charge can be assigned to the matters requiring improvement, and the results of the improvement can be confirmed.

[0082] In addition, it can provide various performance status statistics according to the state such as year, month, data center location, pre-operation service, idle, etc.

[0083] The example screen in Figure 6 displays job history including online and offline job history management, the fault history of the fault processing history manager, the change history of the system change history manager, etc., as well as backup schedule management and various statistical graphs relating to business performance.

[0084] Figure 7 is an example of a screen displaying the automation management function.

[0085] In the present invention, the management server 110 provides an automation management function that provides, through a standardized Redfish RESTful API, a synchronization period (Daily / Weekly / Monthly) setting, an automation collection value (All / Chassis / MGMT / CPU / NIC / HBA / DISK / GPU, etc.) setting, a group-by-group execution period management for automated collection such as schedule information registration, and notification information regarding equipment requiring inspection through daily automatic inspection.

[0086] In the example screen in Figure 7, a menu is displayed for setting the collection synchronization cycle, customizing the automated collection values, and automation settings for registering collection schedule information, as well as a menu for daily inspections that allows automatic classification of equipment that requires daily inspections and checking equipment with MGMT (Management Repository) connection errors.

[0087] As shown in FIG. 7, the management server 110 can display the equipment status in different colors in the daily inspection menu.

[0088] In other words, if there is no abnormality in the equipment, it will be displayed as symbol 1 (green circle), if inspection by an administrator is required (inspection required) it will be displayed as symbol 2 (red circle), if inspection by the naked eye is required (visual inspection required) it will be displayed as symbol 3 (yellow circle), and if it is not possible to connect to MGMT (MGMT inaccessible) it will be displayed as symbol 4 (gray circle).

[0089] Figure 8 is an example of a screen displaying the automation management function.

[0090] In the present invention, the management server 110 provides a configuration diagram management function, which is a configuration diagram view function required for efficiently operating and managing an IT infrastructure environment such as servers, storage, networks, and SANs, which are IT infrastructure components.

[0091] That is, the management server 110 also provides a management function that automatically displays a view of the configuration of resources selected from a user terminal, such as a server, storage, network, SAN, etc. This allows for faster decision-making when a performance problem or failure occurs.

[0092] Referring to FIG. 8, the configuration diagram management function provides a view function of the configuration diagram of the equipment (server, storage, network, SAN, etc.) selected from the user terminal, and provides a search and selection function based on hostname and equipment model, allowing the infrastructure configuration to be checked in real time when performance problems and failures occur.

[0093] FIG. 9 is a diagram showing an example of the configuration of a server integrated monitoring system according to an embodiment of the present invention.

[0094] In the configuration example of FIG. 9, the Redfish API is used, the managed server is connected via the MGMT network, and the administrator terminal 120 can connect to the managed server using a Web connection method.

[0095] In one embodiment of the present invention, a server integration monitoring system uses a Redfish API-based platform to collect hardware system inventory information of multi-vendor x86 servers in real time and distribute BIOS settings, firmware, and the like.

[0096] This will improve maintenance efficiency and reduce operating costs.

[0097] In addition, similar equipment can be identified based on the collected logs, enabling the same faults to be prevented in advance.

[0098] FIG. 1 is an exemplary diagram illustrating a server monitoring function using Redfish events in a server integrated monitoring system according to an embodiment of the present invention.

[0099] Referring to FIG. 10, the management server 110 in the present invention can provide a server monitoring function via Redfish events.

[0100] Redfish events are based on HTTPS, transferring event information from the server to Redfish clients. When an alarm occurs in management, it is sent via HTTP POST and can be received via HTTP GET.

[0101] At this time, you can select the servers to be targeted for important notification email push, status monitoring, and daily inspections, and load the necessary data.

[0102] FIG. 11 is an exemplary diagram illustrating a server configuration job automation function based on Redfish in a server integrated monitoring system according to an embodiment of the present invention.

[0103] Referring to FIG. 11, the management server 110 in the present invention can provide a function for automating server configuration tasks via Redfish.

[0104] This function allows you to locally distribute and update BIOS setting changes, Secure Boot, iDRAC Configuration, etc. It also provides management and updates of firmware inventory for managed servers, and shortens deployment time by applying BIOS standard settings and management standard settings collectively during server deployment, and prevents input of incorrect settings with the automated management function. It also provides a function to update firmware information installed on managed servers according to a preset cycle, automatically select target equipment when emergency firmware is distributed, and push emails to administrators.

[0105] FIG. 1 is an exemplary diagram illustrating a server configuration automation function using Redfish in a server integrated monitoring system according to an embodiment of the present invention.

[0106] In the present invention, the management server 110 can provide server configuration automation functionality via Redfish.

[0107] The unique setting values ​​of a server are stored as metadata in a Server Configuration Profile (SCP), which can be configured in this invention using the Redfish API. The SCP can be exported, previewed, and imported, and can be used to apply configuration information to a newly constructed server using the server configuration automation function of this invention.

[0108] SCP can be shared via HTTPS, NFS, CIFS, and other methods, and is implemented in XML and JSON formats. Using the SSH protocol when configuring the server allows for stable and consistent distribution of many applications.

[0109] In the present invention, unique setting values ​​for physical server distribution are stored as metadata in XML or JSON format on a file sharing server, and configuration information can be automatically applied to newly constructed servers connected to the management network.

[0110] Thus, the configuration automation feature of the present invention allows an operator to quickly configure new servers without having to make separate connections to each server for new server configuration.

[0111] In one embodiment of the present invention, an AI (Artificial Intelligence) analysis function using Redfish is provided.

[0112] In other words, it can collect formatted and unformatted log data from servers and storage devices using SRC (Server remote control) (iDRAC, iLO, IPMI), and perform data classification and pre-processing processes.

[0113] The system then uses the learned data model to predict equipment status and faults, and when important problems occur, sends alarm messages to the user's device via text, email, etc.

[0114] The AI ​​analysis capabilities of the present invention can learn what normal traffic is, discover abnormal traffic, prioritize the required risk levels for users, and analyze and assist with problems.

[0115] It also uses AI to analyze and learn from logs collected during server operation, develops algorithms, and provides solutions to problems by sending warning messages to the client terminal 130 when log information similar to an existing problem is confirmed through the learned algorithm. In other words, the AI ​​analysis function allows for the prevention of problems in advance, rapid sharing of problem occurrences, and real-time analysis.

[0116] The management server 110 can check the BBU (Backup Battery Unit) period of the managed server, and when a predetermined period is reached, transmit the contents of the period to the client terminal of the managed server.

[0117] In addition, the management server 110 can check the BBU charging capacity of the managed server, and when the battery charging efficiency falls below a predetermined value, can notify the client terminal of the managed server of this information.

[0118] For example, the management server 110 can check the BBU charging capacity of a managed server, and when the battery charging efficiency drops below 40%, can notify the client terminal of the managed server of this information.

[0119] The management server 110 can check the remaining capacity of the BBU of the managed server, and if the remaining battery capacity is 10% or less, can notify the customer terminal of the managed server of this information.

[0120] For example, the management server 110 can check the remaining capacity of the BBU of a managed server, and if the remaining battery capacity is 10% or less, can notify this to the client terminal of the managed server.

[0121] In addition, the management server 110 can check the BBU write policy of the managed server, and if the write policy is changed, can notify the client terminal of the managed server of the change.

[0122] The present invention relates to a server integrated management system that integrates and manages a large number of servers, diagnoses various server functions, predicts failures in advance, issues warnings, and presents solutions.

[0123] In the present invention, of the various functions of the server, a BBU (Backup Battery Unit) will be taken as an example for explanation.

[0124] Taking Dell servers as an example, it is necessary to check the status of the BBU battery and proceed with preemptive replacement to prevent cache data loss due to RAID controller battery failure.

[0125] To this end, the battery full charging efficiency (%) is checked by checking the Dell server log, and equipment with a full charging efficiency of less than 50% is inspected and battery replacement is carried out.

[0126] After 36 months, the battery charging efficiency naturally decreases to about 70%, and taking this into consideration, a battery that has an additional decrease of about 20% can be determined to have poor charging efficiency.

[0127] The server integrated management system of the present invention performs periodic BBU checks, charge capacity checks, remaining capacity checks, and write policy checks, thereby preventing cache data loss and preventing risk factors of battery conditions in advance.

[0128] In the server integrated monitoring system of the present invention, when an event occurs, it is diagnosed that the event may cause a server failure, and a warning is given to the system of the server in advance, and information regarding a solution is transmitted in a consolidated manner.

[0129] In this regard, the events that occur on the server are very diverse, and it is possible that new events that have never occurred before may occur.

[0130] In this invention, some of the events that may occur on such a server are given as examples.

[0131] 1. Fan Noise (Reading above 12,000 RPM) on Dell R720 Servers with iDRAC7 version 1.51.51 The recommended solution for this is to downgrade to iDRAC7 version 1.46.45.

[0132] 2. The power usage rate of rack PDU#1 and PDU#2 is shooting to PDU#1 Referring to FIG. 32, not only Dell® servers but also HP® servers are set to operate in Active Standby as the default for the Power Supply, which results in a situation where power is concentrated on one side of the Rack PDU. In order to adjust the balance, it is necessary to adjust the Primary-PSU ratio.

[0133] 3. Abnormal OS behavior after 12th to 14th generation kernel updates for Dell(R) server products In this case, if abnormal operation is detected in the OS (Operating System) after the kernel update in the Dell server, the management server 110 transmits a message indicating a predicted failure that may occur as a result to the corresponding managed server, and also transmits a solution to the predicted failure to the corresponding managed server.

[0134] 4. Service unavailable due to insufficient TCP / IP ports This is a phenomenon that occurs when a network TIME_WAIT session remains unclosed in Windows 2008 if the uptime is 497 days or more.

[0135] This causes problems when ports are occupied and there are no more ports available. This applies to Windows 2008 Server and Windows 2012 Server, and the issue can be resolved by removing the updated patch.

[0136] 5. Windows(R) 2003~2022 Event Log Generation 6. Memory production cycle diagnostics This confirms that a specific production cycle of a specific memory is faulty. The affected equipment is 13th generation equipment (R730, R930, R630), the affected OS is Windows 2012 R2 Server with the KB3064209 hotfix, and the solution is to remove the corresponding hotfix.

[0137] In the present invention, the management server 110 diagnoses the memory production cycle of the managed servers, determines that a predetermined memory production cycle is defective, and notifies the corresponding managed server of this result.

[0138] 7. When using a PCIe Type SSD, the device settings may stop responding. The solution to this is to update BIOS 1.1.4 to 1.2.10.

[0139] 8.12G server temperature sensor does not work properly after BIOS update, so beep (Alert_) occurs continuously The solution to this is to diagnose the BIOS 2.5.2 version and update it with the latest firmware.

[0140] 9. After patch update, BSOD occurs and booting is not possible This event is caused by the August 2014 Patch Tuesday update Windows error KB2982791.

[0141] The problem is with a Windows 2008 server, and the problem can be resolved through a patch update.

[0142] 10. DNS connection occurs on a client using Windows 2012 Active Directory When logging into a domain account from a server, I get the error "Incorrect user name or password" even though the account and password are correct.

[0143] In Windows Server 2008 R2 / Windows 7 and later, DES-CBC-MD5 and DES-CBC-CRC encryption is not used, and only AES256-CTS-HMAC-SHA1-96, AES128-CTS-HMAC-SHA1-96 and RC4-HMAC encryption are used. However, if the AD server is Windows Server 2012 R2 and the domain member is Windows Server 2008 R2 or Windows 7, this is due to a product issue where AES key generation fails when updating the computer account password.

[0144] 11. Vulnerabilities in GNU Bash 4.3 Shell It is known that Bash vulnerabilities allow attackers to modify the content and code of web servers, tamper with websites, leak user data, and launch DDoS attacks. In addition, attack scenarios for Bash code injection vulnerabilities in various environments, such as SSH and DHCP protocols, have also been proposed.

[0145] The problem affects Red Hat® Enterprise Linux® 5, 6, and 7 servers, and the solution is a Bash update.

[0146] 12. Buffer overflow vulnerability in the GNU C library (glibc) When calling the gethostbyname() or gethostbyname2() functions, which are commonly used when connecting to a network, a vulnerable function is called, allowing an external attacker to remotely execute arbitrary code on the vulnerable server.

[0147] The problem affects Red Hat(R) Enterprise Linux(R) 5, 6, and 7 servers, and the solution is a GLIBC update.

[0148] 13. Bugs in Red Hat(R) V5 and V6 series OS This is a bug that causes a reboot phenomenon after 208.5 days in all versions of Red Hat(R) Enterprise Linux(R) 6 or 5 that use Intel(R) CPUs.

[0149] The problem was affecting Red Hat Enterprise Linux 5,6 servers, and the solution was a kernel update.

[0150] 14. Raid Controller Battery Fail I / O performance is degraded due to the Raid Controller Cache being unavailable.

[0151] The problem is with the Raid Controller Battery for Dell(R) Perc 5i and 6i, and the solution to the problem is to proactively replace the Raid Controller Battery for Dell(R) Perc 5i and 6i every 4 to 5 years, which is the usage cycle.

[0152] 15. System down due to CPU IERR error The problem was with a server (PE R720, PE R920) using the Intel (registered trademark) iBridge V2 CPU, and the solution to the problem was to change the BIOS settings.

[0153] For example, in System Profile Settings, set System Profile to Custom, CPU Power Management to Maximum Performance, C1E to Disabled C States Disabled, and Monitor / Mwait to Disabled.

[0154] 16. Unable to connect to management web when using iDrac 1.50.50 F / W (Firmware) (search for applicable version) Upgrade to iDrac F / W (Firmware) 1.51.51 via F / W upgrade on the OS or via media upgrade in daily life.

[0155] This invention proposes a server integrated monitoring system that supports multi-vendors. For example, this invention stores information on hardware systems from three companies, such as Dell (registered trademark), HP (registered trademark), and Lenovo (registered trademark), in one inventory, and uses the information stored in the inventory to inquire about all information related to the hardware, making it possible to utilize the functions.

[0156] For convenience of explanation of the present invention, a server integrated monitoring system that supports multiple vendors will be explained by taking manufacturers such as Dell (registered trademark), HP (registered trademark), and Lenovo (registered trademark) as examples.

[0157] 13 is a flowchart showing a method for managing servers by supporting multiple vendors in a server integrated monitoring system according to an embodiment of the present invention. In FIG. 13, the management server 110 executes each step.

[0158] 13, the managed servers are registered (S201). At this time, the managed servers can be registered using the management IP information of each server.

[0159] For example, you can register the target server using the iDRAC for Dell®, the iLO for HP®, or the iMM for Lenovo®.

[0160] Next, it is determined whether or not to connect to each server (S203), and multi-vendor hardware inventory information is collected (S205). In one embodiment of the present invention, the hardware inventory information of an x86 server hardware system can be collected without distinguishing between manufacturers by using the Redfish API (Application Programming Interface), which is a common hardware standard.

[0161] Then, the collected inventory information is stored (S207). If there is a firmware update event including an emergency firmware update, firmware updates are performed for all managed servers (S209). Then, the changed update information is confirmed (S211). In one embodiment of the present invention, firmware update information can be confirmed via the Redfish API.

[0162] Then, groups are set according to the security level of each server, whether or not it is subject to inspection, its importance, etc. (S215), and server information is checked in real time (S217). In this manner, in one embodiment of the present invention, various information related to the x86 servers in operation, such as detailed hardware specifications, OS (Operating system) information, firmware information, and driver information of each server, can be collected by using the Redfish API, and standardized management of x86 servers can be performed.

[0163] 14 is a flowchart showing a method for preventing failures in advance by analyzing failure logs and patterns in a server integrated monitoring system according to an embodiment of the present invention. The management server 110 executes each step of FIG.

[0164] 14, when a failure occurs in any device of the managed server (S401), the logs and patterns are analyzed (S403). Then, the analyzed data is stored (S405). When the failure is resolved (S407), devices similar to the corresponding device are classified (S409), and a failure response process is performed in advance for the classified similar devices (S411). In this way, in the present invention, by analyzing logs and patterns when a failure occurs and automatically classifying similar devices, it is possible to prevent failures from occurring in similar devices in advance.

[0165] FIG. 15 illustrates an operational model for supporting multi-vendors using Redfish API in a server integrated monitoring system according to an embodiment of the present invention.

[0166] As shown in FIG. 15, in the present invention, the Redfish API is used to collect inventory information about x86 server hardware systems regardless of manufacturer, such as Dell (registered trademark), HP (registered trademark), or Lenovo (registered trademark), and the collected information can be queried and utilized.

[0167] For example, Dell® collects data using iDRAC, HP® collects data using iLO, and Lenovo® collects data using iMM.

[0168] The Redfish API can then be used to distribute and install the OS and firmware across multiple servers.

[0169] In this invention, the Redfish API can be used to quickly check the hardware specifications, OS information, firmware information, etc. of each server.

[0170] Additionally, the present invention can analyze patterns to predict failures, and hardware logs can be used to facilitate pattern analysis.

[0171] The Redfish API has undergone continuous updates since it was first released in 2015, helping multiple server manufacturers provide the same functionality as IPMI.

[0172] In addition, the Redfish API supports BIOS and Secure Boot configuration functions, firmware update functions, and storage and server network configuration functions.

[0173] It also supports the Open Compute Platform, Open stack, SNIA (Storage Networking Industry Association), and provides support for network switch management and external storage management.

[0174] iDRAC, a management tool for Power Edge servers, uses Redfish to support the Redfish RESTful API.

[0175] For example, iDRAC can perform server power (Reset, Reboot, Power Control), server hardware inventory, server monitoring and status check, system log collection, server status change check, and alarms.

[0176] PowerEdge Server can automate the initial settings of servers via Redfish. It can also create templates for various configuration information such as iDRAC initial settings, BIOS, RAID controllers, and network cards, and perform automated deployment of servers.

[0177] An example of using Redfish on the iDRAC of a Power Edge server for server configuration automation (Auto deployment) is as follows.

[0178] Server-specific configuration values ​​are stored as metadata in a Server Configuration Profile (SCP) and are configurable via the Redfish API.

[0179] In addition, various configuration information such as BIOS, iDRAC / LC, PERC RAID Controller, NIC, and HBA can be set via the Redfish API.

[0180] SCP allows you to export, preview, and import configuration information freely to apply to newly created servers.

[0181] SCP can be shared via methods such as HTTPS, NFS, and CIFS, and can be implemented in XML and JSON file formats.

[0182] 16 to 29 are diagrams showing examples of screens of a server integrated monitoring system according to an embodiment of the present invention.

[0183] FIG. 16 is an example of an initial screen, which supports, via a dashboard, the viewing at a glance of information regarding inventory and logs that are automatically collected for the managed servers.

[0184] Figure 17 shows an example of a screen that allows you to check the inventory information of the managed servers in real time. If any information is changed on this screen, the inventory information is automatically updated.

[0185] In the example screen in Figure 18, each part is represented by symbol 5 (red circle) to make it easy to identify when a problem with the managed server is confirmed, and normal parts are represented by symbol 6 (green circle).

[0186] FIG. 19 is an example of a screen where real-time management information of all managed servers, including firmware (F / W) information, can be viewed.

[0187] Figure 20 shows an example of a screen where you can check the real-time CPU details and current status of all managed servers.

[0188] Figure 21 shows an example of a screen where you can check the real-time memory details and current status of all managed servers.

[0189] Figure 22 is an example of a screen where you can check the real-time Raid Controller details and current status of all managed servers.

[0190] Figure 23 is an example of a screen where you can check the real-time disk details and current status of all managed servers.

[0191] Figure 24 is an example of a screen where you can check the real-time detailed information and current status of the PSU (Power supply) of all managed servers.

[0192] Figures 25 and 26 are examples of screens that allow you to check real-time detailed information about the collected logs of all managed servers. Real-time vendor HW error codes are collected and automatically classified, allowing you to check problematic equipment by error code.

[0193] FIG. 27 shows an example of a fault analysis screen, which displays fault analysis information including the cause of the fault, conclusion, and replacement time.

[0194] FIG. 28 is a screen example showing a fault analysis distribution chart for each server in comparison with a client company.

[0195] FIG. 29 is an example of a screen showing a service report function, showing report contents including problem items at the time of occurrence, problem solutions, and recurrence prevention measures.

[0196] FIG. 30 is a classification diagram of system equipment according to an embodiment of the present invention, and FIG. 31 and FIG. 32 are diagrams describing hardware symptoms and their causes according to an embodiment of the present invention.

[0197] 33 to 34 are flowcharts illustrating a method for proactively dealing with a fault in a server integrated monitoring system according to an embodiment of the present invention.

[0198] 33, when a hardware-related problem occurs in a managed server (S101), the management server 110 classifies similar equipment that is likely to cause a failure as dangerous equipment by referring to the classification table of FIG. 30 (S103). Then, a warning message is sent for the classified dangerous equipment (S105), and countermeasures are taken before a failure occurs (S107). Referring to the classification table of FIG. 30, specific similarity judgment criteria for system equipment in one embodiment of the present invention are exemplified, and examples include classification of equipment of the same class, classification of equipment of the same CPU, classification of equipment of the same memory, classification of equipment of the same NIC, classification of equipment of the same Disk, classification of equipment of the same HBA, classification of equipment of the same BIOS, classification of equipment of the same Driver version, classification of equipment of the same OS, and classification of equipment of the same Firmware version.

[0199] Referring to FIG. 34, when a hardware-related problem occurs in a managed server (S301), the management server 110 grasps the fault symptom (S303). Then, referring to the diagrams of FIG. 31 and FIG. 32, the management server 110 checks a symptom code corresponding to the fault symptom (S305). Then, the management server 110 checks the cause corresponding to the symptom code (S307) and sends a countermeasure report accordingly (S309). Then, the management server 110 executes a fault countermeasure corresponding to the fault cause (S311). If there is no symptom code corresponding to the fault symptom in step S305, a new symptom code is generated and added to the list of FIG. 31 and FIG. 32 (S313). Referring to FIG. 31 and FIG. 32, examples of fault causes corresponding to symptom codes for each fault symptom according to an embodiment of the present invention are shown.

[0200] In other words, RAC1198 is an iDrac firmware problem, pluggable memory failure is a memory problem and a BIOS firmware problem, Link Failure is a NIC failure and firmware problem, numerous Link Failure Counts are NIC driver and firmware problems, NIC Link is Down is a NIC driver and firmware problem, Link status and server confirmation request are NIC driver and firmware problems, HOST_DOWN is a NIC driver and firmware problem, yellow light in front of the server is an iDrac firmware problem, SWC5008: critical message output is an iDrac firmware problem, NO_PARTITION alarm is a disk failure, Reset adapte is a BIOS firmware problem, Correctable memory error is a memory problem and a BIOS firmware problem, CPU performance degradation is a BIOS firmware problem, Memory and Slot cannot be displayed is a memory problem and a BIOS firmware problem, Disk fault error is a disk failure, disk predicted fail is a failure due to disk BadBlock, periodic FAN 6 recognition problem is a Fan 6 failure, Fault due to light intensity below 400 is a Gbic failure, NIC GBIC communication failure is a Gbic failure, infinite system reboots are a BIOS firmware problem, LCD Panel specific message output is an iDrac firmware problem, repeated error messages on iDRAC are an iDrac firmware problem, vCenter agent and synchronization errors are EXSi version and OS version problems, server reboots are a BIOS firmware problem, slow HBA Write speed is an HBA firmware and driver problem, slow HBA Read speed is an HBA firmware and driver problem, HBA Link Down is an HBA Gbic and Card problem, HBA duplex failure is an HBA Gbic and Card problem, Riser 1 failure is a Riser Card problem, Riser 2 failure is a Riser Card problem, network redundancy failure is a NetworkCard problem, PSU Alert yellow LED is lit if PSU failure, abnormality caused by low voltage is PSU failure, BIOS setting and NIC firmware / driver problem that prevents PXE boot, motherboard failure that prevents POST boot, motherboard failure that prevents LifeCycle connection, iDRAC Hang symptom is iDrac firmware problem, iDRAC Network disconnection is motherboard failure and iDrac firmware problem, iDRAC SNMP service failure occurs if iDrac firmware problem, server suddenly turns off while in use is motherboard problem, Medium Error occurs if disk failure, ERROR Event confirmation request is an issue due to Error Event, CMC connection failure is due to CMC firmware problem.

[0201] DSET analysis request is a failure due to analysis, TSR Log analysis request is a failure due to analysis, NFS Service startup failure is NFS settings and OS settings check, unable to connect to vCenter is a problem with EXSi version and OS version, NIC Reset is a problem with the Network Card, GPU card failure that cannot recognize GPU, OS Crash occurs is OS Dump analysis, Network error / dropped packets occurs is a problem with the Network Card, CRC error occurs is a problem with the Network Card, server switch is turned off is a problem with the Network Card, problem with communication to the network is not smooth is a problem with the Network Card, same slot event occurs after memory replacement is a memory failure or motherboard failure, disk failure in read-only state and inaccessible disk or RAID configuration problem, switch hangs 3 to 4 times a month is a problem with the motherboard or OS version, LACP Network Speed ​​problem occurs is a problem with the Network Card, cluster failover occurs is a cluster setting problem or HW failure, RTSP synchronization failure is an OS setting or network failure, session degradation occurs is a problem with the Network Card or Gbic, unknown power outage is a PSU failure, server delay and hang symptoms are an application or HW failure, Network Ping Loss indicates a problem with the Network Card or Gbic. An increase in LoadAvg indicates a need to check the CPU. The occurrence of a Fatal Error indicates a problem with the PCI Card or Riser Card. A halt or slow performance during PXE installation indicates a problem with the Network Card or Gbic. The occurrence of a Blue Screen (0x00004f) indicates a motherboard / BIOS / disk / memory failure. The Blue Screen indicates a motherboard / BIOS / disk failure, OSBooting failures are motherboard / BIOS / disk failures, process down, panic during OS installation is motherboard / BIOS / disk failure, server smell is fan / motherboard / PSU problem, solution for NAS inability to connect is network / OS setting problem, KVM inability to connect is motherboard / KVM cable / KVM problem, Disk Amber LED is disk failure, Delay at post boot is motherboard / fan / PCI / memory problem, solution for power failure is PSU failure, reduced TEMING performance is network / OS setting problem, VD Bad Block is disk failure, HBA Loop is HBA failure, Raid configuration information is not visible firmware / disk driver problem, firmware / disk driver problem unable to recognize volume, Kernel Panic is OS / App problem, server reboot when using maximum performance is CPU / PSU / motherboard / memory problem, noticeably slower server processing speed is CPU / PSU / motherboard / memory / disk problem, server will not power on is caused by PSU failure.

[0202] Although the present invention has been described above using several preferred embodiments, these embodiments are illustrative and not limiting.

[0203] It will be understood that a person having ordinary skill in the art to which the present invention pertains can make various changes and modifications without departing from the spirit of the present invention and the scope of rights set forth in the appended claims. [Explanation of symbols]

[0204] 110: Management server 112: Database 120: Administrator terminal 130: Customer terminal 10, 20, 30, 40: Managed Servers

Claims

1. In a server integration monitoring system for monitoring two or more managed servers, A database for storing managed server related data; a management server that collects hardware-related data and software-related data from the managed servers, monitors and manages the status of each managed server, and provides various server monitoring information including related management service statistical data and management service reports to a management terminal used by a manager and to a client terminal that has requested the managed servers; Including, The management server monitors the managed servers according to a preset schedule for monitoring the managed servers, and provides monitoring result information to the management terminal and the client terminal. Server integrated monitoring system.

2. 2. The server integrated monitoring system according to claim 1, The management server provides a schedule setting function that can set a server monitoring period and set data collection values ​​to be collected from the managed servers.

3. 2. The server integrated monitoring system according to claim 1, The management server can use Redfish API to collect information about the x86 servers in operation, including detailed hardware specifications, OS (Operating system) information, firmware information, and driver information of each managed server, and is an integrated server monitoring system that performs standardized management of x86 servers.

4. 2. The server integrated monitoring system according to claim 1, The management server checks the backup battery unit (BBU) period of the managed server, and when a predetermined period is reached, transmits the information to the client terminal of the managed server. Check the BBU charging capacity of the server under management, and if the battery charging efficiency falls below a predetermined value, notify the customer terminal of the server under management. Check the remaining capacity of the BBU of the server to be managed, and if the remaining capacity of the battery is below a predetermined value, notify the customer terminal of the server to which the server is to be managed. Checks the BBU write policy of the server under management, and if the write policy is changed, notifies the client terminal of the server under management. A server integrated monitoring system that checks the battery full charging efficiency (%) by checking the logs of managed servers and notifies the customer terminal of the managed server of the battery replacement message for equipment with a full charging efficiency below a predetermined value.

5. The server integrated monitoring system according to claim 1, The management server collects and stores multi-vendor hardware inventory information from a plurality of registered managed servers.

6. 6. The server integrated monitoring system according to claim 5, The management server performs firmware updates for all managed servers when a firmware update event, including an emergency firmware update, occurs.

7. 2. The server integrated monitoring system according to claim 1, The management server analyzes logs and patterns when a fault occurs in any of the equipment of the managed servers, stores the analyzed data, and when the fault is resolved, classifies the equipment similar to the equipment and performs pre-failure response processing for the classified similar equipment, thus providing a server integrated monitoring system.

8. 2. The server integrated monitoring system according to claim 1, The management server refers to a classification table when a hardware-related problem occurs in the managed server, classifies similar equipment that is likely to cause a failure as dangerous equipment, sends a warning message regarding the classified dangerous equipment, and takes measures to respond to the failure in advance, in this server integrated monitoring system.

9. 9. The server integrated monitoring system according to claim 8, The classification table includes specific criteria for judging similarity of system equipment, and includes classification of equipment of the same class, classification of equipment of the same CPU, classification of equipment of the same memory, classification of equipment of the same NIC, classification of equipment of the same disk, classification of equipment of the same HBA, classification of equipment of the same BIOS, classification of equipment of the same driver version, classification of equipment of the same OS, and classification of equipment of the same firmware version, in a server integrated monitoring system.

10. 10. The server integrated monitoring system according to claim 9, When a hardware-related problem occurs in a managed server, the management server grasps the failure symptoms, refers to a list including failure causes corresponding to symptom codes for each failure symptom, checks the symptom code corresponding to the failure symptom, checks the cause corresponding to the symptom code, sends a countermeasure report accordingly, performs the failure countermeasure corresponding to the cause of the failure, and, if there is no symptom code corresponding to the failure symptom, generates a new symptom code and adds it to the list.

11. The server integrated monitoring system according to claim 10, The above list shows that RAC1198 is an iDrac firmware issue, The connectable memory failure is caused by a memory problem and a BIOS firmware problem. Link failure can occur due to NIC failure or firmware problem. A high Link Failure Count can be caused by a problem with the NIC driver or firmware. NIC Link is Down is caused by NIC driver and firmware issues, Link status and server check requests can be caused by NIC driver and firmware issues, HOST_DOWN can occur due to NIC driver and firmware issues, The yellow light on the front of the server is a problem with the iDrac firmware. SWC5008:critical message output indicates iDrac firmware issue, The NO_PARTITION alarm occurs when a disk failure occurs. Reset adapte fixes BIOS firmware problems, Correctable memory error is a memory problem and a BIOS firmware problem. The slow CPU performance is due to a BIOS firmware problem. The reason why the memory and slots are not displayed is due to a memory problem or a BIOS firmware problem. Disk fault error means disk failure, Disk predicted fail is a failure caused by a disk bad block. Periodic FAN6 recognition problem, Fan6 failure, Faults caused by light intensity below 400 include Gbic failure, NIC GBIC communication failure, System infinite reboots are caused by BIOS firmware issues, LCD Panel specific message output indicates iDrac firmware issue, Repeated error messages on the iDRAC may be due to an iDrac firmware issue, The vCenter agent and sync error is due to EXSi version and OS version issues, The server reboot phenomenon is due to a BIOS firmware problem. The slowdown in HBA Write speed is caused by problems with the HBA firmware and driver. The slowness of HBA Read speed is caused by problems with the HBA firmware and driver. HBA Link Down is a problem with the HBA Gbic and Card. HBA duplex disconnection failure is a problem with HBA Gbic and Card. Riser1 recognition failure is due to a Riser Card problem. Riser2 recognition failure is due to a Riser Card problem. Network redundancy failure is caused by a problem with the Network Card, PSU Alert Yellow LED on indicates PSU failure. Abnormal occurrences due to low voltage include PSU failure, BIOS setting and NIC firmware / driver problems that prevent PXE boot, POST boot failure motherboard failure, LifeCycle connection failure motherboard failure, iDRAC Hang symptoms can be caused by iDrac firmware issues, iDRAC Network disconnection can be caused by a motherboard failure and an iDrac firmware issue, iDRAC SNMP service failure occurs due to iDrac firmware issues, server suddenly powers off while in use, compliance issues, CMC firmware issues with CMC not being able to connect, DSET analysis requests are made based on the following: TSR Log analysis requests are for issues caused by the analysis, NFS Service startup failure may be due to NFS settings and OS settings checks, EXSi version unable to connect to vCenter, OS version issues, NIC Reset can be used to troubleshoot network card problems, GPU card failures, When an OS crash occurs, analyze the OS dump. Network error / dropped packets may be caused by a problem with the network card. CRC errors can occur due to network card problems, The server switch is turned off due to a network card problem. The problem of communication not being smooth on the network (bonding) is due to a network card problem. If the same slot event occurs after memory replacement, it may be due to a memory failure or motherboard failure, a disk failure that is inaccessible in Disk Read Only state, or a problem with the RAID configuration. If the switch hangs 3-4 times a month, it could be due to a problem with the motherboard or OS version. LACP Network Speed ​​problem occurs due to Network Card problem, Cluster failover occurs due to cluster configuration problems or HW failures, RTSP synchronization failures are caused by OS settings or network problems. The session degradation phenomenon may be caused by a problem with the Network Card or Gbic. Unknown power outages can be caused by PSU failure, Server slowness and hangs are caused by application or hardware failures. Network Ping Loss may indicate a problem with your Network Card or Gbic. If LoadAvg increases, check your CPU. Fatal Errors occur due to problems with the PCI Card or Riser Card. Stalls or slow performance during PXE installation can be caused by Network Card or Gbic issues, Blue Screen of Death (0x00004f) can be caused by a motherboard / BIOS / disk / memory failure, Blue Screen can be caused by motherboard / BIOS / disk failure, OS Booting failure may be due to motherboard / BIOS / disk failure, Process down and panic during OS installation may be caused by motherboard / BIOS / disk failure, The smell from the server could be a fan / motherboard / PSU problem, NAS connection failure countermeasures include network / OS setting problems, KVM connection failure motherboard / KVM cable / KVM problems, Disk Amber LED indicates a disk failure. Post boot delays can be caused by motherboard / fan / PCI / memory issues, Power supply failure countermeasures include PSU failure, Teaming performance degradation may be due to network / OS settings issues. VD Bad Block indicates a disk failure. HBA Loop can be used to resolve issues such as HBA failure, firmware / disk driver issues that prevent RAID configuration information from being seen, firmware / disk driver issues that prevent volume recognition, Kernel Panic is an OS / App problem. Server reboot when using maximum performance may be due to CPU / PSU / main board / memory issues, If your server slows down significantly, it may be due to a problem with the CPU, PSU, motherboard, memory, or disk. If the server does not power up, it is due to a PSU failure. Server integrated monitoring system.

Citation Information

Patent Citations

  • Computer supervisory system

    JP1995253956A

  • Method for registration / Revision setting of network configuration information in communication system, and the communication system, and program

    JP2002374250A

  • Information processing system monitoring device, monitoring method, and monitoring program

    JP2014134987A

  • Fault separating method and administrative server

    JP2019009726A

  • Event monitoring device, event management system, and event monitoring method

    JP2020009154A