TW201328246A - Method and system for managing cloud server system - Google Patents

Abstract

A method and a system for managing a cloud server system are provided. The cloud server system comprises a management server and a plurality of nodes, and an electronic apparatus is configured in each of nodes. A network address is assigned to a micro-controller according to the hardware address of the micro-controller received from the electronic apparatus through the management server. And a command is transmitted to the micro-controller through the management server so as to obtain a node related information of the electronic apparatus. Accordingly, the management server may manage the electronic apparatus based on the node related information.

Description

Cloud server system management method and management system

The present invention relates to a cloud server system, and more particularly to a cloud server system management method and management system.

At present, the server is widely used by various enterprises. The development scope is not only combined with the application of the internet and the telecom industry, but also deepens into the lives of ordinary people, such as finance, finance, online banking, and the Internet. The use of credit cards, etc., all rely on the powerful computing power of the server to achieve a high degree of confidentiality and difficulty in being cracked.

There are many types of cloud-based servo systems today. The more common ones are rack servers and tower servers. Among them, the rack server is an optimized structure of the tower server, which is designed to minimize space occupation. Many professional network devices are rack-mounted (such as switches, routers, hardware firewalls, etc.), which are mostly flat, just like drawers. In general, the rack server has a width of 19 inches and a height in U (1U = 1.75 inches = 44.45 mm). There are usually 1U, 2U, 3U, 4U, 5U, 7U standard servers.

After assembling the cloud servo system, it is necessary to deploy the operating system to the cloud servo system. Before deploying the cloud operating system, you need to know the information about all the nodes on the container, including the physical layout of the cabinet, in order to deploy the cloud operating system. Currently, manual information is manually entered for each node. However, this method can be used in a small number of nodes. Once the number of nodes is quite large (for example, more than 500 nodes), the hand motion method is very inefficient and error-prone.

The invention provides a management method and a management system for a cloud server system, which automatically finds node-related information of each node on a container, so that the cloud operation system can be automatically deployed to the cabinet.

Specifically, the present invention provides a management method of a cloud server system, which is adapted to manage a cloud server system through a management server. Here, the cloud servo system includes a plurality of nodes, each node is provided with an electronic device, and the electronic device includes a central processing unit and a microcontroller. In this management method, after the management server receives the hardware address of the microcontroller from the electronic device, the network address is assigned to the microcontroller of the electronic device. Also, the management server sends instructions to the microcontroller based on the network address. When the microcontroller receives the above instruction, the central processing unit is restarted to obtain node related information of the electronic device through the microcontroller during the restarting process. The microcontroller responds to the above instructions and transmits the node related information to the management server, so that the management server manages the electronic device according to the node related information.

In an embodiment of the invention, when the microcontroller receives the above instruction, the central processing unit is rebooted to the command interface shell through the firmware. In the process of rebooting to the command interface shell, the dynamic information in the node related information can be dynamically obtained through the firmware. Moreover, the system manages the firmware structure to obtain static information in the node related information. After that, the node related information is transmitted to the microcontroller.

In an embodiment of the present invention, the node related information includes processor information, network card information, memory information, hard disk information, node location, node height information, node method information, node type information, and firmware information. And at least one of the microcontroller information.

In an embodiment of the present invention, after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the management server may further learn, according to the node related information, that the electronic device is located in the cloud servo system. The location of the node is used to obtain the position order of the electronic device in the cloud servo system. Also, the microcontroller and the network address of the system NIC are reassigned according to the location order.

In an embodiment of the present invention, after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the management server may determine the deployment of the electronic device according to the node related information. Service, and transfer node related information to the cloud deployment program for deployment of the cloud operating system.

In another aspect, the present invention provides a management system for managing a cloud servo system through a management server. The cloud servo system includes a cabinet, the switch includes a switch and a plurality of nodes, and each node is provided with an electronic device. The electronic device includes a central processing unit and a microcontroller, and the central processing unit is coupled to the microcontroller. The management server is coupled to the switch to manage the cloud servo system through the switch. The management server receives the hardware address of the microcontroller from the electronic device to allocate the network address to the microcontroller of the electronic device, and the management server transmits the instruction to the microcontroller according to the network address. In addition, when the microcontroller receives the above instruction, the central processing unit is restarted to obtain node related information of the electronic device through the microcontroller during the restarting process, and the microcontroller responds to the above instruction. The node related information is transmitted to the management server, so that the management server manages the electronic device according to the node related information.

In an embodiment of the present invention, the cabinet includes r racks, each rack includes a rack number module and s slots; each slot includes a slot numbering module and n nodes; Each node includes a node numbering module. The above r, s and n are positive integers greater than or equal to 1. The slot i includes an expander coupled to the node number module of each of the n nodes in the slot i, the slot number module of the slot i, and the rack number of the rack where the slot i is located. The module enables the electronic device disposed in each node to know the location of the node where it is located through the expander. The above i is 1~s.

In an embodiment of the invention, the electronic device further includes a control wafer and a firmware wafer. The control chip is coupled to the central processing unit and the microcontroller. The firmware wafer stores a firmware that is coupled to the control wafer. Wherein, when the microcontroller receives the instruction, the central processing unit is rebooted to the instruction interface shell through the firmware, and in the process of rebooting to the instruction interface shell, the firmware obtains node related information and correlates the node. Information is transferred to the microcontroller.

In an embodiment of the present invention, the management server learns that the electronic device is located at a node position in the cabinet according to the information about the node, and obtains the position sequence of the electronic device in the cabinet, and redistributes the microcontroller according to the position sequence. And the network address of the system network card of the electronic device.

Based on the above, the present invention acquires node-related information of the electronic device through the microcontroller of the electronic device disposed in each node, and transmits the information to the management server, thereby automatically finding the node-related information of each node on the cabinet. In order to automatically deploy the cloud operating system to this cabinet.

The above described features and advantages of the present invention will be more apparent from the following description.

First embodiment

1 is a block diagram of a management system in accordance with a first embodiment of the present invention. Referring to FIG. 1 , the management system 100 includes a management server 110 and a cloud server system 120 . The cloud servo system 120 includes nodes 130_1~130_N, and each node is provided with an electronic device. Here, taking the electronic device 140 of the node 130_1 as an example, the electronic device 140 includes a central processing unit 141 and a microcontroller 143. The central processing unit 141 is coupled to the microcontroller 143. In addition, the electronic devices of the nodes 130_2 to 130_N are similar to the electronic device 140 described above, and have a central processing unit and a microcontroller.

The management server 110 is configured to manage the electronic devices disposed in the node 130_1~the node 130_N in the cloud server system 120. For example, the management server 110 can obtain the node related information from the electronic devices of the node 130_1~the node 130_N to manage the nodes 130_1~130_N, and further deploy the operating system to the cloud servo system 120.

Further, the cloud servo system 120 includes at least one container, and the rack includes a plurality of racks, each of which includes a plurality of slots, each of which includes a plurality of nodes. Moreover, a switch is disposed in the cabinet, and the switch is coupled to the electronic devices disposed in the respective nodes, so that the management server 110 manages the electronic devices through the switch.

The management method of the cloud servo system 120 will be described below with the above management system 100. 2 is a flow chart of a method for managing a cloud server system according to a first embodiment of the present invention. For convenience of description, in the embodiment, the electronic device 140 of the node 130_1 is taken as an example, and the operations of the other nodes 130_2 to 130_N are also the same as those of the node 130_1, and therefore will not be described in detail herein.

Referring to FIG. 1 and FIG. 2 simultaneously, in step S205, the management server 110 receives the hardware address of the microcontroller 143 from the electronic device 140 to allocate the network address to the microcontroller 143 of the electronic device 140. Specifically, the management server 110 has a Dynamic Host Configuration Protocol (DHCP) Servo (Server) function. When the hardware address of the microcontroller 143 of the electronic device 140 is received, an automatic assignment is automatically assigned. The network address is given to the microcontroller 143. At the same time, the hardware address and the network address are recorded in the management server 110. Here, the hardware address is, for example, a Media Access Control (MAC) address, and the network address is, for example, an Internet Protocol (IP) address.

Next, in step S210, the management server 110 transmits an instruction to the microcontroller 143 according to the network address to request the microcontroller 143 to obtain the node related information. The above instructions are, for example, an OEM (Original Equipment Manufacturer) instruction of the Intelligent Platform Management Interface.

In step S215, when the microcontroller 143 receives the above instruction, the central processing unit 141 is turned back on to obtain the node related information of the electronic device 140 through the microcontroller 143 during the reboot. The node related information includes at least one of processor information, network card information, memory information, hard disk information, node position, node height information, node setting information, node type information, firmware information, and microcontroller information.

The above processor information includes the processor model and frequency. Network card information includes bandwidth and MAC address. Memory information includes the number and capacity of memory modules. Hard disk information includes carrier number, hard disk type, hard disk capacity, Revolution Per Minute (RPM), and hard disk cache capacity. The node location includes the rack number, slot number, and node number. Node height information is in U (1U = 1.75 inches = 44.45 mm), usually 1U, 2U, 3U, 4U, 5U, 7U standards. Node-based information includes vertical placement or horizontal placement. The node type information is used to indicate that the node belongs to a service resource pool, a computing resource pool, or a storage pool. The firmware information includes the system firmware version number. The microcontroller information includes the firmware version number of the microcontroller.

The above processor information, network card information, memory information, hard disk information, and node location are dynamically obtained. In other words, it is obtained by the firmware when performing Power On Test Self (POST). Here, the firmware is, for example, a Basic Input Output System (BIOS). Node height information, node-based information, node type information, and firmware information are static data, such as written in the SMBIOS (System Management BIOS) structure, which is also obtained through the BIOS. In addition, the microcontroller information is static data, which is stored in the microcontroller 143, which is obtained through the microcontroller 143.

In detail, the central processing unit 141 is rebooted to an instruction interface shell. Here, the command interface shell is, for example, an Extensible Firmware Interface (EFI) shell, which is a console for launching an application, loading EFI protocols and device drivers, and executing simple code. interface. According to this, when the BIOS performs the boot self-test, the BIOS dynamically obtains the dynamic information in the node-related information, and obtains the static information in the node-related information through the SMBIOS, and then transmits the static information to the microcontroller 143.

Thereafter, in step S220, the microcontroller 143 responds to the above command and transmits node related information to the management server 110. Accordingly, the management server 110 can manage the electronic device 140 in accordance with the node related information.

The method for obtaining the node related information of the other nodes 130_2 to 130_N is the same as described above. That is to say, the management server 110 allocates a network address according to the hardware address of the microcontroller of each node. After that, an IPMI OEM command is issued according to the network address, so that the electronic devices of each node are booted to the EFI shell to obtain node-related information through firmware such as BIOS on the way to booting to the EFI shell. Transfer to the microcontroller. Thereafter, the microcontroller transmits node-related information of each node to the management server 110.

Second embodiment

3 is a block diagram of a management system architecture in accordance with a second embodiment of the present invention. In the present embodiment, ten nodes are listed for explanation. Referring to FIG. 3, in the management system 300, the cabinet 320 is managed by the management server 310. The cabinet 320 includes a switch 321, a rack 323, and a rack 325. The rack numbers of the rack 323 and the rack 325 are 0 and 1, respectively.

Rack 323 includes slot 330 having node 331 and node 333; slot 340 having node 341 and node 343; slot 350 having node 351 and node 353; and slot 360 having node 361. The slot numbers of the slots 330, 340, 350, and 360 are 0 to 3, respectively. Rack 325 includes a slot 370 having a node 371 and a node 373; and a slot 380 having a node 381.

An electronic device is disposed in each of the above nodes. The switch 321 is coupled to each electronic device, such as a system network card coupled to each electronic device, or a network card coupled to a microcontroller of each electronic device.

The components of the electronic device are exemplified below. 4 is a block diagram of an electronic device in accordance with a second embodiment of the present invention. In this embodiment, the microcontroller is, for example, a substrate management controller (hereinafter referred to as BMC), and the firmware chip is, for example, a BIOS chip that stores a BIOS.

Referring to FIG. 4, it is assumed here that the electronic device 400 is disposed in the node 331. The electronic device 400 includes a central processing unit 410, a control chip 420, a BIOS chip 430, a BMC 440, a memory module 450, a node number module 460, and a system network card 470. The BMC 440 also includes a BMC network card 441 and a storage space 442. The storage space 442 is, for example, a Non-Volatile Random Access Memory (NVRAM). The central processing unit 410 is coupled to the memory module 450 and coupled to the BIOS chip 430, the BMC 440, the node number module 460, and the system network card 470 through the control chip 420. Here, please refer to FIG. 3 and FIG. 4 at the same time, the switch 321 is coupled to the system network card 470 and the BMC network card 441.

The central processing unit 410 is configured to execute data in the hardware, the firmware, and the processing software in the electronic device 400. Control chip 420 is a bridge for external processing of central processing unit 410. In the present embodiment, the control wafer 420 includes a north bridge wafer and a south bridge wafer. In other embodiments, the control wafer 420 is, for example, a south bridge wafer, and the north bridge wafer can be integrated with the central processing unit 410.

The memory module 450 is, for example, a dual in-line memory module (DIMM). The node number module 460 is used to store the node number where the electronic device 400 is located. In addition, a register is provided in the control wafer 420 to store the rack number, the slot number, and the node number. For example, set up three scratchpads to store. The BIOS or BMC 440 can control the wafer 420 from the control chip 420 to obtain the node position of the electronic device 400 in the cabinet.

Let's take another example to show how to get the node location. Figure 5 is a block diagram of a rack architecture in accordance with a second embodiment of the present invention. In the embodiment, the rack 323 of the management system 300 is taken as an example. Referring to FIG. 5, the rack 323 includes a rack number module 510 for storing the rack number. In this embodiment, the rack number stored in the rack number module 510 is 0.

The slot 330 includes an expander 520 and a slot number module 530. The electronic device 400 is provided in the node 331 and the electronic device 550 is provided in the node 333. Here, only some of the components of the electronic device 400 are illustrated, and the components of the electronic device 550 are similar to the electronic device 400, and only some of the components are illustrated for convenience of explanation.

In the slot 330, the expander 520 is coupled to the rack number module 510, the slot number module 530, the control chip 420 of the electronic device 400, and the control chip 551 of the electronic device 550. In the node 331, the control chip 420 of the electronic device 400 acquires the rack number 0 and the slot number 0 where the electronic device 400 is located through the expander 520, and the node number module 460 knows that the node number where it is located is 0. In addition, in the node 333, the control chip 551 of the electronic device 550 also obtains the rack number 0 and the slot number 0 where the electronic device 550 is located through the expander 520, and the node number of the node number 553 is known by the node number module 553. Is 1.

Assume that the node position is represented by (r, s, n), r represents the rack number, s represents the slot number, and n represents the node number. Accordingly, the node position of the electronic device 400 is (0, 0, 0), and the node position of the electronic device 550 is (0, 0, 1). By analogy, the node location is stored in the register of the control chip of the electronic device disposed in each node, so that the BIOS or BMC can obtain the node location. Accordingly, each of the electronic devices utilizes its control chip, and in conjunction with the expander 520, the node position of each electronic device, that is, the physical position in the cabinet, can be obtained.

Here, the expander 520 is coupled to the rack number module 510 and the slot number module 530 via a General Purpose Input (GPI) interface, and through an internal integrated circuit (Inter-Integrated Circuit, I ² C). The bus bar is coupled to the control wafer 420 of the electronic device 400 and the control wafer 551 of the electronic device 550. In addition, the control chip 420 and the control chip 551 are also coupled to the node number module 460 and the node number module 553 via the GPI interface, for example. That is to say, the numbers in the rack number module 510, the slot number module 530, the node number module 460, and the node number module 553 can be obtained through the GPI interface.

Further steps to manage the cloud servo system are described below. 6 is a flow chart of a method for managing a cloud server system according to a second embodiment of the present invention. Referring to FIG. 3, FIG. 4 and FIG. 6, in the embodiment, it is assumed that each node in the cabinet 320 is provided with an electronic device 400.

In step S605, it is determined whether the power of the cabinet 320 is turned off. If it is not closed, step S610 is executed to turn off the power of the cabinet 320, and then step S615 is performed to turn on the power. And if the power is off, step S615 is performed. Turn on the power and restart the BMC 440 of all nodes. The purpose of powering down and re-powering is to have the BMC 440 re-execute its initial code and send the MAC address. That is to say, the BMC 440 broadcasts the MAC address of its BMC network card 441 after power-off and power-on.

Next, in step S620, the management server 310 receives the MAC address of the BMC 440 from the electronic device 400, and assigns an IP address to the MAC address. Moreover, the management server 310 also records the MAC address and its corresponding IP address.

For example, FIG. 7A is a schematic diagram of a MAC address table in accordance with a second embodiment of the present invention. 7B is a schematic diagram of a MAC address and an IP address table in accordance with a second embodiment of the present invention. This embodiment takes the 10 nodes of FIG. 3 as an example. That is, the table 710 of FIG. 7A records the MAC addresses transmitted by the nodes 331, 333, 341, 343, 351, 353, 361, 371, 373, 381. In addition, when the management server 310 assigns an IP address to each MAC address, it is recorded in the table 720 of FIG. 7B.

Returning to Figure 6, after assigning the IP address, in step S625, the management server 310 can transmit an instruction (e.g., an IPMI OEM instruction) to the BMC 440 in accordance with the IP address to request the BMC 440 to obtain node related information. Thereafter, in step S630, when the BMC 440 receives the instruction, the BMC 440 will reboot the central processing unit 410 to the EFI shell. Accordingly, in the process of rebooting to the EFI shell, steps S635 to S645 can be performed. In step S635, the dynamic information in the node related information is obtained through the BIOS. Dynamic information includes processor information, network card information (MAC address of system network card 470), memory information, hard disk information, and node location. It should be noted that the node position can also be obtained by the BMC 440 from the register of the control chip 420, and the method of obtaining the node position is shown in FIG. 5.

In addition, in step S640, the static information in the node related information is obtained through the SMBIOS structure, including node height information, node setting information, node type information, and firmware information.

Then, in step S645, the BIOS transmits the node related information to the BMC 440. For example, it is transferred to the storage space 442 of the BMC 440. In addition, the BMC 440 can also obtain its own BMC information (such as the BMC firmware version number and the bandwidth of the BMC network card 441). Thereafter, in step S650, the BMC 440 responds to the above instruction and transmits the node related information to the management server 310. The management server 310 configures its IP address for the MAC address of the system network card 470 of the obtained node related information. Of course, when the cloud OS deployment is performed, the system network card 470 is booted through the network (Network Boot). It will get this IP address. Furthermore, the cloud operating system installation is achieved through the network boot mechanism.

8A and 8B are schematic diagrams of a node related information table in accordance with a second embodiment of the present invention. When the management server 310 receives the node related information of each node in the cloud servo system 320, it is recorded in the table 800 of FIGS. 8A and 8B. Among them, Figure 8A records the information about the six-node node, and 8B records the information about the other four nodes. Here, it is assumed that the ten pieces of node related information recorded in the table 800 are taken from the nodes 331, 333, 341, 343, 351, 353, 361, 371, 373, 381 of FIG. 3, respectively. The table 800 includes nine fields, respectively recording the MAC address of the BMC network card, the IP address and bandwidth of the BMC network card, the MAC address of the system network card, the IP address and bandwidth of the system network card, processor information, and memory. Information, hard drive information, node location, and node type information.

In terms of the node related information of the node 331 and assuming that the electronic device 400 of FIG. 4 is disposed in the node 331, the MAC address of the BMC network card 441 is "00: A0: D1: EC: F8: B1", which is assigned The IP address of the BMC network card 441 is "10.1.0.1", and the bandwidth of the BMC network card 441 is 100 Mbps (bps=bits per second). The system NIC 470 of the node 331 has a MAC address of "00: A0: D1: EA: 34: E1", an IP address of "10.1.0.11", and a bandwidth of 1000 Mbps. In addition, the model of the central processing unit 410 of the node 331 is "Intel(R) Xeon(R) CPU E5540", and its frequency is "2530 MHz". The node 331 includes four memory modules 450, DIMM1~DIMM4, and each of the memory modules 450 has a capacity of 8G. In addition, the carrier number of the hard disk of the node 331 is 1, the hard disk type is SAS (Serial Attached SCSI, SCSI = Small Computer System Interface), the hard disk capacity is 1 TB, and the hard disk rotation speed is 7200 RPM (Revolution Per Minute) and the hard disk cache capacity is 16MB.

It should be noted that the management server 310 can also learn the location of each electronic device in the cloud servo system 320 according to the node related information, so as to obtain the position sequence of each electronic device in the cloud servo system. And, according to the location order, redistribute the BMC network card and the network address of the system network card.

For example, FIG. 9A and FIG. 9B are schematic diagrams of a node related information table after reallocating a network address according to a second embodiment of the present invention. Please refer to FIG. 9A and FIG. 9B, which are obtained by reassigning the BMC network card and the IP address of the system network card in FIG. 8A and FIG. 8B.

In addition, the management server 310 can also determine the service to be deployed by each electronic device according to the node related information, and transmit the node related information to the cloud deployment program for deployment of the cloud operating system.

For example, after deciding which service to deploy, a new field can be added to the node information related table to record the corresponding service type, as shown in FIG. FIG. 10 is a schematic diagram of a node related information table after determining a deployed service type according to a second embodiment of the present invention. Please refer to FIG. 10. FIG. 10 is obtained by adding a field in the table of FIG. 9A and FIG. 9B after deciding the type of service to be deployed. Only some of the fields are shown here to illustrate. Among them, the nodes 331, 333, 341, 343, 351, and 353 are used as a service resource pool. The service types of the node 331 are a physical installer, a physical manager, and a record management (LOG). The service type of the node 333 is virtual management (Virtual Manager) and an application programming interface (API). The service type of node 341 is virtual resource provisioning. The service type of node 343 is a database. The service type of the node 351 is a storage manager. The service type of node 353 is load balance and security.

In summary, the present invention acquires node-related information of an electronic device through a microcontroller of an electronic device disposed in each node, and transmits the information to the management server, thereby automatically finding a node of each node on the cabinet. Relevant information so that the cloud operating system can be automatically deployed to this cabinet.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.

100, 300. . . Management system

110, 310. . . Management server

120. . . Cloud server system

130_1~130_N, 331, 333, 341, 343, 351, 353, 361, 371, 373, 381. . . node

140, 400, 550. . . Electronic device

141, 410. . . Central processing unit

143. . . Microcontroller

320. . . Cabinet

321. . . switch

323, 325. . . frame

330, 340, 350, 360, 370, 380. . . Slot

420, 551. . . Control chip

430. . . BIOS chip

440. . . BMC

441. . . BMC network card

442. . . storage space

450. . . Memory module

460, 553. . . Node number module

470. . . System NIC

510. . . Rack number module

520. . . Expander

530. . . Slot number module

710, 720, 800. . . form

S205~S220. . . Each step of the management method of the first embodiment of the present invention

S605~S650. . . Steps of the management method of the second embodiment of the present invention

1 is a block diagram of a management system in accordance with a first embodiment of the present invention.

2 is a flow chart of a method for managing a cloud server system according to a first embodiment of the present invention.

3 is a block diagram of a management system architecture in accordance with a second embodiment of the present invention.

4 is a block diagram of an electronic device in accordance with a second embodiment of the present invention.

Figure 5 is a block diagram of a rack architecture in accordance with a second embodiment of the present invention.

6 is a flow chart of a method for managing a cloud server system according to a second embodiment of the present invention.

7A is a schematic diagram of a MAC address table in accordance with a second embodiment of the present invention.

7B is a schematic diagram of a MAC address and an IP address table in accordance with a second embodiment of the present invention.

8A and 8B are schematic diagrams of a node related information table in accordance with a second embodiment of the present invention.

9A and 9B are diagrams showing a node related information table after reallocating a network address according to a second embodiment of the present invention.

FIG. 10 is a schematic diagram of a node related information table after determining a deployed service type according to a second embodiment of the present invention.

S205~S220. . . Each step of the management method of the first embodiment of the present invention

Claims (10)

A cloud server system management method is adapted to manage the cloud server system through a management server, the cloud server system includes a plurality of nodes, each of the nodes is provided with an electronic device, and the electronic device includes a central processing unit and A microcontroller, wherein the management method of the cloud server system comprises: the management server receiving a hardware address of the microcontroller from the electronic device to allocate a network address to the micro control of the electronic device The management server transmits an instruction to the microcontroller according to the network address; when the microcontroller receives the instruction, the central processing unit is restarted to pass the reboot during the restarting process; The microcontroller obtains a node related information of the electronic device; and the microcontroller responds to the instruction, and transmits the node related information to the management server, so that the management server manages the electronic device according to the node related information. The method for managing a cloud server system according to claim 1, wherein when the microcontroller receives the command, the method further comprises: rebooting the central processing unit to an instruction through a firmware of the electronic device. Interface shell. The method for managing a cloud server system according to claim 2, wherein the step of obtaining information about the node through the microcontroller during the restarting process comprises: restarting the process to the shell of the command interface The dynamic information of the node is dynamically obtained through the firmware; the static information in the node related information is obtained through a system management firmware structure; and the node related information is transmitted to the microcontroller. The method for managing a cloud server system according to claim 1, wherein the node related information includes a processor information, a network card information, a memory information, a hard disk information, a node location, and a node. At least one of high information, one node setting information, one node type information, one firmware information, and one microcontroller information. The management method of the cloud server system according to claim 1, wherein after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the method further comprises: the management server The node related information is that the electronic device is located at a node position in the cloud servo system, to obtain a position sequence of the electronic device in the cloud servo system; and, according to the position sequence, reallocating the microcontroller and a The network address of the system NIC. The management method of the cloud server system according to claim 1, wherein after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the management server further comprises: The node related information determines the service to be deployed by the electronic device; and transmits the node related information to a cloud deployment program to perform deployment of an operating system. A management system, comprising: a cloud server system, comprising: a cabinet, comprising: a switch; a plurality of nodes, each of the nodes being provided with an electronic device, the electronic device comprising a central processing unit and a microcontroller, and The central processing unit is coupled to the microcontroller; and a management server coupled to the switch to manage the cloud servo system through the switch, wherein the management server receives the microcontroller from the electronic device a hardware address to assign a network address to the microcontroller of the electronic device, and the management server transmits an instruction to the microcontroller according to the network address; wherein, when the micro control When receiving the instruction, the central processing unit is restarted to obtain a node-related information of the electronic device through the microcontroller during the restarting process, and the microcontroller responds to the instruction. Transmitting the node related information to the management server, so that the management server manages the electronic device according to the node related information. The management system of claim 7, wherein the cabinet comprises r racks, each of the racks includes a rack number module and s slots, each of the slots including a plug a slot number module and n nodes, and each of the nodes includes a node number module, where r, s, and n are positive integers greater than or equal to 1, wherein the slot i includes: an expander, a node number module coupled to each of the n nodes in the slot i, a slot number module of the slot i, and a rack number module of the rack in which the slot i is located, so that each is set in each The electronic device in the nodes knows the location of a node where the expander is located, where i is 1~s. The management system of claim 7, wherein the electronic device further comprises: a control chip coupled to the central processing unit and the microcontroller; a firmware wafer storing a firmware, the firmware The chip is coupled to the control chip; wherein, when the microcontroller receives the command, the central processing unit is rebooted to an instruction interface shell through the firmware, and the process of rebooting to the command interface shell The node-related information is obtained by the firmware and the node-related information is transmitted to the microcontroller. The management system of claim 7, wherein the management server knows that the electronic device is located at a node in the cabinet according to the information about the node, to obtain a position of the electronic device in the cabinet. Sequence, and according to the positional order, redistribute the microcontroller and the network address of a system network card of the electronic device.