A substrate management controller management method, device, equipment and medium

Abstract

The application discloses a substrate management controller management method and device, equipment and medium, and relates to the field of computers.The method comprises the following steps: when a target storage device is identified to be connected to a preset USB interface which is previously connected to a substrate management controller, it is determined whether the target storage device is a registered device; if the target storage device is a registered device, the target storage device is mounted to the current substrate management controller, and a data exchange mode between the target storage device and the substrate management controller is determined based on a permission and an operation mode previously set for the target storage device; and a corresponding data exchange operation is triggered based on the data exchange mode.The application can export data in the BMC to the target storage device or import information in the target storage device to the BMC by using the operation mode previously set in the target storage device, so that the BMC can be conveniently managed, and the operation and maintenance steps are greatly simplified.

Description

Technical Field

[0001] This invention relates to the field of computers, and in particular to a baseboard management controller management method, apparatus, device and medium. Background Technology

[0002] BMC, or Baseboard Management Controller, is a system that allows for firmware upgrades and device monitoring even when the device is powered off. However, if the BMC lacks a network connection or the network is disconnected, it becomes difficult to manage and cannot export data to analyze anomalies.

[0003] As can be seen from the above, how to avoid situations where network problems lead to difficulties in management and the inability to export data for analysis is a problem that needs to be solved in this field when managing BMC. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a baseboard management controller management method, apparatus, device, and medium, capable of transmitting data to achieve firmware upgrades and exporting log data to analyze anomalies. The specific solution is as follows:

[0005] In a first aspect, this application discloses a substrate management controller management method, including:

[0006] When a target storage device is detected to be connected to a preset USB interface that is pre-connected to the baseboard management controller, it is determined whether the target storage device is a registered device.

[0007] If the target storage device is a registered device, the target storage device is attached to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the pre-set permissions and operation mode of the target storage device.

[0008] The corresponding data exchange operation is triggered based on the data exchange mode.

[0009] Optionally, determining whether the target storage device is a registered device includes:

[0010] Determine the device ID of the target storage device;

[0011] Determine whether there is configuration information corresponding to the device ID in the local whitelist; the configuration information includes the device ID, permissions, and operation mode of the target storage device.

[0012] If the configuration information corresponding to the device ID exists in all the configuration information in the local whitelist, then the target storage device is determined to be a registered device;

[0013] If no configuration information corresponding to the device ID is found in the local whitelist, the target storage device is determined to be an unregistered device.

[0014] Optionally, after determining the target storage device as an unregistered device, the method further includes:

[0015] The target storage device must not be mounted to the current baseboard management controller.

[0016] Optionally, after prohibiting the target storage device from being mounted to the current baseboard management controller, the method further includes:

[0017] Obtain a storage device registration instruction and determine the configuration information of the target storage device; the configuration information includes the device ID, permissions, and operation mode of the target storage device.

[0018] The configuration information of the target storage device is recorded in the local whitelist, and the target storage device is identified as a registered device.

[0019] Optionally, after triggering the corresponding data exchange operation based on the data exchange mode, the method further includes:

[0020] If the target storage device is a registered device, then the insertion time of the target storage device is determined, and the device registration status, insertion time, configuration information of the target storage device, and operation information of this data exchange operation are stored in the local device insertion / removal log; the device registration status is "registered".

[0021] Accordingly, the provision that if the target storage device is an unregistered device, then prohibiting the mounting of the target storage device to the current baseboard management controller further includes:

[0022] The registration status of the target storage device is determined to be unregistered, and the insertion time of the target storage device is determined. Then, the registration status and insertion time of the target storage device are stored in the local device insertion / removal log; the device registration status is unregistered.

[0023] Optionally, determining the data exchange mode between the target storage device and the baseboard management controller based on the pre-set permissions and operating modes of the target storage device includes:

[0024] Determine the pre-set permissions and operation modes of the target storage device; the permissions include read-only permission, write-only permission, and read-write permission, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode.

[0025] The data exchange mode between the target storage device and the baseboard management controller is determined based on the pre-set permissions and operation mode of the target storage device; the data exchange mode includes a data receiving mode or a data output mode.

[0026] Optionally, triggering the corresponding data exchange operation based on the data exchange mode includes:

[0027] If the data exchange mode is a data receiving mode, then the first data transmitted by the target storage device is received, and the first data is stored in the target storage location corresponding to the first data;

[0028] If the data exchange mode is a data output mode, then the second data is determined from the local storage based on the operation mode, and the second data is transmitted to the target storage device.

[0029] Secondly, this application discloses a substrate management controller management device, comprising:

[0030] The device connection module is used to determine whether the target storage device is a registered device when it is detected that the target storage device is connected to a preset USB interface that is pre-connected to the baseboard management controller;

[0031] The device mounting module is used to mount the target storage device to the current baseboard management controller if the target storage device is a registered device, and to determine the data exchange mode between the target storage device and the baseboard management controller based on the pre-set permissions and operation mode of the target storage device.

[0032] The data exchange module is used to trigger corresponding data exchange operations based on the data exchange mode.

[0033] Thirdly, this application discloses an electronic device, including:

[0034] Memory, used to store computer programs;

[0035] A processor is used to execute the computer program to implement the aforementioned baseboard management controller management method.

[0036] Fourthly, this application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the aforementioned disclosed baseboard management controller management method.

[0037] In this invention, when a target storage device is detected connected to a preset USB interface pre-connected to the baseboard management controller, it is determined whether the target storage device is a registered device. If the target storage device is registered, it is mounted to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the preset permissions and operating modes of the target storage device. A corresponding data exchange operation is triggered based on the data exchange mode. In this way, by identifying the preset permissions and operating modes of the target storage device to determine the data exchange mode between the target storage device and the baseboard management controller, and triggering a corresponding data exchange operation based on the data exchange mode, the target storage device can be used to manage the baseboard management controller. When the baseboard management controller experiences network problems, since the interaction between the target storage device and the baseboard management controller does not require a network, data in the baseboard management controller can be exported to the target storage device or information in the target storage device can be imported into the baseboard management controller through the preset operating modes in the target storage device, thus achieving convenient management of the baseboard management controller and greatly simplifying the operation and maintenance steps. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0039] Figure 1 A flowchart of a baseboard management controller management method provided in this application;

[0040] Figure 2 A flowchart of a specific baseboard management controller management method provided in this application;

[0041] Figure 3 A schematic diagram of the internal structure of software provided in this application;

[0042] Figure 4 This application provides a schematic diagram of the structure of a substrate management controller management device;

[0043] Figure 5 This application provides a structural diagram of an electronic device. Detailed Implementation

[0044] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0045] In existing technologies, when the BMC lacks a network connection or the network is disconnected, the BMC becomes difficult to manage and cannot export data to analyze anomalies. In this application, even when the BMC experiences network problems, it can still transmit data to enable firmware upgrades and export log data to analyze anomalies.

[0046] This invention discloses a baseboard management controller management method, see [link to relevant documentation]. Figure 1 The method includes:

[0047] Step S11: When the target storage device is detected to be connected to a preset USB interface that is pre-connected to the board management controller, it is determined whether the target storage device is a registered device.

[0048] In this embodiment of the invention, the target storage device is a storage device with a USB (Universal Serial Bus) interface. In some preferred embodiments of the invention, for ease of portability and operation, the target storage device can be a USB flash drive (USB flash drive). Furthermore, since the invention can be applied to servers, the baseboard management controller can be a baseboard management controller within the server.

[0049] It is understood that in this embodiment of the invention, the target storage device is connected to the baseboard management controller via a preset USB interface, and the server can quickly and accurately identify the target storage device when it is connected to the preset USB interface.

[0050] In this embodiment, the baseboard management controller management method further includes: when a target storage device is detected connected to a preset USB interface pre-connected to the baseboard management controller and a storage device registration instruction is obtained, determining the device ID (i.e., Identity document) of the target storage device, obtaining the target permissions and target operation mode of the target storage device through a preset interface, setting the permissions and operation mode of the target storage device to the target permissions and the target operation mode, generating configuration information of the target storage device based on the device ID, the target permissions, and the target operation mode, and then writing the configuration information into a local whitelist. It should be noted that in this embodiment, when registering a storage device, the received permissions and operation mode should be corresponding; that is, the operation mode needs to be supported by the permissions. Specifically, if the operation mode is a configuration file import mode, the permissions need to be set to write-only mode or read-write mode. When the permissions are mistakenly set to read-only mode, read-only does not support the write permissions required by the configuration file import mode. At this time, an error message indicating a configuration error will pop up so that the user can perceive and identify it in a timely manner.

[0051] In this embodiment of the invention, the permissions include read-only permission, write-only permission, and read-write permission, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode. The operation modes can be configured according to different application scenarios, and are not limited to the firmware upgrade mode, log collection mode, and configuration file import mode; specific functional extensions can also be made according to the application scenario.

[0052] In this embodiment of the invention, determining whether the target storage device is a registered device may include: determining the device ID of the target storage device; determining whether there is configuration information corresponding to the device ID in all configuration information in the local whitelist; the configuration information includes the device ID, permissions, and operation mode of the target storage device; if there is configuration information corresponding to the device ID in all configuration information in the local whitelist, then the target storage device is determined to be a registered device; if there is no configuration information corresponding to the device ID in all configuration information in the local whitelist, then the target storage device is determined to be an unregistered device.

[0053] It is understood that in this embodiment of the invention, each target storage device has a device ID, and a local whitelist is pre-set in the server. The local whitelist stores all configuration information of all registered target storage devices, and each piece of configuration information includes the target storage device's device ID, permissions, and operating mode.

[0054] In this embodiment, when a target storage device is detected to be connected to a preset USB interface pre-connected to the baseboard management controller, the target storage device is internally authenticated based on the configuration information in the local whitelist. If the configuration information in all the configuration information in the local whitelist corresponds to the device ID, it indicates that the authentication is successful and the target storage device is a registered device. If the configuration information in all the configuration information in the local whitelist does not correspond to the device ID, it indicates that the authentication fails and the target storage device is an unregistered device.

[0055] In some specific implementations, if the target storage device is a USB flash drive, when the target USB flash drive is detected to be inserted into a preset USB interface pre-connected to the baseboard management controller, internal authentication of the target USB flash drive will be performed. Specifically, the device ID of the target USB flash drive will be determined, and the local whitelist will be queried. Then, it will be determined whether there is configuration information corresponding to the device ID of the USB flash drive in all configuration information in the local whitelist. If there is, it indicates that the authentication is successful and the target USB flash drive is a registered device. If there is no configuration information corresponding to the device ID of the target USB flash drive in all configuration information in the local whitelist, it indicates that the authentication fails and the target USB flash drive is an unregistered device.

[0056] Step S12: If the target storage device is a registered device, then the target storage device is attached to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the pre-set permissions and operation mode of the target storage device.

[0057] In this embodiment, when the target storage device is determined to be a registered device, the target storage device is attached to the current baseboard management controller, and the pre-set permissions and operation mode of the target storage device are determined. Then, the data exchange mode between the target storage device and the baseboard management controller is determined based on the permissions and operation mode.

[0058] In this embodiment of the invention, after determining the target storage device as an unregistered device, the method may further include: prohibiting the target storage device from being mounted to the current baseboard management controller.

[0059] It is understood that, in this embodiment of the invention, when the target storage device is determined to be an unregistered device, for security reasons, this method will prohibit the target storage device from being mounted to the current baseboard management controller in order to protect the security of the BMC.

[0060] In this embodiment of the invention, after prohibiting the mounting of the target storage device to the current baseboard management controller, the method may further include: obtaining a storage device registration instruction and determining the configuration information of the target storage device; the configuration information includes the device ID, permissions, and operating mode of the target storage device; recording the configuration information of the target storage device in a local whitelist, and determining the target storage device as a registered device.

[0061] It is understood that in this embodiment, when an unregistered storage device is inserted into the preset USB interface, according to the method proposed by the present invention, the server will first perform internal authentication on the target USB flash drive. If the internal authentication result is an unregistered device, and a storage device registration instruction is obtained at this time, the storage device that is currently in an unregistered state can be registered. Specifically, the target permissions and target operation mode of the unregistered storage device can be obtained through a preset interface, and the permissions and operation mode of the unregistered storage device can be set to the target permissions and the target operation mode. Based on the device ID, the target permissions, and the target operation mode of the unregistered storage device, configuration information of the unregistered storage device is generated, and then the configuration information is written into the local whitelist.

[0062] Step S13: Trigger the corresponding data exchange operation based on the data exchange mode.

[0063] In this embodiment of the invention, after triggering the corresponding data exchange operation based on the data exchange mode, the method may further include: if the target storage device is a registered device, determining the insertion time of the target storage device, and storing the device registration status, insertion time, configuration information of the target storage device, and operation information of this data exchange operation in the local device insertion / removal log; the device registration status is a registered status; correspondingly, if the target storage device is an unregistered device, prohibiting the mounting of the target storage device to the current baseboard management controller, the method further includes: determining the registration status of the target storage device to an unregistered status, determining the insertion time of the target storage device, and then storing the registration status and insertion time of the target storage device in the local device insertion / removal log; the device registration status is an unregistered status.

[0064] In this embodiment, the server also stores a local device insertion / removal log. The local device insertion / removal log stores the device registration status, device configuration information, insertion time information, and operation information of the current data exchange operation for all storage devices historically connected to the preset USB interface, as well as the insertion time and registration status of unregistered devices. In some specific implementations, the log information stored in the local device insertion / removal log may be: (1) Device ID: 01, Registration status: Registered, Insertion time: January 1, 2020, 12:00:00, Permission: Read / Write, Operation mode: Configuration file import mode, Current data exchange operation: Import .xml file; (2) Device ID: 02, Registration status: Unregistered, Insertion time: January 1, 2020, 4:00:00.

[0065] In this embodiment, after determining the data exchange mode between the target storage device and the baseboard management controller based on the preset permissions and operation modes in the target storage device, a corresponding data exchange operation can be triggered based on the data exchange mode. Specifically, if the target storage device is a USB flash drive, when the USB flash drive is inserted into the preset USB interface and it is determined that the USB flash drive is a registered USB flash drive, if it is determined that the permission of the USB flash drive is read-only and the operation mode of the USB flash drive is log collection mode, then the data exchange mode between the USB flash drive and the baseboard management controller will be determined to be data sending mode based on the read-only permission and the log collection mode. At this time, the server will package the operation log in the server and send it to the USB flash drive. The operation and maintenance personnel can then query the BMC's operation log in the USB flash drive so that they can analyze the abnormal reasons for the current abnormal state of the BMC based on the operation log.

[0066] It should be noted that each operating mode should correspond to its required operating permissions. In some other implementations, if the target storage device does not have the permissions corresponding to the operating mode after the server determines the permissions and operating mode, for example, when the target storage device is pre-configured as a configuration file import mode with read-only permissions, the server will identify the conflict between the operating mode and permissions and return an error message indicating a configuration error so that the user can perceive and identify it in a timely manner.

[0067] In this embodiment, when a target storage device is detected connected to a preset USB interface pre-connected to the baseboard management controller, it is determined whether the target storage device is a registered device. If the target storage device is registered, it is mounted to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the preset permissions and operation mode of the target storage device. A corresponding data exchange operation is triggered based on the data exchange mode. Thus, by identifying the preset permissions and operation mode of the target storage device to determine the data exchange mode between the target storage device and the baseboard management controller, and triggering a corresponding data exchange operation based on the data exchange mode, the present invention can utilize the target storage device to manage the baseboard management controller. When the baseboard management controller experiences network problems, since the interaction between the target storage device and the baseboard management controller does not require a network, data in the baseboard management controller can be exported to the target storage device or information in the target storage device can be imported into the baseboard management controller using the preset operation mode in the target storage device, thereby achieving convenient management of the baseboard management controller and greatly simplifying the operation and maintenance steps.

[0068] Figure 2 This is a flowchart illustrating a specific baseboard management controller management method provided in an embodiment of this application.

[0069] See Figure 2 As shown, the method includes:

[0070] Step S21: When it is detected that the target storage device is connected to a preset USB interface that is pre-connected to the board management controller, it is determined whether the target storage device is a registered device.

[0071] For a more detailed description of the process of step S21, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0072] Step S22: If the target storage device is a registered device, then the target storage device is mounted to the current baseboard management controller, and the pre-set permissions and operation modes of the target storage device are determined; the permissions include read-only permissions, write-only permissions, and read-write permissions, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode.

[0073] In this embodiment, the firmware upgrade mode requires either write-only or read-write permissions, the log collection mode requires either read-only or read-write permissions, and the configuration file import mode requires either write-only or read-write permissions.

[0074] In this embodiment, the server and the target storage device should pre-set the operation flow for each operation mode. Specifically, the firmware upgrade mode requires placing the firmware toolkit to be upgraded and the upgrade material package in the target storage device. When the server recognizes that the operation mode of the target storage device is firmware upgrade mode, it will determine the data exchange mode as data receiving mode and receive the firmware toolkit and the upgrade material package sent by the target storage device. Then, after determining the import location of the firmware toolkit and the material package, it will directly import the toolkit and the material package into the import location.

[0075] Specifically, the log collection mode requires pre-determining the log storage path of the BMC and entering the storage path into the target storage device. When the server recognizes that the operation mode of the target storage device is log collection mode, it will determine the data exchange mode as data output mode. At this time, the target storage device will directly use the log storage path to query the storage location of the log and export the log to the target storage device.

[0076] Specifically, the configuration file import mode can pre-configure certain functions applied to the BMC in the target storage device, such as restoring factory settings, enabling remote multi-terminal recording of data, or changing the default dynamically obtained IP address in the BMC network configuration to a static IP address. In this case, the target storage device can store specific program packages. When the server recognizes that the target storage device's operation mode is configuration file import mode, it will determine the data exchange mode as data receiving mode and receive the specific program packages sent by the target storage device. The BMC can then implement specific functions based on the specific program packages.

[0077] It should be noted that multiple operation modes can also be set simultaneously in this embodiment. That is, a log collection mode and a configuration file import mode can be set in the target storage device in advance, and the permissions can be set to read and write permissions. When the target storage device is detected to be connected to a preset USB interface that is pre-connected to the baseboard management controller, and the permissions and operation mode of the target storage device are determined, the log collection operation and configuration file import operation set in the operation mode will be executed simultaneously.

[0078] Specifically, when the target storage device has multiple operating modes simultaneously, they can be executed sequentially according to their priority. In a specific implementation, when the target storage device's operating modes are log collection mode and configuration file import mode, if the priority of the configuration file import mode is higher than that of the log collection mode, then the configuration file import operation will be performed first, followed by the log collection operation after the configuration file import is complete. It should be noted that the priority of the operating modes described in this embodiment can be arbitrarily configured and changed according to different application scenarios.

[0079] Step S23: Determine the data exchange mode between the target storage device and the baseboard management controller based on the preset permissions and operation mode of the target storage device; the data exchange mode includes a data receiving mode or a data output mode.

[0080] It is understood that in this embodiment, when the operation mode is firmware upgrade mode or configuration file import mode, the corresponding data exchange mode should be data receiving mode, and when the operation mode is log collection mode, the corresponding data exchange mode should be data output mode.

[0081] Step S24: If the data exchange mode is a data receiving mode, then the first data transmitted by the target storage device is received, and the first data is stored in the target storage location corresponding to the first data; if the data exchange mode is a data output mode, then the second data is determined from the local storage based on the operation mode, and the second data is transmitted to the target storage device.

[0082] In this embodiment, if the data exchange mode is a data receiving mode and the operation mode is a firmware upgrade mode or a configuration file import mode, then the firmware toolkit and the upgrade material package or a specific program package sent by the target storage device will be received respectively. At this time, the firmware toolkit and the upgrade material package or the specific program package are the first data. If the data exchange mode is a data output mode and the operation mode is a log collection mode, then log data will be determined from the local storage and the log data will be transmitted to the target storage device as the second data.

[0083] The substrate management controller management method in this application can be specifically applied to USB security management software in a server. The software can be internally divided into, for example, Figure 3 The system consists of three parts: a web (World Wide Web) page display, internal authentication and triggering actions, and data storage. The web page displays the USB drive's insertion / removal logs, configuration options, and a local whitelist. The authentication and triggering actions section authenticates the storage device and triggers corresponding actions. The data storage section stores the whitelist and registered USB drive configuration information.

[0084] In this embodiment, the BMC can be managed according to the pre-set permissions and operation modes in the target storage device. Specifically, the BMC can be upgraded with firmware, collected with logs, and imported with configuration files. When the BMC has network problems, it is convenient to upgrade the firmware or export the logs. Specific functions can also be set for the BMC to improve the convenience of operation and maintenance.

[0085] See Figure 4 As shown in the figure, this application discloses a substrate management controller management device, which may specifically include:

[0086] The device connection module 11 is used to determine whether the target storage device is a registered device when it is detected that the target storage device is connected to a preset USB interface that is pre-connected to the baseboard management controller.

[0087] The device mounting module 12 is used to mount the target storage device to the current baseboard management controller if the target storage device is a registered device, and to determine the data exchange mode between the target storage device and the baseboard management controller based on the preset permissions and operation mode of the target storage device.

[0088] The data exchange module 13 is used to trigger corresponding data exchange operations based on the data exchange mode.

[0089] In this invention, when a target storage device is detected connected to a preset USB interface pre-connected to the baseboard management controller, it is determined whether the target storage device is a registered device. If the target storage device is registered, it is mounted to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the preset permissions and operating modes of the target storage device. A corresponding data exchange operation is triggered based on the data exchange mode. In this way, by identifying the preset permissions and operating modes of the target storage device to determine the data exchange mode between the target storage device and the baseboard management controller, and triggering a corresponding data exchange operation based on the data exchange mode, the target storage device can be used to manage the baseboard management controller. When the baseboard management controller experiences network problems, since the interaction between the target storage device and the baseboard management controller does not require a network, data in the baseboard management controller can be exported to the target storage device or information in the target storage device can be imported into the baseboard management controller through the preset operating modes in the target storage device, thus achieving convenient management of the baseboard management controller and greatly simplifying the operation and maintenance steps.

[0090] In some specific embodiments, the device connection module 11 specifically includes:

[0091] An ID determination unit is used to determine the device ID of the target storage device;

[0092] The configuration information judgment unit is used to determine whether there is configuration information corresponding to the device ID in all configuration information in the local whitelist; the configuration information includes the device ID, permissions, and operation mode of the target storage device.

[0093] The configuration information storage unit is used to determine the target storage device as a registered device if there is configuration information corresponding to the device ID in all configuration information in the local whitelist;

[0094] The configuration information absence unit is used to determine the target storage device as an unregistered device if there is no configuration information corresponding to the device ID in all configuration information in the local whitelist.

[0095] In some specific embodiments, the substrate management controller management device further includes:

[0096] The mounting prohibition unit is used to prohibit the target storage device from being mounted to the current baseboard management controller.

[0097] In some specific embodiments, the substrate management controller management device further includes:

[0098] The device registration unit is used to obtain a storage device registration instruction and determine the configuration information of the target storage device; the configuration information includes the device ID, permissions, and operation mode of the target storage device.

[0099] The information recording unit is used to record the configuration information of the target storage device into a local whitelist and to identify the target storage device as a registered device.

[0100] In some specific embodiments, the substrate management controller management device further includes:

[0101] The first insertion / removal log generation unit is used to determine the insertion time of the target storage device if the target storage device is a registered device, and to store the device registration status, insertion time, configuration information of the target storage device, and operation information of this data exchange operation of the target storage device in the local device insertion / removal log; the device registration status is a registered status;

[0102] The second insertion / removal log generation unit is used to determine the registration status of the target storage device as unregistered, determine the insertion time of the target storage device, and then store the registration status and insertion time of the target storage device in the local device insertion / removal log; the device registration status is unregistered.

[0103] In some specific embodiments, the data exchange module 13 includes:

[0104] An information determination unit is used to determine the pre-set permissions and operation modes of the target storage device; the permissions include read-only permissions, write-only permissions, and read-write permissions; the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode.

[0105] A data exchange mode determination unit is used to determine the data exchange mode between the target storage device and the baseboard management controller based on the permissions and operation modes preset in the target storage device; the data exchange mode includes a data receiving mode or a data output mode.

[0106] In some specific embodiments, the data exchange module 13 includes:

[0107] A data receiving unit is configured to receive first data transmitted by the target storage device and store the first data in a target storage location corresponding to the first data if the data exchange mode is a data receiving mode.

[0108] A data output unit is configured to, if the data exchange mode is a data output mode, determine second data from local storage based on the operation mode, and transmit the second data to the target storage device.

[0109] Furthermore, embodiments of this application also disclose an electronic device, Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of use of this application.

[0110] Figure 5 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a display screen 24, an input / output interface 25, a communication interface 26, and a communication bus 27. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the baseboard management controller management method disclosed in any of the foregoing embodiments. Alternatively, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0111] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 26 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0112] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored on it can include an operating system 221, computer programs 222, and virtual machine data 223, etc. The virtual machine data 223 can include various types of data. The storage method can be temporary storage or permanent storage.

[0113] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the baseboard management controller management method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program capable of performing other specific tasks.

[0114] Furthermore, this application also discloses a computer-readable storage medium, which includes random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, magnetic disks, optical disks, or any other form of storage medium known in the art. When the computer program is executed by a processor, it implements the aforementioned board management controller management method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0115] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatuses disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to the method section. Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0116] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0117] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0118] The above provides a detailed description of the baseboard management controller management method, apparatus, device, and storage medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A management method for a baseboard management controller, characterized in that, include: When a target storage device is detected to be connected to a preset USB interface that is pre-connected to the baseboard management controller, it is determined whether the target storage device is a registered device. If the target storage device is a registered device, the target storage device is mounted to the current baseboard management controller, and the data exchange mode between the target storage device and the baseboard management controller is determined based on the pre-set permissions and operation modes of the target storage device; the permissions include read-only permissions, write-only permissions, and read-write permissions, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode; The data exchange mode includes a data receiving mode or a data output mode; The corresponding data exchange operation is triggered based on the data exchange mode.

2. The baseboard management controller management method according to claim 1, characterized in that, The step of determining whether the target storage device is a registered device includes: Determine the device ID of the target storage device; Determine whether there is configuration information corresponding to the device ID in the local whitelist; the configuration information includes the device ID, permissions, and operation mode of the target storage device. If the configuration information corresponding to the device ID exists in all the configuration information in the local whitelist, then the target storage device is determined to be a registered device; If no configuration information corresponding to the device ID is found in the local whitelist, the target storage device is determined to be an unregistered device.

3. The baseboard management controller management method according to claim 2, characterized in that, After determining the target storage device as an unregistered device, the method further includes: The target storage device must not be mounted to the current baseboard management controller.

4. The baseboard management controller management method according to claim 3, characterized in that, After prohibiting the target storage device from being mounted to the current baseboard management controller, the following is also included: Obtain a storage device registration instruction and determine the configuration information of the target storage device; the configuration information includes the device ID, permissions, and operation mode of the target storage device. The configuration information of the target storage device is recorded in the local whitelist, and the target storage device is identified as a registered device.

5. The baseboard management controller management method according to claim 4, characterized in that, After triggering the corresponding data exchange operation based on the data exchange mode, the method further includes: If the target storage device is a registered device, then the insertion time of the target storage device is determined, and the device registration status, insertion time, configuration information of the target storage device, and operation information of this data exchange operation are stored in the local device insertion / removal log; the device registration status is "registered". Accordingly, if the target storage device is an unregistered device, then it is prohibited to attach the target storage device to the current baseboard management controller, and the method further includes: The registration status of the target storage device is determined to be unregistered, and the insertion time of the target storage device is determined. Then, the registration status and insertion time of the target storage device are stored in the local device insertion / removal log; the device registration status is unregistered.

6. The baseboard management controller management method according to claim 1, characterized in that, The step of determining the data exchange mode between the target storage device and the baseboard management controller based on the pre-set permissions and operation modes of the target storage device includes: Determine the pre-set permissions and operation modes of the target storage device; the permissions include read-only permission, write-only permission, and read-write permission, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode. The data exchange mode between the target storage device and the baseboard management controller is determined based on the pre-set permissions and operation mode of the target storage device; the data exchange mode includes a data receiving mode or a data output mode.

7. The baseboard management controller management method according to any one of claims 1 to 6, characterized in that, The triggering of the corresponding data exchange operation based on the data exchange mode includes: If the data exchange mode is a data receiving mode, then the first data transmitted by the target storage device is received, and the first data is stored in the target storage location corresponding to the first data; If the data exchange mode is a data output mode, then the second data is determined from the local storage based on the operation mode, and the second data is transmitted to the target storage device.

8. A substrate management controller management device, characterized in that, include: The device connection module is used to determine whether the target storage device is a registered device when it is detected that the target storage device is connected to a preset USB interface that is pre-connected to the baseboard management controller; The device mounting module is used to mount the target storage device to the current baseboard management controller if the target storage device is a registered device, and to determine the data exchange mode between the target storage device and the baseboard management controller based on the preset permissions and operation modes of the target storage device; the permissions include read-only permissions, write-only permissions, and read-write permissions, and the operation modes include firmware upgrade mode, log collection mode, and configuration file import mode; The data exchange mode includes a data receiving mode or a data output mode; The data exchange module is used to trigger corresponding data exchange operations based on the data exchange mode.

9. An electronic device, characterized in that, It includes a processor and a memory; wherein, when the processor executes a computer program stored in the memory, it implements the baseboard management controller management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein, when the computer programs are executed by a processor, they implement the baseboard management controller management method as described in any one of claims 1 to 7.

Images