CN111565116A - Whole cabinet server management system and configuration method - Google Patents

Abstract

This invention provides a rack-mount server management system and configuration method. The system includes: server computing nodes connected to a data network via a first port and to a management network via a second port; an RMC network port connected to the management network; and a server BMC connected to the RMC via an I2C bus, and the server BMC also connected to the RMC via a USB bus. This invention implements a solution by adding a network MAC address to the BMC, resolving the network topology issue between the RMC and the node BMC. It integrates two existing network topologies, and this design can meet the networking requirements of different customers.

Description

A whole cabinet server management system and configuration method

technical field

The invention relates to the technical field of servers, in particular to a whole cabinet server management system and configuration method.

Background technique

At present, the entire cabinet or multi-node server has a chassis/cabinet management unit RMC to manage the power supply, fans, and IO of the entire machine, and the rest are computing nodes. Each computing node has a BMC responsible for the out-of-band management of the node.

Currently, only two physical MAC addresses are provided on the RMC and node BMC chips, one for the BMC dedicated management network interface (out-of-band management network interface) and the other for the data network interface (system OS network interface). The BMC dedicated network interface is the exclusive interface for BMC out-of-band management and can only be used for BMC out-of-band management; the system data network interface is the network data interface of the server OS for the system OS to perform network communication, and the general data network interface supports the NCSI function. This function enables the data port to support both OS data communication and BMC out-of-band management.

There are two common designs at present. One is that there are two network ports on the computing node, and the other is that there is only one data network port on the computing node, and the management network is internally networked. Its topology distribution is shown in Figure 1 and Figure 2.

Limited by the number of MAC addresses, the two current topologies have their own advantages and disadvantages. In practical applications, some customers require solution A, some customers require solution B, and some customers require both solutions to be reserved. , which requires a different product design. It causes a lot of trouble to the design, management and generation of the server.

SUMMARY OF THE INVENTION

In view of the above shortcomings of the prior art, the present invention provides a whole cabinet server management system and configuration method to solve the above technical problems.

The present invention provides a whole cabinet server management system, the system includes:

The server computing node is connected to the data network through the first port, and is connected to the management network through the second port; the RMC network port is connected to the management network; the server BMC is connected to the RMC through the I2C bus, and the server BMC is also connected to the RMC through the USB bus.

Further, the system also includes:

The USB port of the RMC is connected to the main line of the USB hub; the USB port of the BMC is connected to the branch line of the USB hub.

Further, the system also includes:

The MAC network port of the RMC is connected to the management network, and the management network is connected to the front panel of the server.

Further, the system also includes:

The RMC is connected to the power supply, the cooling module and the IO module through I2C.

The present invention also provides a method for configuring a server management system of a whole cabinet, the method comprising:

USB communication environment in RMC end system and BMC end system;

Configure the RMC IP and BMC IP of the server;

Set the mapping relationship between the BMC port and the remote management server port on the RMC.

Further, the described USB communication environment in the RMC end system and the BMC end system includes:

Configure rndis_host as a dynamic module in RMC's linux system kernel;

Install the USB Gadget driver on the BMC Linux system.

Further, the RMC IP and BMC IP of the configuration server include:

Set a fixed IP for the RMC of the server on the server intranet;

Set a static IP for the BMC according to the slot where the BMC is located.

Further, the method also includes:

The RMC verifies the firmware update file;

The RMC issues the verified firmware update file to the target BMC, and issues a firmware update instruction to the target BMC to control the target BMC to perform firmware update.

Further, the method also includes:

RMC dynamically adds and ages the corresponding port mapping table according to the network status of the node BMC.

The beneficial effect of the present invention is that,

The invention provides a whole cabinet server management system and configuration method. The remaining USB ports of BMC and RMC are used for internal networking, and the technology of TCP/IP over USB is used to virtualize a network MAC address to realize transmission on USB. For network data packets, two topologies in the prior art are integrated to form a unified solution to meet different customer needs. The invention realizes the scheme of adding a network MAC to the BMC, and solves the network topology structure between the RMC and the node BMC. The two current network topologies are integrated, and this design scheme can meet the networking requirements of different customers. RMC can provide independent access to the BMC of each node through port mapping, which is compatible with the original management system and customer's independent access and other special scenarios. There is no need to repeat the design again, saving product development time and cost, and meeting the multi-level networking and network modification needs of customers.

In addition, the present invention has reliable design principle and simple structure, and has a very wide application prospect.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. In other words, other drawings can also be obtained based on these drawings without creative labor.

FIG. 1 is an architecture diagram of an existing whole cabinet server management system.

FIG. 2 is an architecture diagram of an existing whole cabinet server management system.

FIG. 3 is an architectural diagram of a whole cabinet server management system provided by an embodiment of the present application.

Detailed ways

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the embodiments of the present invention and the features of the embodiments may be combined with each other under the condition of no conflict.

In the description of the present invention, it should be noted that the terms "installed", "connected" and "connected" should be understood in a broad sense, unless otherwise expressly specified and limited, for example, it may be a fixed connection or a detachable connection Connection, or integral connection; can be mechanical connection, can also be electrical connection; can be directly connected, can also be indirectly connected through an intermediate medium, can be internal communication between two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood through specific situations.

The present invention will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.

Example 1

Please refer to FIG. 3 , this embodiment provides a whole cabinet server management system, including: a server computing node is connected to a data network through a first port, and is connected to a management network through a second port; the RMC network port is connected to the management network; the server BMC is connected to the management network through The I2C bus is connected to the RMC, and the server BMC is also connected to the RMC through the USB bus.

The specific topology includes:

Two MAC addresses on the node BMC, one for the dedicated management network connection (purple) and one for the data network (green), both ports are output directly from the compute node;

A network MAC on the RMC for the dedicated management network connection (purple), output from the front panel.

RMC's I2C connects power, cooling, IO modules and various computing nodes for low-speed signal communication;

The USB Host of the RMC is connected to the USB HUB to connect each computing node.

The USB Device on the computing node BMC is connected to the USB HUB to form a connection with the RMC.

TCP/IP over USB function introduction:

The TCP/IP over USB technology uses the USB bus to transmit TCP/IP data packets.

The full name of RNDIS (Remote Network Driver Interface Specification) is the abbreviation of the Remote Network Driver Interface Specification. It is a USB Ethernet card model defined by Microsoft. It spans the transport layer, the network layer and the data link layer. The communication interface specification between the program and the upper-layer protocol driver shields the difference of the underlying physical hardware, so that the upper-layer protocol driver can communicate with the underlying network card of any type. NDIS creates a complete development environment for network drivers, just call NDIS functions without considering the kernel of the operating system and the interface with other drivers, so that the network driver can be separated from the complex communication with the operating system , which greatly facilitates the writing of network drivers. In addition, using the encapsulation feature of NDIS, you can focus on the design of one layer of drivers, which reduces the complexity of the design and makes it easy to expand the driver stack. The implementation of RNDIS based on USB is actually TCP/IP over USB, which is to run TCP/IP on the USB device, making the USB device look like a network card.

Example 2

This embodiment provides a method for configuring a server management system in a whole cabinet, and the method includes:

S1. The USB communication environment in the RMC end system and the BMC end system.

The Linux kernel on the RMC side configures rndis_host as a dynamic module.

Location:

->Device Drivers

->Network device support(NETDEVICES[=y])

->USB Network Adapters

->Multi-purpose USB Networking Framework(USB_USBNET[=m])

->Host for RNDIS and ActiveSync devices

Install the USB Gadget driver g_ether.ko in Linux on the BMC side.

Location:

->Device Drivers

->USB support(USB_SUPPORT[=y])

->USB Gadget Support(USB_GADGET[=y])│

->USB Gadget Drivers(<choice>[=m])│

->Ethernet Gadget(with CDC Ethernet support)(USB_ETH[=n])

S2. Configure the RMC IP and BMC IP of the server.

In this design, the internal network IP address adopts a fixed IP address, the RMC address is fixed as 192.168.1.1, the IP address of the node BMC is related to the slot where it is located, the address of slot 0 is fixed to 192.168.1.100, and the address of slot 1 is fixed to 192.168. 1.101, and so on.

There is a hardware IO number in the slot of the server node. After the server node is inserted, the node BMC can sense the current slot address by reading the IO. Then configure the static IP address according to the slot number. After the network is connected, try to connect to the fixed IP address 192.168.1.1/2 of the RMC, report the status information, and synchronize the data to the RMC.

ifconfig usb0 192.168.1.1up

ifconfig usb0 192.168.1.100up

S3. Set the mapping relationship between the BMC port and the remote management server port on the RMC.

In this design, according to some special application scenarios and customer needs, the function of port mapping is added in RMC, which not only maps the BMC addresses of each node in the intranet to the port mapping method, so that it can access the remote management server, and users can also independently Access the function of node BMC.

For example, the external network IP of RMC is 10.16.1.5, the web port of node BMC0 is mapped to 8080, the web port of node BMC1 is mapped to 8081, and so on.

In addition, when the firmware is updated, the customer can directly log in to the RMC to update the firmware of the node BMC. After the RMC receives the firmware verification package, after the verification is OK, it will be forwarded to the node BMC of the matching model, and the BMC will upgrade it itself. Therefore, when the customer uploads the firmware once, RMC will upgrade the BMCs of all matching nodes in batches, and give feedback on which nodes have been successfully upgraded.

For each node BMC allocates IP according to the slot, and also performs the mapping of fixed port numbers in turn. RMC dynamically adds and ages the corresponding port mapping table according to the network status of the node BMC. Users only need to know the management network IP of the RMC and the one they want to access, and add the relevant port number to directly access the node BMC. For example, the external network IP of RMC is 10.16.1.5, the web port of node BMC0 is mapped to 8080, the web port of node BMC1 is mapped to 8081, and so on. Access RMC: directly access 10.16.1.5, access BMC0 directly access 10.16.1.5:8080.

Although the present invention has been described in detail in conjunction with the preferred embodiments with reference to the accompanying drawings, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, those of ordinary skill in the art can make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions should all fall within the scope of the present invention/any Those skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should all be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (9)

1. A whole cabinet server management system is characterized in that, comprising: The server computing node is connected to the data network through the first port, and is connected to the management network through the second port; the RMC network port is connected to the management network; the server BMC is connected to the RMC through the I2C bus, and the server BMC is also connected to the RMC through the USB bus. 2. The whole cabinet server management system according to claim 1, wherein the system further comprises: The USB port of the RMC is connected to the main line of the USB hub; the USB port of the BMC is connected to the branch line of the USB hub. 3. The whole cabinet server management system according to claim 1, wherein the system further comprises: The MAC network port of the RMC is connected to the management network, and the management network is connected to the front panel of the server. 4. The whole cabinet server management system according to claim 1, wherein the system further comprises: The RMC is connected to the power supply, the cooling module and the IO module through I2C. 5. A method for configuring a server management system in an entire cabinet, wherein the method comprises: USB communication environment in RMC end system and BMC end system; Configure the RMC IP and BMC IP of the server; Set the mapping relationship between the BMC port and the remote management server port on the RMC. 6. method according to claim 5, is characterized in that, the described USB communication environment in RMC end system and BMC end system, comprises: Configure rndis_host as a dynamic module in RMC's linux system kernel; Install the USB Gadget driver on the BMC Linux system. 7. The method according to claim 5, wherein the RMC IP and the BMC IP of the configuration server comprise: Set a fixed IP for the RMC of the server on the server intranet; Set a static IP for the BMC according to the slot where the BMC is located. 8. The method according to claim 5, wherein the method further comprises: The RMC verifies the firmware update file; The RMC issues the verified firmware update file to the target BMC, and issues a firmware update instruction to the target BMC to control the target BMC to perform firmware update. 9. The method of claim 5, wherein the method further comprises: RMC dynamically adds and ages the corresponding port mapping table according to the network status of the node BMC.

Images