Identifier generation method, device, storage medium and computer program product

Abstract

The present disclosure relates to the field of computer technology, and in particular to an identifier generation method, device, storage medium and computer program product. The present disclosure generates a fault handling identifier that is different from a common event for a fault event of a key component, and informs a user of the faulty component and corresponding handling measures in the form of a fault handling identifier, so as to facilitate the user to troubleshoot and handle the hardware components of a network device, eliminate the fault of the key component in a timely manner, and improve the efficiency and accuracy of operation and maintenance work.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an identifier generation method, device, storage medium and computer program product. Background Art

[0002] SNMP Trap is a message type in the Simple Network Management Protocol (SNMP) and is used by network devices (such as routers, switches, and servers) to proactively send asynchronous event notifications to the Network Management System (NMS).

[0003] However, the general Trap mechanism is relatively fixed and can only inform users of the occurrence of events, and often cannot meet users' personalized needs for monitoring and processing specific events. Summary of the invention

[0004] In order to solve the above technical problems, the present disclosure provides an identifier generation method, device, storage medium and computer program product.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for generating an identifier, including:

[0006] When a fault event is detected, a fault diagnosis result corresponding to the fault event is obtained, wherein the fault diagnosis result includes a faulty component and a fault handling suggestion;

[0007] If the faulty component belongs to a preset key component, determining a fault suggestion identifier according to the fault handling suggestion;

[0008] A fault handling identifier corresponding to the fault event is generated based on the fault component and the fault suggestion identifier.

[0009] In some embodiments, when a fault event is monitored, obtaining a fault diagnosis result corresponding to the fault event includes:

[0010] When a report event is detected, an event identifier corresponding to the report event is generated;

[0011] If the reported event is a fault event, a fault diagnosis result corresponding to the fault event is obtained.

[0012] In some embodiments, when a report event is monitored to occur, generating an event identifier corresponding to the report event includes:

[0013] Determine an event occurrence component corresponding to the reported event;

[0014] Determine the component identification of the component where the event occurs according to a preset component type identification mapping table;

[0015] An event identifier corresponding to the report event is generated based on the component identification.

[0016] In some embodiments, determining the component identification of the component where the event occurs according to a preset component type identification mapping table includes:

[0017] According to the preset component type identification mapping table, obtaining the component type identification corresponding to the component type of the event occurrence component;

[0018] The component identification is constructed based on the component type identification and the component serial number of the event-occurring component.

[0019] In some embodiments, when a report event is monitored to occur, generating an event identifier corresponding to the report event includes:

[0020] Acquiring identifier function configuration information, where the identifier function configuration information indicates whether the user only needs to obtain a fault handling identifier for the preset key component;

[0021] If it is determined according to the identifier function configuration information that the user only has a need to obtain a fault handling identifier for the preset key component, then when the reported event is a fault event of the preset key component, only a fault handling identifier corresponding to the fault event is generated.

[0022] In some embodiments, the event identifier further includes:

[0023] Sensor type identification, event type identification, event content identification, event level identification.

[0024] In some embodiments, obtaining the fault diagnosis result corresponding to the fault event includes:

[0025] If the faulty component cannot be automatically repaired, determining that the fault handling suggestion is to replace the faulty component; or,

[0026] If the faulty component can be automatically repaired, the fault handling suggestion is determined to be ignoring the fault event.

[0027] In some embodiments, determining a fault suggestion identifier according to the fault handling suggestion includes:

[0028] If the fault handling suggestion is to replace the faulty component, the fault suggestion identifier is set to a first preset value, where the first preset value indicates that the fault suggestion identifier is a replacement identifier; or,

[0029] If the fault handling suggestion is to ignore the fault event, the fault suggestion flag is set to a second preset value, and the second preset value indicates that the fault suggestion flag is an ignore flag.

[0030] In some embodiments, if the faulty component is a preset key component, before determining the fault suggestion identifier according to the fault handling suggestion, the method further includes:

[0031] Based on the key component configuration information, obtain a key component type list;

[0032] If the key component type list includes the component type of the faulty component, it is determined that the faulty component belongs to a preset key component.

[0033] In some embodiments, the generating a fault handling identifier corresponding to the fault event based on the fault component and the fault suggestion identifier includes:

[0034] According to a preset component type identification mapping table, obtaining a component type identification corresponding to the component type of the faulty component;

[0035] Constructing a faulty component identification of the faulty component based on the component type identification and the component serial number of the faulty component;

[0036] A fault handling identifier corresponding to the fault event is generated based on the fault component identifier and the fault suggestion identifier.

[0037] In some embodiments, the method further comprises:

[0038] In response to an identifier screening request from a user, obtaining a screening condition corresponding to the identifier screening request, wherein the screening condition includes at least one identification field and / or identification value in the fault handling identifier;

[0039] Obtain at least one fault handling identifier including the identification field and / or identification value;

[0040] Retrieving the fault event log corresponding to the fault handling identifier;

[0041] The fault handling identifier and / or the fault event log are fed back to the user.

[0042] In some embodiments, the fault handling identifier further includes: a special identifier distinction code and a fault type identifier.

[0043] In a second aspect, an embodiment of the present disclosure provides an electronic device, including:

[0044] Memory;

[0045] Processor; and

[0046] Computer programs;

[0047] The computer program is stored in the memory and is configured to be executed by the processor to implement the method as described in the first aspect.

[0048] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the method described in the first aspect.

[0049] In a fifth aspect, an embodiment of the present disclosure further provides a computer program product, which includes a computer program or instructions, and when the computer program or instructions are executed by a processor, the method described in the first aspect above is implemented.

[0050] The identifier generation method, device, storage medium and computer program product provided in the embodiments of the present disclosure generate a fault handling identifier that is different from ordinary events for the fault events of key components, and inform the user of the faulty components and corresponding processing measures in the form of the fault handling identifier, so as to facilitate the user to troubleshoot and handle the hardware components of the network equipment, eliminate the faults of key components in time, and improve the efficiency and accuracy of operation and maintenance work. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0052] Figure 1 A flow chart of an identifier generation method provided by an embodiment of the present disclosure;

[0053] Figure 2 A schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0054] Figure 3 A flow chart of an identifier generation method provided by another embodiment of the present disclosure;

[0055] Figure 4 A schematic diagram of the structure of an identifier generation device provided in an embodiment of the present disclosure;

[0056] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0057] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0058] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0059] The embodiment of the present disclosure provides a method for generating an identifier, which is introduced below in conjunction with a specific embodiment.

[0060] Figure 1 A flowchart of an identifier generation method provided by an embodiment of the present disclosure, which can be applied to Figure 2 The application scenario shown includes a network device 21 and a network management system (NMS) 22. The network device 21 includes a baseboard management controller (BMC) 211 and multiple hardware components. The hardware components in the network device 21 include a central processing unit (CPU), a power supply unit (PSU), a fan, etc. The baseboard management controller 211 is used to monitor the operation status of the network device 21. When an event occurs in the network device 21, an identifier corresponding to the event is generated to describe the information of the event. The network device 21 actively sends an asynchronous message to the network management system 22 through the Trap mechanism, so that the network management system 22 collects the event information in the network device 21; wherein the network device 21 can be a router, a switch, a server, etc.

[0061] Combine the following Figure 2 The application scenario shown is Figure 1 The kernel upgrade method shown in the figure is introduced. The specific steps of this method are as follows:

[0062] S101. When a fault event is monitored, a fault diagnosis result corresponding to the fault event is obtained, where the fault diagnosis result includes a faulty component and a fault handling suggestion.

[0063] The baseboard management controller 211 monitors the operating status of each component in the network device 21 in real time. When any component fails, a fault event is triggered. When the baseboard management controller 211 monitors the occurrence of a fault event, it will quickly start the fault diagnosis process and obtain the fault diagnosis result corresponding to the fault event.

[0064] Specifically, the baseboard management controller 211 monitors the operating status of the central processing unit (CPU), memory, power supply unit (PSU), fan, etc. Once a fault event is detected, such as excessive CPU temperature, memory check error, unstable PSU output voltage, or abnormal fan speed, the relevant fault information will be recorded. The fault diagnosis service in the baseboard management controller 211 accurately locates the faulty component and possible causes of the fault by analyzing various parameters and logs when the fault occurs. For example, if abnormal data transmission is detected at a port of a network device, it may be due to a problem with the physical link corresponding to the port, such as a damaged network cable or a loose port.

[0065] After determining the faulty component, the fault diagnosis service will give corresponding fault handling suggestions based on the fault type and fault severity. For example, for a fault that can be recovered by resetting the system, a handling suggestion of ignoring the fault may be given; while for a serious fault, a handling suggestion of replacing the component may be given.

[0066] S102: If the faulty component is a preset key component, determine a fault suggestion identifier according to the fault handling suggestion.

[0067] The fault suggestion identifier is used to generate a fault handling identifier corresponding to the fault event, that is, an object identifier (OID) of the fault event.

[0068] The preset key components are components that users pay close attention to, such as CPU, memory, motherboard, PCIE device, etc. If a key component fails, it may cause downtime. Therefore, for the faulty components that belong to the preset key components, an additional fault handling identifier is generated for their fault events.

[0069] Optionally, based on the key component configuration information, a key component type list is obtained; if the key component type list includes the component type of the faulty component, it is determined that the faulty component belongs to a preset key component.

[0070] The key component type list is generated according to the key component configuration information configured by the user, and records the component types of the key components selected by the user from multiple components. When a fault event occurs, the component type of the faulty component is searched in the key component type list. If the key component list contains the component type, the faulty component is determined to be a preset key component; if the key component list does not contain the component type, the faulty component is determined not to be a preset key component.

[0071] The fault handling identifier includes a fault suggestion identifier to instruct the user how to handle the fault event.

[0072] S103: Generate a fault handling identifier corresponding to the fault event based on the fault component and the fault suggestion identifier.

[0073] The fault handling identifier is a string of characters, specifically a 32-bit string, in which different bits represent identification values ​​of different identification fields, such as a fault component identifier and a fault handling identifier.

[0074] Specifically, bits 23-10 are used to identify the faulty component, and bits 4-0 are used to identify the fault handling suggestion.

[0075] The embodiment of the present disclosure obtains a fault diagnosis result corresponding to the fault event when a fault event is monitored, wherein the fault diagnosis result includes a faulty component and a fault handling suggestion; if the faulty component belongs to a preset key component, a fault suggestion identifier is determined according to the fault handling suggestion; a fault handling identifier corresponding to the fault event is generated based on the faulty component and the fault suggestion identifier; a fault handling identifier that is different from an ordinary event is generated for the fault event of the key component, and a user is informed of the faulty component and the corresponding handling measures in the form of the fault handling identifier, so as to facilitate the user to troubleshoot and handle the hardware components of the network device, eliminate the faults of the key components in a timely manner, and improve the efficiency and accuracy of the operation and maintenance work.

[0076] Figure 3 This is a flow chart of an identifier generation method provided by another embodiment of the present disclosure. Figure 3 As shown, the method comprises the following steps:

[0077] S301. When a report event is detected, an event identifier corresponding to the report event is generated.

[0078] The reporting event is any event occurring in the network device 21, including but not limited to: a component status change event, a fault event.

[0079] When any event occurs in the network device 21, an event identifier corresponding to the reported event is generated. Specifically, the event occurrence component corresponding to the reported event is determined; the component identifier of the event occurrence component is determined according to a preset component type identifier mapping table; and the event identifier corresponding to the reported event is generated based on the component identifier.

[0080] Wherein, determining the component identification of the event-occurring component according to a preset component type identification mapping table includes: obtaining the component type identification corresponding to the component type of the event-occurring component according to the preset component type identification mapping table; and constructing the component identification based on the component type identification and the component serial number of the event-occurring component.

[0081] When a report event occurs, a corresponding event log is generated in the network device 21, which records the component where the report event occurs and the detailed content of the report event, etc. The event occurrence component corresponding to the report event is determined based on the event log.

[0082] The preset component type identification mapping table records a plurality of component types and the component type identification corresponding to each component type, and the component types correspond to the component type identifications one by one. An example of the preset component type identification mapping table is given below:

[0083] Table 1 Preset component type identification mapping table

[0084]

[0085] As shown in Table 1, the preset component type identification mapping table provides the component type identification corresponding to each component type, and the component type identification will constitute a part of the event identifier. The component type identification is specifically stored as a hexadecimal value.

[0086] Since there may be multiple components of the same component type in the network device 21, for example, there may be multiple fans of the same type, resulting in the same component type identifier for the multiple components. To further distinguish different components of the same type, component serial numbers are respectively assigned to different components of the same component type, for example, different numbers are used as component serial numbers for different components of the same component type.

[0087] By combining the component type identifier and the component serial number, a unique identifier, called a component identifier, can be determined for each component in the network device 21.

[0088] Optionally, the event identifier also includes: a sensor type identifier, an event type identifier, an event content identifier, and an event level identifier.

[0089] Among them, the sensor type identifier represents the type of sensor that triggers the reporting event, including parameter sensors and the event-occurring component itself. For example, when the reporting event is that the CPU temperature increases, the corresponding type of sensor that triggers the reporting event is the temperature sensor; when the reporting event is that the fan speed is too high, since the fan component itself has a speed monitoring function, the corresponding type of sensor that triggers the reporting event is the fan.

[0090] The event type identifier represents the event type of the reported event, including Threshold type, Generic type, Sensor-specific type, and OEM type. Among them, Threshold type is a threshold type event, which means an event triggered when a parameter or indicator exceeds or falls below a preset threshold; Generic type event is a discrete type event recorded in the general specification, which means an event triggered when a component enters or is in a specific state; Sensor-specific type event is a discrete type event not recorded in the general specification; OEM type event is an extensible custom event.

[0091] The event content identifier represents the status and specific content of the reported event, where the event status represents whether the reported event is a trigger event or a release event. For example, when the CPU temperature exceeds the threshold, the corresponding report event is a trigger event, specifically a threshold type trigger event; when the CPU temperature returns to the normal range, the corresponding report event is a release event, indicating that the state of the CPU temperature exceeding the threshold is released. Event content is a fine-grained classification under the above event type.

[0092] The incident level indicator represents the severity of the reported incident.

[0093] The following is an event identifier structure table:

[0094] Table 2 Event identifier composition table

[0095]

[0096] As shown in Table 2, in the 32-bit event identifier, Bit31-Bit24 is the component type identifier, refer to the Sensor Type Code column in Table 42-3, Sensor Type Codes in the IPMI 2.0 specification, and expand on this basis. Bit23-Bit18 is the component serial number, and 6 bits can represent up to 64 components of the same component type. Bit17-Bit10 is the sensor type identifier, refer to the Sensor TypeCode column in Table 42-3, Sensor Type Codes in the IPMI 2.0 specification, such as temperature is 0x01h, voltage is 0x02h, current is 0x03h, fan is 0x04h, etc. Bit9-Bit8 is the event type identifier. Refer to the Event / Reading Type Code Range column in Table 42-1, Event / Reading Type Code Ranges in the IPMI2.0 specification. Redefine the Threshold type to 0x00h, the Generic type to 0x01h, the Sensor-specific type to 0x02h, and the OEM type to 0x03h. Bit7-Bit2 is the event content identifier, where Bit7 is the event status. Setting it to 0 means triggering the event, and setting it to 1 means releasing the event. Bit6-Bit2 is the event content. Refer to the Event column in Table 42-3, Sensor Type Codes in the IPMI2.0 specification. Bit1-Bit0 is the event level identifier. For example, 0x00 is defined as the info level, 0x01 is defined as the warning level, and 0x10 is defined as the critical level.

[0097] The following describes the specific method of generating event identifiers in conjunction with specific reporting events.

[0098] First, an example of a threshold type event is given. BMC represents temperature monitoring as a temperature sensor event. When the monitored temperature exceeds or falls below the set threshold, a report event representing a trigger event is generated; if the monitored temperature returns to normal, a report event representing a release event is generated.

[0099] Taking the first PSU in network device 21 as an example, when the temperature of the first PSU is higher than the threshold, a trigger event is generated. The component type identifier of the first PSU is 8, the component serial number is 1, the Temperature sensor type identifier value is 1, the event type identifier of the threshold type event is 0, the trigger event Upper Critical - going high, the value is 9, the event level is Critical, and the event level identifier is 2.

[0100] Correspondingly, the structure of the PSU high temperature trigger event identifier (PSU high temperature trigger OID) is shown in the following table:

[0101] Table 3 PSU high temperature trigger OID

[0102]

[0103] The binary data combination of each field in Table 3 is 10000000000001000000010000100110, which is converted into hexadecimal data as 80040426, that is, the PSU high temperature trigger event identifier is 0x80040426.

[0104] When the temperature of the first PSU returns to normal, a release event is generated. The component type identifier of the first PSU is 8, and the component serial number is 1. The Temperature sensor type identifier value is 1, and the event type identifier of the threshold type event is 0. The release event Upper Critical - going high has a value of 41, an event level of Critical, and an event level identifier of 2.

[0105] Correspondingly, the structure of the PSU high temperature release event identifier (PSU high temperature release OID) is shown in the following table:

[0106] Table 4 PSU high temperature release OID

[0107]

[0108] The binary data combination of each field in Table 4 is 10000000000001000000010010100110, which is converted into hexadecimal data as 800404A6, that is, the PSU high temperature release event identifier is 0x800404A6.

[0109] In some embodiments, an example of a discrete type event is given. The register of a complex programmable logic device (CPLD) stores the power-on status of the mainboard. The BMC represents the change of the mainboard power-on status as a discrete state sensor event. When the mainboard has an abnormal power failure, a bit in a register of the CPLD is set. When the BMC detects that the bit is set, it will generate a report event. When the abnormality is restored, the bit in a register of the CPLD will be cleared, and the BMC will generate a report event again.

[0110] Taking the 0th main board (Main Board) in network device 21 as an example, when the 0th main board has an abnormal power failure, a trigger event is generated. The component type of the 0th main board is identified as 15, and the component serial number is 0; the Power Supply sensor type is identified as 8, and the Sensor specific event type is identified as 2; the event state of the trigger event Power Supply Failure detected is identified as 1, the event level is Critical, and the event level is identified as 2.

[0111] Correspondingly, the structure of the mainboard abnormal power failure event identifier (mainboard abnormal power failure event OID) is shown in the following table:

[0112] Table 5 Mainboard abnormal power failure event OID

[0113]

[0114] The binary data combination of each field in Table 5 is 10101000000000010001000000110, which is converted into hexadecimal data as 15002206. The mainboard abnormal power-off event identifier is 0x15002206.

[0115] When the 0th mainboard recovers from abnormal power failure, a release event is generated. The component type of the 0th mainboard is 15, and the component serial number is 0. The Power Supply sensor type is 8, and the Sensor specific event type is 2. The event status of the triggering event Power Supply Failure detected is 33, the event level is Critical, and the event level is 2.

[0116] Correspondingly, the structure of the mainboard power failure recovery event identifier (mainboard power failure recovery event OID) is shown in the following table:

[0117] Table 6 Mainboard power-off recovery event OID

[0118]

[0119] The binary data combination of each field in Table 6 is 10101000000000010001010000110, which is converted into hexadecimal data as 15002286. The mainboard power-off recovery event identifier is 0x15002286.

[0120] In other embodiments, another example of a discrete type event is given. The status register of the PSU stores the current status of the PSU, and the BMC represents the status of the PSU as a discrete status Sensor event. When the PSU has a power supply abnormality, the bit in the status register of the PSU will be set. After the BMC finds that the bit is set, it generates a report event. When the abnormality is restored, the bit in the status register of the PSU is cleared, and the BMC generates a report event again.

[0121] Taking the first PSU in network device 21 as an example, when the first PSU has a power supply abnormality, a trigger event is generated. The component type of the first PSU is identified as 8, the component serial number is 1, the sensor type is Power Supply, and the sensor is identified as 8; the Sensor specific event type is identified as 2; the event state of the trigger event Power Supply Failure detected is identified as 1, the event level is Critical, and the event level is identified as 2.

[0122] Correspondingly, the structure of the PSU power supply abnormal event identifier (PSU power supply abnormal event OID) is shown in the following table:

[0123] Table 7 PSU power supply abnormal event OID

[0124]

[0125] The binary data combination of each field in Table 7 is 1000000001000010001000000110, which is converted into hexadecimal data as 8042206. The PSU power supply abnormality event identifier is 0x8042206.

[0126] When the power supply of the first PSU returns to normal, a release event is generated. The component type of the first PSU is 8, the component sequence is 1, the sensor type is Power Supply, and the sensor is 8. The Sensor specific event type is 2. The event status of the release event Power Supply Failure detected is 33, the event level is Critical, and the event level is 2.

[0127] Accordingly, the structure of the PSU power restoration event identifier (PSU power restoration event OID) is shown in the following table:

[0128] Table 8 PSU power recovery event OID

[0129]

[0130] The binary data of each field in Table 8 is combined to obtain 1000000001000010001010000110, which is converted into hexadecimal data as 8042286. The PSU power supply recovery event identifier is 0x8042286.

[0131] S302: Determine whether the reported event is a fault event. If so, execute S303; if not, execute S306.

[0132] S303: If the reported event is a fault event, obtain a fault diagnosis result corresponding to the fault event.

[0133] S304, determine whether the faulty component is a preset key component; if so, execute S305; if not, execute S306.

[0134] S305: Generate a fault processing identifier corresponding to the fault event.

[0135] Specifically, a fault suggestion identifier is determined according to the fault handling suggestion; and a fault handling identifier corresponding to the fault event is generated based on the fault component and the fault suggestion identifier.

[0136] Specifically, the implementation process and principle of S303-S305 are consistent with those of S101-S103, and will not be repeated here.

[0137] S306, end.

[0138] The disclosed embodiment covers the component identifier in the event identifier to clarify the component type and component serial number of the event, thereby effectively solving the problem that different components have the same event identifiers due to the same event attributes such as sensor type and event type. At the same time, the event can be fully described through the sensor type identifier, event type identifier, event content identifier, and event level identifier in the event identifier, thereby facilitating users' operation and maintenance of the system.

[0139] Referring to Table 5 and Table 7 in the above embodiment, for the same sensor type, event type, event content and event level, the report events of different components are distinguished due to the component type identifier and the component serial number in the event identifier; the same is true for Table 6 and Table 8, which shows that the problem of the same OID when the same report event occurs in different components is solved, which makes it convenient for users to directly distinguish the report events about different components through the event OID.

[0140] On the basis of the above embodiment, when a report event is monitored, an event identifier corresponding to the report event is generated, including: obtaining identifier function configuration information, the identifier function configuration information indicates whether the user only has a fault handling identifier acquisition requirement for the preset key component; if it is determined according to the identifier function configuration information that the user only has a fault handling identifier acquisition requirement for the preset key component, then when the report event is a fault event of the preset key component, only a fault handling identifier corresponding to the fault event is generated.

[0141] Optionally, if it is determined based on the identifier function configuration information that the user only has a need to obtain a fault handling identifier for the preset key component, when the reported event is a non-fault event, or a fault event that does not belong to the preset key component, only an event identifier for the reported event is generated.

[0142] The identifier function configuration information indicates the user's concern for fault handling. When the user's concern for fault handling is high, the identifier function configuration information can be configured so that when the reported event is a fault event of a preset key component, only the fault handling identifier corresponding to the fault event is generated; and for non-fault events, or fault events that do not belong to the preset key components, only the event identifier of the reported event is generated.

[0143] Alternatively, if it is determined based on the identifier function configuration information that the user has a need to obtain an event identifier for the preset key component, then when the reported event is a fault event of the preset key component, an event identifier and a fault handling identifier for the fault event are generated.

[0144] The disclosed embodiment determines whether to generate only a corresponding fault handling identifier for a fault event of a preset key component, or to generate an event identifier and a fault handling identifier, based on the user's demand for obtaining a fault handling identifier, so as to meet the needs of different users or different businesses and improve the flexibility of identifier generation.

[0145] In some embodiments, obtaining the fault diagnosis result corresponding to the fault event includes: if the faulty component cannot be automatically repaired, determining that the fault handling suggestion is to replace the faulty component; or, if the faulty component can be automatically repaired, determining that the fault handling suggestion is to ignore the fault event.

[0146] Correspondingly, determining the fault suggestion identifier based on the fault handling suggestion includes: if the fault handling suggestion is to replace the faulty component, then setting the fault suggestion identifier position to a first preset value, and the first preset value indicates that the fault suggestion identifier is a replacement identifier; or, if the fault handling suggestion is to ignore the fault event, then setting the fault suggestion identifier position to a second preset value, and the second preset value indicates that the fault suggestion identifier is an ignore identifier.

[0147] When a fault event occurs, after detection and evaluation by the fault detection service, it is found that the faulty component has been damaged to the extent that it cannot be automatically repaired by its own mechanism or external auxiliary means. At this time, the fault handling suggestion is to replace the faulty component. For example, when the hard disk is physically damaged and cannot be automatically repaired, it is necessary to replace the hard disk in time, and the corresponding fault handling suggestion of replacing the faulty component is given, that is, the replacement part identification.

[0148] When the fault detection service detects and evaluates that the faulty component has the function of automatic repair and the current fault condition is within its automatic repair capability, the fault handling recommendation can be determined to be to ignore the fault event. In this case, the component itself can effectively solve the fault problem without human intervention, and the device or system can continue to operate normally. Accordingly, the fault handling recommendation of ignoring the fault event is given, that is, the ignore mark.

[0149] Correspondingly, the fault handling identifier includes a fault suggestion identification field, called a fault suggestion identification bit, which can be set to a first preset value or a second preset value, wherein the first preset value represents a replacement mark, and the second preset value represents an ignore mark.

[0150] The disclosed embodiment determines the fault suggestion identifier in the fault handling identifier based on the fault handling suggestion, so that the user can quickly determine the corresponding fault handling means based on the fault handling identifier, thereby further improving operation and maintenance efficiency.

[0151] In some embodiments, the fault handling identifier further includes: a special identifier distinction code and a fault type identifier.

[0152] The special identifier distinction code is used to distinguish the event identifier from the fault handling identifier, the OID with the special identifier distinction code is the fault handling identifier, and the OID without the special identifier distinction code is the event identifier. Optionally, the special identifier distinction code is a fixed string, such as 0xFF.

[0153] The fault type identifier represents the fault content corresponding to the fault event.

[0154] Optionally, the fault handling identifier also includes a fault component identifier. Generating a fault handling identifier corresponding to the fault event based on the fault component and the fault suggestion identifier includes: obtaining a component type identifier corresponding to the component type of the fault component according to a preset component type identifier mapping table; constructing a fault component identifier of the fault component based on the component type identifier and the component serial number of the fault component; and generating a fault handling identifier corresponding to the fault event based on the fault component identifier and the fault suggestion identifier.

[0155] The preset component type identification mapping table gives the component type identification corresponding to each component type, and the component type identification will constitute a part of the fault handling identifier. Since there may be multiple components of the same component type in the network device 21, the components that fail each time may also be different components under the same component type. In order to further distinguish different components of the same type, component serial numbers are respectively assigned to different components under the same component type, for example, different numbers are used as component serial numbers of different components under the same component type. Combined with the component type identification and the component serial number, the specific faulty component corresponding to the fault event is determined.

[0156] The following is a table of fault handling identifiers:

[0157] Table 9 Fault handling identifier composition table

[0158]

[0159] As shown in Table 9, the fault handling identifier includes a special identifier identification code, a component type identifier, a component serial number, a fault type identifier, and a fault suggestion identifier.

[0160] On this basis, an example of the composition of a fault handling identifier is given. When a CPU fault occurs, after analysis by the BMC fault diagnosis service, it is determined that the first CPU has a Processor Socket Disable fault, and the fault handling recommendation is to replace the component. The corresponding CPU fault handling identifier (CPU fault handling OID) is shown in the following table:

[0161] Table 10 CPU fault handling OID

[0162]

[0163] The binary data combination of each field in Table 10 is 11111111000001110000010101100001, which is converted into hexadecimal data as FF070561. The CPU fault processing identifier is 0xFF070561.

[0164] In the disclosed embodiment, the fault handling identifier fully describes the various attributes of the fault event. The user can clearly identify the fault identification code based on the special identifier difference code, and further obtain corresponding fault handling suggestions, which is convenient for troubleshooting and handling of system faults.

[0165] In some embodiments, the method also includes: responding to a user's identifier filtering request, obtaining filtering conditions corresponding to the identifier filtering request, the filtering conditions including at least one identification field and / or identification value in the fault handling identifier; obtaining at least one fault handling identifier containing the identification field and / or identification value; retrieving a fault event log corresponding to the fault handling identifier; and feeding back the fault handling identifier and / or the fault event log to the user.

[0166] When a user sends an identifier screening request to the system, the system will first parse the request to obtain the screening conditions corresponding to the request. The screening conditions mainly involve key information in the fault handling identifier, specifically, may include at least one identification field and / or identification value in the fault handling identifier.

[0167] Among them, the identification fields are the various fields that make up the fault handling identifier, including: special identifier distinction code, component type identifier, component serial number, fault type identifier, and fault suggestion identifier; and the identification value is the specific value corresponding to each identification field.

[0168] After obtaining the screening conditions, the system will search the database to find at least one fault handling identifier containing the specified identification field and / or identification value. Optionally, the screening conditions also include a plurality of identification fields and / or identification value logical calculation relationships, such as AND, OR, NOT logical relationships.

[0169] After finding the fault handling identifiers that meet the conditions, the system will further retrieve the fault event logs corresponding to these identifiers. The fault event log records detailed information such as the occurrence of the fault, the handling process, and the handling results, providing users with a more comprehensive and in-depth understanding of the fault handling situation and helping users to better understand the details of the entire fault event. Finally, the system will feedback the selected fault handling identifiers and / or fault event logs to the user.

[0170] The disclosed embodiment searches for qualified fault handling identifiers and / or fault event logs based on the user's identifier screening request, so that the user can quickly find the fault handling data he needs according to the fault handling identifier and / or fault event log, thereby better performing fault analysis, processing effect evaluation and other tasks, improving the efficiency and accuracy of fault handling, greatly enhancing the user experience in fault handling data query, and enabling the user to obtain valuable information more conveniently.

[0171] Figure 4 The schematic diagram of the structure of the identifier generation device provided in the embodiment of the present disclosure. The identifier generation device may be a BMC as described in the above embodiment, or the identifier generation device may be a component or assembly in the BMC. The identifier generation device provided in the embodiment of the present disclosure may execute the processing flow provided in the identifier generation method embodiment, such as Figure 4 As shown, the identifier generating device 40 includes a first acquisition module 41, a first determination module 42, and a generation module 43; the first acquisition module 41 is used to obtain a fault diagnosis result corresponding to the fault event when a fault event is monitored, and the fault diagnosis result includes a fault component and a fault handling suggestion; the first determination module 42 is used to determine a fault suggestion identifier according to the fault handling suggestion if the fault component belongs to a preset key component; the generation module 43 is used to generate a fault handling identifier corresponding to the fault event based on the fault component and the fault suggestion identifier.

[0172] Optionally, the first acquisition module 41 includes a first generation unit 411 and a first acquisition unit 412; the first generation unit 411 is used to generate an event identifier corresponding to the report event when a report event is monitored; the first acquisition unit 412 is used to obtain the fault diagnosis result corresponding to the fault event if the report event is a fault event.

[0173] Optionally, the first generating unit 411 is specifically configured to determine an event occurrence component corresponding to the reported event; determine a component identification of the event occurrence component according to a preset component type identification mapping table; and generate an event identifier corresponding to the reported event based on the component identification.

[0174] Optionally, the first generating unit 411 is specifically configured to obtain the component type identifier corresponding to the component type of the event-occurring component according to the preset component type identifier mapping table; and construct the component identifier based on the component type identifier and the component serial number of the event-occurring component.

[0175] Optionally, the first generation unit 411 is also used to obtain identifier function configuration information, and the identifier function configuration information represents whether the user only has a fault handling identifier acquisition requirement for the preset key component; if it is determined according to the identifier function configuration information that the user only has a fault handling identifier acquisition requirement for the preset key component, then when the reported event is a fault event of the preset key component, only a fault handling identifier corresponding to the fault event is generated.

[0176] Optionally, the event identifier also includes: a sensor type identifier, an event type identifier, an event content identifier, and an event level identifier.

[0177] Optionally, the first acquisition module 41 is used to determine that the fault handling suggestion is to replace the faulty component if the faulty component cannot be automatically repaired; or, if the faulty component can be automatically repaired, determine that the fault handling suggestion is to ignore the fault event.

[0178] Optionally, the first determination module 42 is used to set the fault suggestion identification position to a first preset value if the fault handling suggestion is to replace a faulty component, and the first preset value indicates that the fault suggestion identification is a replacement mark; or, if the fault handling suggestion is to ignore the fault event, set the fault suggestion identification position to a second preset value, and the second preset value indicates that the fault suggestion identification is an ignore mark.

[0179] Optionally, the identifier generating device 40 further includes a second determining module 44, which is used to obtain a key component type list based on key component configuration information; if the key component type list includes the component type of the faulty component, it is determined that the faulty component belongs to a preset key component.

[0180] Optionally, the generation module 43 includes a second acquisition unit 431, a construction unit 432, and a second generation unit 433; the second acquisition unit 431 is used to obtain the component type identifier corresponding to the component type of the faulty component according to a preset component type identifier mapping table; the construction unit 432 is used to construct the faulty component identifier of the faulty component based on the component type identifier and the component serial number of the faulty component; the second generation unit 433 generates a fault handling identifier corresponding to the fault event based on the faulty component identifier and the fault suggestion identifier.

[0181] Optionally, the identifier generating device 40 also includes a screening module 45, the screening module 45 includes a third acquisition unit 451, a fourth acquisition unit 452, a retrieval unit 453, and a feedback unit 454; the third acquisition unit 451 is used to respond to the user's identifier filtering request, and obtain the filtering conditions corresponding to the identifier filtering request, and the filtering conditions include at least one identification field and / or identification value in the fault handling identifier; the fourth acquisition unit 452 is used to obtain at least one fault handling identifier containing the identification field and / or identification value; the retrieval unit 453 is used to retrieve the fault event log corresponding to the fault handling identifier; the feedback unit 454 is used to feed back the fault handling identifier and / or the fault event log to the user.

[0182] Optionally, the fault handling identifier also includes: a special identifier distinction code and a fault type identifier.

[0183] Figure 4The identifier generation device of the illustrated embodiment can be used to execute the technical solution of the above-mentioned method embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0184] Figure 5 The electronic device provided by the embodiment of the present disclosure may be a BMC as described in the above embodiment. The electronic device provided by the embodiment of the present disclosure may execute the processing flow provided by the kernel upgrade method embodiment, such as Figure 5 As shown, the electronic device 50 includes: a memory 51, a processor 52, a computer program and a communication interface 53; wherein the computer program is stored in the memory 51 and is configured so that the processor 52 executes the identifier generation method as described above.

[0185] In addition, an embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored. The computer program is executed by a processor to implement the identifier generation method described in the above embodiment.

[0186] In addition, an embodiment of the present disclosure further provides a computer program product, which includes a computer program or instructions, and when the computer program or instructions are executed by a processor, the identifier generation method as described above is implemented.

[0187] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0188] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating an identifier, characterized in that: The method comprises: When a fault event is detected, a fault diagnosis result corresponding to the fault event is obtained, wherein the fault diagnosis result includes a faulty component and a fault handling suggestion; If the faulty component belongs to a preset key component, determining a fault suggestion identifier according to the fault handling suggestion; A fault handling identifier corresponding to the fault event is generated based on the fault component and the fault suggestion identifier.

2. The identifier generation method according to claim 1, characterized in that: When a fault event is monitored, obtaining a fault diagnosis result corresponding to the fault event includes: When a report event is detected, an event identifier corresponding to the report event is generated; If the reported event is a fault event, a fault diagnosis result corresponding to the fault event is obtained.

3. The identifier generation method according to claim 2, characterized in that: When a report event is monitored, generating an event identifier corresponding to the report event includes: Determine an event occurrence component corresponding to the reported event; Determine the component identification of the component where the event occurs according to a preset component type identification mapping table; An event identifier corresponding to the report event is generated based on the component identification.

4. The identifier generation method according to claim 3, characterized in that: The step of determining the component identification of the component where the event occurs according to a preset component type identification mapping table includes: According to the preset component type identification mapping table, obtaining the component type identification corresponding to the component type of the event occurrence component; The component identification is constructed based on the component type identification and the component serial number of the event-occurring component.

5. The identifier generation method according to claim 2, characterized in that: When a report event is monitored, generating an event identifier corresponding to the report event includes: Acquiring identifier function configuration information, where the identifier function configuration information indicates whether the user only needs to obtain a fault handling identifier for the preset key component; If it is determined based on the identifier function configuration information that the user only has a need to obtain a fault handling identifier for the preset key component, then when the reported event is a fault event of the preset key component, only a fault handling identifier corresponding to the fault event is generated.

6. The identifier generation method according to any one of claims 2 to 5, characterized in that: The event identifier also includes: Sensor type identification, event type identification, event content identification, event level identification.

7. The identifier generation method according to claim 1, characterized in that: The obtaining of the fault diagnosis result corresponding to the fault event includes: If the faulty component cannot be automatically repaired, determining that the fault handling suggestion is to replace the faulty component; or, If the faulty component can be automatically repaired, the fault handling suggestion is determined to be ignoring the fault event.

8. The identifier generation method according to claim 7, characterized in that: The determining a fault suggestion identifier according to the fault handling suggestion includes: If the fault handling suggestion is to replace the faulty component, the fault suggestion identifier is set to a first preset value, where the first preset value indicates that the fault suggestion identifier is a replacement identifier; or, If the fault handling suggestion is to ignore the fault event, the fault suggestion flag is set to a second preset value, and the second preset value indicates that the fault suggestion flag is an ignore flag.

9. The identifier generation method according to claim 1, characterized in that: If the faulty component is a preset key component, before determining the fault suggestion identifier according to the fault handling suggestion, the method further includes: Based on the key component configuration information, obtain a key component type list; If the key component type list includes the component type of the faulty component, it is determined that the faulty component belongs to a preset key component.

10. The identifier generation method according to claim 1, characterized in that: The generating a fault handling identifier corresponding to the fault event based on the fault component and the fault suggestion identifier includes: According to a preset component type identification mapping table, obtaining a component type identification corresponding to the component type of the faulty component; Constructing a faulty component identification of the faulty component based on the component type identification and the component serial number of the faulty component; A fault handling identifier corresponding to the fault event is generated based on the fault component identifier and the fault suggestion identifier.

11. The identifier generation method according to claim 1, characterized in that: The method further comprises: In response to an identifier screening request from a user, obtaining a screening condition corresponding to the identifier screening request, wherein the screening condition includes at least one identification field and / or identification value in the fault handling identifier; Obtain at least one fault handling identifier including the identification field and / or identification value; Retrieving the fault event log corresponding to the fault handling identifier; The fault handling identifier and / or the fault event log are fed back to the user.

12. The identifier generation method according to any one of claims 7 to 11, characterized in that: The fault processing identifier also includes: a special identifier distinction code and a fault type identifier.

13. An electronic device, characterized in that: include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and is configured to be executed by the processor to implement the method according to any one of claims 1 to 12.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

15. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

Images