Method for managing server in it resource management system

The IT resource management system addresses server failure challenges by standardizing operations and using the Redfish API for proactive failure prediction and automated management, enhancing efficiency and security while reducing costs.

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

Patent Information

Application Number
JP2024070587
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 lacking specialized server administrators, resulting in significant downtime and losses.

Method used

A server management method in an IT resource management system that collects data from multiple servers, standardizes operations, and uses the Redfish API to monitor and manage x86 servers, including OS, firmware, and hardware information, enabling proactive failure prediction, firmware updates, and automated management.

Benefits of technology

The system improves operational efficiency, reduces operational costs, enhances security, and facilitates convenient management of multiple servers by preemptively predicting failures, providing warnings, and automating responses to minimize downtime.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156644000001_ABST
    Figure 2024156644000001_ABST
Patent Text Reader

Abstract

To provide a method for preventing faults that may occur in servers in advance to reduce damages due to the server faults.SOLUTION: A management method in an IT resource management system for managing IT resources including two or more servers to be managed includes the steps of: collecting hardware-related data and software-related data from the servers 10-40 to be managed, in a management server 110; and identifying and managing status of the servers to be managed, based on the data collected from the management server, and providing various server management information including management service statistical data and management service reports related to the managed status of the servers, to an administrator terminal 120 and a customer terminal 130.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 management technique for systematizing and standardizing IT (Information Technology) resources such as servers, storage, and networks. [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 large-capacity servers, failures can occur frequently due to various factors such as the operation of various application programs, storage, reading, and transfer of data, etc. Therefore, each company assigns separate server administrators to manage these 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. Even if a server administrator with specialized skills is employed for server management, if the server administrator is located far away from the servers due to a business trip or other reason, it is difficult for the administrator to be notified of the status of the servers promptly when a server failure occurs, making it difficult to deal smoothly with the server failure. Even if the server administrator is notified of the server failure, it is difficult to deal with it immediately because he or she is located far away, and this can ultimately result in huge losses such as the server going down.

[0006] In the past, in a server integrated management system that integratedly manages multiple servers, if a failure occurs in a server, this is detected and the failure is recovered after the fact. However, in this conventional method of recovering from a failure, the operation of the server is interrupted during the recovery period, resulting in losses due to the interruption of use of the server, and there are problems with the loss due to the manpower and costs required for recovery. [Prior art documents] [Patent documents]

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

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

[0009] 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]

[0010] To achieve the above object, the present invention relates to a server management method in an IT resource management system for managing IT resources including two or more managed servers.

[0011] The server management method includes the steps of collecting relevant data, grasping and managing the current status of each managed server based on the data collected from the management server, and providing various server management information including related management service statistical data and management service reports to an administrator terminal and a customer terminal.

[0012] In a server management method according to one embodiment of the present invention, the management server may further include a step of storing information including an OS, BIOS, and firmware collected from each managed server, a step of distributing firmware to a corresponding managed server when a firmware update event including an emergency firmware update occurs, and a step of the management server checking firmware information of the managed server and confirming whether the firmware update has been completed.

[0013] 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

[0014] 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 server failures in advance and reducing damage caused by server failures.

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

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

[0017] 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]

[0018] [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 server management method 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 server configuration task automation function 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 advance in an IT resource management system according to an embodiment of the present invention. [Figure 15] 1 illustrates an operational model for supporting multi-vendor 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. [Diagram 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] 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] 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

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

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

[0021] The terms used in this application are merely used to describe examples in specific implementations and are not intended to limit the present invention.

[0022] The singular includes the plural unless the context clearly indicates otherwise. 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 understood that one or more other features do not preclude the presence or additional possibility of 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 a person of ordinary skill in the art to which the present invention belongs. Terms such as commonly used predefined terms should be interpreted as having a meaning consistent with the contextual meaning of the relevant art, and should not be interpreted as ideal or overly formal meanings unless expressly defined in this application.

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

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

[0026] The present invention relates to a server management method in an IT resource management system for managing IT resources including two or more managed servers, and includes the steps of collecting hardware-related data and software-related data from the managed servers, and grasping and managing the current status of each managed server based on the data collected from the management server, and providing various server management information including related management service statistical data and management service reports to an administrator terminal and a customer terminal.

[0027] In a server management method according to one embodiment of the present invention, the method may further include a step in which the management server stores information including an OS, BIOS, and firmware collected from each managed server, a step in which the management server distributes firmware to a corresponding managed server when a firmware update event including an emergency firmware update occurs, and a step in which the management server checks firmware information of the managed server and confirms whether the firmware update has been completed.

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

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

[0030] 1 and 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. The administrator terminal 120 is a terminal used by an administrator who manages the IT resource management system.

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

[0032] 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 smartphone, etc. In one embodiment of the present invention, the user terminal is a concept including the administrator terminal 120 and the customer terminal 130.

[0033] The database 112 stores data related to the managed servers 10, 20, 30, 40. The management server 110 collects data from the managed servers 10, 20, 30, 40, grasps and manages the current status of each managed server, and provides various server management information including related management service statistical data and management service reports 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 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.

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

[0039] 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, when a predetermined event occurs in the managed server (10, 20, 30, and 40), 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 the event.

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

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

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

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

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

[0045] 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 customer terminal 130 on a quarterly basis.

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

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

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

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

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

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

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

[0053] FIG. 2 conceptually illustrates the operational process of an IT resource management 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 illustrated.

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

[0055] Then, the collected data is classified, 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, data is reclassified, and data rows are generated.

[0056] Additionally, a page is called up on the user terminal using Flask, and a data analysis module searches the database 112, performs analysis, and performs data visualization, which is then transmitted to a Flask Response User Web page.

[0057] 3 is a flowchart showing a server management method in an IT resource management system according to an embodiment of the present invention. The embodiment of FIG. 3 is an embodiment using the Redfish API.

[0058] Referring to Fig. 3, the management server 110 stores information such as OS, BIOS, firmware, etc. collected from each managed server (S2010). Then, 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). Then, 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. Fig. 4 is an example of a main dashboard screen.

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

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

[0061] The example screen in Figure 4 displays server, storage, and network operation status information, providing pie charts for the total number of servers in operation and the number of servers by manufacturer. It also provides monthly performance status information, providing bar graphs for the number of tasks, changes, and failures.

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

[0063] 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 equipment installations and changes to servers, etc., and provides reliable data in real time.

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

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

[0066] In addition, to provide related 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 operation equipment by year and vendor, a list of recently registered equipment, and additional customization methods.

[0067] 6 is an example of a screen displaying the performance management function. In the present invention, the management server 110 provides a performance management function for managing scheduled tasks, items changed by tasks, etc., history after the occurrence of a fault, and improvement results.

[0068] In this way, when the cause of a failure is clear, the present invention can record and manage the failure to prevent it from reoccurring, assign a person in charge to the matters that need improvement, and check the improvement results. In addition, it can provide various performance status statistics according to the state such as by year, month, data center location, before operation service, idle, etc.

[0069] The example screen in Figure 6 displays job history including online and offline job history management, fault history from the fault handling history manager, change history from the system change history manager, and various statistical graphs relating to backup schedule management and performance status.

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

[0071] The example screen in Figure 7 displays a menu for daily inspections that allows you to set the collection synchronization cycle, customize automated collection values, and register collection schedule information, as well as automatically classify equipment that requires daily inspections and check equipment with MGMT (Management Repository) connection errors.

[0072] 7, the management server 110 can display different colors depending on the equipment status in the daily inspection menu. That is, if there is no abnormality in the equipment, it can be displayed with symbol 1 (green circle), if the equipment requires inspection by the administrator ("inspection required"), it can be displayed with symbol 2 (red circle), if the equipment requires inspection by the naked eye ("visual inspection required"), it can be displayed with symbol 3 (yellow circle), and if it is not possible to connect to MGMT ("MGMT inaccessible"), it can be displayed with symbol 4 (gray circle).

[0073] 8 is an example of a screen displaying the automation management function. 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.

[0074] 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 servers, storage, networks, SANs, etc., thereby enabling faster decision-making when performance issues or failures occur.

[0075] Referring to Figure 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 or failures occur.

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

[0077] 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., thereby improving maintenance efficiency and reducing operational costs.

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

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

[0080] Redfish events are based on HTTPS, which transfers event information from the server to the Redfish client. When an alarm occurs in management, it is transferred to HTTP POST and can be received via HTTP GET.

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

[0082] 11 is an exemplary diagram illustrating a function of automating server configuration tasks 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 tasks using Redfish.

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

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

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

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

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

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

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

[0090] The learned data model is then used to predict equipment status and faults, and when important problems occur, alarm messages are sent to the user's device via text, email, etc.

[0091] The AI ​​analysis function of the present invention can learn what normal traffic is, discover abnormal traffic, set the priority of risk levels required by the user, and analyze and support problems. Furthermore, the AI ​​analyzes and learns from logs collected during server operation, develops algorithms, and provides a solution to the problem by transmitting an alarm 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 can prevent problems in advance, quickly share the occurrence of problems, and perform real-time analysis.

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

[0093] In addition, the management server 110 can check the BBU charging capacity of the managed server, and if the battery charging efficiency falls below a predetermined value, can notify the customer terminal of the managed server of the content. For example, the management server 110 can check the BBU charging capacity of the managed server, and if the battery charging efficiency falls below 40%, can notify the customer terminal of the managed server of the content.

[0094] The management server 110 can check the remaining capacity of the BBU of a managed server, and if the remaining battery power is less than a predetermined value, can notify the customer terminal of the managed server of the content. For example, the management server 110 can check the remaining capacity of the BBU of a managed server, and if the remaining battery power is less than 10%, can notify the customer terminal of the managed server of the content.

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

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

[0097] In this invention, among various functions of a server, BBU (Backup Battery Unit) will be exemplified for explanation. Taking Dell (registered trademark) server as an example, in order to prevent cache data loss due to battery failure of RAID controller, it is necessary to check the battery status of BBU and proceed with preemptive replacement.

[0098] For this purpose, the battery full charging efficiency (%) is checked by checking the Dell server log, and if any equipment has a full charging efficiency of less than 50%, a battery replacement is recommended. After 36 months, the battery charging efficiency naturally decreases to about 70%, and taking this into consideration, a battery with an additional decrease of about 20% can be determined to have poor charging efficiency.

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

[0100] In the IT resource management 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 server system in advance, and information on a solution is transmitted in a comprehensive manner. In this regard, events that occur in a server are very diverse, and new events that have not occurred before may occur.

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

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

[0103] 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, so in order to adjust the balance, the Primary-PSU ratio needs to be adjusted.

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

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

[0106] 5. Windows 2003~2022 Event Log Generation 6. Memory production cycle diagnostics This is to confirm that a specific production cycle of a specific memory is defective, the faulty equipment is 13th generation equipment (R730, R930, R630), the faulty OS is Windows 2012 R2 Server with the 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 servers, determines that a predetermined memory production cycle is defective, and notifies the managed servers accordingly.

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

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

[0109] 9. After patch update, BSOD occurs and booting is not possible This event is a phenomenon caused by the Patch Tuesday update Windows error KB2982791 in August 2014. The affected system is a Windows 2008 server, and the error can be resolved through a patch update.

[0110] 10. DNS connection error occurs on a client using Windows 2012 Active Director When logging in to a domain account from a server, an error "User name or password is incorrect" occurs even if the account and password are correct. This is due to a product problem where AES key generation fails when updating the computer account password when Windows Server 2008 R2, Windows 7, or later does not use DES-CBC-MD5 or DES-CBC-CRC encryption, but only AES256-CTS-HMAC-SHA1-96, AES128-CTS-HMAC-SHA1-96, or RC4-HMAC encryption is used, but the AD server is Windows Server 2012 R2 and the domain member is Windows Server 2008 R2 or Windows 7.

[0111] 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. Other 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,7 servers, and the solution is a Bash update.

[0112] 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 remotely execute arbitrary code on the vulnerable server. The problem affects Red Hat Enterprise Linux(R) 5,6,7 servers, and the solution is a GLIBC update.

[0113] 13. Radhat V5 and V6 series OS bugs This is a bug that causes a reboot phenomenon to occur after 208.5 days on all versions of Red Hat Enterprise Linux(R) 6 or 5 that use Intel(R) CPU. The problem affects Red Hat Enterprise Linux(R) 5 and 6 servers, and the solution to the problem is a kernel update.

[0114] 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(R) Perc 5i and 6i, and the solution to this problem is to proactively replace the Raid Controller Battery for Dell(R) Perc 5i and 6i every 4 to 5 years.

[0115] 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 was to change the BIOS settings. For example, set System Profile Settings to Custom, CPU Power Management to Maximum Performance, C1E to Disabled C States Disabled, and Monitor / Mwait to Disabled.

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

[0117] This invention proposes an IT resource management system that supports multiple vendors. For example, this invention stores information about 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, enabling the utilization of functions.

[0118] For the convenience of explaining the present invention, an IT resource management system that supports multiple vendors will be described by taking manufacturers such as Dell (registered trademark), HP (registered trademark), and Lenovo (registered trademark) as examples.

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

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

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

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

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

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

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

[0126] FIG. 15 illustrates an operational model for supporting multi-vendor using Redfish API in an IT resource management system according to an embodiment of the present invention.

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

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

[0129] In addition, the Redfish API can be used to distribute and install OS and firmware to multiple servers. In the present invention, the Redfish API can be used to quickly check the hardware specifications, OS information, firmware information, etc. of each server. In addition, the present invention can analyze patterns to predict failures, and the hardware log can be used to perform the pattern analysis.

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

[0131] Additionally, the Redfish API supports BIOS and Secure Boot configuration functions, firmware update functions, and storage and server network configuration functions.

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

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

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

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

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

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

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

[0139] 16 to 29 are diagrams showing example screens of an IT resource management system according to an embodiment of the present invention.

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

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

[0142] In the example screen of Fig. 18, each part is represented by symbol 5 (red circle) so that when a problem with the managed server is confirmed, it can be easily recognized, and normal parts are represented by symbol 6 (green circle). Fig. 19 is an example screen where you can check the real-time management information of the entire managed server, including firmware (F / W) information.

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

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

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

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

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

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

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

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

[0151] FIG. 29 is an example of a screen showing an example of the service report function, and shows report contents including the problem at the time of occurrence, the solution to the problem, and measures to prevent recurrence.

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

[0153] 33-34 are 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.

[0154] 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), sends a warning message for the classified dangerous equipment (S105), and takes countermeasures before a failure occurs (S107).

[0155] Referring to the classification table of FIG. 30, specific criteria for determining similarity of system equipment in one embodiment of the present invention are illustrated, such as 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, classification of equipment of the same firmware version, etc.

[0156] Referring to Fig. 34, when a hardware-related problem occurs in a managed server (S301), the management server 110 grasps the fault symptoms (S303). Then, referring to Figs. 31 and 32, the management server 110 checks a 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). 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 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.

[0157] 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, many Link Failure Counts are NIC driver and firmware problems, NIC Link is Down is a NIC driver and firmware problem, Link Status and Server Inspection Request are NIC driver and firmware problems, HOST_DOWN is a NIC driver and firmware problem, Yellow light on the 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 are not 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 Fan 6 failure, Fault due to light intensity below 400 is Gbic failure, NIC GBIC communication not possible, 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, synchronization errors with the vCenter agent are an EXSi version and OS version problem, 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 cutoff failure is an HBA Gbic and Card problem, Riser1 not being recognized is a Riser Card problem, Riser2 not being recognized is a Riser Card problem, network duplex failure is NetworkIf the symptom is a card problem, PSU Alert yellow LED is lit means PSU failure, abnormality due to low voltage is PSU failure, PXE boot is not possible due to BIOS setting and NIC firmware / driver problems, POST boot is not possible due to motherboard failure, LifeCycle connection is not possible due to motherboard failure, iDRAC Hang symptoms are iDrac firmware problems, iDRAC Network disconnection is motherboard failure and iDrac firmware problems, iDRAC SNMP service failure is an iDrac firmware problem, server suddenly turns off while in use is a motherboard problem, Medium Error occurs is a disk failure, ERROR Event confirmation request is a problem caused by an Error Event, and CMC connection is not possible is due to a CMC firmware problem.

[0158] 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 not recognized is a GPU card failure, OS crash occurs is OS dump analysis, Network error / dropped packet occurs is a problem with the network card, CRC error occurs is a problem with the network card, Server switch is off is a problem with the network card, Problem of communication to the network (bonding) not being smooth is a problem with the network card, Occurrence of the same slot event after memory replacement is a memory failure or motherboard failure, Disk failure that cannot be accessed in Disk Read Only state or RAID configuration problem, Symptom of switch hanging 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 phenomenon occurs is a problem with the network card or Gbic, Unknown power cut is a PSU failure, Server delay and hanging phenomenon is an application or HW failure, Network Ping Loss indicates a network card or Gbic problem, LoadAvg increase indicates CPU check is required, Fatal Error occurs when there is a PCI Card or Riser Card problem, Stop or performance degradation during PXE installation indicates a network card or Gbic problem, Blue Screen (0x00004f) occurs when there is a motherboard / BIOS / disk / memory failure, Blue Screen is a motherboard / BIOS / disk failure, OS Booting failure is a motherboard / BIOS / disk failure, Process Down and panic during OS installation are motherboard / BIOS / disk failure, Smell from server is a fan / motherboard / PSU problem, NAS connection failure solution is network / OS setting problem, KVM connection failure motherboard / KVM cable / KVM problem, Disk AmberAn LED indicates a disk failure, a delay post boot indicates a motherboard / fan / PCI / memory problem, a solution to a power failure is a PSU failure, reduced teaming performance is a network / OS setting problem, a VD Bad Block is a disk failure, an HBA Loop is an HBA failure, a firmware / disk driver problem where Raid configuration information is not visible, a firmware / disk driver problem where volume cannot be recognized, a Kernel Panic is an OS / App problem, a server reboot when using maximum performance is a CPU / PSU / motherboard / memory problem, server processing slows down significantly due to a CPU / PSU / motherboard / memory / disk problem, and a server not being able to power on is caused by a PSU failure.

[0159] Although the present invention has been described above using several preferred embodiments, these embodiments are illustrative and not limiting. It will be understood that those skilled 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 presented in the appended claims. [Explanation of symbols]

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

Claims

1. A server management method in an IT resource management system for managing IT resources including two or more managed servers, comprising: collecting, at a management server, hardware-related and software-related data from the managed servers; Based on the data collected from the management server, grasp and manage the current status of each managed server, and provide various server management information including related management service statistical data and management service reports to an administrator terminal and a customer terminal; A method for managing a server, including:

2. 2. The server management method according to claim 1, The management server stores information including OS, BIOS, and firmware collected from each managed server; the management server distributing firmware to a corresponding managed server when a firmware update event occurs, including an emergency firmware update; the management server checking firmware information of the managed server to determine whether firmware update has been completed; Further comprising a server management method.

3. 3. The server management method according to claim 2, The management server uses 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 performs standardized management of the x86 servers.

4. 2. The server management method 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 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. How to manage your server.

5. 2. The server management method according to claim 1, A server management method in which a management server analyzes logs and patterns when a failure occurs in equipment of a managed server, stores the analyzed data, and when the failure is resolved, classifies similar equipment to the corresponding equipment and performs pre-failure response processing for the classified similar devices.

6. 2. The server management method according to claim 1, A server management method in which, when a hardware-related problem occurs in a managed server, a management server refers to a classification table, classifies similar equipment having a high possibility of causing a failure as dangerous equipment, sends a warning message regarding the classified dangerous equipment, and takes countermeasures in advance of a failure.

7. 7. The server management method according to claim 6, The classification table includes specific criteria for judging similarity of 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.

8. The server management method according to claim 7, 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.

9. 9. The server management method according to claim 8, 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 can be caused by NIC driver and firmware issues, Link status and server inspection requests can help troubleshoot NIC driver and firmware issues, HOST_DOWN occurs 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 can fix BIOS firmware issues, Correctable memory error is a problem with memory and BIOS firmware. The CPU performance degradation is due to a BIOS firmware problem. Memory problems and BIOS firmware problems that are not indicated by the Memory and Slot labels include Gbic failures, System infinite reboots are caused by BIOS firmware issues, LCD Panel specific message output indicates iDrac firmware issue, Repeated error messages on iDRAC may be due to iDrac firmware issues, The vCenter agent and sync error may be due to EXSi version, 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 duplication failure is caused by a network card problem, PSU Alert Yellow LED on indicates PSU failure. Abnormalities caused by low voltage include PSU failure, PXE boot failure BIOS setting, NIC firmware / driver problem, 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, an iDrac firmware problem, iDRAC SNMP service failure may be caused by iDrac firmware issue, The symptom of the server suddenly shutting down during use is a motherboard problem, A medium error occurs when a disk failure occurs. The ERROR Event confirmation request is for problems caused by an Error Event, inability to connect to CMC, problems with CMC firmware, DSET analysis requests are made based on the following: TSR Log analysis requests are for issues caused by the analysis, The failure to start the NFS service may be due to the following: Check the NFS settings and OS settings, EXSi version and OS version issues that cannot connect to the vCenter, NIC Reset is a solution to network card problems, If the GPU cannot be recognized, it may be due to a GPU card failure. When OS crash occurs, OS dump analysis, Network error / dropped packets may be caused by a problem with the network card. CRC errors occur due to network card problems. The server switch is turned off due to a network card problem. Problems with smooth communication to the network (Bonding) may be due to network card problems, The occurrence of the same slot event after memory replacement may indicate a memory failure or motherboard failure, a disk failure that is inaccessible due to a 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 failure may be due to OS settings, network failure, The occurrence of session degradation may be due to network card or Gbic problems. 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 network card or Gbic problem. If LoadAvg increases, check your CPU. Fatal Error occurs due to a problem 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 is caused by 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, The degradation of Teming performance may be due to network / OS configuration issues, VD Bad Block indicates a disk failure. HBA loops can occur due to 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 / motherboard / memory problems, server processing may be significantly slowed down due to CPU / PSU / motherboard / memory / disk problems, If the server does not power up, it may be due to a PSU failure, Including dealing with the causes of How to manage your server.

Citation Information

Patent Citations

  • Computer supervisory system

    JP1995253956A

  • 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

  • Server management system for supporting multi-vendor

    JP2024050522A