Device management method and device for target device, device and storage medium
By storing characteristic parameters in the target device's memory, the baseboard management controller automatically obtains the bus access address and link, solving the problem of poor BMC scalability and realizing automatic management and adaptation to new types of devices.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- INSPUR SUZHOU INTELLIGENT TECH CO LTD
- Filing Date
- 2023-05-11
- Publication Date
- 2026-07-14
Smart Images
Figure CN116578458B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and more specifically to a device management method, apparatus, device, and storage medium for a target device. Background Technology
[0002] In server systems, the BMC (Baseboard Management Controller) is primarily used for platform management, specifically monitoring the temperature, voltage, fan status, and power status of various components (such as CPU, memory, and chipset). As business grows, servers need to support an increasingly diverse range of component types, therefore the BMC must continuously adapt to these new component types.
[0003] Currently, when managing components, the BMC needs to know the component's device information (such as the component address) in advance. Therefore, when adding a new type of component, maintainers need to manually modify the BMC's code or configuration files to add the device information for the new component. This approach results in poor scalability of the BMC; that is, every time a new type of component is added, the BMC image needs to be redeployed and upgraded to support the management of the new component type. Summary of the Invention
[0004] In view of this, the present invention provides a device management method, management device, electronic device, and computer-readable storage medium for a target device, which has good scalability.
[0005] This invention provides a device management method for a target device, wherein the target device includes a memory for storing characteristic parameters of the target device; the method includes:
[0006] If the target device is detected to be connected to the server motherboard, a request is sent to the target device to obtain the bus access address of the memory;
[0007] Based on the bus access address returned by the target device, the target bus link where the memory is located is determined;
[0008] The characteristic parameters of the target device are read from the memory via the target bus link; and
[0009] The target device is managed based on the aforementioned characteristic parameters.
[0010] In some embodiments, the method is applied to a substrate management controller, which is connected to the memory via an I2C bus;
[0011] The step of determining the target bus link with the memory based on the bus access address returned by the target device includes:
[0012] Based on the bus access address, all I2C bus links of the baseboard management controller are traversed, and the bus link that can access the memory is taken as the target bus link.
[0013] In some embodiments, after obtaining the device information, the method further includes:
[0014] Establish a relationship table corresponding to the target device;
[0015] The characteristic parameters of the target device are written into the relationship table to facilitate the management of the target device based on the relationship table.
[0016] In some embodiments, the characteristic parameter includes a first device characteristic to be monitored by the target device, and an interface for obtaining the actual characteristic value of the first device characteristic;
[0017] The management of the target device based on the aforementioned characteristic parameters includes:
[0018] Obtain the first target interface corresponding to the first device characteristic from the relationship table, and obtain the actual characteristic value of the first device characteristic from the first target interface;
[0019] The target device is managed based on the actual characteristic values of the first device characteristics.
[0020] In some embodiments, the characteristic parameter includes a second device characteristic to be monitored by the target device, and the theoretical characteristic value of the second device characteristic;
[0021] The management of the target device based on the aforementioned characteristic parameters includes:
[0022] Obtain the actual characteristic value of the second device characteristic, and obtain the theoretical characteristic value of the second device characteristic from the relationship table;
[0023] When the actual characteristic value of the second device does not match the theoretical characteristic value, the target device is managed.
[0024] In some embodiments, the characteristic parameters include a third device characteristic to be monitored by the target device, an interface for obtaining the actual characteristic value of the third device characteristic, and the theoretical characteristic value of the third device characteristic.
[0025] The management of the target device based on the aforementioned characteristic parameters includes:
[0026] Obtain the second target interface corresponding to the third device characteristic from the relationship table, and obtain the actual characteristic value of the third device characteristic from the second target interface;
[0027] Obtain the theoretical characteristic value of the third device characteristic from the relationship table;
[0028] When the actual characteristic value of the third device does not match the theoretical characteristic value, the target device is managed.
[0029] In some embodiments, sending a request to the target device to obtain the bus access address of the memory includes:
[0030] Based on the MCTP over SMBus protocol, a dynamic address is assigned to the target device;
[0031] Based on the dynamic address assigned to the target device, communicate with the target device to obtain the bus access address of the memory.
[0032] In another aspect, the present invention provides a management device for a target device, the target device including a memory for storing characteristic parameters of the target device, the device information including the characteristic parameters of the target device; the device includes:
[0033] The address acquisition module is used to send a request to the target device to obtain the bus access address of the memory when the target device is detected to be connected to the server motherboard.
[0034] The link determination module is used to determine the target bus link where the memory is located based on the bus access address returned by the target device.
[0035] An information acquisition module is used to read the characteristic parameters from the memory via the target bus link; and
[0036] The management module is used to manage the target device based on the aforementioned characteristic parameters.
[0037] In another aspect, the present invention provides an electronic device comprising a processor and a memory, the memory being used to store a computer program which, when executed by the processor, implements the method described above.
[0038] In another aspect, the present invention provides a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the method described above.
[0039] In some embodiments of this application, device information is stored in the memory of the target device. When the target device is connected to the server motherboard, the bus access address of the memory is obtained from the target device, and the target bus link where the memory is located is determined based on the bus access address. Then, the device information of the target device can be read from the memory through the target bus link to manage the target device. In this way, when a new type of device is connected to the server motherboard, the baseboard control manager can automatically read the device information from the memory of the target device and manage the target device based on the device information. This eliminates the need to manually modify the code or configuration file of the baseboard control manager, and thus eliminates the need to redistribute and upgrade the baseboard control manager image for new types of devices. This gives the baseboard control manager good scalability and allows it to automatically adapt to device management. Attached Figure Description
[0040] The features and advantages of the invention will be more clearly understood by referring to the accompanying drawings, which are schematic and should not be construed as limiting the invention in any way. In the drawings:
[0041] Figure 1 A schematic diagram illustrating the communication connection between the target device and the baseboard management controller is shown.
[0042] Figure 2 A flowchart illustrating a device management method provided in one embodiment of this application is shown;
[0043] Figure 3 A schematic diagram of the process for obtaining a bus access address according to an embodiment of this application is shown;
[0044] Figure 4 This illustration shows a schematic diagram of the connection between a baseboard management controller and other devices according to an embodiment of this application;
[0045] Figure 5 A schematic diagram of a management device provided in one embodiment of this application is shown;
[0046] Figure 6 A schematic diagram of an electronic device provided in one embodiment of this application is shown. Detailed Implementation
[0047] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, 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 a part of the embodiments of the present invention, not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.
[0048] In this application, the target device can refer to a device that needs to be connected to a server motherboard, such as various network cards, RAID cards, fans, power supplies, etc. The target device may include a memory used to store the characteristic parameters of the target device. The memory may include, but is not limited to, EEPROM (Electrically Erasable Programmable Read Only Memory).
[0049] Characteristic parameters can be pre-written into the memory of the target device by the manufacturer at the time of shipment. These parameters characterize the parameters required for managing the target device or its sub-components, such as the device type, device identifier, supported protocol versions, the maximum allowable ambient temperature for the target device or its sub-components during operation, the access addresses of sensors on the target device, and the protocols supported by the firmware. It is understandable that the characteristic parameters of a target device can differ depending on its type. For example, for a network interface card (NIC), the corresponding characteristic parameters may include, but are not limited to, the allowable chip temperature, optical module temperature, FPGA module temperature, critical power supply VR, Ethernet port information, and the corresponding acquisition interfaces, as well as the protocols supported by the NIC. For a fan, the corresponding characteristic parameters may include, but are not limited to, the maximum and minimum allowable fan speeds, and the number of fan rotors. Within the same target device, different characteristic parameters can be used to represent different characteristics. Using R... max To indicate the maximum permissible fan speed, use R. min This indicates the minimum permissible fan speed. The following provides a detailed explanation of these characteristics.
[0050] In some embodiments, the characteristic parameters may include a first device characteristic to be monitored by the target device, and an interface for obtaining the actual characteristic value of the first device characteristic. The actual characteristic value may refer to the actual value of the device characteristic of the target device during operation. The interface may refer to the channel or method for obtaining the actual characteristic value of the first device characteristic of the target device. The interface includes, but is not limited to, the communication protocol required to obtain the actual characteristic value, the access address corresponding to the detection device for detecting the actual characteristic value, and the parameters required to obtain the actual characteristic value. The detection device for detecting the actual characteristic value may be located in the target device. For example, a network interface card (NIC) may include a temperature sensor. The temperature sensor can detect the temperature of the NIC or its sub-components (such as optical modules or chips). The obtained characteristic parameters may include the I2C address of the temperature sensor. Based on the I2C address of the temperature sensor, the actual temperature value of the NIC or its sub-components can be obtained from the temperature sensor.
[0051] In some embodiments, the characteristic parameters may include a second device characteristic to be monitored for the target device, and a theoretical characteristic value for the second device characteristic. The theoretical characteristic value refers to the range of values supported by the device characteristic during the operation of the target device. The theoretical characteristic value can be used to characterize the capabilities of the target device. For example, assuming the maximum speed supported by a fan is 10 revolutions per second, then during the operation of the fan, the maximum speed of the fan needs to be controlled within 10 revolutions per second.
[0052] In some embodiments, the characteristic parameters include the third device characteristic to be monitored by the target device, the interface for obtaining the actual characteristic value of the third device characteristic, and the theoretical characteristic value of the third device characteristic. Simply put, the third device characteristic has two attributes: an interface and a theoretical characteristic value. These two attributes can be found in the relevant descriptions above and will not be repeated here.
[0053] See also Figure 1 This is a schematic diagram illustrating the communication connection between target device 12 and baseboard management controller 11 when the target device 12 is connected to the server motherboard. Those skilled in the art will understand that the server motherboard has pre-installed cabling to form communication lines. When target device 12 is connected to the server motherboard, target device 12 can connect to baseboard management controller 11 through these communication lines. Figure 1 In this configuration, target device 12 includes a main chip 121 and a memory 122. The main chip 121 can communicate with the baseboard management controller 11 based on the MCTP (Message Control Transfer Protocol) protocol. Specifically, the main chip 121 can communicate with the baseboard management controller 11 based on the MCTP over SMBus Discovery protocol. The memory 122 is connected to the baseboard management controller 11 via an I2C (Inter-Integrated Circuit) bus.
[0054] It should be noted that, Figure 1 This is just an example illustration of one target device 12. In practical applications, the board management controller 11 can also be connected to multiple target devices 12.
[0055] based on Figure 1 As shown in the diagram, this application provides a device management method for a target device. The device management method can be applied to... Figure 1 The baseboard management controller is described above. Specifically, a control program can be pre-programmed into the baseboard management controller, and when the control program runs, it can implement the device management method of this application. Please refer to [link to relevant documentation]. Figure 2 This is a flowchart illustrating a device management method provided in one embodiment of this application. Figure 2 In this context, the equipment management method includes the following steps:
[0056] Step S21: If the target device is detected to be connected to the server motherboard, a request is sent to the target device to obtain the bus access address of the memory.
[0057] See also Figure 1 In this embodiment, the memory bus access address can refer to the address corresponding to accessing the memory via the I2C bus. The board management controller can assign a dynamic address to the target device based on the MCTP over SMBus protocol, and communicate with the target device based on the assigned dynamic address to obtain the memory bus access address. Please refer to [link to details]. Figure 3 This is a schematic diagram of the process for obtaining a bus access address provided in one embodiment of this application. Figure 3 The flowchart shown may specifically include the following steps:
[0058] In step S311, after the target device connects to the server motherboard, it notifies the board management controller based on the ARP (Address Resolution Protocol). In the MCTP protocol, this process can be described as "Notify ARP Master".
[0059] In step S312, when the baseboard management controller receives a message from the target device, it determines that the target device has been detected accessing the server motherboard and sends a response to the target device indicating that it is ready to allocate an address. In the MCTP protocol, this process can be described as "prepare to ARP".
[0060] In step S313, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0061] In step S314, the baseboard management controller sends a device restart message to the target device to restart the target device. In the MCTP protocol, this process can be described as "Reset Device".
[0062] In step S315, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0063] In step S316, the baseboard management controller sends a message to the target device to obtain the device identifier. In the MCTP protocol, this process can be described as "Get UDID".
[0064] In step S317, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0065] In step S318, the board management controller assigns a dynamic address to the target device. Specifically, this dynamic address can be an address generated based on the device identifier. In the MCTP protocol, this process can be described as "Assign Address".
[0066] In step S319, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0067] In step S320, the substrate management controller sends a message to the target device again to obtain the device identifier. In the MCTP protocol, this process can be described as "Get UDID".
[0068] In step S321, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0069] In step S322, the board management controller sends a request to the target device based on the assigned communication address to obtain the memory bus access address. In the MCTP protocol, this process can be described as "MCTP over SMBus with MessageType (Vendor Defined-IANA)".
[0070] In step S323, the target device returns a response to the board management controller. In the MCTP protocol, this process can be described as "ACK".
[0071] At this point, the board management controller can obtain the first bus address of the memory in the target device. This first bus address can be the address of the memory when accessing it via the I2C bus.
[0072] Step S22: Based on the bus access address returned by the target device, determine the target bus link where the memory is located.
[0073] In this embodiment, all I2C bus links of the board management controller can be traversed based on the bus access address, and the bus link that is successfully paired with the bus access address can be used as the target bus link. Successful pairing with the bus access address means that the access address of the device in the bus link is successfully paired with the bus access address obtained in step S11. For easier understanding, please refer to [link to relevant documentation]. Figure 4 This is a schematic diagram illustrating the connection between a baseboard management controller and other devices, provided in one embodiment of this application. Figure 4In this example, assume the baseboard management controller connects to memory A, memory B, memory C, and device D via I2C bus links 1, 2, 3, and 4, respectively, with memory C being the target device's memory. According to the I2C communication principle, during the traversal process, the baseboard management controller can access memory C through bus links 1, 2, 3, and 4 based on the bus access address of memory C obtained in step S11. Clearly, only in bus link 3 can the device address of memory C successfully match the bus access address sent by the baseboard management controller; therefore, bus link 3 is the target bus link.
[0074] Step S23: Read the characteristic parameters of the target device from the memory via the target bus link.
[0075] In this embodiment, after obtaining the characteristic parameters of the target device, the baseboard management controller can establish a relationship table corresponding to the target device and write at least the characteristic parameters of the target device into the relationship table so as to manage the target device based on the relationship table.
[0076] In some embodiments, the relationship table may include the target bus link where the target device is located, the device type of the target device, the first device characteristic, the interface type for obtaining the actual characteristic value of the first device characteristic, the interface parameters, and the interface address. For ease of understanding, please refer to Table 1, which is an example of the relationship table corresponding to the target device being a fan.
[0077] Table 1 Relationship Table
[0078]
[0079] In some embodiments, the relationship table may include the target bus link where the target device is located, the device type of the target device, the second device characteristics, and the theoretical characteristic values of the second device characteristics. For ease of understanding, please refer to Table 2, which is an example of the relationship table corresponding to the target device being a fan.
[0080] Table 2 Relationship Table
[0081]
[0082] In some embodiments, the relationship table may include the target bus link where the target device is located, the device type of the target device, the third device characteristic, the interface type for obtaining the actual characteristic value of the third device characteristic, the interface parameters, the interface address, and the theoretical characteristic value of the third device characteristic. For ease of understanding, please refer to Table 3, which is an example of the relationship table corresponding to the target device being a fan.
[0083] Table 3 Relationship Table
[0084]
[0085] In some embodiments, the relationship table includes fields such as target bus link, target device device type, device characteristics, interface type for obtaining the actual characteristic value of the device characteristics, interface parameters, interface address, and theoretical characteristic value of the device characteristics. Some fields are selected and filled in according to the actual situation of each device characteristic. For ease of understanding, please refer to Table 4, which is an example of the relationship table corresponding to a fan as the target device.
[0086] Table 4 Relationship Table
[0087]
[0088] It is understandable that Table 4 is equivalent to integrating Tables 1 to 3 into a single relational table.
[0089] In some embodiments, the relational table may be established in the program code as a data structure. In other embodiments, the relational table may also be established in a database.
[0090] It is understood that the fields included in each relationship table can be determined according to the actual situation, and this application does not impose any restrictions on this. For example, in some embodiments, the relationship table may not include a field for device type.
[0091] Step S24: Manage the target device based on the characteristic parameters.
[0092] In some embodiments, managing the target device based on characteristic parameters includes:
[0093] Retrieve the first target interface corresponding to the first device characteristic from the relation table, and retrieve the actual characteristic value of the first device characteristic from the first target interface;
[0094] The target device is managed based on the actual characteristic values of the first device.
[0095] The first device characteristic refers to the device characteristic whose actual characteristic value can be obtained through the interface provided by the target device.
[0096] Managing a target device can involve controlling the operation of other devices besides the target device itself. For example, the baseboard control manager can obtain the actual device temperature during network card operation through the temperature interface provided by the network card. When the actual device temperature of the network card exceeds the maximum allowable temperature of the network card, the fan can be controlled to operate, thereby managing the network card's temperature.
[0097] Of course, managing a target device can also mean controlling it. For example, the baseboard control manager obtains the actual rotational speed of the fan during operation through the speed interface provided by the fan. When the actual fan speed exceeds the maximum speed, the manager controls the fan motor to reduce its speed, thus achieving fan speed reduction management.
[0098] In some embodiments, managing the target device based on characteristic parameters includes:
[0099] Obtain the actual characteristic value of the second device characteristic, and obtain the theoretical characteristic value of the second device characteristic from the relation table;
[0100] When the actual characteristic value of the second device does not match the theoretical characteristic value, the target device is managed.
[0101] Here, the second device characteristic refers to a device characteristic whose theoretical characteristic value can be obtained from the relation table, but whose actual characteristic value is obtained through a non-interface method. Simply put, the baseboard control manager detects the actual characteristic value of the second device characteristic through other devices besides the target device, and at the same time, obtains the theoretical characteristic value of the second device characteristic from the relation table.
[0102] A mismatch between actual and theoretical characteristic values can manifest as the actual value being unequal to the theoretical value, greater than the theoretical value, less than the theoretical value, or outside the theoretical range. The specific judgment logic can be determined based on the actual characteristics of the equipment. For example, suppose that in the characteristic parameters of the target equipment, the highest equipment temperature represents the maximum allowable temperature, and the lowest equipment temperature represents the minimum allowable temperature. Then, when matching the actual equipment temperature with the highest equipment temperature in the characteristic parameters, a mismatch should occur if the actual equipment temperature is greater than the highest equipment temperature; conversely, when matching the actual equipment temperature with the lowest equipment temperature in the characteristic parameters, a mismatch should occur if the actual equipment temperature is less than the lowest equipment temperature.
[0103] Managing a target device can also include controlling other devices besides the target device to manage it, or controlling the target device itself to achieve target management. For example, suppose the target device is a network interface card (NIC). In the relationship table, the maximum allowable temperature of the NIC is 50 degrees Celsius (i.e., the theoretical characteristic value). The baseboard management controller, through a temperature sensor outside the NIC, detects that the actual device temperature of the NIC exceeds 50 degrees Celsius and controls the fan to operate to cool the NIC. As another example, suppose the target device is a fan. In the relationship table, the maximum allowable speed of the fan is 10 revolutions per second (i.e., the theoretical characteristic value). The baseboard management controller, through a speed sensor outside the fan, detects that the actual fan speed exceeds 10 revolutions per second and controls the fan motor to reduce its speed to achieve fan speed reduction management.
[0104] In some embodiments, managing the target device based on characteristic parameters includes:
[0105] Retrieve the second target interface corresponding to the third device characteristic from the relation table, and retrieve the actual characteristic value of the third device characteristic from the second target interface;
[0106] Obtain the theoretical characteristic values of the third device from the relation table;
[0107] When the actual characteristic value of the third device does not match the theoretical characteristic value, the target device is managed.
[0108] Here, the third device characteristic refers to a device characteristic whose theoretical characteristic value can be obtained from the relation table, but whose actual characteristic value is obtained through an interface. Simply put, the baseboard control manager obtains the actual characteristic value of the third device characteristic through the interface provided by the target device, and simultaneously obtains the theoretical characteristic value of the third device characteristic from the relation table. When the obtained actual characteristic value does not match the theoretical characteristic value, the target device is managed. The management of the target device is similar to the related descriptions above and will not be repeated here.
[0109] In summary, in some embodiments of this application, characteristic parameters are stored in the memory of the target device. When the target device is connected to the server motherboard, the bus access address of the memory is obtained from the target device, and the target bus link where the memory is located is determined based on the bus access address. Then, the characteristic parameters of the target device can be read from the memory through the target bus link to manage the target device. Thus, when a new type of device is connected to the server motherboard, the baseboard control manager can automatically read the characteristic parameters from the target device's memory and manage the target device based on these parameters. This eliminates the need for manual modification of the baseboard control manager's code or configuration files, and avoids the need to redistribute and upgrade the baseboard control manager image for new types of devices. This gives the baseboard control manager good scalability and allows it to automatically adapt to device management.
[0110] Please see Figure 5 This is a schematic diagram of a management device for a target device, provided as an embodiment of this application. The target device includes a memory for storing characteristic parameters of the target device; the management device includes:
[0111] The address acquisition module is used to send a request to the target device to obtain the memory bus access address when the target device is detected to be connected to the server motherboard.
[0112] The link determination module is used to determine the target bus link where the memory is located based on the bus access address returned by the target device.
[0113] The information acquisition module is used to read the characteristic parameters of the target device from the memory via the target bus link; and
[0114] The management module is used to manage target devices based on characteristic parameters.
[0115] In some embodiments, the method is applied to a substrate management controller, which is connected to the memory via an I2C bus; the link determination module is specifically used to traverse all I2C bus links of the substrate management controller based on the bus access address, and select the bus link that can access the memory as the target bus link.
[0116] In some embodiments, after obtaining device information, the management module is specifically used to establish a relationship table corresponding to the target device; and to write at least the characteristic parameters of the target device into the relationship table so as to manage the target device based on the relationship table.
[0117] In some embodiments, the characteristic parameters include a first device characteristic to be monitored for the target device, and an interface for obtaining the actual characteristic value of the first device characteristic; the management module is specifically used to obtain the first target interface corresponding to the first device characteristic from the relationship table, and obtain the actual characteristic value of the first device characteristic from the first target interface; and to manage the target device based on the actual characteristic value of the first device characteristic.
[0118] In some embodiments, the characteristic parameters include a second device characteristic to be monitored for the target device, and a theoretical characteristic value of the second device characteristic; the management module is specifically used to obtain the actual characteristic value of the second device characteristic, and to obtain the theoretical characteristic value of the second device characteristic from the relationship table; and to manage the target device when the actual characteristic value of the second device characteristic does not match the theoretical characteristic value.
[0119] In some embodiments, the characteristic parameters include a third device characteristic to be monitored by the target device, an interface for obtaining the actual characteristic value of the third device characteristic, and a theoretical characteristic value of the third device characteristic; the management module is specifically used to obtain the second target interface corresponding to the third device characteristic from the relationship table, and obtain the actual characteristic value of the third device characteristic from the second target interface; obtain the theoretical characteristic value of the third device characteristic from the relationship table; and manage the target device when the actual characteristic value and the theoretical characteristic value of the third device characteristic do not match.
[0120] In some embodiments, the address acquisition module is specifically used to assign a communication address to the target device based on the MCTP protocol; and to send a request to the target device based on the communication address assigned to the target device in order to obtain the stored bus access address.
[0121] Please see Figure 6 The diagram below illustrates an electronic device according to an embodiment of this application. The electronic device includes a processor and a memory, the memory storing a computer program that, when executed by the processor, implements the variable management method described above.
[0122] The processor can be a central processing unit (CPU). It can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations thereof.
[0123] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the embodiments of this invention. The processor executes various functional applications and data processing by running the non-transitory software programs, instructions, and modules stored in the memory, thereby implementing the methods described in the above embodiments.
[0124] The memory may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created by the processor, etc. Furthermore, the memory may include high-speed random access memory and non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include memory remotely located relative to the processor, which can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0125] One embodiment of this application also provides a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the variable management method described above.
[0126] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described variable management method.
[0127] The aforementioned management device and electronic device are the device and equipment items corresponding to the device management method of this application. The beneficial effects of the device and equipment can be found in the description related to the method, and will not be repeated here.
[0128] Although the implementation method of the present invention has been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.
Claims
1. A method for managing equipment for a target device, characterized in that, The method is applied to a substrate management controller, wherein the target device includes a main chip and a memory for storing characteristic parameters of the target device, the substrate management controller communicates with the main chip based on the MCTP protocol, and the substrate management controller is connected to the memory via an I2C bus; the method includes: If the target device is detected to be connected to the server motherboard, a request is sent to the target device to obtain the bus access address of the memory; Based on the bus access address returned by the target device, the target bus link where the memory is located is determined; The characteristic parameters of the target device are read from the memory via the target bus link; and The target device is managed based on the aforementioned characteristic parameters; Sending a request to the target device to obtain the bus access address of the memory includes: Based on the MCTP over SMBus protocol, a dynamic address is assigned to the target device; based on the dynamic address assigned to the target device, communication is established with the target device to obtain the bus access address of the memory; Determining the target bus link where the memory resides based on the bus access address returned by the target device includes: Based on the bus access address, the I2C bus links where the baseboard management controller is located are traversed, and the bus links that are successfully paired with the bus access address are taken as the target bus links. The characteristic parameters are pre-written into the memory by the manufacturer when the target device leaves the factory; the characteristic parameters are used to characterize the parameters required for managing the target device or its sub-components, and the characteristic parameters include at least one or more of the following parameters: the device type of the target device, the device identifier, the supported protocol version, the maximum allowable ambient temperature of the target device or its sub-components during operation, the access address of the sensors on the target device, and the protocols supported by the firmware.
2. The method as described in claim 1, characterized in that, After obtaining the characteristic parameters of the target device, the method further includes: Establish a relationship table corresponding to the target device; The characteristic parameters of the target device are written into the relationship table to facilitate the management of the target device based on the relationship table.
3. The method as described in claim 2, characterized in that, The characteristic parameters include a first device characteristic to be monitored for the target device, and an interface for obtaining the actual characteristic value of the first device characteristic; The management of the target device based on the aforementioned characteristic parameters includes: Obtain the first target interface corresponding to the first device characteristic from the relationship table, and obtain the actual characteristic value of the first device characteristic from the first target interface; The target device is managed based on the actual characteristic values of the first device characteristics.
4. The method as described in claim 2, characterized in that, The characteristic parameters include the second device characteristic to be monitored by the target device, and the theoretical characteristic value of the second device characteristic; The management of the target device based on the aforementioned characteristic parameters includes: Obtain the actual characteristic value of the second device characteristic, and obtain the theoretical characteristic value of the second device characteristic from the relationship table; When the actual characteristic value of the second device does not match the theoretical characteristic value, the target device is managed.
5. The method as described in claim 2, characterized in that, The characteristic parameters include the third device characteristic to be monitored by the target device, as well as the interface for obtaining the actual characteristic value of the third device characteristic and the theoretical characteristic value of the third device characteristic; The management of the target device based on the aforementioned characteristic parameters includes: Obtain the second target interface corresponding to the third device characteristic from the relationship table, and obtain the actual characteristic value of the third device characteristic from the second target interface; Obtain the theoretical characteristic value of the third device characteristic from the relationship table; When the actual characteristic value of the third device does not match the theoretical characteristic value, the target device is managed.
6. A management device for a target device, characterized in that, The device is applied to a substrate management controller. The target device includes a main chip and a memory for storing characteristic parameters of the target device. The substrate management controller communicates with the main chip based on the MCTP protocol, and the substrate management controller is connected to the memory via an I2C bus. The device includes: The address acquisition module is used to send a request to the target device to obtain the bus access address of the memory when the target device is detected to be connected to the server motherboard. The link determination module is used to determine the target bus link where the memory is located based on the bus access address returned by the target device. An information acquisition module is used to read the characteristic parameters from the memory via the target bus link; and The management module is used to manage the target device based on the aforementioned characteristic parameters; Sending a request to the target device to obtain the bus access address of the memory includes: Based on the MCTP over SMBus protocol, a dynamic address is assigned to the target device; based on the dynamic address assigned to the target device, communication is established with the target device to obtain the bus access address of the memory; Determining the target bus link where the memory resides based on the bus access address returned by the target device includes: Based on the bus access address, the I2C bus links where the baseboard management controller is located are traversed, and the bus links that are successfully paired with the bus access address are taken as the target bus links. The characteristic parameters are pre-written into the memory by the manufacturer when the target device leaves the factory; the characteristic parameters are used to characterize the parameters required for managing the target device or its sub-components, and the characteristic parameters include at least one or more of the following parameters: the device type of the target device, the device identifier, the supported protocol version, the maximum allowable ambient temperature of the target device or its sub-components during operation, the access address of the sensors on the target device, and the protocols supported by the firmware.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 5.
8. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory being used to store a computer program that, when executed by the processor, implements the method as described in any one of claims 1 to 5.