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

Abstract

The present invention relates to a server management system that manages a server to be managed upon request from a customer, and includes an administrator terminal used by an administrator who manages the server management system, a customer terminal used by each customer who has requested the server to be managed, and a management server that collects data from the server to be managed, manages the server to identify the status of each server to be managed, and provides various server management information including management service statistical data and management service reports related thereto to the administrator terminal and the customer terminal.
According to the present invention, by providing a fault response function, a server management function, and a service statistics function to enable a server administrator to comprehensively manage servers, there is an effect of enabling more convenient and efficient server management.

Description

Server management system capable of responding to failure

The present invention relates to a server management system for managing servers, and more specifically, to a server management system for analyzing failure patterns occurring in servers, managing server status and history, and providing various functions for related statistics and services.

As computers have become larger and faster, system failures caused by errors or viruses have become more frequent. In particular, large-capacity servers can experience frequent failures due to various factors, such as the operation of various applications and data storage, retrieval, and transmission. Therefore, each company has a dedicated server administrator assigned to manage these servers and handle any failures that may occur.

However, server management requires specialized skills, and hiring such professionals can be quite expensive. Consequently, many small businesses, especially, opt to hire appropriate individuals from their existing staff rather than hire dedicated technicians as server administrators. This makes it difficult to maintain smooth server management, and it's even more difficult to respond effectively to server failures.

In addition, even if a server administrator with specialized skills is hired to manage the server, if the server administrator is away from the server due to business trips or other reasons, it is difficult to promptly notify the administrator of the server's status when a server failure occurs, making it difficult to respond smoothly when a server failure occurs. Furthermore, even if the server administrator is notified of a server failure, it is difficult to respond immediately because they are away, which can ultimately result in huge losses, such as the server going down.

Traditionally, in server integrated management systems that manage multiple servers, if a server failure occurs, the failure is detected and repaired after the fact. However, this conventional post-failure recovery method suffers from the following drawbacks: server operations are interrupted during the recovery period, resulting in losses due to server downtime, and significant losses due to the labor and costs required for recovery.

Republic of Korea Publication Patent No. 10-2015-0124642

The present invention has been devised to solve the above problems, and it analyzes the failure pattern occurring in the server, and warns of the occurrence of a failure when a specific event occurs, thereby enabling the occurrence of a failure to be prevented in advance, and provides a management function for managing the history of servers, and provides related service statistics and service reports.

Its purpose is to provide a server management system.

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

In order to achieve the above purpose, the present invention relates to a server management system for managing a server to be managed as requested by a customer, and includes an administrator terminal used by an administrator managing the server management system, a customer terminal used by each customer who requested the server to be managed, and a management server that collects data from the server to be managed, manages the server by grasping the status of each server to be managed, and provides various server management information including management service statistical data and management service reports related thereto to the administrator terminal and the customer terminal.

The above management server provides a preventive analysis function that analyzes the failure pattern of the managed server and prevents the occurrence of similar failures. Through the preventive analysis function, when a predetermined event occurs on the managed server, a predicted failure occurrence message can be proactively sent to the customer terminal that requested the managed server, warning that a failure may occur due to the occurred event.

The above management server can provide a history management function that manages the installation, failure, and technical support history of the managed server.

The above management server can provide a delivery management function that manages the delivery history of the managed server.

When an equipment-related event occurs on a managed server, the above management server can classify the risky equipment according to predetermined classification criteria, send a warning message for the risky equipment to the management terminal and the customer terminal, and perform preemptive failure response measures for the risky equipment.

When an equipment-related event occurs on a managed server, the above management server can identify a failure symptom of the equipment, analyze the cause based on a failure code corresponding to the failure symptom, send a report including a failure response plan to the management terminal and the customer terminal, and perform failure response measures for the equipment.

According to the present invention, by providing a fault response function, a server management function, and a service statistics function to enable a server administrator to comprehensively manage servers, there is an effect of enabling more convenient and efficient server management.

In addition, according to the present invention, by analyzing failure patterns for customers who own servers and providing server management functions to proactively respond to failures, there is an effect of processing and delivering data that meets the needs of customers.

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

The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

In addition, when describing with reference to the attached drawings, identical components will be assigned the same reference numerals regardless of the drawing numbers, and redundant descriptions thereof will be omitted. When describing the present invention, if a detailed description of a related known technology is judged to unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

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

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

The administrator terminal (120) is a terminal used by an administrator who manages the server management system.

The customer terminal (130) is a terminal used by each customer who has requested the managed server (10, 20, 30, 40).

In one embodiment of the present invention, the administrator terminal (120) and the customer terminal (130) can be implemented in various terminal forms capable of wired and wireless communication, such as a desktop computer, laptop computer, tablet PC, mobile phone, cell phone, or smart phone.

The management server (110) collects data from managed servers (10, 20, 30, 40), manages the status of each managed server by identifying the status of the server, and provides various server management information including management service statistical data and management service reports related thereto to the administrator terminal (120) and customer terminal (130).

The management server (110) provides a preventive analysis function that analyzes the failure pattern of the managed server (10, 20, 30, 40) and prevents the occurrence of similar failures. Through the preventive analysis function, when a predetermined event occurs in the managed server (10, 20, 30, 40), an expected failure occurrence message warning that a failure may occur due to the occurred event can be preemptively transmitted to the customer terminal that requested the managed server.

The management server (110) can provide a history management function that manages the installation, failure, and technical support history of the managed server (10, 20, 30, 40).

The management server (110) can provide a delivery management function that manages the delivery history of the managed server (10, 20, 30, 40).

When an equipment-related event occurs on a managed server, the management server (110) can classify the risky equipment according to predetermined classification criteria, send a warning message for the risky equipment to the management terminal (120) and the customer terminal, and perform preemptive failure response measures for the risky equipment.

When an equipment-related event occurs on a server to be managed, the management server (110) can identify a failure symptom of the equipment, analyze the cause according to a failure code corresponding to the failure symptom, send a report including a failure response plan to the management terminal (120) and the customer terminal, and perform failure response measures for the equipment.

In the present invention, the management server (110) can provide a data delivery service function that processes and delivers data related to the management of a server to be managed according to a request from a customer terminal (130).

In addition, the management server (110) can analyze critical failures of the managed server, propagate similar cases to prevent server failures in advance, and provide failure statistics of each server on a quarterly basis to the management terminal (120) and customer 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 by parts.

The present invention relates to a server management system that manages a plurality of management target servers (10, 20, 30, 40) commissioned by a customer.

In one embodiment of the present invention, the managed server, which is the server to be managed, may be various servers, and may be, for example, a Dell server (10), an HP server (20), an IBM server (30), or an X86 server (40).

The managed server (10, 20, 30, 40) and the management server (110) communicate through various wired and wireless communication methods, and can communicate, for example, through HTTP communication or JSON format POST transmission method.

Additionally, the managed servers (10, 20, 30, 40) can automatically execute scripts according to a set schedule on various x86 servers in a large-scale computing environment.

The administrator connects to the management server (110) through the administrator terminal (120), executes a batch program according to a schedule set in the management server (110), and manages the change history by comparing it with existing data.

The management server (110) automatically collects hardware information and software information of the managed servers (10, 20, 30, 40), determines the status of each server based on this, and provides management services according to the needs of each server.

The management server (110) can check the BBU (Backup Battery Unit) cycle of the managed server and, when a predetermined cycle is reached, transmit this information to the customer terminal of the managed server.

In addition, the management server (110) can check the BBU charging capacity of the managed server and, if the battery charging efficiency decreases below a predetermined value, can notify the customer terminal of the managed server of this information. For example, the management server (110) can check the BBU charging capacity of the managed server and, if the battery charging efficiency decreases below 40%, can notify the customer terminal of this information.

The management server (110) can check the remaining battery capacity of the BBU of the managed server and, if the remaining battery capacity is below a predetermined level, can notify the customer terminal of the managed server of this information. For example, the management server (110) can check the remaining battery capacity of the BBU of the managed server and, if the remaining battery capacity is below 10%, can notify the customer terminal of this information.

In addition, the management server (110) can check the BBU write policy of the managed server, and if the write policy is changed, it can notify the customer terminal of the managed server of this change.

The present invention relates to a server integrated management system that manages multiple servers in an integrated manner. The system diagnoses various server functions, predicts and warns of potential failures, and suggests solutions. Among the various server functions, the present invention will be described using the Backup Battery Unit (BBU) as an example.

Taking Dell servers as an example, to prevent cache data loss due to RAID controller battery failure, it's necessary to check the battery status of the BBU and perform preemptive battery replacement. To do this, check the Dell server's log to determine the battery full charging efficiency (%). Identify devices with a full charging efficiency of less than 50% and replace the batteries accordingly. After 36 months, battery charging efficiency naturally declines to around 70%. Taking this into account, a battery with an additional decrease of approximately 20% can be deemed to have poor charging efficiency.

The server integrated management system of the present invention performs BBU cycle check, charge capacity check, remaining capacity check, and write policy check, thereby preventing cache data loss and preventing risk factors regarding battery status in advance.

The server management system of the present invention diagnoses when an event occurs that a server failure may occur, alerts the server system in advance, and provides information on how to resolve the issue. In this regard, events occurring on servers are extremely diverse, and unprecedented events may even occur. The present invention will now exemplify several of the events that can occur on such servers.

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

As a workaround, we recommend downgrading to iDRAC7 version 1.46.45.

2. Power usage in rack PDU#1 and PDU#2 is concentrated in PDU#1.

Referring to Figure 17, not only Dell servers but also HP servers are set to operate in Active Standby by default for the power supply, which causes power to be concentrated on one side of the rack PDU. To achieve balance, the ratio of Primary to PSU needs to be adjusted.

3. OS malfunction after kernel update for Dell server products 12th to 14th generation.

At this time, if an abnormal operation is found in the OS (Operating System) after a kernel update on the Dell server, the management server (110) sends a message of an expected failure that may occur due to this to the management target server, and also transmits a solution to the expected failure to the management target server.

4. Service unavailable due to lack of TCP/IP ports.

This issue occurs when a network TIME_WAIT session remains unclosed on Windows 2008 systems with uptime exceeding 497 days. This causes ports to become occupied, and problems arise when no more ports are available. The issue affects Windows 2008 Server and Windows 2012 Server, and can be resolved by uninstalling the updated patch.

5. Windows 2003 ~ 2022 event log occurrence.

6. Diagnosis of memory production cycle.

This confirms that a specific production cycle of a specific memory is defective, the target of the failure is the 13th generation equipment (R730, R930, R630), the defective OS is a server that includes the KB3064209 hotfix in Windows 2012 R2 Server, and the solution is to remove the hotfix.

In the present invention, the management server (110) diagnoses the memory production cycle of the managed server, determines that a predetermined memory production cycle is defective, and notifies the managed server of this information.

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.

8. Issue where the temperature sensor does not function properly and an alarm sound (Alert_) continues to occur after the 12G Server BIOS update.

The solution to this is to diagnose BIOS version 2.5.2 and update to the latest firmware.

It's updating.

9. BSOD occurs after patch update and booting is not possible.

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

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

10. DNS connection error occurs on clients using Windows 2012 Active Director.

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

Starting with Windows Server 2008 R2 / Windows 7, DES-CBC-MD5 and DES-CBC-CRC encryptions are not used, and only AES256-CTS-HMAC-SHA1-96, AES128-CTS-HMAC-SHA1-96, and RC4-HMAC encryptions are used. This phenomenon occurs due to a product issue in which AES key generation fails when renewing the password for a computer account when the AD server is Windows Server 2012 R2 and the domain member is Windows Server 2008 R2 or Windows 7.

11. Vulnerability in the GNU Bash 4.3 Shell.

Bash vulnerabilities are known to allow attackers to alter web server content and code, deface websites, leak user data, and conduct DDoS attacks. Furthermore, Bash code injection vulnerability attack scenarios have been reported in various environments, including SSH and DHCP protocols.

The affected servers are Red Hat Enterprise Linux 5, 6, and 7, and the workaround is to update Bash.

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

This is a phenomenon in which a vulnerable function is called when calling the gethostbyname() and gethostbyname2() functions, which are frequently used when connecting to a network, allowing an external attacker to remotely execute arbitrary code on a vulnerable server.

The affected servers are Red Hat Enterprise Linux 5, 6, and 7, and the workaround is to update GLIBC.

13. Bugs in Radhat V5 and V6 series OS.

A bug that causes reboots after 208.5 days in all versions of Red Hat Enterprise Linux 6 or 5 using Intel CPUs.

The affected servers are Red Hat Enterprise Linux 5 and 6, and the workaround is a kernel update.

14. Raid Controller Battery Fail.

I/O performance is degraded due to the unavailability of the RAID Controller Cache. The issue is with the RAID Controller Battery for Dell Perc 5i and 6i, and the solution is to replace the RAID Controller Battery for Dell Perc 5i and 6i every 4 to 5 years.

15. System down due to CPU IERR error.

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

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

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

Upgrade to 1.51.51 by upgrading F/W on the iDrac F/W (Firmware) OS or upgrading via media in daily life.

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

Figure 2 is an example of the initial screen, and the progress status of the managed server, statistical graphs of failure symptoms by part, etc. are displayed on one screen.

Figure 3 is an example of a delivery history management screen, showing items such as the server's customer company, management code, order number, model name, and introduction year.

Figure 4 is an example of a delivery history management detail screen displayed when a server is selected in Figure 3, and information about the corresponding server and specific system information are displayed.

Figure 5 is an example of a service period management screen among delivery history management, and is an example of a screen that can manage the service period of each server.

Figure 6 is an example of a parts management detail screen among the delivery history management, in which information such as the model name, customer, and number of pieces of equipment for each part is displayed.

Figures 7 to 10 are examples of screens for managing failure history through the TSR (Terminate and Stay Resident) log.

Figure 7 is an example of a TSR log analysis screen, and Figure 8 is an example of a screen showing TSR log analysis statistics, in which the proportion of action methods of inspection 30%, replacement 20%, BIOS firmware update 15%, R/C firmware update 15%, iDrac firmware update 10%, and location change 10% are shown in a graph.

Figures 9 and 10 are examples of critical issue management screens.

Figures 11 to 13 are examples of screens providing customer-specific failure analysis services through statistics.

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

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

Figure 13 is an example screen showing the failure analysis distribution for each server compared to the customer.

Figure 14 is an example screen illustrating the service report function, and the report contents including the time of occurrence, issue, problem resolution, and recurrence prevention measures are illustrated.

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

Figures 18 and 19 are flowcharts showing a method for preemptive response to a failure in a server management system according to one embodiment of the present invention.

Referring to Fig. 18, when a hardware-related issue occurs in a managed server (S101), the management server (110) classifies similar equipment with a high possibility of failure as dangerous equipment by referring to the classification table of Fig. 15 (S103).

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

Referring to the classification table of FIG. 15, specific similarity judgment criteria of system equipment in one embodiment of the present invention are exemplified, including same class equipment classification, same CPU equipment classification, same memory equipment classification, same NIC equipment classification, same disk equipment classification, same HBA equipment classification, same BIOS equipment classification, same driver version equipment classification, same OS equipment classification, and same firmware version equipment classification.

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

Then, referring to the diagrams of Figures 16 and 17, the symptom code according to the failure symptom is confirmed (S305). Then, the cause corresponding to the symptom code is confirmed (S307), and a response plan report is sent accordingly (S309). Then, the failure response measures corresponding to the failure cause are performed (S311).

If there is no symptom code corresponding to the failure symptom at step S305, a new symptom code is created 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 failure symptom according to one embodiment of the present invention are exemplified. That is, RAC1198 is an iDrac firmware issue, correctable memory failure is a memory issue and BIOS firmware issue, Link Failure occurs as a NIC failure and firmware issue, Link Failure Count occurs in large numbers as a NIC driver and firmware issue, NIC Link is Down is a NIC driver and firmware issue, Link status and server check request is a NIC driver and firmware issue, HOST_DOWN occurs as a NIC driver and firmware issue, server front yellow light occurs as an iDrac firmware issue, SWC5008:critical message output is an iDrac firmware issue, NO_PARTITION alarm occurs as a disk failure, Reset adapter 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 are a memory issue and BIOS firmware issue, Disk fault error is a disk failure, disk predicted fail is a failure due to disk BadBlock, periodic FAN 6 recognition problem is a Fan 6 failure, Fault due to light intensity below 400 is a Gbic failure, and NIC GBIC communication failure is Gbic failure, infinite system reboot is a BIOS firmware issue, LCD Panel specific message output is an iDrac firmware issue, iDRAC repetitive error message occurs iDrac firmware issue, vCenter agent synchronization error is EXSi version and OS version issue, server reboot phenomenon is BIOS firmware issue, HBA write speed decrease is HBA firmware and driver issue, HBA read speed decrease is HBA firmware and driver issue, HBA link down is HBA Gbic and card issue, HBA redundancy switch failure is HBA Gbic and card issue, Riser1 recognition failure is Riser Card issue, Riser2 recognition failure is Riser Card issue, network redundancy failure is Network Card issue, PSU Alert yellow LED lighting is PSU failure, abnormality due to low voltage is PSU failure, PXE boot failure is BIOS setting and NIC firmware/driver issue, POST boot failure is motherboard failure, LifeCycle connection failure is motherboard failure, iDRAC Hang symptom is iDrac firmware issue, iDRAC network disconnection is motherboard failure and iDrac firmware issue, iDRAC SNMP service failure is caused by an iDrac firmware issue, the server suddenly shutting down while in use is caused by a motherboard issue, Medium Error is caused by a disk failure, ERROR Event confirmation request is caused by an Error Event issue, and CMC inaccessibility is caused by a CMC firmware issue.

And, 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 failure is EXSi version and OS version issue, NIC Reset is a Network Card issue, GPU recognition failure is GPU Card failure, OS Crash occurs when OS Dump analysis occurs, Network error/dropped packets occurs when Network Card issue, CRC error occurs when Network Card issue, Server-switch disconnection phenomenon is Network Card issue, Network (Bonding) communication not smooth issue is Network Card issue, Same slot event after memory replacement is memory failure or motherboard failure, Disk Read Only status inaccessible is disk failure or RAID configuration issue, Switch Hang symptom 3-4 times a month is motherboard or OS version issue, LACP Network Speed problem occurs when Network Card issue, Cluster failover occurs when Cluster setting issue or HW failure, RTSP synchronization failure is OS setting or Network failure, Session degradation phenomenon occurs when Network Card or Gbic issue, Unknown power cut is PSU failure, Server slowdown and hang phenomenon is application or HW failure, Network Ping Loss indicates a Network Card or Gbic issue, LoadAvg increase indicates a CPU check-up, Fatal Error occurs indicates a PCI Card or Riser Card issue, Stopping or performance degradation during PXE installation indicates a Network Card or Gbic issue, Blue Screen (0x00004f) indicates a motherboard/BIOS/disk/memory failure, Blue Screen indicates a motherboard/BIOS/disk failure, OS Booting failure indicates a motherboard/BIOS/disk failure, Process Down and panic during OS installation indicates a motherboard/BIOS/disk failure, Burning smell from the server indicates a fan/motherboard/PSU issue, NAS inaccessibility indicates a network/OS setting issue, KVM inaccessibility indicates a motherboard/KVM cable/KVM issue, Disk Amber LED indicates a disk failure, Post boot delay indicates a motherboard/fan/PCI/memory issue, Power supply failure indicates a PSU failure, Teaming performance degradation indicates a network/OS setting issue, VD Bad Block indicates a disk failure, HBA Loop indicates an HBA failure, Raid configuration information is not visible. Firmware/disk driver issues, Volume not recognized is a firmware/disk driver issue, Kernel Panic is an OS/App issue, Server rebooting when using maximum performance is a CPU/PSU/mainboard/memory issue, Server processing speed is noticeably slow due to CPU/PSU/mainboard/memory/disk issue, Server not turning on is due to PSU failure.

While the present invention has been described using several preferred embodiments, these embodiments are illustrative and not limiting. Those skilled in the art will appreciate that various changes and modifications can be made without departing from the spirit and scope of the invention as set forth in the appended claims.

110 Management Server 120 Administrator Terminal
130 customer terminals 10, 20, 30, 40 managed servers

Claims (6)

In a server management system that manages servers commissioned by customers,
An administrator terminal used by an administrator who manages the above server management system;
Customer terminals used by each customer who has requested the above-mentioned management target server; and
A management server that collects data from the above-mentioned managed servers, manages the status of each managed server by identifying the status of each managed server, and provides various server management information including management service statistical data and management service reports related thereto to the above-mentioned administrator terminal and the above-mentioned customer terminal.
The above management server provides a preventive analysis function that analyzes the failure pattern of the managed server and prevents the occurrence of similar failures. Through the preventive analysis function, when a predetermined event occurs on the managed server, a predicted failure occurrence message is proactively sent to the customer terminal that requested the managed server, warning that a failure may occur due to the event.
The above management server provides a history management function that manages the installation, failure, and technical support history of the managed server.
When an equipment-related event occurs on the managed server, the above management server classifies the risky equipment according to predetermined classification criteria, sends a warning message about the risky equipment to the above management terminal and the customer terminal, and performs preemptive failure response measures for the risky equipment.
When an equipment-related event occurs on the managed server, the above management server identifies the failure symptoms of the equipment, analyzes the cause according to the failure code corresponding to the failure symptom, sends a report including the failure response plan to the above management terminal and the customer terminal, and performs failure response measures for the equipment.
The above management server checks the BBU (Backup Battery Unit) cycle of the managed server, and when a predetermined cycle is reached, transmits this information to the customer terminal of the managed server.
The above management server checks the BBU charging capacity of the managed server, and if the battery charging efficiency decreases below a predetermined value, it notifies the customer terminal of the managed server of this information.
The above management server checks the remaining capacity of the BBU of the managed server, and if the remaining capacity of the battery is below a predetermined level, it notifies the customer terminal of the managed server of this information.
The above management server checks the BBU write policy of the managed server, and if the write policy is changed, it notifies the customer terminal of the managed server of this change.
When a hardware-related issue occurs on a managed server, the above management server refers to the classification table to classify similar equipment with a high probability of failure as dangerous equipment, sends a warning message for the classified dangerous equipment, and performs preventive measures for failure.
At this time, the above classification table includes specific similarity judgment criteria for system equipment, including same class equipment classification, same CPU equipment classification, same memory equipment classification, same NIC equipment classification, same disk equipment classification, same HBA equipment classification, same BIOS equipment classification, same driver version equipment classification, same OS equipment classification, and same firmware version equipment classification.
When a hardware-related issue occurs in a managed server, the above management server identifies a failure symptom, checks the symptom code according to the failure symptom by referring to a list containing the failure cause corresponding to the symptom code for each failure symptom, checks the cause corresponding to the symptom code, sends a response plan report accordingly, performs failure response measures corresponding to the failure cause, and if there is no symptom code corresponding to the failure symptom, creates a new symptom code and adds it to the above list.
At this time, the above list is RAC1198 iDrac firmware issue, connector memory failure is memory issue and BIOS firmware issue, Link Failure occurrence is NIC failure and firmware issue, Link Failure Count occurrence is NIC driver and firmware issue, NIC Link is Down is NIC driver and firmware issue, Link status and server check request is NIC driver and firmware issue, HOST_DOWN occurrence is NIC driver and firmware issue, server front yellow light occurrence is iDrac firmware issue, SWC5008:critical message output is iDrac firmware issue, NO_PARTITION alarm occurrence is disk failure, Reset adapter is BIOS firmware issue, Correctable memory error is memory issue and BIOS firmware issue, CPU performance degradation is BIOS firmware issue, Memory and Slot not displayed is memory issue and BIOS firmware issue, Disk fault error is disk failure, disk predicted fail is failure due to disk BadBlock, periodic FAN 6 recognition problem is Fan 6 failure, Fault due to light amount below 400 is Gbic failure, NIC GBIC communication failure is Gbic failure, infinite system reboot is a BIOS firmware issue, LCD Panel specific message output is an iDrac firmware issue, iDRAC repetitive error message occurs iDrac firmware issue, vCenter agent synchronization error is EXSi version and OS version issue, server reboot phenomenon is BIOS firmware issue, HBA write speed decrease is HBA firmware and driver issue, HBA read speed decrease is HBA firmware and driver issue, HBA link down is HBA Gbic and card issue, HBA redundancy switch failure is HBA Gbic and card issue, Riser1 recognition failure is Riser Card issue, Riser2 recognition failure is Riser Card issue, network redundancy failure is Network Card issue, PSU Alert yellow LED lighting is PSU failure, abnormality due to low voltage is PSU failure, PXE boot failure is BIOS setting and NIC firmware/driver issue, POST boot failure is motherboard failure, LifeCycle connection failure is motherboard failure, iDRAC Hang symptom is iDrac firmware issue, iDRAC network disconnection is motherboard failure and iDrac firmware issue, iDRAC SNMP service failure is an iDrac firmware issue, the server suddenly shuts down during use is a motherboard issue, Medium Error occurs is a disk failure, ERROR Event confirmation request is an issue due to an Error Event, CMC connection failure is a CMC firmware issue, DSET analysis request is a failure due to analysis, TSR Log analysis request is a failure due to analysis, NFS Service startup failure is an NFS setting and OS setting check, vCenter connection failure is an EXSi version and OS version issue, NIC Reset is a Network Card issue, GPU not recognized is a GPU Card failure, OS Crash occurs when OS Dump is analyzed, Network error/dropped packets occur is a Network Card issue, CRC error occurs is a Network Card issue, Server-switch disconnection is a Network Card issue, Network (Bonding) communication not smooth is a Network Card issue, Same slot event after memory replacement is a memory failure or motherboard failure, Disk Read Only status inaccessibility is a disk failure or RAID configuration issue, Switch hang symptom 3-4 times a month is a motherboard or OS version issue, LACP Network Speed problem occurs is a Network Card issue, Cluster fail Overload occurrence is a cluster configuration issue or HW failure, RTSP synchronization failure is an OS configuration or Network failure, session degradation phenomenon is a Network Card or Gbps issue, unknown power cut is a PSU failure, server slowness and hang phenomenon is an application or Hbps issue, Network Ping Loss is a Network Card or Gbps issue, LoadAvg increase requires CPU inspection, Fatal Error occurs is a PCI Card or Riser Card issue, freezing or performance degradation during PXE installation is a Network Card or Gbps issue, Blue Screen occurrence (0x00004f) 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 is a motherboard/BIOS/disk failure, Burning smell from the server is a fan/mainboard/PSU issue, NAS access failure is a network/OS configuration issue, KVM connection failure is a motherboard/KVM cable/KVM issue, Disk Amber LED is a disk failure, Delay during Post Boot A server management system characterized by including the following causes: motherboard/fan/PCI/memory issues, power supply failure measures are PSU failure, teaming performance degradation is network/OS setting issues, VD Bad Block is disk failure, HBA Loop is HBA failure, Raid configuration information not visible is firmware/disk driver issues, Volume not recognized is firmware/disk driver issues, Kernel Panic is OS/App issues, server rebooting when using maximum performance is CPU/PSU/motherboard/memory issues, server processing speed is significantly slowed down is CPU/PSU/motherboard/memory/disk issues, and server power not coming on is PSU failure.
delete delete delete delete delete