It resource management system for providing server configuration automation function

The IT resource management system addresses the challenge of managing complex IT environments by using Redfish API for standardized server configuration and monitoring, enhancing operational efficiency and reducing costs through preemptive failure prediction and management.

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

Patent Information

Application Number
JP2024070592
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

The complexity of IT environments, particularly large-capacity servers, leads to frequent failures due to various factors, necessitating specialized server administrators, which are costly and difficult to manage, especially in small companies, and result in significant operational disruptions and losses.

Method used

An IT resource management system that collects and monitors data from multiple servers, provides server configuration automation, and uses the Redfish API to standardize and manage IT resources, enabling preemptive failure prediction and standardized operations.

Benefits of technology

The system improves operational efficiency, reduces costs, enhances security, and facilitates convenient management of multiple servers by predicting failures, reducing downtime, and enabling efficient troubleshooting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156645000001_ABST
    Figure 2024156645000001_ABST
Patent Text Reader

Abstract

To relate to an IT resource management system for managing IT resources including two or more servers to be managed.SOLUTION: An IT resource management system is configured to collect a hardware-related data and software-related data from servers to be managed, monitor and manage status of the servers to be managed, and provide various server monitoring information, including management service statistical data and management service reports related to the monitored and managed status of the servers, to an administrator terminal used by an administrator and a customer terminal that has requested the server to be managed. The management server provides a server configuration automation function so that unique setting values of the servers to be managed are stored as metadata in an SCP (Server configuration profile). This invention produces an effect of preventing faults being likely to occur in the servers in advance and of reducing damages due to the server faults.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a management technique for systematizing and standardizing IT (Information Technology) resources such as servers, storage, and networks, and more specifically to a server management technique that provides a function for automating server configuration. [Background technology]

[0002] Recently, IT (Information Technology) environments such as servers, storage, and networks have become more complex, resulting in a lack of available work time. As computer systems become larger in capacity and faster, computer problems caused by system errors and viruses are becoming more frequent.

[0003] Especially in the case of large-capacity servers, failures can occur frequently due to various factors such as the operation of various application programs, data storage, reading, transfer, etc. Therefore, each company assigns separate server administrators to manage such servers and handle failures when they occur.

[0004] However, server management requires specialized skills, and hiring such specialized staff is quite costly. Therefore, particularly 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.

[0005] In such cases, server management is difficult to carry out smoothly, and it is almost impossible to deal smoothly with server failures that occur.

[0006] 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 for the administrator to be promptly notified of the status of the server 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 deal with it immediately because he or she is located remotely, which can ultimately result in huge losses such as the server going down.

[0007] 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, this 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 according to the manpower and cost required for recovery. [Prior art documents] [Patent documents]

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

[0009] The present invention has been devised to solve the above-mentioned problems, and its object is to provide an IT resource system that can improve operational efficiency, reduce operational costs, and strengthen security by systematizing IT resources and standardizing operations.

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

[0011] In order to achieve the above object, the present invention relates to an IT resource management system for managing IT resources including two or more managed servers. The IT resource management system includes a management server that collects related data and software related data, 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 an administrator terminal used by an administrator and a customer terminal that has requested the managed server, and the management server provides a server configuration automation function by storing unique setting values ​​of each managed server as metadata of a Server Configuration Profile (SCP).

[0012] The management server can use the Redfish API to provide server configuration automation capabilities.

[0013] The management server can distribute the SCP to the newly created managed servers and apply the configuration information. Effect of the Invention

[0014] According to the present invention, by monitoring a large number of managed servers, it is possible to prevent server failures in advance by predicting and warning about server failures and providing solutions, thereby reducing damage caused by server failures. In addition, according to the present invention, it is possible to improve operational efficiency, reduce operational costs, and strengthen security by systematizing IT resources and standardizing operations.

[0015] Furthermore, the present invention has the effect of enabling a large number of servers to be managed more conveniently and efficiently.

[0016] Furthermore, 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 the overall configuration of an IT resource management system according to an embodiment of the present invention. [Diagram 2] 2 is a diagram conceptually illustrating an operation process in an IT resource management system according to an embodiment of the present invention. [Diagram 3] 2 is a flowchart illustrating a method for automating server configuration in an IT resource management system according to an embodiment of the present invention. [Figure 4] 4 is a screen example showing functions provided by an IT resource management system according to an embodiment of the present invention. [Diagram 5] 4 is a screen example showing functions provided by an IT resource management system according to an embodiment of the present invention. [Figure 6] 4 is a screen example showing functions provided by an IT resource management system according to an embodiment of the present invention. [Figure 7] 4 is a screen example showing functions provided by an IT resource management system according to an embodiment of the present invention. [Figure 8] 4 is a screen example showing functions provided by an IT resource management system according to an embodiment of the present invention. [Figure 9] 1 is a diagram illustrating an example of the configuration of an IT resource management 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 an IT resource management system according to an embodiment of the present invention. [Figure 11] FIG. 1 is an exemplary diagram illustrating a function of automating server configuration work using Redfish in an IT resource management 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 an IT resource management system according to an embodiment of the present invention. [Figure 13]1 is a flowchart illustrating a method for managing servers with multi-vendor support in an IT resource management system according to an embodiment of the present invention. [Figure 14] 1 is a flowchart illustrating a method for analyzing failure logs and patterns to prevent failures in an IT resource management system according to an embodiment of the present invention. [Figure 15] FIG. 1 illustrates an operational model for supporting multi-vendors using Redfish API in an IT resource management system according to an embodiment of the present invention. [Figure 16] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 17] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 18] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 19] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 20] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 21] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 22] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 23] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 24] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Diagram 25] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 26] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 27] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 28] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Figure 29] FIG. 2 is a diagram showing an example of a screen of an IT resource management system according to an embodiment of the present invention. [Diagram 30] FIG. 2 is a diagram showing classification of system equipment according to an embodiment of the present invention. [Diagram 31] FIG. 2 is a diagram illustrating hardware symptoms and their causes according to an embodiment of the present invention. [Diagram 32] FIG. 2 is a diagram illustrating hardware symptoms and their causes according to an embodiment of the present invention. [Diagram 33] 1 is a flow chart illustrating a method for proactively responding to failures in an IT resource management system according to an embodiment of the present invention. [Diagram 34] 1 is a flow chart illustrating a method for proactively responding to failures in an IT resource management system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] The present invention can be modified in various ways and can have various implementations, but specific implementations are illustrated in the drawings and described in detail. However, it is understood that this is not intended to limit the present invention to the specific embodiments, and includes all modifications, equivalents, and alternatives within the spirit and technical scope of the present invention.

[0019] The terms used in this application are merely used to describe examples in specific implementations and are not intended to limit the present invention. A singular expression includes a plural expression unless otherwise clearly meant in the context.

[0020] 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 are to be understood as not precluding the presence or additional possibility of one or more other features.

[0021] 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.

[0022] 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.

[0023] In the following description, referring to the accompanying drawings, the same components are denoted by the same reference numerals regardless of their reference numerals, and redundant description thereof will be omitted.

[0024] 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.

[0025] The present invention relates to an IT resource management system for managing IT resources including two or more managed servers. The IT resource management system 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 a client terminal that has requested the managed servers. The management server provides a server configuration automation function that stores the unique setting values ​​of each managed server as metadata in a Server Configuration Profile (SCP).

[0026] The management server can use the Redfish API to provide server configuration automation capabilities.

[0027] The management server can distribute the SCP to newly created managed servers and apply the configuration information.

[0028] Fig. 1 is a diagram conceptually showing the overall configuration of an IT resource management system according to an embodiment of the present invention, and Fig. 2 is a diagram conceptually showing an operation process in the IT resource management system according to an embodiment of the present invention. Referring to Fig. 1 and Fig. 2, the IT resource management system of the present invention includes a management server 110, a database 112, an administrator terminal 120, and a customer terminal 130.

[0029] The administrator terminal 120 is a terminal used by an administrator who manages the IT resource management system. The customer terminal 130 is a terminal used by each customer who has requested the managed servers 10, 20, 30, and 40.

[0030] In one embodiment of the present invention, the administrator terminal 120 and the customer terminal 130 can be realized in various terminal forms 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.

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

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

[0033] The management server 110 collects data from the managed servers 10, 20, 30, 40, grasps and manages the current status of each managed server, including related management service statistical data and management service reports. The management server 110 provides various server management information to the administrator terminal 120 and the customer terminal 130.

[0034] 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.

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

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

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

[0038] The management server 110 can collect information on the x86 servers in operation, including detailed hardware specifications, OS (Operating system) information, firmware information, and driver information of each managed server, using Redfish API, and can perform standardized management of the x86 servers. 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, and can preemptively send a predicted failure occurrence message to a client terminal that requested the managed server, warning that a failure may occur due to a predetermined event that occurs in the managed servers (10, 20, 30, and 40) through the preventive analysis function.

[0039] 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 .

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

[0041] When an equipment-related event occurs in a managed server, the management server 110 classifies the dangerous equipment according to a predetermined classification standard, and sends a warning message regarding the dangerous equipment to the administrator terminal 120 and the corresponding customer terminal. Then, a failure response measure can be taken in advance for the dangerous equipment.

[0042] When an equipment-related event occurs in a managed server, the management server 110 grasps the fault symptoms of the equipment, analyzes the cause according to the fault code corresponding to the fault symptoms, sends a report including a fault response plan to the administrator terminal 120 and the customer terminal, and executes fault response measures for the equipment.

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

[0044] 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.

[0045] 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.

[0046] The present invention relates to an IT resource management system that manages a plurality of managed servers 10, 20, 30, and 40 at the request of a customer.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] The management server 110 automatically collects hardware and software information of the managed servers 10, 20, 30, and 40, grasps the current state of each server based on the collected information, and provides management services according to the request status of each server. Figure 2 conceptually illustrates an operation process of an IT resource management system according to an embodiment of the present invention, and in Figure 2, the managed server is a Dell server 10 to which the iDRAC9 version is applied, and an example of a platform using the Redfish API (Application Programming Interface) is shown.

[0052] 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.

[0053] Then, the collected data is classified and data pre-processing is performed. The pre-processed data is stored in the database 112, and learning is performed on the data stacked in the database through an AI learning data model, so as to reclassify the data and generate data rows.

[0054] Then, the user terminal calls up the page using Flask, searches the database 112 in the data analysis module, performs analysis, performs data visualization, and transmits it to a Flask Response User Web page. Figure 3 is a flowchart showing a method for automating server configuration in an IT resource management system according to an embodiment of the present invention.

[0055] The embodiment of FIG. 3 is an embodiment using Redfish API. Referring to FIG. 3, the management server 110 stores information such as OS, BIOS, firmware, etc. collected from each managed server (S2010). When a firmware update event such as an emergency firmware update occurs, the management server 110 distributes firmware to the corresponding managed server (S2020, S2030). Next, the management server 110 checks firmware information of the managed server (S2040) and checks whether the firmware update has been completed (S2050). FIGS. 4 to 8 are example screens showing functions provided by an IT resource management system according to an embodiment of the present invention.

[0056] 4 is an example of a main dashboard screen. Referring to FIG. 4, the management server 110 provides a main dashboard screen that displays important information on one screen based on resource information collected from the managed servers 10, 20, 30, and 40 and the number of registered performances. 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 time is spent on a certain task, and whether stabilized firmware for each component of the managed server is applied through the dashboard screen, so that the user can check important managed server information at a glance through the dashboard screen.

[0057] 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.

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

[0059] 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.

[0060] 5 is an example of a screen displaying the resource management function. In the present invention, the management server 110 provides a resource management function that automatically collects and organizes a list of new installations and changes of equipment such as servers, and provides reliable data in real time.

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

[0062] 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.

[0063] To provide relevant statistical information, it provides pie charts for equipment status such as operation, idle, pre-service, and disposal, and various statistical graphs such as the current status of operating equipment by year and vendor, a list of recently registered equipment, and additional customization methods. Figure 6 is an example of a screen displaying the performance management function.

[0064] 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.

[0065] 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.

[0066] In addition, various performance statistics can be provided according to the situation such as year, month, data center location, pre-operation service, idle, etc.

[0067] The example screen in Figure 6 displays job history including online and offline job history management, the fault processing history manager's fault history, the system change history manager's change history, and more. It also displays backup schedule management and various statistical graphs relating to business performance.

[0068] 7 is an example of a screen displaying an automation management function. In the present invention, the management server 110 provides an automation management function that provides notification information on equipment requiring inspection through daily automatic inspection, and manages execution periods by group for automated collection such as setting a synchronization period (Daily / Weekly / Monthly), setting automated collection values ​​(All / Chassis / MGMT / CPU / NIC / HBA / DISK / GPU, etc.), and registering schedule information, through a standardized Redfish RESTful API.

[0069] In the example screen of Fig. 7, a menu of daily inspections is displayed, which allows the user to set the collection synchronization period, customize the automated collection value, register collection schedule information, automatically classify equipment that requires daily inspection, and check equipment with MGMT (Management Repository) connection errors. As shown in Fig. 7, the management server 110 can display the equipment in different colors depending on the equipment status in the daily inspection menu.

[0070] 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).

[0071] 8 is an example of a screen displaying the configuration diagram management. 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 a server, storage, network, SAN, etc., which are IT infrastructure components.

[0072] That is, the management server 110 provides a configuration management function that automatically displays a view of the configuration of a resource selected from a user terminal, such as a server, storage, network, SAN, etc., thereby enabling faster decision-making when a performance problem or failure occurs. Referring to Fig. 8, in the configuration management function, a configuration diagram view function of the equipment (server, storage, network, SAN, etc.) selected from a user terminal is provided, and a search and selection function based on a hostname and equipment model is provided, allowing the infrastructure configuration to be checked in real time when a performance problem or failure occurs.

[0073] Fig. 9 is a diagram showing a configuration example of an IT resource management system according to an embodiment of the present invention. In the configuration example of Fig. 9, the Redfish API is used, the managed servers are connected via the MGMT network, and the administrator terminal 120 can connect to the managed servers via a web connection method.

[0074] In one embodiment of the present invention, the IT resource management system collects inventory information of multi-vendor x86 server hardware systems in real time using a Redfish API-based platform, and distributes BIOS settings, firmware, etc. This improves maintenance efficiency and reduces operating costs. In addition, similar equipment can be identified based on collected logs, allowing the system to prevent similar failures in advance.

[0075] 10 is an exemplary diagram illustrating a server monitoring function using Redfish events in an IT resource management system according to an embodiment of the present invention. Referring to FIG. 10, the management server 110 in the present invention can provide a server monitoring function using Redfish events.

[0076] Redfish events transfer server event information to Redfish clients based on HTTPS, and when an alarm occurs in management, it is transferred to HTTP POST and can be received via HTTP GET. At this time, you can select the target servers for important notification email push, status monitoring, and daily inspection, and load the required data.

[0077] 11 is an exemplary diagram illustrating a function of automating server configuration work using Redfish in an IT resource management system according to an embodiment of the present invention. Referring to FIG. 11, a management server 110 in the present invention can provide a function of automating server configuration work using Redfish.

[0078] 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, and automatically selects the target equipment when emergency firmware is distributed and pushes an email to the administrator.

[0079] 12 is an exemplary diagram illustrating a server configuration automation function using Redfish in an IT resource management system according to an embodiment of the present invention. In the present invention, the management server 110 can provide a server configuration automation function using Redfish.

[0080] The unique setting values ​​of a server are stored as metadata in a Server Configuration Profile (SCP), and this metadata can be configured using the Redfish API in the present invention.

[0081] The SCP allows for Export, Preview, and Import, and can be used to apply configuration information to newly created servers via the server configuration automation features of the present invention.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] In one embodiment of the present invention, an AI (Artificial Intelligence) analysis function using Redfish is provided, which collects formatted and unformatted log data from servers and storage devices using SRC (Server remote control) (iDRAC, iLO, IPMI), and performs data classification and pre-processing.

[0086] 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.

[0087] The AI ​​analytics capabilities of the present invention can learn what normal track picks are, spot abnormal traffic, prioritize the risk levels required for users, and analyze and assist with problems.

[0088] Through AI, it analyzes and learns from logs collected during server operation, develops algorithms, and provides a solution to a problem by sending an alert message 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.

[0089] 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.

[0090] 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.

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

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

[0093] 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.

[0094] 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.

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

[0096] Taking a Dell server as an example, to prevent cache data loss due to battery failure in the RAID controller, it is necessary to check the status of the BBU battery and proceed with preemptive replacement. For this, check the Dell server log to confirm the battery full charging efficiency (%), check for equipment with a full charging efficiency of less than 50%, and proceed with battery replacement.

[0097] 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.

[0098] 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.When an event occurs, the IT resource management system of the present invention diagnoses that the event may cause a server failure, warns the server system in advance, and transmits information on solutions in a consolidated manner.

[0099] In this regard, events that occur in a server are very diverse, and events that have never occurred before may occur. In the present invention, some of the events that may occur in such a server are illustrated as examples.

[0100] 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.

[0101] 2. The power usage rate of PDU#1 and PDU#2 in the rack 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 in one of the rack PDUs, so in order to achieve a balance, the Primary-PSU ratio needs to be adjusted.

[0102] 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) of the Dell (registered trademark) server after a kernel update, the management server 110 sends a message to the managed server indicating a possible failure that may occur as a result of the abnormal operation, and also transmits a solution to the predicted failure to the corresponding managed server.

[0103] 4. Service unavailable due to insufficient TCP / IP ports This is a phenomenon where a network TIME_WAIT session remains unclosed if the uptime is 497 days or more on Windows 2008. This occupies a port and becomes a problem when there are no more ports available. This applies to Windows 2008 Server and Windows 2012 Server, and the problem can be resolved by deleting the updated patch.

[0104] 5. Windows(R) 2003~2022 Event Log Generation

[0105] 6. Memory production cycle diagnostics This is to confirm that a specific memory production cycle is defective, the faulty equipment is 13th generation equipment (R730, R930, R630), the faulty OS is Windows 2012 R2 Server with KB3064209 hotfix, and the solution is to remove the corresponding hotfix. In the present invention, the management server 110 diagnoses the memory production cycle of the managed server, determines that a predetermined memory production cycle is defective, and notifies the managed server of this.

[0106] 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.

[0107] After updating the BIOS on the 8.12G server, the temperature sensor does not work properly, causing a continuous beep (Alert_). The solution to this is to diagnose the BIOS 2.5.2 version and update it with the latest firmware.

[0108] 9. Booting not possible after BSOD occurs after patch update This event is a phenomenon caused by the Patch Tuesday update Windows error KB2982791 in August 2014. The target of the error is Windows (registered trademark) 2008 Server, and the error can be resolved through a patch update.

[0109] 10. DNS connection error occurs on a client using Windows 2012 Active Director When logging into a domain account from a server, an error "Incorrect username or password" occurs even if the account and password are correct. This is due to a product issue where AES key generation fails when updating a computer account password when the AD server is Windows Server 2012 R2 and the domain member is Windows Server 2008 R2 or Windows 7, but 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 in Windows Server 2008 R2 and Windows 7, respectively.

[0110] 11. Vulnerabilities in GNU Bash 4.3 Shell It is known that Bash vulnerabilities allow attackers to modify web server content and code, 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 raised. The problem affects Red Hat Enterprise Linux(R) 5, 6, and 7 servers, and the solution is a Bash update.

[0111] 12. Buffer overflow vulnerability in the GNU C library (glibc) When calling the gethostbyname() or gethostbyname2() functions, which are often used when connecting to a network, a vulnerable function is called, allowing an external attacker to execute arbitrary code remotely on the vulnerable server. The problem affects Red Hat Enterprise Linux(R) 5,6,7 servers, and the solution is a GLIBC update.

[0112] 13. Radhat V5 and V6 series OS bugs The bug causes a reboot phenomenon after 208.5 days in all versions of Red Hat Enterprise Linux (registered trademark) 6 or 5 using Intel (registered trademark) CPUs. The problem affects Red Hat Enterprise Linux (registered trademark) 5 and 6 servers, and the solution to the problem is a kernel update.

[0113] 14. Raid Controller Battery Fail I / O performance is reduced due to the inability to use the Raid Controller Cache. The problem is with the Raid Controller Battery for Dell Perc(R) 5i and 6i, and the solution to this problem is to proactively replace the Raid Controller Battery for Dell Perc(R) 5i and 6i every 4 to 5 years.

[0114] 15. System down due to CPU IERR error The affected servers are those using Intel (registered trademark) iBridge V2-compatible CPUs (PE R720, PE R920), and the solution to this problem is to change the BIOS settings. 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.

[0115] 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.

[0116] The present invention proposes an IT resource management system that supports multiple vendors. For example, the present 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 query all information related to the hardware and utilize functions. For ease of explanation of the present invention, an IT resource management system that supports multiple vendors will be explained using manufacturers such as Dell (registered trademark), HP (registered trademark), and Lenovo (registered trademark) as examples.

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

[0118] Referring to Fig. 13, the managed servers are registered (S201). At this time, the target servers can be registered using the management IP information of each server. For example, the target servers can be registered using iDRAC for Dell (registered trademark), iLO for HP (registered trademark), and iMM for Lenovo (registered trademark).

[0119] 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.

[0120] The collected inventory information is then 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.

[0121] Next, 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, can be collected by using the Redfish API, and standardized management of x86 servers can be performed.

[0122] 14 is a flowchart showing a method for preventing failures by analyzing failure logs and patterns in an IT resource management system according to an embodiment of the present invention. The subject that executes each step in FIG.

[0123] 14, when a fault occurs in any of the devices of the managed server (S401), the logs and patterns are analyzed (S403). The analyzed data is then stored (S405). When the fault is resolved (S407), devices similar to the device are classified (S409), and a fault response process is performed on the classified similar devices in advance (S411). In this way, in the present invention, when a fault occurs, the logs and patterns are analyzed and similar devices are automatically classified, thereby making it possible to prevent faults from occurring in similar devices.

[0124] 15 illustrates an operation model for supporting multi-vendor using Redfish API in an IT resource management system according to an embodiment of the present invention. As shown in FIG. 15, the present invention uses Redfish API to collect inventory information about x86 server hardware systems regardless of manufacturer, such as Dell®, HP®, Lenovo®, etc., and to query and utilize the collected information.

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

[0126] In addition, the Redfish API can be used to distribute and install OS and firmware to multiple servers. In this invention, the Redfish API can be used to quickly check the hardware specifications, OS information, firmware information, etc. of each server.

[0127] The present invention can analyze patterns to predict failures and can use hardware logs to facilitate pattern analysis.

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

[0129] In addition, Redfish API supports BIOS and Secure Boot configuration functions, firmware update functions, storage and server network configuration functions, and supports Open Compute Platform, Open stack, SNIA (Storage Networking Industry Association), network switch management, and external storage management.

[0130] iDRAC, a management tool for Power Edge servers, uses Redfish to support the Redfish RESTful API. For example, iDRAC can power the server (Reset, Reboot, Power Control), inventory the server's hardware, monitor and check the status of the server, collect system logs, check the server state changes, and generate alarms.

[0131] 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 can automate the deployment of servers.

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

[0133] The server's unique configuration values ​​are stored as metadata in the server configuration profile (SCP) and can be configured with the Redfish API. In addition, various settings such as BIOS, iDRAC / LC, PERC RAID Controller, NIC, and HBA can be configured via the Redfish API.

[0134] SCP can be exported, previewed, and imported, allowing you to freely apply configuration information to newly built servers. SCP can be shared via methods such as HTTPS, NFS, and CIFS, and can be realized in XML and JSON file formats.

[0135] 16 to 29 are diagrams showing examples of screens of an IT resource management system according to an embodiment of the present invention. Fig. 16 shows an example of an initial screen, which supports a dashboard to view information on inventory and logs automatically collected for a managed server at a glance.

[0136] 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.

[0137] 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).

[0138] 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.

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

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

[0141] 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.

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

[0143] 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 the managed servers.

[0144] Figures 25 and 26 are examples of screens that allow you to check real-time detailed information on the logos collected by all managed servers. Real-time vendor HW error codes are collected and automatically classified, and problematic equipment can be checked for each error code.

[0145] 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.

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

[0147] 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.

[0148] FIG. 30 is a table classifying system equipment according to an embodiment of the present invention, and FIGS. 31 and 32 are tables describing hardware symptoms and their causes according to an embodiment of the present invention.

[0149] 33-34 are flow charts illustrating a method for proactively responding to failures in an IT resource management system according to an embodiment of the present invention.

[0150] 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 risk equipment by referring to the classification table of FIG. 30 (S103). Then, a warning message is sent for the classified risk 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 illustrated, 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.

[0151] Referring to Fig. 34, when a hardware-related problem occurs in a managed server (S301), the management server 110 grasps the fault symptoms (S303). Next, referring to the diagrams of Figs. 31 and 32, the management server 110 checks the symptom code corresponding to the fault symptoms (S305). Then, the management server 110 checks the cause corresponding to the symptom code (S307) and sends a countermeasure report accordingly (S309). Next, the management server 110 executes the 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 Figs. 31 and 32 (S313). Referring to Figs. 31 and 32, examples of fault causes corresponding to symptom codes for each fault symptom according to an embodiment of the present invention are shown.

[0152] 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, Link Failure Count is a NIC driver and firmware problem, NIC Link is Down is a NIC driver and firmware problem, Link status and server confirmation request is a NIC driver and firmware problem, 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 disk BadBlock failure, periodic FAN 6 recognition problem is Fan 6 failure, Fault due to light intensity below 400 is a Gbic failure, NIC GBIC communication failure is a Gbic failure, System infinite reboot is 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 reboot phenomenon is 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, Riser1 failure is a Riser Card problem, Riser2 failure is a Riser Card problem, network redundancy failure is a Network Card problem, PSUIf the Alert yellow LED is lit, it indicates a PSU failure, if an abnormality occurs due to low voltage, it indicates a PSU failure, if there is a problem with the BIOS settings and NIC firmware / driver that prevents PXE boot, if there is a motherboard failure that prevents POST boot, if there is a motherboard failure that prevents LifeCycle connection, if there is an iDRAC Hang symptom, it indicates an iDrac firmware problem, if the iDRAC Network disconnection occurs, it indicates a motherboard failure and iDrac firmware problem, if the iDRAC SNMP service failure occurs, it indicates an iDrac firmware problem, if the server suddenly turns off while in use, it indicates a motherboard problem, if a Medium Error occurs, it indicates a disk failure, if a request to confirm an ERROR Event is a problem caused by an Error Event, if you cannot connect to the CMC, it is caused by a CMC firmware problem.

[0153] In addition, if a DSET analysis request is made, a TSR Log analysis request is made, a failure due to analysis, if an NFS Service startup fails, check the NFS settings and OS settings; if an EXSi version or OS version is not available for connection to vCenter, a NIC Reset is a Network Card problem; if a GPU card is unable to recognize the GPU, an OS Crash occurs, OS Dump analysis; if a network error / dropped packets occurs, it is a Network Card problem; if a CRC error occurs, it is a Network Card problem; if a server switch is turned off, it is a Network Card problem; if communication to the network is not smooth, it is a Network Card problem; if the same slot event occurs after memory replacement, it is a memory failure or motherboard failure; if a disk is in a read-only state and cannot be accessed, it is a disk failure or a RAID configuration problem; if a switch hangs 3 to 4 times a month, it is a motherboard or OS version problem; if an LACP Network Speed ​​problem occurs, it is a Network Card problem; if a cluster failover occurs, it is a cluster setting problem or a HW failure; if an RTSP synchronization failure occurs, it is an OS setting or a Network failure; if a session degradation phenomenon occurs, it is a Network Card or Gbic problem; if an unknown power outage occurs, it is a PSU failure; if a server is slow or hangs, it is an application or HW failure; if a network ping occurs, it is a 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, a Blue Screen indicates a motherboard / BIOS / disk failure, or an OSBooting failures are motherboard / BIOS / disk failures, process down, panic during OS installation is motherboard / BIOS / disk failure, smell from the server is fan / motherboard / PSU problems, solution for NAS inability to connect is network / OS setting problems, 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 due to PSU failure.

[0154] Although the present invention has been described with reference to several preferred embodiments, these embodiments are illustrative and not limiting.

[0155] 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 invention and the scope of rights set forth in the appended claims. [Explanation of symbols]

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

Claims

1. 1. An IT resource management system for managing IT resources including two or more managed servers, comprising: 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 the manager and to a customer terminal that has requested the managed server; The management server provides a server configuration automation function to store unique setting values ​​of each managed server as metadata of a Server Configuration Profile (SCP). IT resource management system.

2. 2. The IT resource management system according to claim 1, An IT resource management system, wherein the management server provides the server configuration automation function using a Redfish API.

3. 3. The IT resource management system according to claim 2, The management server distributes the SCP to the newly constructed managed server and applies the configuration information to the managed server.

4. 2. The IT resource management system according to claim 1, The management server includes: Check the BBU (Backup Battery Unit) cycle of the managed server, and when the predetermined cycle is reached, send the information to the client terminal of the managed server. Check the BBU charging capacity of the managed server, and if the battery charging efficiency falls below a predetermined value, notify the customer terminal of the managed server of this information, Check the remaining capacity of the BBU of the managed server, and if the remaining battery capacity is below a predetermined value, notify the customer terminal of the managed server of this information, Checks the BBU write policy of the managed server, and if the write policy is changed, notifies the client terminal of the managed server of the change. Check the battery full charging efficiency (%) through the log of the managed server, and send a message to the customer terminal of the managed server to notify the battery replacement for the equipment whose full charging efficiency is less than a predetermined value. IT resource management system.

5. 2. The IT resource management 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 IT resource management system according to claim 5, The management server, when there is a firmware update event, including an emergency firmware update, initiates firmware updates for all managed servers.

7. 2. The IT resource management system according to claim 1, The management server 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 similar equipment to the failed equipment and performs response processing for the classified similar equipment in advance of a failure. This is an IT resource management system.

8. 2. The IT resource management system according to claim 1, The management server classifies similar equipment that is likely to cause a failure into dangerous equipment by referring to a classification table when a hardware-related problem occurs in the managed server, sends a warning message to the classified dangerous equipment, and takes countermeasures in advance of a failure, in an IT resource management system.

9. 9. The IT resource management system according to claim 8, The classification table includes specific similarity judgment criteria for system equipment, including 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 an IT resource management system.

10. 10. The IT resource management 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 the failure causes corresponding to the 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, executes 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. 11. The IT resource management system according to claim 10, The list may include: 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 number of Link Failure Counts may be due to NIC driver and firmware issues. 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 CPU performance degradation 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 FAN 6 recognition issues can be caused by Fan 6 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 iDRAC can be caused by iDrac firmware issues, 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 redundant transfer 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. Abnormalities caused by low voltage include PSU failure, BIOS settings that prevent PXE boot, and NIC firmware / driver problems, 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, The iDRAC SNMP service failure can be caused by an iDrac firmware issue, If the server suddenly shuts off while in use, it is likely due to a motherboard problem. A Medium Error may occur due to a disk failure, The ERROR Event confirmation request is for problems caused by Error Events, problems with CMC firmware that prevent connection to CMC, DSET analysis requests are made based on the following: TSR Log analysis requests are for issues caused by the analysis, NFS Service startup failure: Check NFS settings and OS settings, EXSi version unable to connect to vCenter, OS version problem, 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 off phenomenon is due to a network card problem. The problem of communication to the network (bonding) not being smooth is due to a problem with the network card, 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 (0x00004f) may 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 delay may be due to 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 / mainboard / memory issues, If the server processing slows down significantly, it may be due to CPU / PSU / motherboard / memory / disk problems. Server won't power up due to PSU failure, including troubleshooting IT resource management 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