KR20230073469A - Server management system capable of responding to failure - Google Patents

Abstract

The present invention relates to a server management system for managing a management target server requested by a customer, comprising: a manager terminal used by a manager who manages the server management system; a customer terminal used by each customer requesting the management target server; and a management server for collecting data from the management target server to recognize and manage the current status of each management target server, and providing various server management information including management service statistics data and management service reports related thereto to the manager terminal and the customer terminal. According to the present invention, a failure response function, a server management function, and a service statistics function are provided to enable a server manager to comprehensively manage servers, thereby enabling the servers to be managed more conveniently and more efficiently.

Description

Server management system capable of responding to failure

The present invention relates to a server management system for managing servers, and more particularly, server management that analyzes failure patterns occurring in servers, manages server status and history, and provides various functions for related statistics and services. It's about the system.

[0002] Recently, as computers have increased in capacity and speed, computer failures due to system errors or viruses have frequently occurred. In particular, in the case of a large-capacity server, errors due to various factors such as operation of various application programs and data storage, reading, and transmission may frequently occur. Therefore, in each company, a separate server manager who manages such a server is resident to manage the server and to handle it when a failure occurs.

However, server management requires specialized skills, and considerable costs are required to employ such specialized personnel. Therefore, in particular, small companies, etc., do not employ professional technicians as server administrators, but select an appropriate person from among existing personnel in the company and place them as server administrators. In such a case, it is difficult to smoothly manage the server, and moreover, it is almost impossible to smoothly cope with server failure.

In addition, even when a server manager with specialized skills is employed for server management, if the server manager is away from the server due to business trips, etc., it is difficult to promptly notify the manager of the server's situation when a server failure occurs. In case of occurrence, it was difficult to smoothly cope with it. Furthermore, even if the server manager is notified of the occurrence of a server failure, it is difficult to respond immediately to it because it is located in a remote location, which can result in huge losses such as the server being down.

Conventionally, in a server integrated management system that integrates and manages a plurality of servers, when a failure occurs in a certain server, it is detected and the failure is restored after the fact. However, this conventional post-failure recovery method has problems in that the operation of the server is stopped during the period of restoring the server in which the failure occurred, loss occurs due to server use suspension, and damage due to manpower and cost required for recovery is large. there is.

Republic of Korea Patent Publication 10-2015-0124642

The present invention has been devised to solve the above problems, analyzes failure patterns occurring in servers, warns failures when a specific event occurs, thereby preemptively preventing failures, and managing the history of servers. to provide management functions, related service statistics, and service reports.

Its purpose is to provide a server management system.

The object of the present invention is not limited to the object mentioned above, and other objects not mentioned will be clearly understood by those skilled in the art from the description below.

To achieve the above object, the present invention relates to a server management system for managing a management target server requested by a customer, wherein a manager terminal used by a manager who manages the server management system, and each customer who has requested the management target server It collects data from the customer terminal and the management target server, grasps and manages the current status of each management target server, and provides various server management information, including management service statistical data and management service reports, to the manager terminal and the management target server. and a management server provided to the customer terminal.

The management server analyzes the failure pattern of the management target server to provide a preventive analysis function to prevent similar failures from occurring, and through the preventive analysis function, when a predetermined event occurs in the management target server, a failure according to the occurred event may occur. An expected failure occurrence message warning that there is a failure may be preemptively transmitted to the customer terminal requesting the management target server.

The management server may provide a history management function for managing installation, failure, and technical support records of the management target server.

The management server may provide a delivery management function for managing the delivery history of the management target server.

When an equipment-related event occurs in the management target server, the management server classifies dangerous equipment according to predetermined classification criteria, sends a warning message about the dangerous equipment to the manager terminal and the corresponding customer terminal, and sends a warning message to the corresponding dangerous equipment. It is possible to take pre-failure countermeasures for

When an equipment-related event occurs in the management target server, the management server identifies a failure symptom of the corresponding equipment, analyzes the cause according to a failure code corresponding to the corresponding failure symptom, and sends a report including a failure response plan to the manager terminal. And it is sent to the corresponding customer terminal, and failure response measures for the corresponding equipment may be performed.

According to the present invention, by providing a failure response function, a server management function, and a service statistics function so that the server manager can comprehensively manage the servers, there is an effect of enabling the server to be managed more conveniently and efficiently.

In addition, according to the present invention, it is possible to process and deliver data suitable for the customer's needs by analyzing the failure pattern to the customer who owns the server, preemptively responding to the failure, and providing a server management function. There is an effect.

1 conceptually illustrates the overall configuration of a server management system according to an embodiment of the present invention.
2 to 14 illustrate screen examples of a server management system according to an embodiment of the present invention.
15 is a diagram of classifying system equipment according to an embodiment of the present invention.
16 and 17 are diagrams describing hardware symptoms and their causes according to an embodiment of the present invention.
18 to 19 are flowcharts showing a failure prevention method in a server management system according to an embodiment of the present invention.

Since the present invention can make various changes and have various embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, the terms "include" or "have" are intended to designate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, but one or more other features It should be understood that the presence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded.

Unless defined otherwise, 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 the present invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in the present application, it should not be interpreted in an ideal or excessively formal meaning. don't

In addition, in the description with reference to the accompanying drawings, the same reference numerals are given to the same components regardless of reference numerals, and overlapping descriptions thereof will be omitted. In describing the present invention, if it is determined that a detailed description of related known technologies may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted.

1 conceptually illustrates the overall configuration of a server management system according to an embodiment of the present invention.

Referring to FIG. 1 , the server management system of the present invention includes a management server 110 , a manager terminal 120 and a customer terminal 130 .

The manager terminal 120 is a terminal used by a manager who manages a server management system.

The customer terminal 130 is a terminal used by each customer who has requested the management target server 10 , 20 , 30 , or 40 .

In one embodiment of the present invention, the manager terminal 120 and the customer terminal 130 may be implemented in various terminal types capable of wired and wireless communication such as a desktop computer, a laptop computer, a tablet PC, a mobile phone, a mobile phone, and a smart phone.

The management server 110 collects data from the management target servers 10, 20, 30, and 40, identifies and manages the current status of each management target server, and manages various types of management service statistical data and management service reports. Server management information is provided to the manager terminal 120 and the customer terminal 130 .

The management server 110 analyzes failure patterns of the managed servers 10, 20, 30, and 40 to provide a preventive analysis function to prevent similar failures from occurring. , 30, 40), when a predetermined event occurs, an expected failure occurrence message warning that a failure may occur according to the occurred event may be preemptively transmitted to the customer terminal requesting the management target server.

The management server 110 may provide a history management function for managing installation, failure, and technical support records of the management target servers 10 , 20 , 30 , and 40 .

The management server 110 may provide a delivery management function for managing delivery records of the management target servers 10 , 20 , 30 , and 40 .

When an equipment-related event occurs in the management target server, the management server 110 classifies dangerous equipment according to predetermined classification criteria and sends a warning message about the dangerous equipment to the manager terminal 120 and the corresponding customer terminal, It is possible to take pre-failure countermeasures for the relevant dangerous equipment.

When a device-related event occurs in the management target server, the management server 110 identifies a failure symptom of the corresponding equipment, analyzes the cause according to a failure code corresponding to the corresponding failure symptom, and sends a report including a failure response plan to the administrator. It can be sent to the terminal 120 and the corresponding customer terminal, and take measures to cope with the failure of the corresponding equipment.

In the present invention, the management server 110 may provide a data delivery service function of processing and delivering data related to the management of the management target server according to the request of the customer terminal 130 .

In addition, the management server 110 analyzes critical failures of the server to be managed and propagates the same case to prevent server failures in advance. It can be provided to the terminal 130.

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 issues for each part.

The present invention relates to a server management system for managing a plurality of management target servers (10, 20, 30, 40) requested by a customer.

In one embodiment of the present invention, the server to be managed, which is the server to be managed, may be various servers, for example, Dell server 10, HP server 20, IBM server 30, X86 server 40 can

The management target servers 10 , 20 , 30 , and 40 and the management server 110 communicate through various wired and wireless communication methods, and for example, may communicate through HTTP communication or a POST transmission method in JSON format.

In addition, the management target servers 10, 20, 30, and 40 may automatically execute scripts according to a predetermined schedule in various x86 servers in a large-scale computing environment.

The manager accesses the management server 110 through the manager terminal 120, executes a batch program according to a schedule determined in the management server 110, and manages the change history by comparing with existing data.

The management server 110 automatically collects hardware information and software information of the management target servers 10, 20, 30, and 40, identifies the current status of each server based on this, and provides management services according to the requirements of each server. provides

The management server 110 may check the BBU (Backup Battery Unit) cycle of the management target server and transmit the content to the customer terminal of the management target server when a predetermined cycle is reached.

In addition, the management server 110 may check the BBU charging capacity of the management target server and notify the customer terminal of the management target server of this content when the charging efficiency of the battery decreases below a predetermined value. For example, the management server 110 may check the BBU charging capacity of the management target server and notify the customer terminal of the management target server of this content when the charging efficiency of the battery is reduced to 40% or less.

The management server 110 may check the BBU remaining capacity of the management target server and notify the customer terminal of the management target server of the content when the battery remaining amount is less than a predetermined value. For example, the management server 110 may check the BBU remaining capacity of the management target server and notify the customer terminal of the management target server of this content when the remaining battery capacity is 10% or less.

In addition, the management server 110 may check the BBU write policy of the management target server and notify the customer terminal of the management target server of this content when the write policy is changed.

As for the server integrated management system that integrates and manages a plurality of servers of the present invention, various functions of the server are diagnosed, failures are predicted and warned in advance, and solutions are presented together. In the present invention, a BBU (Backup Battery Unit) among various functions of a server will be described as an example.

Taking the Dell server as an example, in order to prevent cache data loss due to battery failure of the RAID controller, it is necessary to check the battery status of the BBU and proceed with preemptive replacement. To this end, check the full charging efficiency (%) of the battery through the log check of the Dell server, check the equipment whose full charging efficiency is less than 50%, and proceed with replacing the battery. After 36 months, the battery charging efficiency naturally decreases to around 70%, and considering this, a battery with an additional decrease of about 20% can be determined as poor charging efficiency.

The integrated server management system of the present invention performs BBU periodic inspection, charging capacity inspection, remaining capacity inspection, and write policy inspection, thereby preventing cache data loss and risk factors for battery status in advance. can do.

In the server management system of the present invention, when a certain event occurs, it is diagnosed that a server failure may occur through the corresponding event, a warning is given to the system of the corresponding server in advance, and information on a solution is delivered together. In this regard, events occurring in the server are very diverse, and unprecedented events may newly occur. Now, in the present invention, several events among events that may occur in such a server will be exemplified.

1. Fan noise (Reading 12,000 RPM or higher) on product Dell R720 server applied with iDRAC7 version 1.51.51.

As a workaround for this, it is recommended to downgrade to iDRAC7 1.46.45 version.

2. The power utilization in Rack PDU#1 and PDU#2 is biased toward PDU#1.

Referring to FIG. 17, not only the Dell server, but also the HP server is set to operate in Active Standby as the default of the power supply, so power is supplied to the Rack PDU There is a situation where it is driven to one side, but in order to balance, it is necessary to match the ratio of Primary - PSU.

3. OS abnormal operation after kernel update of Dell server products 12th to 14th generation.

At this time, the management server 110 sends an expected failure occurrence message that may occur due to an abnormal operation on the operating system (OS) after updating the kernel in the dell server to the corresponding management target server. , and along with it, the solution for the expected failure is delivered to the corresponding management target server.

4. Unavailability of service due to lack of TCP/IP ports.

This is a phenomenon in which the Network TIME_WAIT session remains without being closed when the Uptime is 497 days or more in Windows 2008. This causes ports to be occupied and becomes a problem when there are no more ports. Windows 2008 Server and Windows 2012 Server are targeted, and the failure can be resolved by removing the updated patch.

5. Windows 2003 ~ 2022 event log occurrence.

6. Memory production cycle diagnosis.

This is to confirm that a specific production cycle of a specific memory is defective. The target of failure is 13th generation equipment (R730, R930, R630), and the failure OS is Windows 2012 R2 Server with KB3064209 hotfix. , and the workaround is to remove the hotfix.

In the present invention, the management server 110 diagnoses the memory production cycle of the management target server, determines a predetermined memory production cycle as defective, and informs the corresponding management target server of this information.

7. If you are using a PCIe type SSD, response stops in device settings.

The workaround for this is to update BIOS 1.1.4 -> 1.2.10.

8. After updating the BIOS of the 12G Server, the temperature sensor does not work properly and the alert_ continues to sound.

A workaround for this is to diagnose the BIOS 2.5.2 version and update to the latest firmware.

is to update

9. Unable to boot after BSOD after patch update

This event is caused by the August 2014 Patch Tuesday update windows error KB2982791.

The target of failure is windows2008 server, and the failure can be resolved through patch update.

10. DNS connection error in client using Windows 2012 Active Director.

When logging in with a domain account on the server, the error “The user name or password is incorrect” occurs even though the account and password are normal.

From Windows Server 2008 R2 / Windows 7, without DES-CBC-MD5 and DES-CBC-CRC encryption, AES256-CTS-HMAC-SHA1-96, AES128-CTS-HMAC-SHA1-96, RC4 -Only HMAC encryption is used. If the AD server is Windows Server 2012 R2 and the domain member is Windows Server 2008 R2 or Windows 7, the password for the computer account This is a phenomenon caused by an issue in the product in which AES key generation fails during renewal.

11. Vulnerability in GNU Bash 4.3 Shell.

It is known that attackers can change web server contents and code, tamper with websites, leak user data, and perform DDoS attacks by using Bash vulnerabilities. In addition to this, attack scenarios for Bash code injection vulnerabilities under various environments such as SSH and DHCP protocols are also being raised.

The target of failure is Red Hat Enterprise Linux 5, 6, 7 server, and the solution to the failure is Bash update.

12. Buffer overflow vulnerability in the GNU C library (glibc).

Vulnerable functions are called when gethostbyname() and gethostbyname2() functions, which are often used when connecting to a network, are called. External attackers can remotely execute arbitrary code on the vulnerable server.

The target of failure is Red Hat Enterprise Linux 5, 6, 7 server, and the solution to the failure is GLIBC update.

13. Bugs in Radhat V5 and V6 family OS.

This is a bug that reboots after 208.5 days in all versions of Red Hat Enterprise Linux 6 or 5 using Intel CPU.

The failure target is a Red Hat Enterprise Linux 5 or 6 server, and the solution to the failure is a kernel update.

14. Raid Controller Battery Fail.

I/O performance is degraded due to the unavailability of the Raid Controller Cache. The target of failure is the Raid Controller Battery for Dell Perc 5i, 6i, and the way to solve the failure is to pre-replace the Raid Controller Battery for Dell Perc 5i, 6i every 4 to 5 years.

15. System down due to CPU IERR error.

The target of failure is a server using CPU using Intel iBridge V2 (PE R720, PE R920), and the solution to the failure is to change the BIOS setting.

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

16. When using iDrac 1.50.50 F/W (Firmware) (search for the corresponding version), management web access is not possible.

F/W upgrade on the iDrac F/W (Firmware) OS or upgrade to 1.51.51 through the media in daily life.

2 to 14 illustrate screen examples of a server management system according to an embodiment of the present invention.

2 is an example of an initial screen, and the progress state of the server to be managed, a statistical graph of failure symptoms for each part, and the like are displayed on one screen.

3 is an example of a delivery history management screen, in which items such as a server's client company, management code, order number, model name, and introduction year are exemplified.

FIG. 4 is an example of a detailed delivery history management screen displayed when one server is selected in FIG. 3 , in which information of the corresponding server and specific system information are displayed.

5 is an example of a service period management screen among delivery history management, and is an example of a screen capable of managing the service period of each server.

6 is an example of a parts management detailed screen in delivery history management, and information on the model name, customer company, and number of equipment for each part is displayed.

7 to 10 are examples of failure history management screens through a Terminate and Stay Resident (TSR) log.

7 is an example of a TSR log analysis screen, and FIG. 8 is an example of a screen showing TSR log analysis statistics, with inspection 30%, replacement 20%, BIOS firmware update 15%, R/C firmware update 15%, iDrac firmware update 10% , the rate of action measures for 10% position change is shown in the graph.

9 and 10 are examples of critical issue management screens.

11 to 13 are examples of failure analysis service provision screens for each customer through statistics.

11 is an example of a failure analysis screen for each part, in which the failure rate for each major part is displayed in a circle graph, and the detailed failure rate for each part is also displayed in a circle graph.

12 is an example of a failure analysis screen and displays failure analysis information including cause of failure, conclusion, and replacement time.

13 is a screen example illustrating a failure analysis distribution map for each server compared to a customer company.

14 is an example of a screen illustrating a service report function, and the contents of the report including occurrence time, issues, problem solving, and recurrence prevention measures are exemplified.

15 is a diagram categorizing system equipment according to an embodiment of the present invention, and FIGS. 16 and 17 are diagrams describing hardware symptoms and their causes according to an embodiment of the present invention.

18 to 19 are flowcharts showing a failure prevention method in a server management system according to an embodiment of the present invention.

Referring to FIG. 18, when a hardware-related issue occurs in the management target server (S101), the management server 110 refers to the classification table of FIG. 15 and classifies similar equipment with a high probability of failure as dangerous equipment (S103). .

Then, a warning message for the classified dangerous equipment is sent (S105), and failure preemptive measures are performed (S107).

Referring to the classification table of FIG. 15, in one embodiment of the present invention, specific similarity judgment criteria of system equipment are exemplified, and the same class equipment classification, the same CPU equipment classification, the same Memory equipment classification, the same NIC equipment classification, and the same Disk Device classification, same HBA device classification, same BIOS device classification, same Driver version device classification, same OS device classification, same Firmware version device classification, etc. are exemplified.

Referring to FIG. 19 , when a hardware-related issue occurs in a management target server (S301), the management server 110 identifies a failure symptom (S303).

Then, referring to the charts in FIGS. 16 and 17, a symptom code according to a disorder symptom is checked (S305). Then, the cause corresponding to the symptom code is checked (S307), and a countermeasure report is sent accordingly (S309). Then, a failure countermeasure corresponding to the cause of failure is performed (S311).

If there is no symptom code corresponding to the disorder symptom in step S305, a new symptom code is generated and added to the list of FIGS. 16 and 17 (S313).

Referring to FIGS. 16 and 17 , causes of failure corresponding to symptom codes for each symptom of failure according to an embodiment of the present invention are illustrated. That is, RAC1198 is an iDrac firmware issue, a memory issue and a BIOS firmware issue for a correctable memory failure, a NIC failure and a firmware issue for Link Failure, a NIC driver and firmware issue for multiple Link Failure Counts, and a NIC driver and firmware issue for NIC Link is Down. and firmware issues, Link status and server check request are NIC driver and firmware issues, HOST_DOWN occurrence is NIC driver and firmware issues, server front yellow light occurrence is iDrac firmware issues, SWC5008:critical message output is iDrac firmware issues, and NO_PARTITION alarm occurrence is Disk failure, Reset adapte is a BIOS firmware issue, Correctable memory error is a memory issue and BIOS firmware issue, CPU performance degradation is a BIOS firmware issue, Memory and Slot not displayed is a memory issue and BIOS firmware issue, Disk fault error is a disk failure, disk Predicted failure is 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 failure is Gbic failure, system infinite reboot is BIOS firmware issue, LCD Panel specific message output iDrac firmware issue for iDRAC, iDrac firmware issue for repeated error message, synchronization error with vCenter agent is EXSi version and OS version issue, server reboot phenomenon is BIOS firmware issue, HBA write speed slowdown is HBA firmware and driver issue, HBA Read speed degradation is an HBA firmware and driver issue, HBA Link Down is an HBA Gbic and Card issue, HBA redundancy transfer failure is an HBA Gbic and Card issue, Riser1 failure is a Riser Card issue, Riser2 failure is a Riser Card issue, network redundancy failure is Network Card issue, PSU Alert Yellow LED is on PSU failure, abnormality due to low voltage indicates PSU failure, PXE booting failure indicates BIOS setting and NIC firmware/driver issue, POST boot failure indicates motherboard failure, LifeCycle connection failure on mainboard Failure, iDRAC hang symptom is iDrac firmware issue, iDRAC network disconnection is mainboard failure and iDrac firmware issue, iDRAC SNMP service failure is iDrac firmware issue, server suddenly turned off during use is mainboard issue, Medium Error is disk failure, ERROR Event confirmation requests are responded to issues caused by Error Events, and CMC connection failures are caused by CMC firmware issues.

In addition, DSET analysis request is a failure according to analysis, TSR Log analysis request is a failure according to analysis, NFS service startup failure is NFS setting and OS setting check, vCenter connection is not possible, EXSi version and OS version issue, NIC reset is Network Card issue , GPU unrecognized GPU card failure, OS crash occurrence OS dump analysis, network error/dropped packets occurrence network card issue, CRC error occurrence network card issue, server-switch disconnection phenomenon network card issue, network (bonding) Network card issue for poor communication, memory failure or motherboard failure for the same slot event after memory replacement, disk failure or RAID configuration issue that cannot be accessed in Disk Read Only state, switch 3-4 times a month Hang symptoms include mainboard or OS version issues, network card issues for LACP network speed issues, cluster configuration issues or HW failures for cluster failover occurrences, OS settings or network failures for RTSP synchronization failures, and network failures for session deterioration. Card or Gbic issue, unknown power cutoff indicates PSU failure, server slowdown and hang phenomenon indicates application or HW failure, Network Ping Loss indicates Network Card or Gbic issue, LoadAvg increase indicates CPU inspection, Fatal Error occurrence indicates PCI Card or riser Card issue, stopping or performance degradation during PXE installation is Network Card or Gbic issue, Blue Screen occurrence (0x00004f) is main board/BIOS/disk/memory failure, Blue Screen is main board/BIOS/disk failure, OS Boot failure is main Board/bios/disk failure, process down and panic during OS installation are mainboard/bios/disk failure, burning smell from server is fan/mainboard/PSU issue, NAS access is not possible, network/OS setting issue, KVM connection is not possible is a main board/KVM cable/KVM issue, Disk Amber LED is a disk failure, Post boot delay is a main board/fan/PCI/memory issue, power supply failure is a PSU failure, teaming performance degradation is a network/OS setting issue, VD Bad Block is a disk failure, HBA Loop is an HBA failure, Raid configuration information is not visible is a firmware/disk driver issue, Volume is not recognized as a firmware/disk driver issue, Kernel Panic is an OS/App issue, and server rebooting when using maximum performance CPU/PSU/Main board/Memory issues, CPU/PSU/Main board/Memory/Disk issues for significantly slow server processing speed, and PSU failures for server power failure.

The present invention has been described above using several preferred embodiments, but these embodiments are illustrative and not limiting. Those skilled in the art to which the present invention pertains will understand that various changes and modifications can be made without departing from the spirit of the present invention and the scope of rights set forth in the appended claims.

110 management server 120 manager terminal
130 Customer terminal 10, 20, 30, 40 Management target server

Claims (6)

In the server management system that manages the management target server requested by the customer,
an administrator terminal used by an administrator who manages the server management system;
a customer terminal used by each customer who requested the management target server; and
Collecting data from the management target server, identifying and managing the current status of each management target server, and providing various server management information including management service statistical data and management service reports related to this to the manager terminal and the customer terminal management server
Server management system comprising a.
The method of claim 1,
The management server analyzes the failure pattern of the management target server to provide a preventive analysis function to prevent similar failures from occurring, and through the preventive analysis function, when a predetermined event occurs in the management target server, a failure according to the occurred event may occur. A server management system characterized in that it preemptively transmits an expected failure occurrence message warning that there is a corresponding management target server to a customer terminal requesting the management target server.
The method of claim 1,
The server management system, characterized in that the management server provides a history management function for managing the installation, failure, technical support history of the management target server.
The method of claim 1,
The server management system, characterized in that the management server provides a delivery management function for managing the delivery history of the management target server.
The method of claim 1,
When an equipment-related event occurs in the management target server, the management server classifies dangerous equipment according to predetermined classification criteria, sends a warning message about the dangerous equipment to the manager terminal and the corresponding customer terminal, and sends a warning message to the corresponding dangerous equipment. A server management system characterized in that it performs pre-failure measures for.
The method of claim 1,
When an equipment-related event occurs in the management target server, the management server identifies a failure symptom of the corresponding equipment, analyzes the cause according to a failure code corresponding to the corresponding failure symptom, and sends a report including a failure response plan to the manager terminal. And server management system, characterized in that for sending to the corresponding customer terminal, and performing failure response measures for the corresponding equipment.

Images