CN108898230B - Equipment management method and management server - Google Patents

Equipment management method and management server Download PDF

Info

Publication number
CN108898230B
CN108898230B CN201810506587.1A CN201810506587A CN108898230B CN 108898230 B CN108898230 B CN 108898230B CN 201810506587 A CN201810506587 A CN 201810506587A CN 108898230 B CN108898230 B CN 108898230B
Authority
CN
China
Prior art keywords
configuration
model
service server
sub
component
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810506587.1A
Other languages
Chinese (zh)
Other versions
CN108898230A (en
Inventor
任宏亮
宋铜铃
杜垠
潘玉园
赵辉昌
李继伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XFusion Digital Technologies Co Ltd
Original Assignee
XFusion Digital Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by XFusion Digital Technologies Co Ltd filed Critical XFusion Digital Technologies Co Ltd
Priority to CN201810506587.1A priority Critical patent/CN108898230B/en
Priority to CN202210800994.XA priority patent/CN115204423A/en
Publication of CN108898230A publication Critical patent/CN108898230A/en
Application granted granted Critical
Publication of CN108898230B publication Critical patent/CN108898230B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/20—Administration of product repair or maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451—User profiles; Roaming

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application discloses a device management method and a management server, the method is applied to a device management system, the device management system comprises a management server and at least one service server, a preset model library of the management server comprises at least one sub-model, each sub-model comprises configuration items and configuration parameters of components, the method comprises the following steps: the method comprises the steps that a management server obtains component identification of components in each service server, and determines a first sub-model set in a preset model library according to the component identification of a first service server, wherein the first sub-model set comprises at least one sub-model corresponding to the component identification of the first service server; and sending first configuration information to the first service server, wherein the first configuration information carries at least one configuration item and configuration parameters in the first submodel set, so that the first service server configures the configuration parameters of the configuration item of at least one component to be configured according to the first configuration information.

Description

Equipment management method and management server
Technical Field
The present application relates to the technical field of servers, and in particular, to an apparatus management method and a management server.
Background
Operation and maintenance personnel need to perform parameter configuration on components of the service server in operation and maintenance scenes such as service server deployment in an bureau, newly-added service servers, component change of the service servers and the like. The components may include devices or firmware such as a RAID (redundant array of independent disks), a BIOS (Basic Input Output System), and a network card. For example, configuring the parameters of the RAID may be configuring a level of the RAID or other configuration items so that the RAID implements corresponding functions.
In practical applications, as shown in fig. 1, the management software of the management server typically performs parameter configuration on the components of the service server. For example, the service server 1 includes a RAID card of the type 3108, and when the management software configures parameters of the service server 1, the configuration parameters of the attributes of the RAID card of the output type 3108, for example, the configuration parameters of the level of the RAID card of the output type 3108, are fixed at three levels of RAID0, RAID1, and RAID10, respectively. The user may select the configuration parameters. The management software sends the configuration parameters RAID1 selected by the user to the service server 1. The service server 1 configures a RAID level to RAID 1.
However, in many cases, the management software needs to be updated to configure the parameters of the service server. For example, when a service server 2 having a different component from the service server 1 is newly added to the system, the management software needs to be updated, so that the management software can provide the user with the corresponding configuration parameters output by the service server 2, thereby performing parameter configuration. That is, each time a service server with a different component is newly added to the system, the management software needs to be updated, so that the parameter configuration can be performed.
Therefore, the existing server operation and maintenance mode has the problem of low maintenance efficiency.
Disclosure of Invention
The application provides an equipment management method and a management server, so that the maintenance efficiency of a server operation and maintenance mode is improved, and the parameter configuration is quickly carried out on the components of a service server.
In a first aspect, the present application provides a device management method, where the method is applied in a device management system, the device management system includes a management server and at least one service server, the management server is configured to manage the at least one service server, the management server has a preset model library, the preset model library includes at least one sub-model, each sub-model includes configuration items and configuration parameters of components, and the method includes: the management server acquires the component identifier of each component in at least one service server; the management server determines a first sub-model set in a preset model library according to the part identification of a first service server, wherein the first service server is any one of at least one service server, and the first sub-model set comprises at least one sub-model corresponding to the part identification of the first service server; the management server sends first configuration information to the first service server, wherein the first configuration information carries at least one configuration item and configuration parameters in the first sub-model set, so that the first service server configures the configuration parameters of the configuration item of at least one component to be configured according to the first configuration information.
It can be seen that, by implementing the method described in the first aspect, when a component of the service server is changed, the latest configuration item and configuration parameters of the service server can be dynamically obtained without updating management software, which is beneficial to quickly perform parameter configuration on the configuration item of the component of the service server, and improves the maintenance efficiency of the operation and maintenance mode of the server. And different service servers may have partially identical components, by implementing the method described in the first aspect, a plurality of service servers may reuse the same sub-model, thereby contributing to saving development cost.
As an optional implementation manner, when the sub-model corresponding to the identifier of the first component does not exist in the preset model library, the management server obtains the configuration item and the configuration parameter of the first component from the first service server, where the first component is any one of the components of the first service server; and the management server adds a first sub-model in a preset model library according to the configuration items and the configuration parameters of the first component, wherein the first sub-model comprises the configuration items and the configuration parameters of the first component. By implementing the optional implementation mode, the submodels in the preset model library can be expanded, so that the submodels in the preset model library are more complete.
Optionally, if there is no sub-model including configuration items and configuration parameters of the firmware corresponding to the identifier of the first component (for example, the identifier of the first component may be a CPU identifier or a motherboard identifier) in the preset model library, the management server obtains the configuration items and the configuration parameters of the firmware from the first service server. And the management server adds a first sub-model in a preset model library according to the configuration items and the configuration parameters of the firmware, wherein the first sub-model comprises the configuration items and the configuration parameters of the firmware. By implementing the optional implementation mode, the submodels in the preset model library can be expanded, so that the submodels in the preset model library are more complete.
As an optional implementation manner, a specific implementation manner of the management server obtaining the identifier of the component in each service server in the at least one service server is as follows: when detecting that at least one service server is electrified, the management server acquires the identifier of a component in each service server in at least one service server; or the management server periodically acquires the identification of the component in each service server in at least one service server. By implementing the optional implementation mode, the latest part identifier of the service server can be determined in time, and the latest sub-model set corresponding to the service server can be further determined in time.
Optionally, if the first service server is not powered on for the first time, after the management server obtains the identifier of the component of the first service server, when the power-on detects that the component of the first service server is changed from the component of the first service server detected by the last power-on, the management server determines the first sub-model set in the preset model library according to the identifier of the component of the first service server.
Optionally, the management server periodically obtains an identifier of a component in each service server in the at least one service server; when detecting that the component of the first service server is changed in the period compared with the component of the first service server detected in the previous period, the management server determines a first sub-model set in a preset model library according to the component identifier of the first service server.
As an optional implementation manner, the specific implementation manner of the management server determining the first sub-model set in the preset model library according to the component identifier of the first service server is as follows: the management server determines at least one second submodel set corresponding to at least one component type of the first service server in a preset model library, wherein each second submodel set comprises submodels corresponding to components in the same type, and the component type is used for indicating component classification information to which the components of the first service server belong; the management server determines a first set of submodels from at least one second set of submodels based on at least one component identification of the first business server.
By implementing the optional implementation mode, the second submodel set can be determined according to the category of the component, the second submodel set comprises submodels corresponding to the components in the same category, and then the submodels corresponding to the component identifiers are searched in the second submodel set, so that the searching range of the submodels corresponding to the component identifiers can be reduced, and the submodels corresponding to the component identifiers can be searched more quickly.
As an optional implementation manner, before the management server sends the first configuration information to the first service server, the management server selects at least one configuration item and configuration parameters in the first sub-model set as the configuration item and configuration parameters included in the first configuration information.
By implementing the optional implementation mode, configuration items and configuration parameters can be flexibly selected from the first submodel set for parameter configuration.
As an optional implementation manner, the submodel of the first submodel set further includes preset display rules of configuration items and configuration parameters; before the management server selects at least one configuration item and configuration parameters from the first submodel set as the configuration items and configuration parameters included in the first configuration information, the configuration items and configuration parameters in the first submodel set are displayed according to preset display rules in the first submodel set.
In practical application, if a component of the service server is changed or the service server is newly added to the device management system, the management software needs to be updated to update the configuration items and the configuration parameters of the service server in the management software and update the display rules of the configuration items and the configuration parameters. By implementing the optional implementation mode, the configuration items and the display rules of the configuration parameters are added into the sub-model, and the management server can dynamically acquire the configuration items and the display rules of the configuration parameters of the service server, so that management software is not required to be updated, and parameter configuration can be conveniently and rapidly performed on the configuration items of the service server.
As an optional implementation manner, the submodels of the first submodel set further include a dependent configuration item, a depended configuration item, and a dependent condition; and displaying the dependent configuration items and the configuration parameters of the dependent configuration items in the first sub-model set according to whether the current configuration parameters of the dependent configuration items meet the dependent conditions.
By setting the dependency relationship, the user experience is improved, and the configuration items are prevented from being conflicted. And by adding the dependent configuration item, the depended configuration item and the dependent condition into the submodel, the management server can dynamically acquire the dependent configuration item, the depended configuration item and the dependent condition of the service server, so that management software does not need to be updated, and parameter configuration can be conveniently and quickly performed on the configuration item of the service server.
Optionally, after the management server sends the first configuration information to the first service server, the management server may generate a configuration file, where the configuration file includes the first configuration information. The management server stores the configuration file, so that the user can input an instruction when the user wants to perform the same configuration next time, the management server directly selects the configuration file, and the configuration item of at least one component to be configured is subjected to parameter configuration through the configuration parameters in the configuration file.
In a second aspect, there is provided a management server, which may perform the method of the first aspect or the possible embodiments of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and/or hardware. Based on the same inventive concept, the principle and the advantageous effects of the management server for solving the problems can be found in the first aspect or the possible embodiments and advantageous effects of the first aspect, and repeated details are not repeated.
In a third aspect, there is provided a management server, comprising: a processor, a memory, a communication interface; the processor, the communication interface and the memory are connected. The communication interface is used for realizing communication with the service server. Wherein one or more programs are stored in the memory, and the processor invokes the programs stored in the memory to implement the solution in the first aspect or the possible implementation manner of the first aspect, and the implementation manner and the advantageous effects of the management server for solving the problem may refer to the possible implementation manner and the advantageous effects of the first aspect or the first aspect, and repeated details are omitted.
In a fourth aspect, a computer program product is provided, which, when run on a computer, causes the computer to perform the method of the first aspect or the possible embodiments of the first aspect described above.
In a fifth aspect, a chip product for managing a server is provided, which performs the method of the first aspect or the method in the possible implementation manner of the first aspect.
A sixth aspect provides a computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of the first aspect or the method of a possible implementation of the first aspect.
Drawings
Fig. 1 is a schematic structural diagram of a device management system provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a device management method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another device management method provided in an embodiment of the present application;
FIG. 4 is a schematic view of an interface provided by an embodiment of the present application;
FIG. 5 is a schematic view of another interface provided by embodiments of the present application;
fig. 6 is a schematic structural diagram of a management server according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another management server provided in an embodiment of the present application.
Detailed Description
Specific embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The embodiment of the application provides an equipment management method and a management server, which are beneficial to quickly configuring parameters of components of a service server.
In order to better understand the embodiments of the present application, the following describes a communication system according to the embodiments of the present application.
Referring to fig. 1, fig. 1 is a schematic diagram of a device management system according to an embodiment of the present disclosure. As shown in fig. 1, the device management system includes a management server and at least one service server, that is, the device management system includes a management server and one or more service servers, and fig. 1 takes the case that the device management system includes 3 service servers as an example. The management server is used for managing each service server in the equipment management system. One or more components are included in each service server. The component may be hardware, firmware, software, or the like. Hardware (hardware) is a short term for computer hardware and refers to a general term for various physical devices in a computer system, which are composed of electronic, mechanical, and optoelectronic components. For example, the hardware may be a Redundant Array of Independent Disks (RAID), a Network Interface Card (NIC), and the like. Firmware refers to a program written into an erasable read only memory (eprom) or an eeprom, and is software that serves as the lowest layer of the system. For example, the firmware may include a basic input/output system (BIOS), or the like. The software may be an operating system, application software, or the like.
The management server can perform parameter configuration on the components of each service server in the equipment management system so that the service servers can meet service requirements. The management server can carry out parameter configuration on a plurality of business servers with the same components simultaneously in batch. For example, if the service servers 1 to 3 have the same components, the management server can perform parameter configuration on the service servers 1 to 3 in batch. Or, the management server may also perform parameter configuration for each service server separately, which is not limited in the embodiment of the present application.
Wherein, a component has one or more configuration items to be configured, and each configuration item can correspond to one or more configuration parameters. The management server configures the configuration item through one configuration parameter of the configuration item. For example, as shown in table 1 below, the RAID card in the service server has three configuration items, which are "RAID controller ID", "RAID level", and "boot disk", respectively. The 2 configuration parameters corresponding to the RAID controller ID are RAIDStorage0 and RAIDStorage1, respectively. The 5 configuration parameters corresponding to the "RAID level" are "RAID 0", "RAID 1", "RAID 5", "RAID 6", and "RAID 10", respectively. The 2 configuration parameters corresponding to the "boot disk" are yes and no, respectively. "yes" indicates that the current RAID group is to be the boot disk, and "no" indicates that the current RAID group is not to be the boot disk. The management server may configure "RAID controller ID" by "RAIDStorage 0", configure "RAID level" by "RAID 0", and configure "boot disk" by "yes".
TABLE 1
Configuration item Configuring parameters
RAID controller ID RAIDStorage0、RAIDStorage1
RAID level RAID0、RAID1、RAID5、RAID6、RAID10
Starting disc Yes, no
As another example, as shown in table 2 below, the BIOS in the service server has four configuration items, which are "system start mode", "energy efficiency mode", "VTd support", and "intercept remap", respectively. The 2 configuration parameters corresponding to the system starting mode are a Legacy mode and a UEFI mode respectively. The 2 configuration parameters corresponding to the energy efficiency mode are low power consumption and high performance respectively. The 2 configuration parameters corresponding to VTd support are enabled and disabled, respectively. The 2 configuration parameters corresponding to the "interrupt remap" are "enable" and "disable", respectively. The management server can configure a system starting mode through a UEFI mode, configure an energy efficiency mode through a low power consumption mode, configure VTd support through an enable mode, and configure an InterruptRemap through the enable mode.
TABLE 2
Configuration item Configuring parameters
System start-up mode Legacy mode, UEFI mode
Energy efficiency mode Low power consumption and high performance
VTd support Enable, disable
InterruptRemap Enable, disable
As another example, the operating system may have the configuration items "operating system version" and the configuration parameters may be "CentOS7.3" and "CentOS7.4". The current version of the operating system is "CentOS7.2". The management server may configure the "os version" by "centos 7.4", i.e. the management server upgrades the os to the centos7.4 version.
As another example, the firmware may have a configuration item "firmware version" and the configuration parameters may be "0.0.2", "0.0.3". The firmware current version is "0.0.1". The management server may configure the "firmware version" by "0.0.3", i.e., the management server upgrades the firmware to version 0.0.3.
The following describes the device management method and the management server provided by the present application in detail.
Referring to fig. 2, fig. 2 is a schematic flowchart of a device management method according to an embodiment of the present disclosure. As shown in fig. 2, the device management method includes the following steps 201 to 204, wherein:
201. the management server obtains a component identifier of a component in each service server in the at least one service server.
Wherein the management server obtains component identifications of one or more components of each service server of the device management system. For example, the management server obtains component identifications of one or more components in the business servers 1-3 shown in FIG. 1. For example, the component may be hardware, firmware, software, and the like, the hardware may be a RAID card, a network card, a CPU, a motherboard (i.e., a single board), and the like, the firmware may be a BIOS and the like, and the software may be an operating system and the like.
Alternatively, the management server may obtain the component identifier of the component from each service server of the device management system through a Baseboard Management Controller (BMC). Specifically, the management server may obtain an identifier of the component of the specified type from the service server through the BMC, and the service server may return the identifier of the component of the specified type from the management server. For example, the management server may obtain the identifier of the RAID card from the service server through the BMC, and the service server may return the identifier of the RAID card.
Wherein the part identification is used to indicate identity information of the part. Optionally, the component identifier may be information capable of determining the identity of the component, such as a component model number, a component version number, or a component name. For example, if the component is hardware, the component identification may be a component model number. For example, the model of the RAID card may be "LSI 3108", or "LSI 3008", or "LSI 2208". The network card model can be "MZ 910" or "MZ 920", etc. The CPU model may be "IntelxeonV 3", "IntelxeonV 5", or the like. The model of the main board can be 'CH 121', 'RH 1288' and the like. If the component is firmware or software, the component identification may be a component version number. For example, the version number of the firmware may be 0.0.1, 0.0.2, etc. The version number of the operating system may be CentOS7.2, CentOS7.3, etc.
As an optional implementation manner, a specific implementation manner of the management server obtaining the identifier of the component in each service server in the at least one service server is as follows: when detecting that at least one service server is powered on, the management server acquires the identifier of the component in each service server in at least one service server. By implementing the optional implementation mode, the part identification of the service server can be timely acquired, and the submodel set of the service server is further determined in advance, so that the management server can perform parameter configuration on the configuration items of the parts of the service server according to the configuration items and the configuration parameters in the submodel set of the service server when the parts of the service server need to be subsequently configured with parameters.
Optionally, if the first service server is powered on for the first time, that is, the first service server is a service server newly added to the device management system, and after the management server obtains the identifier of the component of the first service server, step 202 may be directly performed, that is, the first sub-model set corresponding to the first service server is determined. The first service server is any one of at least one service server included in the equipment management system. For example, the first service server may be any one of the service servers 1 to 3 in the device management system shown in fig. 1.
Optionally, if the first service server is not powered on for the first time, after the management server obtains the identifier of the component of the first service server, when the power on detects that the component of the first service server is changed from the component of the first service server detected by the last power on, step 202 is executed. For example, the first service server is the service server 1, when the service server 1 is powered on for the first time, the management server detects that the components of the service server 1 are a RAID card with the model "LSI 3108" and a network card with the model "MZ 910", and the management server executes step 202. When the service server 1 is powered on for the second time, the management server detects whether the components of the service server 1 are the RAID card with the model "LSI 3108" and the network card with the model "MZ 910", that is, the components in the service server 1 are not changed, and then the management server ends the flow. If the service server 1 is powered on for the second time, the management server detects that the component of the service server 1 is a RAID card with the model "LSI 2208" and a network card with the model "MZ 920", that is, the component in the service server 1 is changed, the management server performs step 202, that is, the first sub-model set of the service server 1 is determined again.
As an optional implementation manner, a specific implementation manner of the management server obtaining the identifier of the component in each service server in the at least one service server is as follows: the management server periodically obtains the identification of the components in each of the at least one service server. By implementing the optional implementation mode, the latest part identifier of the service server can be determined in time, and the latest sub-model set corresponding to the service server can be further determined in time.
Alternatively, the management server may periodically obtain the identification of the component in each of the at least one service server after detecting that the first service server is powered on. When detecting that the component of the first service server is changed from the component of the first service server detected in the previous cycle in this cycle, step 202 is executed to re-determine the first sub-model set of the service server 1.
202. The management server determines a first set of sub-models in a preset model library according to the identification of the component of the first service server.
The preset model library comprises at least one sub-model, and each sub-model comprises configuration items and configuration parameters of components. For example, the preset model library includes 6 sub-models, which are respectively sub-models 1 to 6. The sub-model 1 and the sub-model 2 both include configuration items and configuration parameters of the RAID card. The submodel 3 and the submodel 4 both comprise configuration items and configuration parameters of the network card. Sub-model 5 and sub-model 6 each include configuration items and configuration parameters of the BIOS. The submodel 1 and the submodel 2 include configuration items and configuration parameters that are not the same. The submodel 3 and the submodel 4 include configuration items and configuration parameters that are not the same. The submodel 5 and the submodel 6 include configuration items and configuration parameters that are not the same. Alternatively, the file format of the sub-model may be a markup file format, for example, the file format of the sub-model may be xml or json, etc. The markup type file format is small in size, generally several to dozens of KB, beneficial to downloading by a user and easy to expand.
Each sub-model comprises one or more configuration items, and each configuration item corresponds to one or more configuration parameters. For example, sub-model 1 may include configuration items and configuration parameters as shown in Table 1 above. As another example, sub-model 5 may include configuration items and configuration parameters as shown in Table 2 above.
Wherein the first set of submodels includes at least one submodel corresponding to the component identification of the first service server.
It should be noted that, for any service server in the management system, the process of determining, by the management server, the first sub-model corresponding to the service server is the same, and in the following description of the embodiment of the present application, how the management server determines the first sub-model corresponding to the first service server and the first configuration information is described as an example.
Alternatively, the management server may set in advance the correspondence relationship between the submodel and the component identifier. After the management server obtains the component identifier of the first service server, the sub-model corresponding to the component identifier of the first service server is determined in a preset model library according to the corresponding relation between the preset sub-model and the component identifier, and therefore the first sub-model set is determined.
Generally, hardware is different, and configuration items and configuration parameters of the hardware are also different. Therefore, the correspondence relationship between the identification of the hardware and the submodel including the configuration item and the configuration parameter of the hardware may be set in advance. In general, some hardware is different, configuration items and configuration parameters of firmware are different, and because identification of firmware is simpler, identification of firmware produced by different manufacturers is the same, but configuration items and configuration parameters of firmware may be different. Therefore, in order to uniquely determine the currently required sub-model including the configuration items and configuration parameters of the firmware, the correspondence relationship between the identification of the hardware and the sub-model including the configuration items and configuration parameters of the firmware may be preset. Of course, the corresponding relationship between the identifier of the firmware and the sub-model including the configuration item and the configuration parameter of the firmware may also be preset. Generally, the software is different, and the configuration items and configuration parameters of the software are also different. Therefore, the correspondence between the identification of the software and the submodel including the configuration item and the configuration parameter of the software may be set in advance.
For example, the correspondence relationship between the RAID card identification and the sub model including the configuration item and the configuration parameter of the RAID card may be set in advance. The corresponding relation between the network card identification and the submodel comprising the configuration items and the configuration parameters of the network card can be preset. The corresponding relation between the CPU identification or the mainboard identification and the submodel comprising the configuration items and the configuration parameters of the BIOS can be preset, or the submodel comprising the BIOS version number and the configuration items and the configuration parameters of the BIOS can be preset. The correspondence of the operating system identification with the sub-model including the configuration items and configuration parameters of the operating system may be set in advance.
For example, the component identifier includes a component model number. The preset model library comprises the submodels 1-6. The sub-models and component models may be mapped as shown in table 3 below. Here, "LSI 3108" and "LSI 3008" are RAID card models. "MZ 910" and "MZ 920" are network card models. "IntelxeonV 3" and "IntelxeonV 5" are CPU models.
When the management server detects that the RAID card model of the first service server is 'LSI 3108', the network card model is 'MZ 910' and the CPU model is 'IntelxeonV 3', the sub-model 5 corresponding to the sub-model 1 corresponding to the 'LSI 3108', the sub-model 3 corresponding to the 'MZ 910' and the 'IntelxeonV 3' is determined. The management server acquires the submodel 1, the submodel 3 and the submodel 5 from a preset model library, wherein the submodel 1, the submodel 3 and the submodel 5 are submodels in a first submodel set.
TABLE 3
Component identification Sub-model
LSI3108 Submodel 1
LSI3008 Submodel 2
MZ910 Submodel 3
MZ920 Submodel 4
IntelxeonV3 Submodel 5
IntelxeonV5 Submodel 6
For another example, as shown in Table 4 below, BIOS version numbers "0.0.1" and "0.0.2" each correspond to sub-model 5. BIOS version number "0.0.3" corresponds to sub-model 6. When the management server detects that the RAID card model of the first service server is 'LSI 3108', the network card model is 'MZ 910' and the BIOS version number is '0.0.1', the sub-model 1 corresponding to 'LSI 3108', the sub-model 3 corresponding to 'MZ 910' and the sub-model 5 corresponding to '0.0.1' are determined. The management server acquires the submodel 1, the submodel 3 and the submodel 5 from a preset model library, wherein the submodel 1, the submodel 3 and the submodel 5 are submodels in a first submodel set.
TABLE 4
Component identification Sub-model
LSI3108 Submodel 1
LSI3008 Submodel 2
MZ910 Submodel 3
MZ920 Submodel 4
0.0.1 or 0.0.2 Submodel 5
0.0.3 Submodel 6
Or, the name of the sub-model in the preset model library may include a component identifier, and the sub-model corresponding to the component identifier is the sub-model whose sub-model name includes the component identifier. The management server determines the submodel with the name of the submodel including the component identifier of the first service server in a preset model library, so that a first submodel set is determined. This makes it possible to avoid separately establishing the correspondence between the identification of the submodel and the identification of the component as shown in table 3.
For example, taking the part identifier as the part model, the preset model library includes the submodels 1-6. The name of the submodel 1 is "RAID-LSI 3108", the name of the submodel 2 is "RAID-LSI 3008", the name of the submodel 3 is "NIC-MZ 910", the name of the submodel 4 is "NIC-MZ 920", the name of the submodel 5 is "BIOS-intelxeon v 3", and the name of the submodel 6 is "BIOS-intelxeon v 5". The management server acquires the component models of the first service server as "LSI 3108", "MZ 910", and "IntelxeonV 3". The management server finds "LSI 3108" in the name of sub-model 1, "MZ 910" in the name of sub-model 3, and "intelxeon v 3" in the name of sub-model 5. Thus, the first set of submodels determined by the management server comprises submodel 1, submodel 3 and submodel 5.
As an optional implementation manner, the specific implementation manner of the management server determining the first sub-model set in the preset model library according to the identifier of the component of the first service server is as follows: the management server determines at least one second submodel set corresponding to at least one component type of the first service server in a preset model library, wherein each second submodel set comprises submodels corresponding to components in the same type, and the component type is used for indicating component classification information to which the components of the first service server belong; the management server determines a first set of submodels from at least one second set of submodels based on at least one component identification of the first business server.
By implementing the optional implementation mode, the second submodel set can be determined according to the category of the component, the second submodel set comprises submodels corresponding to the components in the same category, and then the submodels corresponding to the component identifiers are searched in the second submodel set, so that the searching range of the submodels corresponding to the component identifiers can be reduced, and the submodels corresponding to the component identifiers can be searched more quickly.
For example, a class of components typically includes a plurality of different models of components. For example, a RAID card of the type "LSI 3108", a RAID card of the type "LSI 3008", and a RAID card of the type "LSI 2208" all belong to one component category, that is, the component category is a RAID card. Similarly, the network card with the model "MZ 910" and the network card with the model "MZ 920" also belong to a component category, that is, the component category is the network card. Similarly, the CPU component classes of model numbers "IntelxeonV 3" and "IntelxeonV 5" are CPUs.
As shown in table 5 below, the management server may previously store the correspondence relationship of the component category and the second sub-model set. The second submodel set 1 includes the submodel 1 and the submodel 2. The second submodel set 2 includes the submodel 3 and the submodel 4. The second submodel set 3 includes the submodel 5 and the submodel 6. The management server acquires the model number "LSI 3108" of the RAID card, the model number "MZ 910" of the network card, and the model number "IntelxeonV 3" of the CPU of the first service server. The management server determines that the component type RAID card corresponds to a second submodel set 1, determines that the component type network card corresponds to a second submodel set 2, and determines that the component type CPU corresponds to a second submodel set 3. The management server acquires the submodel 1 from the second submodel set 1 according to the model "LSI 3108", acquires the submodel 3 from the second submodel set 2 according to the model "MZ 910", and acquires the submodel 5 from the second submodel set 3 according to the model "intelxeon v 3". For how the management server obtains the sub-model from the second sub-model set according to the model, refer to the above description, for example, according to the pre-established correspondence between the model and the sub-model, determine the sub-model corresponding to the component model of the first service server, or determine the sub-model whose name includes the component model of the first service server.
TABLE 5
Class of parts Second set of submodels
RAID Second set of submodels 1
NIC Second set of submodels 2
CPU Second set of submodels 3
Of course, when the identifier of the firmware corresponds to the sub-model including the configuration item and the configuration parameter of the firmware, the second sub-model set corresponding to the component type of the firmware may be determined first, and then the sub-model corresponding to the identifier of the firmware is obtained from the second sub-model set corresponding to the component type of the firmware. For example, when the identification of the BIOS corresponds to a sub-model including a configuration item and a configuration parameter of the BIOS, a second sub-model set corresponding to the component type "BIOS" may be determined first, and then the sub-model corresponding to the identification of the BIOS may be obtained from the second sub-model set corresponding to the component type "BIOS".
As an optional implementation manner, when the sub-model corresponding to the identifier of the first component does not exist in the preset model library, the management server obtains the configuration item and the configuration parameter of the first component from the first service server, where the first component is any one of the components of the first service server. And the management server adds a first sub-model in a preset model library according to the configuration items and the configuration parameters of the first component, wherein the first sub-model comprises the configuration items and the configuration parameters of the first component. By implementing the optional implementation mode, the submodel can be automatically generated, and the submodel in the preset model library can be expanded, so that the submodel in the preset model library is more complete.
For example, the RAID card model of the first service server acquired by the management server is "LSI 3108" and the network card model is "MZ 910". The submodel corresponding to the network card model MZ910 does not exist in the preset model library. Therefore, the management server obtains the configuration item and the configuration parameters of the network card with the model of "MZ 910" from the first service server. And the management server generates a first sub-model according to the configuration item and the configuration parameters of the network card with the model of 'MZ 910'. The first sub-model comprises configuration items and configuration parameters of a network card with the model of 'MZ 910'. After the management server generates the first sub-model, the first sub-model is stored in the preset model library so as to expand the sub-models in the preset model library, so that the sub-models in the preset model library are more perfect. Optionally, the management server may establish and store a corresponding relationship between the model "MZ 910" and the first sub-model, or include the model "MZ 910" in the name of the first sub-model, so that the corresponding first sub-model may be found according to the component model "MZ 910". After the management server generates the first submodel, the first submodel and the submodel corresponding to the model "LSI 3108" acquired from the preset model library are determined as submodels in the first submodel set.
Optionally, if there is no sub-model including configuration items and configuration parameters of the firmware corresponding to the identifier of the first component (for example, the identifier of the first component may be a CPU identifier or a motherboard identifier) in the preset model library, the management server obtains the configuration items and the configuration parameters of the firmware from the first service server. And the management server adds a first sub-model in a preset model library according to the configuration items and the configuration parameters of the firmware, wherein the first sub-model comprises the configuration items and the configuration parameters of the firmware.
Optionally, after the first sub-model set is determined, the first sub-model set corresponding to the first service server may be stored, so that the configuration items of the components of the first service server are subsequently configured according to the configuration items and the configuration parameters in the first sub-model set.
Optionally, when the sub-model corresponding to the identifier of the first component does not exist in the preset model library, the sub-model corresponding to the identifier of the first component may also be downloaded from the internet. For example, the sub-models may be published to a company official network by a management software development team, so that when the sub-model corresponding to the identification of the first part does not exist in the preset model library, the management server may download the sub-model corresponding to the identification of the first part from the company official network.
Optionally, the sub-models in the pre-set model library may be copied from other devices.
203. The management server sends the first configuration information to the first service server.
After determining a first sub-model set in a preset model library according to the identifier of the component of the first service server, the management server sends first configuration information to the first service server. The first configuration information carries at least one configuration item and configuration parameters in the first submodel set, so that the first service server configures the configuration parameters of the configuration item of the at least one component to be configured according to the first configuration information. The component to be configured may be a part of the first service server, that is, the management server may perform parameter configuration on only a part of the component of the first service server. Alternatively, the component to be configured may also be all components of the first service server, and this embodiment of the present application is not limited.
For example, the first set of submodels includes submodel 1 and submodel 5 described above. Sub model 1 includes configuration items and configuration parameters of the RAID card. The submodel 5 includes configuration items and configuration parameters of the BIOS. The configuration items and configuration parameters included in the sub-model 1 can be as shown in table 1 above. The submodel 5 may include configuration items and configuration parameters as shown in table 2 above. The management server may configure only the configuration items of the RAID card. For example, the management server transmits, to the first service server, first configuration information including configuration items "RAID controller ID" and "RAID level", a configuration parameter "RAIDStorage 0" for configuring the "RAID controller ID", and a configuration parameter "RAID 10" for configuring the "RAID level". After the first service server receives the first configuration information, the RAID controller ID of the RAID card is configured as RAIDStorage0, and the RAID level is configured as RAID 10.
For the configuration items and the configuration parameters of different components to be configured, the management server can send the configuration items and the configuration parameters to the first service server through different configuration paths through the BMC. For example, the component to be configured includes a RAID card and a BIOS. The management server can send the configuration items and the configuration parameters of the RAID card to the first service server through the BMC through the configuration path 1, and send the configuration items and the configuration parameters of the BIOS to the first service server through the BMC through the configuration path 2. Thus, after receiving the configuration item and the configuration parameter through the configuration path 1, the first service server configures the configuration item of the RAID card using the configuration parameter. After the first service server receives the configuration item and the configuration parameters through the configuration path 2, the configuration item of the BIOS is configured by using the configuration parameters.
Optionally, the method and the device can also be used in a scenario of firmware upgrade of the first service server. The part identification of the first service server acquired by the management server comprises the version number of the firmware. And the management server acquires the sub-model corresponding to the firmware version number. The configuration item included in the sub-model corresponding to the firmware version number is a firmware version, and the configuration parameter is one or more firmware version numbers. After the management server obtains the sub-model corresponding to the firmware version number, at least one configuration item and configuration parameters in the sub-model can be used as configuration parameters in first configuration information, and the first configuration information is sent to the first service server. And after receiving the first configuration information, the first business server upgrades the firmware version to the version in the first configuration information. For example, when the first configuration information includes a configuration item "firmware version" and a configuration parameter "0.0.2", the first service server upgrades the version of the firmware to 0.0.2.
Optionally, the method and the system can also be used in a scenario of upgrading an operating system of the first service server. The part identification of the first service server acquired by the management server comprises the version number of the operating system. And the management server acquires the sub-model corresponding to the version number of the operating system. The configuration item included in the sub-model corresponding to the version number of the operating system is the version of the operating system, and the configuration parameter is one or more version numbers of the operating system. After the management server obtains the sub-model corresponding to the version number of the operating system, at least one configuration item and configuration parameters in the sub-model can be used as configuration parameters in first configuration information, and the first configuration information is sent to the first service server. And after receiving the first configuration information, the first business server upgrades the version of the operating system to the version in the first configuration information. For example, when the configuration item "os version" and the configuration parameter "centros 7.3" are included in the first configuration information, the first business server upgrades the version of the os version to centros 7.3.
204. And the first service server configures the configuration parameters of the configuration items of at least one component to be configured according to the first configuration information.
Optionally, the management server may send the first configuration information to the plurality of service servers in batch to achieve the purpose of batch configuration. For example, the service server 1 and the service server 2 have the same components, and the same parameter configuration is required. The management server can send the first configuration information to the service server 1 and the service server 2 at the same time, so that the service server 1 and the service server 2 perform parameter configuration on the configuration items of the components according to the first configuration information.
It can be seen that by implementing the method described in fig. 2, the preset model library includes at least one sub-model, and each sub-model includes configuration items and configuration parameters of the component. The management server can dynamically acquire a submodel set corresponding to the service server, wherein the submodel set comprises at least one submodel corresponding to the component identifier of the service server. Therefore, the management server can dynamically obtain the configuration items and the configuration parameters of the service server, so that the configuration items of the components of the service server can be subjected to parameter configuration subsequently. It can be seen that by implementing the method described in fig. 2, when the component of the service server is changed, the latest configuration item and configuration parameter of the service server can be dynamically obtained without updating the management software, which is beneficial to quickly perform parameter configuration on the configuration item of the component of the service server, and improves the maintenance efficiency of the operation and maintenance mode of the server. And different service servers may have partially identical components, by implementing the method described in fig. 2, a plurality of service servers can reuse the same sub-model, thereby being beneficial to saving development cost.
As a possible embodiment, after step 203, the management server may also store the first configuration information, and establish a new sub-model in the preset model library, where the sub-model is used to identify component configuration parameter set information of the first service server, so that when the management node performs operation of updating the configuration parameters or upgrading the firmware or upgrading the OS again, the management node quickly acquires a sub-model set corresponding to the first service server, determines the first configuration parameter, and sends the first configuration parameter to the first service server, thereby improving the operation and maintenance efficiency of the service server, reducing the operation time of operation and maintenance scenarios such as parameter configuration, firmware upgrade, and OS upgrade, and reducing the influence on the operation and application on the service server.
Referring to fig. 3, fig. 3 is a schematic flowchart of a device management method according to an embodiment of the present disclosure. The device management method shown in fig. 3 is different from the device management method shown in fig. 2 in that, after determining the first sub-model set, the management server in fig. 3 may display the configuration items and the configuration parameters in the first sub-model set according to preset display rules in the first sub-model set, and may select at least one configuration item and configuration parameter in the first sub-model set as the configuration item and configuration parameter included in the first configuration information. As shown in fig. 3, the device management method includes the following steps 301 to 306, wherein:
301. the management server obtains an identification of a component in each of the at least one service server.
302. The management server determines a first set of sub-models in a preset model library according to the identification of the component of the first service server.
The specific implementation of steps 301 and 302 is the same as that of steps 201 and 202 described above, and specific reference may be made to the description corresponding to steps 201 and 202 described above, which is not described herein again.
303. And the management server displays the configuration items and the configuration parameters in the first sub-model set according to the preset display rules in the first sub-model set.
The submodels of the first submodel set further comprise configuration items and preset display rules of configuration parameters. After the management server determines the first sub-model set, the configuration items and the configuration parameters in the first sub-model set can be displayed according to the preset display rules in the first sub-model set.
In practical application, if a component of the service server is changed or the service server is newly added to the device management system, the management software needs to be updated to update the configuration items and the configuration parameters of the service server in the management software and update the display rules of the configuration items and the configuration parameters. By implementing step 303, the management server can dynamically obtain the configuration items and the display rules of the configuration parameters of the service server by adding the display rules of the configuration items and the configuration parameters to the sub-model, so that the management software does not need to be updated, which is beneficial to quickly configure the configuration items of the service server.
Alternatively, the preset display rule of the configuration item may include at least one of a display order of the configuration item and a menu path of the configuration item. The display order of the configuration items refers to the display order among several configuration items of the same component. The menu path of the configuration item refers to the directory where the configuration item is located.
Optionally, the preset display rule of the configuration parameter includes at least one of whether the configuration parameter is read only, whether the configuration parameter is grayed, and whether the configuration parameter is hidden. Whether the configuration parameters are read-only or not refers to whether the configuration parameters are read-only or not and cannot be changed. Whether or not the arrangement parameter is grayed out means whether or not the arrangement parameter is to be grayed out for display in the case where the dependency condition is not satisfied. Whether a configuration parameter is hidden or not refers to whether the configuration parameter needs to be hidden when not involved.
For example, table 6 below exemplifies a sub-model corresponding to a RAID card, and the sub-model may include information as shown in table 6 below.
TABLE 6
Figure BDA0001671617820000121
As an optional implementation manner, the submodels of the first submodel set further include a dependent configuration item, a depended configuration item, and a dependent condition; and displaying the dependent configuration items and the configuration parameters of the dependent configuration items in the first sub-model set according to whether the current configuration parameters of the dependent configuration items meet the dependent conditions.
By setting the dependency relationship, the user experience is improved, and the configuration items are prevented from being conflicted. And by adding the dependent configuration item, the depended configuration item and the dependent condition into the submodel, the management server can dynamically acquire the dependent configuration item, the depended configuration item and the dependent condition of the service server, so that management software does not need to be updated, and parameter configuration can be conveniently and quickly performed on the configuration item of the service server.
For example, table 7 below exemplifies a sub-model corresponding to the BIOS, and the sub-model may include information as shown in table 7 below. When the current configuration parameter supported by the dependent configuration item 'VTd' meets the dependent condition, that is, when the current configuration parameter supported by the dependent configuration item 'VTd' is 'enabled', the dependent configuration item 'intercept remap' and the configuration parameter thereof are not hidden. Otherwise, hiding the dependent configuration item 'InterruptRemap' and its configuration parameters.
TABLE 7
Figure BDA0001671617820000131
Optionally, the first sub-model set may further include at least one of a data type of the configuration parameter (e.g., an enumeration type, a boolean type, etc.), a creation manner of the configuration parameter (e.g., single selection, multiple selection, etc.), help information, alarm information, a currently configured value of the configuration item, a default value of the configuration item, a maximum string length of the configuration parameter, a minimum string length of the configuration parameter, a maximum value of the configuration parameter, a minimum value of the configuration parameter, and an effective mode (e.g., effective immediately or effective after restart), etc.
304. The management server selects at least one configuration item and configuration parameters in the first sub-model set as configuration items and configuration parameters included in the first configuration information.
Alternatively, the management server may select configuration items to be configured and select appropriate configuration parameters from the displayed configuration items according to a selection instruction input by the user.
For example, the first set of submodels includes submodel 1 and submodel 5 described above. The configuration items and configuration parameters included in the sub-model 1 can be as shown in table 1 above. The submodel 5 may include configuration items and configuration parameters as shown in table 2 above. Fig. 4 is a schematic diagram of a display interface, as shown in fig. 4, the management server may output configuration items and configuration parameters included in the first sub-model set. The user may select the configuration items to be configured and the appropriate configuration parameters. As shown in fig. 4, the user selects the configuration item "RAID controller ID" to be configured as "RAIDStorage 0", the configuration item "RAID level" to be configured as "RAID 10", and the configuration item "boot disk" to be configured as "yes". After receiving a selection instruction input by a user, the management server selects a configuration item "RAID controller ID" and a corresponding configuration parameter "RAIDStorage 0", and a configuration item "RAID level" and a corresponding configuration parameter "RAID 10", and a configuration item "launch disk" and a corresponding configuration parameter "yes", as configuration items and configuration parameters included in the first configuration information.
By implementing step 304, configuration items and configuration parameters can be flexibly selected from the first sub-model set for parameter configuration.
305. The management server sends the first configuration information to the first service server.
Optionally, after the management server sends the first configuration information to the first service server, the management server may generate a configuration file, where the configuration file includes the first configuration information. The management server stores the configuration file, so that the user can input an instruction when the user wants to perform the same configuration next time, the management server directly selects the configuration file, and the configuration item of at least one component to be configured is subjected to parameter configuration through the configuration parameters in the configuration file.
306. And the first service server updates the configuration parameters of the configuration items of the component according to the first configuration information.
The specific implementation of the above 305 and 306 portions is the same as that of the above 203 and 204, and for details, reference may be made to the description corresponding to the above 203 and 204, which is not repeated herein.
In order to be able to illustrate the content of the present application more clearly, the solution of the present application is further explained below with reference to three complete examples. In the first example, parameter configuration is performed by the management server on the RAID card and the BIOS of the service server. The second example takes the case that the management server upgrades the operating system of the service server. In the third example, the management server upgrades the firmware of the service server.
Example one:
the management server has a preset model library. The preset model library comprises 4 sub-models which are respectively 1-4 sub-models. The sub model 1 and the sub model 2 both comprise configuration items and configuration parameters of the RAID card. Sub-model 3 and sub-model 4 each include configuration items and configuration parameters of the BIOS. The submodel 1 and the submodel 2 include configuration items and configuration parameters that are not the same. The submodel 3 and the submodel 4 include configuration items and configuration parameters that are not the same. The submodels in the preset model library have a corresponding relationship with the part models, and the corresponding relationship is shown in the following table 8. "LSI 3108" and "LSI 3008" are component models of RAID cards. "IntelxeonV 3" and "IntelxeonV 5" are component models of the CPU. Different part models correspond to different submodels.
TABLE 8
Component identification Sub-model
LSI3108 Submodel 1
LSI3008 Submodel 2
IntelxeonV3 Submodel 3
IntelxeonV5 Submodel 4
The management server can acquire the models of the RAID cards and the CPU models of the business servers 1-3 when the business servers 1-3 are powered on. Or the management server can periodically acquire the models of the RAID cards and the CPU models of the business servers 1-3. The management server acquires a RAID card model of "LSI 3108" and a CPU model of "IntelxeonV 3" of the service server 1. The service server 2 has a RAID card model of "LSI 3108" and a CPU model of "IntelxeonV 3". The service server 3 has a RAID card model of "LSI 2208" and a CPU model of "IntelxeonV 5".
The management server can directly search the sub-model corresponding to the RAID card model "LSI 3108" and the sub-model corresponding to the CPU model "intelxeon v 3" of the service server 1 in the preset model library according to the correspondence in table 8 above. As shown in table 8 above, the management server determines submodel 1 corresponding to "LSI 3108" and submodel 3 corresponding to "IntelxeonV 3". Therefore, the management server determines that the first sub-model set 1 corresponding to the business server 1 includes the sub-model 1 and the sub-model 3.
Alternatively, the management server may set in advance a correspondence relationship between the component category and the second submodel set. The correspondence is shown in table 9 below. After the management server obtains the model "LSI 3108" of the RAID card and the model "intelxeon v 3" of the CPU of the service server 1, it may first determine that the component type "RAID card" corresponds to the second sub-model set 1 and determine that the component type "CPU" corresponds to the second sub-model set 2. The management server acquires submodel 1 from the second submodel set 1 according to the model "LSI 3108", and acquires submodel 3 from the second submodel set 3 according to the model "intelxeon v 3", and composes the submodel 1 and the submodel 3 into the first submodel set 1.
TABLE 9
Class of parts Second set of submodels
RAID Second set of submodels 1
CPU Second set of submodels 2
Similarly, the management server determines that the service server 2 corresponds to the first sub-model set 1 according to the same principle.
When the management server determines the first sub-model set 2 corresponding to the business server 3, it is detected that the sub-model corresponding to the RAID card model "LSI 2208" does not exist in the preset model library. The management server thus acquires configuration items and configuration parameters of the RAID card of model "LSI 2208" from the service server 3. And generating a sub-model 5 according to the configuration items and configuration parameters of the acquired RAID card with the model of 'LSI 2208', wherein the sub-model 5 comprises the configuration items and configuration parameters of the RAID card with the model of 'LSI 2208'. The management server establishes a correspondence relationship between the submodel 5 and the model "LSI 2208", and stores the submodel 5 in a preset model library. And the final management server determines that the first sub-model set 2 corresponding to the business server 3 comprises a sub-model 4 and a sub-model 5.
Or, the management server can also determine the first sub-model set corresponding to the service servers 1-3 in another mode. The preset model library comprises 4 different submodels which are respectively submodels 1-4. The sub-model 1 and the sub-model 2 both include configuration items and configuration parameters of the RAID card. Sub-model 3 and sub-model 4 each include configuration items and configuration parameters of the BIOS. The submodels in the preset model library have a corresponding relationship with the part models, and the corresponding relationship is shown in the following table 10. "LSI 3108" and "LSI 3008" are component models of RAID cards. The component models of different RAID cards correspond to different sub-models. "0.0.1", "0.0.2", and 0.0.3 are part version numbers of the BIOS. The version numbers of different BIOS may correspond to the same sub-model or to different sub-models.
Watch 10
Component identification Sub-model
LSI3108 Submodel 1
LSI3008 Submodel 2
0.0.1 or 0.0.2 Submodel 3
0.0.3 Submodel 4
The management server can acquire the type of the RAID card and the version number of the BIOS of the business server 1-3 when the business server 1-3 is powered on. Or the management server can periodically acquire the type of the RAID card and the version number of the BIOS of the business servers 1-3. The management server acquires that the RAID card type of the service server 1 is "LSI 3108" and the version number of the BIOS is "0.0.1". The service server 2 has a RAID card model number of "LSI 3108" and a version number of BIOS of "0.0.1". The service server 3 has a RAID card model number of "LSI 2208" and a version number of BIOS of "0.0.3".
The management server can directly search the sub-model corresponding to the RAID card model "LSI 3108" of the service server 1 and the sub-model corresponding to the version number "0.0.1" of the BIOS in the preset model library according to the correspondence in table 10 above. As shown in table 10 above, the management server specifies submodel 1 corresponding to "LSI 3108" and submodel 3 corresponding to "0.0.1". Therefore, the management server determines that the first sub-model set 1 corresponding to the business server 1 includes the sub-model 1 and the sub-model 3.
Alternatively, the management server may set in advance a correspondence relationship between the component category and the second submodel set. After the management server obtains the model number "LSI 3108" of the RAID card of the service server 1 and the version number "0.0.1" of the BIOS, it may first determine that the component type "RAID card" corresponds to the second sub-model set 1 and determine that the component type "BIOS" corresponds to the second sub-model set 2. The management server acquires the submodel 1 from the second submodel set 1 according to the model number "LSI 3108", acquires the submodel 3 from the second submodel set 3 according to the version number "0.0.1", and combines the submodel 1 and the submodel 3 into the first submodel set 1.
Similarly, the management server determines that the service server 2 corresponds to the first sub-model set 1 according to the same principle. The management server determines that the first sub-model set 2 corresponding to the business server 3 comprises the sub-model 4 by the same principle. And because there is no sub-model corresponding to the RAID card of the service server 3 of model "LSI 2208" in the preset model library. The management server therefore acquires the configuration items and configuration parameters of the RAID card of model "LSI 2208" to the service server 3. And generating a sub-model 5 according to the configuration items and configuration parameters of the acquired RAID card with the model of 'LSI 2208', wherein the sub-model 5 comprises the configuration items and configuration parameters of the RAID card with the model of 'LSI 2208'. The management server establishes a correspondence relationship between the submodel 5 and the model "LSI 2208", and stores the submodel 5 in a preset model library. And the final management server determines that the first sub-model set 2 corresponding to the business server 3 comprises a sub-model 4 and a sub-model 5.
After the management server determines the first sub-model sets corresponding to the business servers 1-3, the user can open a configuration interface. The management server can display the configuration items and the configuration parameters in the first sub-model set in a configuration interface for selection by a user. The management server can display the configuration items and the configuration parameters in the first submodel set according to preset display rules in the first submodel set. Taking the example that the management server outputs the configuration items and the configuration parameters in the first sub-model set 1 in the configuration interface for the user to select, the output interface may be as shown in fig. 5. The user may select the configuration items to be configured and the appropriate configuration parameters. As shown in fig. 5, the user selects the configuration item "RAID controller ID" to be configured as "RAIDStorage 0", the configuration item "RAID level" to be configured as "RAID 10", and the configuration item "boot disk" to be configured as "yes". The user selects the configuration item 'system startup mode' to be configured into 'UEFI mode', the configuration item 'energy efficiency mode' to be configured into 'low power consumption', the configuration item 'VTd support' to be configured into 'enable', and the configuration item 'InterruptRemap' to be configured into 'enable'. Of course, the user may also select only the configuration parameters of the RAID card or BIOS for configuration. The user may also select the service server that needs to be configured. As shown in fig. 5, the user may choose to configure with the service server 1 and the service server 2.
After receiving the configuration instruction input by the user, the management server sends first configuration information to the service server 1 and the service server 2. Wherein the first configuration information includes configuration items and configuration parameters selected by the user as shown in fig. 5. After the service server 1 and the service server 2 receive the first configuration information, the configuration items are configured correspondingly according to the configuration parameters in the first configuration information.
Example two:
the management server has a preset model library. The preset model library comprises 2 submodels, namely a submodel 1 and a submodel 2. Sub-model 1 and sub-model 2 each include configuration items and configuration parameters of the operating system. And the submodels in the preset model library have corresponding relations with the operating system identifications. If the os id can be the os version number. For example, the version number of the operating system may be CentOS7.2, CentOS7.3, or the like. The correspondence between the sub-models in the preset model library and the operating system identifiers is shown in table 11 below.
TABLE 11
Operating system version number Sub-model
CentOS7.2 Submodel 1
CentOS7.3 Submodel 2
The management server can acquire the operating system version number of the business server 1-3 when the business server 1-3 is powered on. The management server can periodically acquire the operating system version numbers of the service servers 1-3. The version number of the operating system of the service servers 1-3 acquired by the management server is CentOS7.2. The management server obtains the submodel 1 corresponding to the centros7.2 according to the corresponding relation shown in the table 11, and the submodel 1 is used as a submodel included in the first submodel set of the service servers 1-3. Of course, if there are sub-models corresponding to other types of components in the preset model library. The management server may determine the second sub-model set corresponding to the operating system, and then determine the sub-model 1 corresponding to "centros 7.2" from the second sub-model set.
After the management server determines the first sub-model sets corresponding to the business servers 1-3, the user can open a configuration interface. The management server can display the configuration items and the configuration parameters in the first sub-model set in the configuration interface for the user to select. The management server may output the configuration items and configuration parameters in the sub-model 1 for the user to select. For example, the configuration item included in the sub-model 1 is "os version", and the configuration parameters are "centros 7.3", "centros 7.4", and "centros 7.5". If the user selects the configuration parameter 'CentOS7.5' and selects to upgrade the operating system of the service servers 1-3, the management server sends the configuration item 'operating system version' and the configuration parameter 'CentOS7.5' to the service servers 1-3, so that the service servers 1-3 upgrade the operating system version to 'CentOS7.5'. Optionally, the user can upload the installation package of "CentOS7.5" on the management server, and the management server can send the installation package of "CentOS7.5" to the business servers 1-3 together with the configuration item "operating system version" and the configuration parameter "CentOS7.5".
Example three:
the management server has a preset model library. The preset model library comprises 2 submodels, namely a submodel 1 and a submodel 2. Sub-model 1 and sub-model 2 each include configuration items and configuration parameters of the firmware. And the submodels in the preset model library have corresponding relations with the firmware identifications. If the firmware identification can be a version number of the firmware. For example, the version number of the firmware may be 0.0.1, 0.0.2, etc. The correspondence between the sub-models in the pre-set model library and the firmware identifications is shown in table 12 below.
TABLE 12
Firmware version number Sub-model
0.0.1 Submodel 1
0.0.2 Submodel 2
The management server can acquire the firmware version number of the business servers 1-3 when the business servers 1-3 are powered on. The management server obtains the firmware version number of the business servers 1-3 as 0.0.1. The management server obtains the submodel 1 corresponding to "0.0.1" as the submodel included in the first submodel set of the service servers 1-3 according to the corresponding relationship shown in the table 11. Of course, if there are submodels corresponding to other types of components in the preset model library, the management server may determine the second submodel set corresponding to the firmware, and then determine the submodel 1 corresponding to "0.0.1" from the second submodel set.
The management server may output the configuration items and configuration parameters in the sub-model 1 for the user to select. For example, the configuration item included in the sub model 1 is "firmware version", and the configuration parameters are "0.0.2", "0.0.3", "0.0.4". If the user selects the configuration parameter '0.0.4' and selects to upgrade the firmware of the service servers 1 to 3, the management server sends the configuration item 'firmware version' and the configuration parameter '0.0.4' to the service servers 1 to 3, so that the service servers 1 to 3 upgrade the firmware version to '0.0.4'. Alternatively, the user may upload the installation package of "0.0.4" on the management server, and the management server may send the installation package of "0.0.4" to the business servers 1-3 along with the configuration item "firmware version" and configuration parameters "0.0.4".
A device management method provided in an embodiment of the present invention is described in detail above with reference to fig. 1 to 5, and a management server provided in an embodiment of the present invention is described below with reference to fig. 6 to 7.
Referring to fig. 6, fig. 6 is a management server according to an embodiment of the present invention. The management server is deployed in an equipment management system, the equipment management system further comprises at least one service server, the management server is used for managing the at least one service server, a preset model library is arranged in the management server, the preset model library comprises at least one sub-model, each sub-model comprises configuration items and configuration parameters of components, and the management server comprises: a communication module 601 and a processing module 602. Wherein:
a communication module 601, configured to obtain a component identifier of a component in each service server in at least one service server; a processing module 602, configured to determine a first sub-model set in a preset model library according to a component identifier of a first service server, where the first service server is any one of at least one service server, and the first sub-model set includes at least one sub-model corresponding to the component identifier of the first service server; the communication module 601 is further configured to send first configuration information to the first service server, where the first configuration information carries at least one configuration item and configuration parameters in the first submodel set, so that the first service server configures the configuration parameters of the configuration item of the at least one component to be configured according to the first configuration information.
Optionally, the communication module 601 is further configured to, when the preset model library does not have a sub-model corresponding to the identifier of the first component, obtain a configuration item and a configuration parameter of the first component from the first service server, where the first component is any one of components of the first service server; the processing module 602 is further configured to add a first sub-model in the preset model library according to the configuration item and the configuration parameter of the first component, where the first sub-model includes the configuration item and the configuration parameter of the first component.
Optionally, the communication module 601 is specifically configured to: when detecting that at least one service server is electrified, acquiring the identifier of a component in each service server in the at least one service server; alternatively, the identification of the components in each of the at least one service server is periodically obtained.
Optionally, the processing module 602 is specifically configured to: determining at least one second submodel set corresponding to at least one component type of the first service server in a preset model library, wherein each second submodel set comprises submodels corresponding to components in the same type, and the component type is used for indicating component classification information to which the components of the first service server belong; a first set of submodels is determined from at least one second set of submodels based on at least one component identification of the first service server.
Optionally, the processing module 602 is further configured to select at least one configuration item and configuration parameter in the first sub-model set as the configuration item and configuration parameter included in the first configuration information before the communication module 601 sends the first configuration information to the first service server.
Optionally, the submodel of the first submodel set further includes preset display rules of configuration items and configuration parameters; the processing module 602 is further configured to, before the processing module 602 selects at least one configuration item and configuration parameter in the first sub-model set as the configuration item and configuration parameter included in the first configuration information, display the configuration item and configuration parameter in the first sub-model set according to a preset display rule in the first sub-model set.
It should be understood that the management server according to the embodiment of the present invention may be implemented by an application-specific integrated circuit (ASIC), or a Programmable Logic Device (PLD), which may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. When the implementation method of device management shown in fig. 2 and 3 can also be implemented by software, the management server and each module thereof may also be a software module.
The management server according to the embodiment of the present invention may correspond to perform the method described in the embodiment of the present invention, and the above and other operations and/or functions of each unit in the management server are respectively to implement corresponding flows of each method in fig. 2 and fig. 3, and are not described herein again for brevity.
It can be seen that the management server described in fig. 6 can dynamically obtain the configuration items and configuration parameters of the service server, so that the configuration items of the components of the service server can be subsequently parameter configured. Therefore, when the component of the service server is changed, the management server can dynamically acquire the latest configuration item and configuration parameter of the service server without updating the management software, which is beneficial to quickly configure the parameter of the configuration item of the component of the service server, and improves the maintenance efficiency of the operation and maintenance mode of the server. And different business servers may have partially same components, and a plurality of business servers can multiplex the same submodel, which is beneficial to saving development cost.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a management server according to an embodiment of the present disclosure. As shown in fig. 7, the management server 700 includes a processor 701, a memory 702, and a communication interface 703. The processor 701, the memory 702, and the communication interface 703 are connected by a bus.
The processor 701 may be a Central Processing Unit (CPU), a general purpose processor, a coprocessor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The processor 701 may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of DSPs and microprocessors, or the like.
The memory 702, may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct bus RAM (DR RAM).
The bus may include a power bus, a control bus, a status signal bus, and the like, in addition to the data bus. The communication interface 703 is used to implement communication with a service server.
The processor 701 calls the program code stored in the memory 702 to execute the steps executed by the management server in the above method embodiment.
It should be understood that the management server 700 according to the embodiment of the present invention may correspond to the management server shown in fig. 6 in the embodiment of the present invention, and may correspond to an operation step of executing, as an execution subject, a corresponding management server in the methods for implementing device management according to the embodiments of fig. 2 and fig. 3, and the foregoing and other operations and/or functions of each module in the management server 700 are respectively for implementing corresponding flows of each method in fig. 2 to fig. 3, and are not described again for brevity.
It can be seen that the management server described in fig. 7 can dynamically obtain the configuration items and configuration parameters of the service server, so that the configuration items of the components of the service server can be subsequently parameter configured. Therefore, when the component of the service server is changed, the management server can dynamically acquire the latest configuration item and configuration parameter of the service server without updating the management software, which is beneficial to quickly configure the parameter of the configuration item of the component of the service server, and improves the maintenance efficiency of the operation and maintenance mode of the server. And different business servers may have partially same components, and a plurality of business servers can multiplex the same sub-model, which is beneficial to saving development cost.
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded or executed on a computer, cause the flow or functions according to embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a Solid State Drive (SSD).
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (8)

1. A device management method is applied to a device management system, the device management system comprises a management server and at least one business server, the management server is used for managing the at least one business server, the management server is provided with a preset model library, the preset model library comprises at least one sub-model, each sub-model comprises configuration items and configuration parameters of components, and the method comprises the following steps:
the management server acquires the component identifier of each component in each service server in the at least one service server;
the management server determines a first sub-model set in a preset model library according to the part identification of a first service server, wherein the first service server is one of the at least one service server, and the first sub-model set comprises at least one sub-model corresponding to the part identification of the first service server;
the management server selects at least one configuration item and configuration parameters in the first sub-model set;
the management server sends first configuration information to the first service server, wherein the first configuration information carries the at least one configuration item and configuration parameters selected from the first submodel set so as to indicate the first service server to configure the configuration parameters of the configuration item of at least one component to be configured according to the first configuration information;
the method for determining the first sub-model set in the preset model library by the management server according to the component identifier of the first service server comprises the following steps:
the management server determines at least one second submodel set corresponding to at least one component type of the first business server in the preset model library, wherein each second submodel set comprises submodels corresponding to components of the same type, and the component type is used for indicating component classification information to which the components of the first business server belong;
the management server determines the first set of submodels from the at least one second set of submodels based on at least one component identification of the first service server.
2. The method of claim 1, further comprising:
when the sub-model corresponding to the identifier of the first component does not exist in the preset model library, the management server acquires the configuration item and the configuration parameter of the first component from the first service server, wherein the first component is any one of the components of the first service server;
and the management server adds a first sub-model in the preset model library according to the configuration item and the configuration parameter of the first component, wherein the first sub-model comprises the configuration item and the configuration parameter of the first component.
3. The method of claim 1 or 2, wherein the acquiring, by the management server, the identification of the component in each of the at least one service server comprises:
when the management server detects that the at least one service server is powered on, acquiring the identifier of a component in each service server in the at least one service server; alternatively, the first and second electrodes may be,
the management server periodically obtains the identification of the components in each of the at least one service server.
4. The method according to claim 1 or 2, characterized in that the submodels of the first set of submodels further comprise preset display rules for configuration items and configuration parameters;
before the management server selects at least one configuration item and configuration parameters in the first set of submodels, the method further comprises:
and displaying the configuration items and the configuration parameters in the first submodel set according to preset display rules in the first submodel set.
5. A management server is deployed in a device management system, the device management system further includes at least one service server, the management server is configured to manage the at least one service server, the management server has a preset model library, the preset model library includes at least one sub-model, each sub-model includes configuration items and configuration parameters of components, and the management server includes:
the communication module is used for acquiring the component identifier of each service server in the at least one service server;
the processing module is used for determining a first sub-model set in a preset model library according to the component identification of a first service server, wherein the first service server is one service server in the at least one service server, and the first sub-model set comprises at least one sub-model corresponding to the component identification of the first service server;
the processing module is further used for selecting at least one configuration item and configuration parameters in the first submodel set;
the communication module is further configured to send first configuration information to the first service server, where the first configuration information carries the at least one configuration item and the configuration parameter selected from the first submodel set, so as to instruct the first service server to configure the configuration parameter of the configuration item of the at least one component to be configured according to the first configuration information;
the processing module is specifically configured to:
determining at least one second submodel set corresponding to at least one component category of the first service server in the preset model library, wherein each second submodel set comprises submodels corresponding to components in the same category, and the component category is used for indicating component classification information to which the components of the first service server belong;
determining the first set of submodels from the at least one second set of submodels based on at least one component identification of the first traffic server.
6. The management server according to claim 5,
the communication module is further configured to, when a sub-model corresponding to the identifier of the first component does not exist in the preset model library, obtain a configuration item and a configuration parameter of the first component from the first service server, where the first component is any one of components of the first service server;
the processing module is further configured to add a first sub-model in the preset model library according to the configuration item and the configuration parameter of the first component, where the first sub-model includes the configuration item and the configuration parameter of the first component.
7. The management server according to claim 5 or 6, wherein the communication module is specifically configured to:
when detecting that the at least one service server is powered on, acquiring the identifier of the component in each service server in the at least one service server; alternatively, the first and second electrodes may be,
periodically obtaining an identification of the component in each of the at least one service server.
8. The management server according to claim 5 or 6, wherein the submodel of the first submodel set further comprises preset display rules of configuration items and configuration parameters;
the processing module is further configured to display the configuration items and the configuration parameters in the first sub-model set according to preset display rules in the first sub-model set before the processing module selects at least one configuration item and configuration parameters in the first sub-model set.
CN201810506587.1A 2018-05-24 2018-05-24 Equipment management method and management server Active CN108898230B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201810506587.1A CN108898230B (en) 2018-05-24 2018-05-24 Equipment management method and management server
CN202210800994.XA CN115204423A (en) 2018-05-24 2018-05-24 Equipment management method and management server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810506587.1A CN108898230B (en) 2018-05-24 2018-05-24 Equipment management method and management server

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202210800994.XA Division CN115204423A (en) 2018-05-24 2018-05-24 Equipment management method and management server

Publications (2)

Publication Number Publication Date
CN108898230A CN108898230A (en) 2018-11-27
CN108898230B true CN108898230B (en) 2022-08-16

Family

ID=64343199

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202210800994.XA Pending CN115204423A (en) 2018-05-24 2018-05-24 Equipment management method and management server
CN201810506587.1A Active CN108898230B (en) 2018-05-24 2018-05-24 Equipment management method and management server

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202210800994.XA Pending CN115204423A (en) 2018-05-24 2018-05-24 Equipment management method and management server

Country Status (1)

Country Link
CN (2) CN115204423A (en)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109660391B (en) * 2018-12-10 2022-03-08 浪潮电子信息产业股份有限公司 Method, system and related device for upgrading firmware of pooling server system
TWI736842B (en) * 2019-02-18 2021-08-21 緯創資通股份有限公司 Method for controlling setup configuration and related computer system
CN111061498B (en) * 2019-12-25 2024-03-15 上海众源网络有限公司 Configuration information management system
CN111585794B (en) * 2020-04-20 2023-03-31 南京南瑞继保电气有限公司 Communication method, device and system based on acquisition board card and storage medium
CN111600749B (en) * 2020-04-29 2023-01-24 厦门市美亚柏科信息股份有限公司 Method and system for managing multiple servers and computer storage medium
CN112052029B (en) * 2020-08-20 2022-08-12 厦门亿联网络技术股份有限公司 Configuration method and system of USB device management software and computer device
CN112152841B (en) * 2020-09-03 2023-06-20 锐捷网络股份有限公司 Verification method, verification device, switch, equipment and storage medium
CN112114885B (en) * 2020-09-15 2024-05-10 青岛海信移动通信技术有限公司 Terminal, control equipment and service processing method
CN113076350B (en) * 2021-03-02 2024-05-07 无锡先导智能装备股份有限公司 Welding abnormality detection method, welding abnormality detection device, computer device, and storage medium
CN113342420A (en) * 2021-06-28 2021-09-03 杭州涂鸦信息技术有限公司 Firmware configuration method, device, equipment and storage medium
CN114360137A (en) * 2021-11-30 2022-04-15 浙江朱道模块集成有限公司 Information acquisition automatic guide system for hospital
CN114760314A (en) * 2022-04-06 2022-07-15 中国工商银行股份有限公司 Server management method, device, computer equipment and storage medium

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103201723A (en) * 2012-08-03 2013-07-10 华为技术有限公司 Memory configuration method and memory configuration management server
CN104503798A (en) * 2014-12-29 2015-04-08 杭州华三通信技术有限公司 Method and device for configuring server
WO2015081908A3 (en) * 2013-12-04 2015-07-23 腾讯科技（深圳）有限公司 Method, device, and system for updating parameter value
CN107046560A (en) * 2016-12-27 2017-08-15 郑州云海信息技术有限公司 A kind of computer system configurations centralized management system and method
CN107341025A (en) * 2016-05-03 2017-11-10 北京京东尚科信息技术有限公司 Using update method and device
CN107391193A (en) * 2017-07-21 2017-11-24 郑州云海信息技术有限公司 A kind of client, the system and method for configuration server
CN107733708A (en) * 2017-10-16 2018-02-23 平安科技（深圳）有限公司 Device parameter collocation method, device, computer equipment and storage medium
CN107807789A (en) * 2017-09-29 2018-03-16 曙光信息产业(北京)有限公司 Configure RAID method, apparatus and server

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103201723A (en) * 2012-08-03 2013-07-10 华为技术有限公司 Memory configuration method and memory configuration management server
WO2015081908A3 (en) * 2013-12-04 2015-07-23 腾讯科技（深圳）有限公司 Method, device, and system for updating parameter value
CN104503798A (en) * 2014-12-29 2015-04-08 杭州华三通信技术有限公司 Method and device for configuring server
CN107341025A (en) * 2016-05-03 2017-11-10 北京京东尚科信息技术有限公司 Using update method and device
CN107046560A (en) * 2016-12-27 2017-08-15 郑州云海信息技术有限公司 A kind of computer system configurations centralized management system and method
CN107391193A (en) * 2017-07-21 2017-11-24 郑州云海信息技术有限公司 A kind of client, the system and method for configuration server
CN107807789A (en) * 2017-09-29 2018-03-16 曙光信息产业(北京)有限公司 Configure RAID method, apparatus and server
CN107733708A (en) * 2017-10-16 2018-02-23 平安科技（深圳）有限公司 Device parameter collocation method, device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN108898230A (en) 2018-11-27
CN115204423A (en) 2022-10-18

Similar Documents

Publication Publication Date Title
CN108898230B (en) Equipment management method and management server
US10102035B2 (en) Techniques for computing resource discovery and management in a data center
CN105745617B (en) Selective power management for pre-boot firmware updates
US10268628B2 (en) Method for extracting BIOS attributes for BIOS management and system therefor
JP2016058083A (en) System and method for managing plurality of bios default setting
US8578360B1 (en) Dynamically updating a computer system and firmware image utilizing an option read only memory (OPROM) data structure
US9965288B2 (en) Preconfiguring hardware and speeding up server discovery prior to bios boot
CN115605844A (en) Microcode (microcode) hot upgrading method for bare computer cloud deployment
US11630660B2 (en) Firmware management
US10579801B2 (en) Selecting and loading firmware volumes based on license
US11847441B2 (en) Secure and flexible pipeline management tool
US10146551B2 (en) Initializing and reconfiguring replacement motherboards
JP2018519556A (en) System and method for provisioning cloud services across heterogeneous computing environments
CN110119623A (en) A kind of credible main board implementation method for realizing that firmware is actively measured using TPCM
CN106873970A (en) The installation method and device of a kind of operating system
CN111159090B (en) Information processing method and device and electronic equipment
US11113070B1 (en) Automated identification and disablement of system devices in a computing system
US8959191B2 (en) Script modification suggestion
US10540151B1 (en) Graphical customization of a firmware-provided user interface (UI)
CN110119625A (en) A kind of trusted computing method
US20230097733A1 (en) Methods and systems to automatically deploy vulnerability fixes for software and firmware components
US11093256B2 (en) System and method for dynamically installing driver dependencies
CN113703805A (en) Upgrading method, system, terminal and storage medium of arm64 architecture virtualization system
CN112328288A (en) Method, system, equipment and storage medium for updating server component
CN110119624A (en) A kind of security measure method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20211228

Address after: 450046 Floor 9, building 1, Zhengshang Boya Plaza, Longzihu wisdom Island, Zhengdong New Area, Zhengzhou City, Henan Province

Applicant after: Super fusion Digital Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Applicant before: HUAWEI TECHNOLOGIES Co.,Ltd.

GR01 Patent grant
GR01 Patent grant