Hardware management method, device and equipment in credential environment and medium

Abstract

The invention provides a hardware management method, device and equipment in a credential environment and a medium, and the method comprises the steps: deploying a credential hardware management tool based on Redfish, IPMI and SNMP Trap protocols in the credential environment, so as to manage multiple server hardware of different models; according to the tool, Redfish and an IPMI protocol are used for information collection and interaction with a CMDB, and meanwhile, Redfish and an SNMP Trap protocol are used for active / passive alarm collection; and the collected alarm information is sent to an operation and maintenance tool and is used for generating network topology, updating firmware in batches and providing technical support. According to the invention, hardware management in a credential environment can be realized.

Description

Technical Field

[0001] The present application relates to the field of alarm management technology, and in particular to a hardware management method, device, equipment and medium in an information and communication environment. Background Art

[0002] With the rapid development of information technology, informatization has become a key means for all industries to enhance their competitiveness and achieve business innovation. In the process of informatization construction, server hardware, as the core infrastructure supporting various applications and businesses, is of vital importance for its stability and reliability. However, with the diversification and complexity of server hardware, how to efficiently manage these hardware resources and ensure their normal operation has become an urgent problem to be solved.

[0003] Traditionally, server hardware management mainly relies on dedicated management tools provided by manufacturers, but these tools often have problems such as poor compatibility and low management efficiency. Especially in the environment of information technology innovation (i.e. information technology application innovation), due to the involvement of server hardware of different brands and models, as well as self-controllable operating systems and databases and other components, traditional management methods can no longer meet actual needs. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a hardware management method, device, electronic device and storage medium in a trusted computing environment, which can realize hardware management in a trusted computing environment.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] In a first aspect, an embodiment of the present application provides a hardware management method in a trusted computing environment, the method comprising:

[0007] Deploy an ICT hardware management tool based on the Redfish protocol, IPMI protocol and SNMP Trap protocol in the ICT environment; wherein the ICT environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms on the managed server hardware;

[0008] Based on the trusted hardware management tool, alarm information of multiple server hardware of different models in the trusted environment is collected;

[0009] The alarm information is sent as upstream data to an operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

[0010] In a second aspect, an embodiment of the present application further provides a hardware management device in a trusted environment, the device comprising:

[0011] A deployment module, used to deploy an ICT hardware management tool based on the Redfish protocol, the IPMI protocol and the SNMP Trap protocol in the ICT environment; wherein the ICT environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms for the managed server hardware;

[0012] A collection module, used to collect alarm information of multiple server hardware of different models in the credible innovation environment based on the credible innovation hardware management tool;

[0013] The sending module is used to send the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

[0014] In the third aspect, an embodiment of the present application also provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to execute the hardware management method in the trusted innovation environment described in any one of the first aspects.

[0015] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the hardware management method in the trusted innovation environment described in any one of the first aspects is executed.

[0016] The embodiments of the present application have the following beneficial effects:

[0017] (1) Unified management across models: The embodiment of the present application implements unified management of multiple server hardware of different models in the trusted innovation environment by deploying trusted innovation hardware management tools based on the Redfish protocol, IPMI protocol, and SNMPTrap protocol. This greatly simplifies operation and maintenance work, reduces management costs, and improves management efficiency.

[0018] (2) Efficient alarm management: By using the Redfish protocol and SNMP Trap protocol, the embodiment of the present application can collect active / passive alarm information of the managed server hardware in real time and accurately. Through information interaction with the CMDB, the alarm information can be quickly located and processed, thereby effectively reducing the risk and impact of failures.

[0019] (3) Intelligent classification and location: By counting and classifying the alarm information, the embodiment of the present application can intelligently identify and locate the fault type. This helps the operation and maintenance personnel to quickly understand the fault situation and formulate effective solutions, thereby improving the efficiency and accuracy of fault handling.

[0020] (4) Optimizing the operation and maintenance process: The embodiment of the present application sends the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool can generate network topology, batch update firmware and provide technical support based on this data. This not only optimizes the operation and maintenance process, but also improves the automation level of operation and maintenance work.

[0021] (5) Good scalability: The embodiment of the present application supports the adaptation of new server hardware models. By obtaining the model of the new server hardware and expanding the trusted hardware management tool, it can be ensured that the management tool can continue to meet the development needs of the trusted environment.

[0022] (6) Compatibility and flexibility: The trusted innovation environment includes multiple components such as the front-end application server, the back-end application server, and the database. The front-end application server uses the Kylin v10 operating system, and the database is the Oceanbase database. This design makes the embodiment of the present application have good compatibility and flexibility, and can adapt to trusted innovation environments of different scales and types.

[0023] (7) Improve operation and maintenance efficiency and quality: By integrating hardware management, alarm collection and processing, operation and maintenance tool support and other aspects, the embodiments of the present application provide comprehensive and convenient management means for operation and maintenance personnel. This not only improves the operation and maintenance efficiency, but also improves the quality and reliability of the operation and maintenance work.

[0024] To sum up, the embodiments of the present application have significant beneficial effects in hardware management under the information and communication technology environment, can reduce management costs, improve management efficiency, optimize operation and maintenance processes, improve operation and maintenance quality, and have good scalability and compatibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0026] Figure 1 is a flowchart of steps S101-S103 provided in an embodiment of the present application;

[0027] Figure 2 It is a flowchart of steps S201-S202 provided in an embodiment of the present application;

[0028] Figure 3 This is one of the hardware management principle diagrams in the information innovation environment provided by the embodiment of the present application;

[0029] Figure 4 It is a flowchart of steps S401-S403 provided in an embodiment of the present application;

[0030] Figure 5 This is the second schematic diagram of hardware management in the trusted innovation environment provided by the embodiment of the present application;

[0031] Figure 6 It is a flowchart of steps S601-S602 provided in an embodiment of the present application;

[0032] Figure 7 This is the third schematic diagram of hardware management in the trusted innovation environment provided by the embodiment of the present application;

[0033] Figure 8 This is the fourth schematic diagram of hardware management in the trusted innovation environment provided by the embodiment of the present application;

[0034] Fig. 9 It is a flowchart of steps S901-S902 provided in an embodiment of the present application;

[0035] Fig.10 It is a structural diagram of a hardware management device in a trusted computing environment provided by an embodiment of the present application;

[0036] Fig.11 It is a schematic diagram of the composition structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0037] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0038] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0039] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0040] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0041] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0042] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0043] See also Figure 1 , Figure 1This is a flowchart of steps S101-S103 of the hardware management method in the trust innovation environment provided by the embodiment of the present application, which will be combined with Figure 1 Steps S101-S103 are shown for explanation.

[0044] In step S101, a trusted computing hardware management tool based on the Redfish protocol, IPMI protocol and SNMP Trap protocol is deployed in the trusted computing environment; wherein the trusted computing environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms for the managed server hardware.

[0045] The Redfish protocol is used to collect information about the hardware of the managed server and to exchange information with the configuration management database (CMDB). Redfish is an open, REST-based industry standard protocol with a simple, unified, scalable and secure management method, suitable for hardware management of modern servers. The IPMI protocol is also used for information collection, and may focus on lower-level hardware management functions such as remote monitoring, power management, event logging, etc. IPMI is implemented through a hardware-based management controller (BMC) and does not require operating system support. It is suitable for various servers and embedded systems. The SNMP Trap protocol is used to collect alarm information about the hardware of the managed server, including active alarms and passive alarms. SNMP Trap allows managed devices to actively notify the SNMP manager without waiting for the manager to poll, which improves the timeliness of alarm responses.

[0046] Deploy the trusted hardware management tool based on the above protocol in the trusted environment. Ensure that the management tool can communicate with each server hardware and correctly configure the relevant parameters.

[0047] In step S102, alarm information of multiple server hardware of different models in the trusted computing environment is collected based on the trusted computing hardware management tool.

[0048] Here, management tools are used to collect real-time alarm information of multiple server hardware of different models in the information innovation environment. The alarm information includes hardware failure, performance degradation, security vulnerabilities, etc.

[0049] In step S103, the alarm information is sent as upstream data to an operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

[0050] Here, the collected alarm information is sent to the operation and maintenance tool as upstream data. The operation and maintenance tool performs further analysis and processing based on the received upstream data. The operation and maintenance tool uses the alarm information and other relevant data to generate a network topology diagram of the information creation environment to help administrators intuitively understand the connection relationship and status of each server hardware. Based on the alarm information, the operation and maintenance tool can automatically or manually trigger the firmware update operation to ensure that the firmware version of each server hardware remains consistent and secure. The operation and maintenance tool can also provide technical support to technicians, such as troubleshooting, performance optimization, etc.

[0051] In some embodiments, see Figure 2 , Figure 2 It is a flow chart of steps S201-S202 provided in an embodiment of the present application. The alarm information of multiple server hardware of different models in the trusted computing environment is collected based on the trusted computing hardware management tool. It can be achieved through steps S201-S202, which will be explained in combination with each step.

[0052] In step S201, for the multiple server hardwares of different models, the Redfish interface documents of the multiple server hardwares of different models are obtained, and a common interface document is determined from the Redfish interface documents.

[0053] In step S202, based on the common interface document, the alarm information is captured through the Redfish protocol and the IPMI protocol, and information is exchanged with the CMDB.

[0054] See also Figure 3 , Figure 3 This is one of the hardware management principle diagrams in the trust innovation environment provided by the embodiment of the present application, such as Figure 3 As shown in the figure, we use Redfish and IPMI protocols to capture and collect information from managed servers and interact with the company's internal CMDB. Information capture process We collected most server Redfish interfaces and tried to find common interface documents to capture information.

[0055] Specifically, for multiple different types of server hardware deployed in the trusted innovation environment, obtain their respective Redfish interface documents. Redfish interface documents are provided by server hardware manufacturers to describe the functions, parameters, and calling methods of their Redfish management interfaces. These documents usually include information such as the URL, request method, request parameters, and response format of the RESTful API.

[0056] After obtaining the Redfish interface documents of multiple different types of server hardware, you need to analyze these documents to find the common interfaces between them. Common interfaces refer to interfaces with the same or similar functions and consistent parameter formats in the Redfish interface documents of different types of server hardware. Common interface document: Through comparative analysis, determine a common interface document that contains all the common interfaces related to the alarm information that needs to be collected. This common interface document will serve as the basis for subsequent capture of alarm information.

[0057] Based on the common interface document, choose to use the Redfish protocol and IPMI protocol to capture alarm information. The Redfish protocol is mainly used to obtain the status, configuration, and alarm information of the server hardware through RESTful API calls, while the IPMI protocol may be used to obtain lower-level hardware management information. Information capture: According to the interface description in the common interface document, send requests to the server hardware through the Redfish protocol and IPMI protocol to obtain alarm information. These alarm information may include hardware failures, performance anomalies, security events, etc.

[0058] The captured alarm information is integrated and formatted to meet the storage and query requirements of CMDB, and the integrated alarm information is sent to CMDB for storage and management. CMDB is the abbreviation of configuration management database, which is used to store and manage configuration items and their relationships in IT environment. Through information interaction with CMDB, functions such as centralized management, correlation analysis and historical tracing of alarm information can be realized.

[0059] The above method, through the steps of obtaining Redfish interface documents, determining common interface documents, capturing alarm information, and interacting with CMDB, realizes the effective collection and management of hardware alarm information of multiple different models of servers in the information innovation environment. This helps to improve operation and maintenance efficiency, reduce operation and maintenance costs, and provide stable and reliable support for the enterprise's IT environment.

[0060] In some embodiments, see Figure 4 , Figure 4 It is a flow chart of steps S401-S403 provided in an embodiment of the present application. The alarm information of multiple server hardware of different models in the trusted computing environment is collected based on the trusted computing hardware management tool. It can be achieved through steps S401-S403, which will be explained in combination with each step.

[0061] In step S401, for the multiple server hardwares of different models, alarm events of the multiple server hardwares of different models are counted, and the same keyword information is captured based on the alarm events.

[0062] In step S402, the warning information is classified and located based on the keyword information.

[0063] In step S403, the alarm information is actively / passively collected through the Redfish protocol and the SNMP Trap.

[0064] See also Figure 5 , Figure 5 This is the second schematic diagram of hardware management in the trust innovation environment provided by the embodiment of the present application, such as Figure 5 As shown in the figure, Redfish and SNMP Trap protocols are used to collect active and passive alarms from managed servers. In order to achieve alarm collection compatibility with servers of multiple brands and models, the BMC alarm event information of all models is counted, and the same keywords [memory, dimm], [cpu], [disk, hdd, drive], [raid], [pcie], [fan], [power, psu] are captured to classify and locate alarms, instead of matching the entire alarm event with the fault content, which optimizes the matching mechanism of internal alarm events in the product.

[0065] Specifically, for multiple different types of server hardware deployed in the information innovation environment, first count the alarm events they generate. These alarm events may be caused by hardware failures, software anomalies, network problems, and other reasons. After counting the alarm events, capture the same or similar keyword information from each alarm event. These keyword information can be the description of the alarm event, error code, impact range, etc.

[0066] Based on the captured keyword information, the alarm information is classified. The purpose of classification is to group alarm information with similar characteristics or attributes into one category for subsequent unified processing and analysis. Based on the classification, the source of the alarm information is further located, including determining the key information such as the server hardware model, location, and business that generated the alarm event, so that the operation and maintenance personnel can quickly locate the problem and take appropriate solutions.

[0067] Active collection: Actively send requests to server hardware through the Redfish protocol to obtain its real-time alarm information. The Redfish protocol supports RESTful API calls, which can easily obtain the status, configuration and alarm information of server hardware.

[0068] Passive collection: Receive alarm information actively sent by server hardware through the SNMP Trap protocol. When the server hardware detects an abnormality or failure, it will actively send a Trap message to the SNMP manager (i.e., the Xinchuang hardware management tool), containing detailed information of the alarm event.

[0069] After completing the statistics of alarm information, capturing keyword information, classification and positioning, and active / passive collection, the Xinchuang hardware management tool will integrate and store these alarm information. Operation and maintenance personnel can view and manage these alarm information through the Xinchuang hardware management tool, quickly locate problems and take solutions based on the classification and positioning results. At the same time, the Xinchuang hardware management tool can also be integrated with the CMDB (configuration management database) to associate alarm information with configuration items to achieve more comprehensive IT asset management.

[0070] The above method, through the steps of counting alarm events, capturing keyword information, classifying and locating alarm information, and actively / passively collecting alarm information, realizes the effective collection and management of hardware alarm information of multiple different models of servers in the information innovation environment. This helps to improve operation and maintenance efficiency, reduce operation and maintenance costs, and provide stable and reliable support for the enterprise's IT environment.

[0071] In some embodiments, in some embodiments, see Figure 6 , Figure 6 It is a flowchart of steps S601-S602 provided in an embodiment of the present application. When the alarm information is classified and located based on the keyword information, steps S601-S602 can also be executed, and each step will be explained in combination.

[0072] In step S601, in the case where a fault generates multiple alarm items, the corresponding relationship between an alarm item and a fault type is located based on the keyword information.

[0073] In step S602, the alarm entries generated within a specified time before and after the alarm entry are classified as the alarm entry.

[0074] Here, when a fault occurs, multiple alarm entries may be triggered. These alarm entries may contain the same or similar keyword information, pointing to the same fault. Using the captured keyword information, locate an alarm entry that best represents the fault type from multiple alarm entries. This can be achieved by comparing the alarm entry's description, error code, impact range and other keyword information. Once the alarm entry that best represents the fault is located, a corresponding relationship between the alarm entry and the fault type is established. This helps operation and maintenance personnel quickly identify and understand the nature of the fault.

[0075] To avoid missing other alarm information related to the main alarm entry, you can specify a time range, usually a period of time before and after the main alarm entry is generated. Within this time range, all alarm entries generated are merged under the main alarm entry. These related alarm entries may provide more details or context information about the fault, which helps operation and maintenance personnel to understand the fault more comprehensively.

[0076] After completing the correspondence between alarm items and fault types and merging related alarm items, the Xinchuang hardware management tool will integrate and store this information. Operation and maintenance personnel can view and manage these integrated alarm information through the Xinchuang hardware management tool, quickly locate problems based on fault types and related alarm items, and take corresponding solutions. At the same time, this information can also be stored and analyzed as historical data for future fault prediction and prevention.

[0077] The above method achieves more accurate classification and location of alarm information by locating the correspondence between alarm items and fault types, merging related alarm items, etc. This helps improve operation and maintenance efficiency, reduce false positives and false negatives, and provide more stable and reliable support for the enterprise's IT environment.

[0078] In some embodiments, the information innovation environment includes a front-end application server, a back-end application server and a database; the front-end application server uses the Kylin v10 operating system, and the database is an Oceanbase database; the back-end application server is used to manage the managed servers, collect server information, and store the alarm information in the database, and interact with the CMDB and the alarm platform to access the front-end application server through a terminal or a jump server to view information and conduct alarm inspections.

[0079] See also Figure 7 , Figure 7 This is the third schematic diagram of hardware management in the trust innovation environment provided by the embodiment of the present application, such as Figure 7 As shown in the figure, the system consists of a front-end application server, a back-end application server, and a database. The front-end and back-end servers use the Kylin v10 operating system, and the database uses the Oceanbase database to meet the requirements of information innovation. The back-end application server manages the managed servers, collects server information and alarms and stores them in the database, and interacts with the company's internal CMDB and alarm platform for data. Users access the front-end application server through a terminal or a jump server to view information, conduct alarm inspections, and other operations.

[0080] See also Figure 8 , Figure 8 This is the hardware management principle diagram of the trust innovation environment provided by the embodiment of the present application. Figure 8 Describe the detailed data flow.

[0081] Figure 8 The process of collecting, processing, visualizing and displaying data from the hard pipe platform is described. Figure 8 As shown, the whole process starts with the "hard pipe platform", then goes through multiple steps and branches, and finally completes the display and processing of data.

[0082] 1. Data collection.

[0083] First, the hard pipe platform sets a regular task through the "scheduled task module", which captures data based on the "filter conditions". The "filter conditions" here can be set according to specific needs in order to filter out specific logs or data.

[0084] Next, the task is divided into two main branches:

[0085] Log capture request: This branch sends a request to the log system to capture log data under specific conditions. The log data will then be processed by "formatted log data" to generate formatted data that meets the display or processing requirements. In addition, it also includes the processing of "logs from various manufacturers" to process log data generated by different device manufacturers.

[0086] Log data: This branch directly obtains existing log data for subsequent processing and analysis.

[0087] 2. Data processing.

[0088] The processing module is responsible for further processing the collected data. In this step, we mainly perform log visualization and management operations.

[0089] Log visualization: By visualizing the formatted log data, we can generate various charts and reports for better understanding and analysis of the data. In particular, the "Alarm Visualization" branch also focuses on displaying data related to alarms to help operation and maintenance personnel quickly discover and respond to potential problems.

[0090] Managers: The processing module can also provide data to managers for review and analysis. This helps managers understand the overall performance and problem points of the system so that they can make corresponding decisions.

[0091] 3. Data presentation

[0092] In the data display stage, we mainly complete it through the "Data Display" branch. This branch includes two sub-branches: "Formatting" and "Hardware Data".

[0093] Formatting: This sub-branch is responsible for the final formatting of the data to ensure that the data can be presented to the user in the best way.

[0094] Hardware data: This sub-branch focuses on displaying data related to hardware, including hardware data of various manufacturers, various types of hardware data, and hardware information. These data can help users better understand the status and performance of the hardware.

[0095] In addition, the embodiments of the present application also include some other related processing. For example, the original hardware data will be filtered and formatted by the device manufacturer data to generate the device manufacturer information. The alarm data will be processed through the steps of capturing, parsing and filtering the alarm data, and finally displayed to the operation and maintenance personnel.

[0096] The above embodiment describes in detail the entire process of the hard pipe platform data flow diagram, and comprehensively explains the data collection, processing and display. Through these steps, we can achieve comprehensive monitoring and management of the hard pipe platform data to ensure the normal operation and efficient operation and maintenance of the system.

[0097] In some embodiments, in some embodiments, see Fig. 9 , Fig. 9 It is a flowchart of steps S901-S902 provided in an embodiment of the present application. When the alarm information is classified and located based on the keyword information, steps S901-S902 may also be executed, and each step will be described in combination.

[0098] In step S901, the model of the newly added server hardware is obtained.

[0099] In step S902, the trusted hardware management tool is expanded based on the model of the newly added server hardware to adapt to the model of the newly added server hardware.

[0100] Here, when new server hardware is added to the trusted innovation environment, the model information of these new hardware needs to be identified and obtained first. This can be achieved by checking the nameplate of the hardware, using the hardware management tool to query, or referring to the documentation provided by the manufacturer. After obtaining the model information of the new hardware, its characteristics need to be analyzed. This includes understanding the hardware configuration, management interface (such as Redfish, IPMI, etc.), supported protocols and alarm mechanisms of the new hardware. According to the characteristics of the new hardware, the existing trusted innovation hardware management tools are updated or expanded. This may include adding support for new hardware models, updating the calling method of the management interface, and adding parsing and processing of new alarm information. After the management tool is expanded, it needs to be fully tested and verified. This includes testing the management functions of the new hardware to ensure that the management tool can correctly identify, monitor and manage the new hardware; at the same time, it is also necessary to test the functions such as the collection, classification and location of alarm information to ensure that the alarm information of the new hardware can be accurately captured and processed.

[0101] After completing the expansion and testing of the trusted hardware management tools, the new server hardware can be formally incorporated into the trusted environment for management. Operation and maintenance personnel can view and manage the status, configuration, and alarm information of these new hardware through the updated management tools to ensure that they can run stably and meet business needs. At the same time, as the trusted environment continues to develop, operation and maintenance personnel also need to regularly update and maintain management tools to adapt to the continuous emergence of new hardware and new technologies.

[0102] The above method achieves the adaptation and management of new hardware by obtaining the model of the newly added server hardware and expanding the trusted hardware management tool. This helps to maintain the stability and scalability of the trusted environment and provide more reliable support for the enterprise's IT environment.

[0103] In summary, the embodiments of the present application have the following beneficial effects:

[0104] (1) Unified management across models: The embodiment of the present application implements unified management of multiple server hardware of different models in the trusted innovation environment by deploying trusted innovation hardware management tools based on the Redfish protocol, IPMI protocol, and SNMPTrap protocol. This greatly simplifies operation and maintenance work, reduces management costs, and improves management efficiency.

[0105] (2) Efficient alarm management: By using the Redfish protocol and SNMP Trap protocol, the embodiment of the present application can collect active / passive alarm information of the managed server hardware in real time and accurately. Through information interaction with the CMDB, the alarm information can be quickly located and processed, thereby effectively reducing the risk and impact of failures.

[0106] (3) Intelligent classification and location: By counting and classifying the alarm information, the embodiment of the present application can intelligently identify and locate the fault type. This helps the operation and maintenance personnel to quickly understand the fault situation and formulate effective solutions, thereby improving the efficiency and accuracy of fault handling.

[0107] (4) Optimizing the operation and maintenance process: The embodiment of the present application sends the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool can generate network topology, batch update firmware and provide technical support based on this data. This not only optimizes the operation and maintenance process, but also improves the automation level of operation and maintenance work.

[0108] (5) Good scalability: The embodiment of the present application supports the adaptation of new server hardware models. By obtaining the model of the new server hardware and expanding the trusted hardware management tool, it can be ensured that the management tool can continue to meet the development needs of the trusted environment.

[0109] (6) Compatibility and flexibility: The trusted innovation environment includes multiple components such as the front-end application server, the back-end application server, and the database. The front-end application server uses the Kylin v10 operating system, and the database is the Oceanbase database. This design makes the embodiment of the present application have good compatibility and flexibility, and can adapt to trusted innovation environments of different scales and types.

[0110] (7) Improve operation and maintenance efficiency and quality: By integrating hardware management, alarm collection and processing, operation and maintenance tool support and other aspects, the embodiments of the present application provide comprehensive and convenient management means for operation and maintenance personnel. This not only improves the operation and maintenance efficiency, but also improves the quality and reliability of the operation and maintenance work.

[0111] To sum up, the embodiments of the present application have significant beneficial effects in hardware management under the information and communication technology environment, can reduce management costs, improve management efficiency, optimize operation and maintenance processes, improve operation and maintenance quality, and have good scalability and compatibility.

[0112] Based on the same inventive concept, the embodiment of the present application also provides a hardware management device in a trusted computing environment corresponding to the hardware management method in the trusted computing environment in the first embodiment. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the hardware management method in the trusted computing environment mentioned above, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0113] like Fig.10 As shown, Fig.10 1 is a schematic diagram of the structure of the hardware management device 1000 in the trust innovation environment provided by the embodiment of the present application. The hardware management device 1000 in the trust innovation environment includes:

[0114] Deployment module 1001, used to deploy an ICT hardware management tool based on the Redfish protocol, IPMI protocol and SNMPTrap protocol in the ICT environment; wherein the ICT environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms for the managed server hardware;

[0115] The collection module 1002 is used to collect alarm information of multiple server hardware of different models in the credible innovation environment based on the credible innovation hardware management tool;

[0116] The sending module 1003 is used to send the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

[0117] Those skilled in the art should understand that Fig.10 The implementation functions of each unit in the hardware management device 1000 in the trusted computing environment shown can be understood by referring to the relevant description of the hardware management method in the trusted computing environment mentioned above. Fig.10 The functions of each unit in the hardware management device 1000 in the trusted computing environment shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0118] In a possible implementation, the collection module 1002 collects alarm information of multiple server hardware of different models in the trusted innovation environment based on the trusted innovation hardware management tool, including:

[0119] For the multiple server hardwares of different models, obtain the Redfish interface documents of the multiple server hardwares of different models, and determine the common interface document from the Redfish interface documents;

[0120] Based on the common interface document, the alarm information is captured through the Redfish protocol and the IPMI protocol, and information interaction is performed with the CMDB.

[0121] In a possible implementation, the collection module 1002 collects alarm information of multiple server hardware of different models in the trusted innovation environment based on the trusted innovation hardware management tool, including:

[0122] For the multiple server hardwares of different models, counting the alarm events of the multiple server hardwares of different models, and capturing the same keyword information based on the alarm events;

[0123] Classifying and locating the warning information based on the keyword information;

[0124] The alarm information is actively / passively collected through the Redfish protocol and the SNMP Trap.

[0125] In a possible implementation manner, the same keyword information includes at least the following keywords:

[0126] [memory,dimm],[cpu],[disk,hdd,drive],[raid],[pcie],[fan],[power,psu].

[0127] In a possible implementation manner, when the collection module 1002 classifies and locates the alarm information based on the keyword information, the method further includes:

[0128] In the case where a fault generates multiple alarm items, locating a corresponding relationship between an alarm item and a fault type based on the keyword information;

[0129] Alarm entries generated within a specified time before or after this alarm entry are classified as this alarm entry.

[0130] In a possible implementation, the information innovation environment includes a front-end application server, a back-end application server and a database; the front-end application server uses the Kylin v10 operating system, and the database is an Oceanbase database; the back-end application server is used to manage the managed servers, collect server information, and store the alarm information in the database, and interact with the CMDB and the alarm platform to access the front-end application server through a terminal or a jump server to view information and perform alarm inspections.

[0131] In a possible implementation, the deployment module 1001 further includes:

[0132] Get the model of the newly added server hardware;

[0133] The collection module 1002 further includes:

[0134] The trusted hardware management tool is expanded based on the model of the newly added server hardware to adapt to the model of the newly added server hardware.

[0135] The hardware management device in the above-mentioned trusted innovation environment has the following beneficial effects:

[0136] (1) Unified management across models: The embodiment of the present application implements unified management of multiple server hardware of different models in the trusted innovation environment by deploying trusted innovation hardware management tools based on the Redfish protocol, IPMI protocol, and SNMPTrap protocol. This greatly simplifies operation and maintenance work, reduces management costs, and improves management efficiency.

[0137] (2) Efficient alarm management: By using the Redfish protocol and SNMP Trap protocol, the embodiment of the present application can collect active / passive alarm information of the managed server hardware in real time and accurately. Through information interaction with the CMDB, the alarm information can be quickly located and processed, thereby effectively reducing the risk and impact of failures.

[0138] (3) Intelligent classification and location: By counting and classifying the alarm information, the embodiment of the present application can intelligently identify and locate the fault type. This helps the operation and maintenance personnel to quickly understand the fault situation and formulate effective solutions, thereby improving the efficiency and accuracy of fault handling.

[0139] (4) Optimizing the operation and maintenance process: The embodiment of the present application sends the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool can generate network topology, batch update firmware and provide technical support based on this data. This not only optimizes the operation and maintenance process, but also improves the automation level of operation and maintenance work.

[0140] (5) Good scalability: The embodiment of the present application supports the adaptation of new server hardware models. By obtaining the model of the new server hardware and expanding the trusted hardware management tool, it can be ensured that the management tool can continue to meet the development needs of the trusted environment.

[0141] (6) Compatibility and flexibility: The trusted innovation environment includes multiple components such as the front-end application server, the back-end application server, and the database. The front-end application server uses the Kylin v10 operating system, and the database is the Oceanbase database. This design makes the embodiment of the present application have good compatibility and flexibility, and can adapt to trusted innovation environments of different scales and types.

[0142] (7) Improve operation and maintenance efficiency and quality: By integrating hardware management, alarm collection and processing, operation and maintenance tool support and other aspects, the embodiments of the present application provide comprehensive and convenient management means for operation and maintenance personnel. This not only improves the operation and maintenance efficiency, but also improves the quality and reliability of the operation and maintenance work.

[0143] To sum up, the embodiments of the present application have significant beneficial effects in hardware management under the information and communication technology environment, can reduce management costs, improve management efficiency, optimize operation and maintenance processes, improve operation and maintenance quality, and have good scalability and compatibility.

[0144] like Fig.11 As shown, Fig.11 The present invention provides a schematic diagram of the structure of an electronic device 1100, wherein the electronic device 1100 includes:

[0145] A processor 1101, a storage medium 1102 and a bus 1103, wherein the storage medium 1102 stores machine-readable instructions executable by the processor 1101. When the electronic device 1100 is running, the processor 1101 communicates with the storage medium 1102 via the bus 1103, and the processor 1101 executes the machine-readable instructions to perform the steps of the hardware management method in the trusted computing environment described in the embodiment of the present application.

[0146] In actual application, the components in the electronic device 1100 are coupled together via the bus 1103. It is understood that the bus 1103 is used to realize the connection and communication between these components. In addition to the data bus, the bus 1103 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.11 Various buses are labeled as bus 1103.

[0147] The above electronic device has the following beneficial effects:

[0148] (1) Unified management across models: The embodiment of the present application implements unified management of multiple server hardware of different models in the trusted innovation environment by deploying trusted innovation hardware management tools based on the Redfish protocol, IPMI protocol, and SNMPTrap protocol. This greatly simplifies operation and maintenance work, reduces management costs, and improves management efficiency.

[0149] (2) Efficient alarm management: By using the Redfish protocol and SNMP Trap protocol, the embodiment of the present application can collect active / passive alarm information of the managed server hardware in real time and accurately. Through information interaction with the CMDB, the alarm information can be quickly located and processed, thereby effectively reducing the risk and impact of failures.

[0150] (3) Intelligent classification and location: By counting and classifying the alarm information, the embodiment of the present application can intelligently identify and locate the fault type. This helps the operation and maintenance personnel to quickly understand the fault situation and formulate effective solutions, thereby improving the efficiency and accuracy of fault handling.

[0151] (4) Optimizing the operation and maintenance process: The embodiment of the present application sends the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool can generate network topology, batch update firmware and provide technical support based on this data. This not only optimizes the operation and maintenance process, but also improves the automation level of operation and maintenance work.

[0152] (5) Good scalability: The embodiment of the present application supports the adaptation of new server hardware models. By obtaining the model of the new server hardware and expanding the trusted hardware management tool, it can be ensured that the management tool can continue to meet the development needs of the trusted environment.

[0153] (6) Compatibility and flexibility: The trusted innovation environment includes multiple components such as the front-end application server, the back-end application server, and the database. The front-end application server uses the Kylin v10 operating system, and the database is the Oceanbase database. This design makes the embodiment of the present application have good compatibility and flexibility, and can adapt to trusted innovation environments of different scales and types.

[0154] (7) Improve operation and maintenance efficiency and quality: By integrating hardware management, alarm collection and processing, operation and maintenance tool support and other aspects, the embodiments of the present application provide comprehensive and convenient management means for operation and maintenance personnel. This not only improves the operation and maintenance efficiency, but also improves the quality and reliability of the operation and maintenance work.

[0155] To sum up, the embodiments of the present application have significant beneficial effects in hardware management under the information and communication technology environment, can reduce management costs, improve management efficiency, optimize operation and maintenance processes, improve operation and maintenance quality, and have good scalability and compatibility.

[0156] An embodiment of the present application also provides a computer-readable storage medium, which stores executable instructions. When the executable instructions are executed by at least one processor 1101, the hardware management method in the trusted computing environment described in the embodiment of the present application is implemented.

[0157] In some embodiments, the storage medium can be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface storage, an optical disk, or a compact disc read-only memory (CD ROM); it can also be various devices including one or any combination of the above memories.

[0158] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0159] As an example, executable instructions may, but do not necessarily, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, for example, in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (for example, files storing one or more modules, subroutines, or code portions).

[0160] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0161] The computer-readable storage medium has the following advantages:

[0162] (1) Unified management across models: The embodiment of the present application implements unified management of multiple server hardware of different models in the trusted innovation environment by deploying trusted innovation hardware management tools based on the Redfish protocol, IPMI protocol, and SNMPTrap protocol. This greatly simplifies operation and maintenance work, reduces management costs, and improves management efficiency.

[0163] (2) Efficient alarm management: By using the Redfish protocol and SNMP Trap protocol, the embodiment of the present application can collect active / passive alarm information of the managed server hardware in real time and accurately. Through information interaction with the CMDB, the alarm information can be quickly located and processed, thereby effectively reducing the risk and impact of failures.

[0164] (3) Intelligent classification and location: By counting and classifying the alarm information, the embodiment of the present application can intelligently identify and locate the fault type. This helps the operation and maintenance personnel to quickly understand the fault situation and formulate effective solutions, thereby improving the efficiency and accuracy of fault handling.

[0165] (4) Optimizing the operation and maintenance process: The embodiment of the present application sends the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool can generate network topology, batch update firmware and provide technical support based on this data. This not only optimizes the operation and maintenance process, but also improves the automation level of operation and maintenance work.

[0166] (5) Good scalability: The embodiment of the present application supports the adaptation of new server hardware models. By obtaining the model of the new server hardware and expanding the trusted hardware management tool, it can be ensured that the management tool can continue to meet the development needs of the trusted environment.

[0167] (6) Compatibility and flexibility: The trusted innovation environment includes multiple components such as the front-end application server, the back-end application server, and the database. The front-end application server uses the Kylin v10 operating system, and the database is the Oceanbase database. This design makes the embodiment of the present application have good compatibility and flexibility, and can adapt to trusted innovation environments of different scales and types.

[0168] (7) Improve operation and maintenance efficiency and quality: By integrating hardware management, alarm collection and processing, operation and maintenance tool support and other aspects, the embodiments of the present application provide comprehensive and convenient management means for operation and maintenance personnel. This not only improves the operation and maintenance efficiency, but also improves the quality and reliability of the operation and maintenance work.

[0169] To sum up, the embodiments of the present application have significant beneficial effects in hardware management under the information and communication technology environment, can reduce management costs, improve management efficiency, optimize operation and maintenance processes, improve operation and maintenance quality, and have good scalability and compatibility.

[0170] In the several embodiments provided in the present application, it should be understood that the disclosed methods and electronic devices can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0171] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0172] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0173] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a platform server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0174] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A hardware management method in a trusted computing environment, characterized in that: The method comprises: Deploy an ICT hardware management tool based on the Redfish protocol, IPMI protocol and SNMP Trap protocol in the ICT environment; wherein the ICT environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms on the managed server hardware; Based on the trusted hardware management tool, alarm information of multiple server hardware of different models in the trusted environment is collected; The alarm information is sent as upstream data to an operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

2. The method according to claim 1, characterized in that The collecting of alarm information of multiple server hardware of different models in the credible innovation environment based on the credible innovation hardware management tool includes: For the multiple server hardwares of different models, obtain the Redfish interface documents of the multiple server hardwares of different models, and determine the common interface document from the Redfish interface documents; Based on the common interface document, the alarm information is captured through the Redfish protocol and the IPMI protocol, and information interaction is performed with the CMDB.

3. The method according to claim 1, characterized in that The collecting of alarm information of multiple server hardware of different models in the credible innovation environment based on the credible innovation hardware management tool includes: For the multiple server hardwares of different models, counting the alarm events of the multiple server hardwares of different models, and capturing the same keyword information based on the alarm events; Classifying and locating the warning information based on the keyword information; The alarm information is actively / passively collected through the Redfish protocol and the SNMP Trap.

4. The method according to claim 3, characterized in that: The same keyword information includes at least the following keywords: [memory,dimm],[cpu],[disk,hdd,drive],[raid],[pcie],[fan],[power,psu].

5. The method according to claim 3, characterized in that: When the warning information is classified and located based on the keyword information, the method further includes: In the case where a fault generates multiple alarm items, locating a corresponding relationship between an alarm item and a fault type based on the keyword information; Alarm entries generated within a specified time before or after this alarm entry are classified as this alarm entry.

6. The method according to claim 1, characterized in that The information innovation environment includes a front-end application server, a back-end application server and a database; the front-end application server uses the Kylin v10 operating system, and the database is an Oceanbase database; the back-end application server is used to manage the managed servers, collect server information, and store the alarm information in the database, and interact with the CMDB and the alarm platform to access the front-end application server through a terminal or a jump server to view information and conduct alarm inspections.

7. The method according to claim 1, characterized in that The method further comprises: Get the model of the newly added server hardware; The trusted hardware management tool is expanded based on the model of the newly added server hardware to adapt to the model of the newly added server hardware.

8. A hardware management device in a trusted computing environment, characterized in that: The device comprises: A deployment module, used to deploy an ICT hardware management tool based on the Redfish protocol, the IPMI protocol and the SNMP Trap protocol in the ICT environment; wherein the ICT environment includes multiple server hardware of different models, the Redfish protocol and the IPMI protocol are used to collect information on the managed server hardware and interact with the CMDB, and the Redfish protocol and the SNMP Trap protocol are used to actively / passively collect alarms for the managed server hardware; A collection module, used to collect alarm information of multiple server hardware of different models in the credible innovation environment based on the credible innovation hardware management tool; The sending module is used to send the alarm information as upstream data to the operation and maintenance tool, so that the operation and maintenance tool generates a network topology, updates firmware in batches, and provides technical support based on the upstream data.

9. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the hardware management method in the information innovation environment as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the hardware management method in the information and communication environment as described in any one of claims 1 to 7 is executed.

Images