Node management method for server chassis and related apparatus

Abstract

The present application relates to the technical field of servers, and in particular to a node management method for a server chassis and a related apparatus. The node management method for a server chassis comprises: an Ethernet switch controller arranged in a server chassis acquiring a communication request, wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller; identifying a request subject of the communication request and a target node, wherein the target node is one of the plurality of chassis nodes; and in response to the request subject being an external node outside the server chassis, performing authentication on the request subject, and in response to the authentication being successful, communicating with the target node in a first communication mode; and in response to the request subject being a chassis node, communicating with the target node in a second communication mode. By using the present method, the chassis nodes in the server chassis can be flexibly managed, so as to improve the server management efficiency, and further improve the reliability of the communication of the chassis nodes.

Description

Server chassis node management method and related device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to a Chinese patent application filed with the Patent Office of China on March 26, 2024, with application number 202410348297.4 and application name “Node management method and related device for server chassis”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of server technology, and in particular to a node management method for a server chassis, a node management device for a server chassis, a server chassis, a computer device, and a computer-readable storage medium. Background Art

[0004] Generally speaking, in many data centers and enterprise network environments, there are multiple chassis nodes inside the server chassis, such as the motherboard node and the network card node. Multiple chassis nodes work together to implement various server functions, such as monitoring hardware status, managing power supply, and performing remote management operations.

[0005] However, most chassis nodes communicate with each other through an I2C (Inter-Integrated Circuit, two-wire serial) bus communication method such as IPMB (Intelligent Platform Management BUS), which is prone to slow speed problems. Summary of the Invention

[0006] The present application provides a node management method for a server chassis, a node management device for a server chassis, a server chassis, a computer device, and a computer-readable storage medium.

[0007] On the one hand, a node management method for a server chassis is provided, and the node management method for the server chassis includes: an Ethernet switch controller provided in the server chassis obtains a communication request; wherein, the server chassis also includes multiple chassis nodes connected to the Ethernet switch controller; identifying a request subject and a target node of the communication request; wherein, the target node is one of the multiple chassis nodes; in response to the request subject being an external node outside the server chassis, authenticating the request subject, and in response to the authentication being passed, communicating with the target node through a first communication method; and in response to the request subject being a chassis node, communicating with the target node through a second communication method.

[0008] In one or more embodiments of the present application, multiple chassis nodes include multiple first nodes and at least one second node; wherein the first node is a node visible to external nodes, and the second node is a node hidden relative to external nodes; in response to the target node being the second node, the request subject is authenticated, and in response to the authentication being passed, communicating with the target node through a first communication method includes: the Ethernet switch controller sends the communication request to one of the first nodes, and one of the first nodes acts as a forwarding node; the forwarding node and / or the target node authenticates the request subject; in response to the authentication being passed, the forwarding node forwards the communication request to the target node.

[0009] In one or more embodiments of the present application, the forwarding node and the target node authenticate the requesting subject, including: the forwarding node verifies the first identity identifier of the requesting subject; in response to the first identity identifier passing the verification, the forwarding node communicates with the target node through a third communication method; the target node verifies the second identity identifier of the requesting subject; in response to the second identity identifier passing the verification, it is determined that the authentication is successful.

[0010] In one or more embodiments of the present application, the forwarding node communicates with the target node through a third communication method, including: obtaining interface information of the request subject; querying the transmission configuration information to obtain the interface information of the target node that matches the interface information of the request subject; wherein the transmission configuration information includes the pre-configured interface information of each first node, second node and external node, as well as the interface information of the target node when each serves as the request subject; the forwarding node communicates with the target node based on the interface information of the target node.

[0011] In one or more embodiments of the present application, the node management method includes: periodically updating the first identity identifier and the verification of the forwarding node at intervals of a first preset time; periodically updating the second identity identifier and the verification of the target node at intervals of a second preset time; wherein the second preset time is greater than the first preset time.

[0012] In one or more embodiments of the present application, in response to the target node being the first node, authenticating the request subject, and in response to successful authentication, communicating with the target node through a first communication method includes: a connector port of an Ethernet switch controller receiving a communication request; wherein the connector port is a port connected to an external node; the Ethernet switch controller sending the communication request from the connector port to a port connected to the target node; the target node authenticating the request subject in response to the communication request input from its port connected to the Ethernet switch controller; and accepting the communication request in response to successful authentication of the request subject.

[0013] In one or more embodiments of the present application, in response to the requesting subject being a chassis node, communicating with the target node through the second communication method includes: the requesting subject sends communication data to the Ethernet switch controller; the Ethernet switch controller broadcasts communication data carrying the authentication network address to the chassis node; wherein the authentication network address includes the network address of the requesting subject and / or the network address of the target node, and the target node is configured to obtain the communication data when identifying the authentication network address; the target node obtains the communication data in response to identifying the network address.

[0014] In one or more embodiments of the present application, the communication data includes at least one of temperature information, power consumption information, and resource utilization; the node management method includes: a baseboard management controller provided in the requesting subject monitors the operating information of the requesting subject; wherein the operating information includes at least one of temperature information, power consumption information, and resource utilization; the baseboard management controller processes the operating information to obtain communication data monitored by the baseboard management controller.

[0015] In one or more embodiments of the present application, the step of authenticating the request subject includes:

[0016] determining a forwarding node for forwarding the communication request to a target node; and

[0017] The request subject is authenticated by the forwarding node and the target node respectively.

[0018] On the other hand, a node management device for a server chassis is provided, which includes: a connection interface and an Ethernet switch controller; the connection interface is used to connect to an external node; the Ethernet switch controller is arranged in the server chassis and connected to the connection interface, and is used to obtain communication requests; wherein, the server chassis also includes multiple chassis nodes connected to the Ethernet switch controller; identifying a request subject and a target node of a communication request; wherein, the target node is one of the multiple chassis nodes; in response to the request subject being an external node outside the server chassis, communicating with the target node through a first communication method; in response to the request subject being a chassis node, communicating with the target node through a second communication method.

[0019] On the other hand, a server chassis is provided, which includes: a chassis node and a node management device of the server chassis; the chassis node includes multiple motherboard nodes and at least one network card node; the node management device is such as the server chassis in any of the above embodiments, connected to the chassis node and the external node outside the server chassis.

[0020] In one or more embodiments of the present application, the chassis node includes multiple first nodes and at least one second node, and the first node is connected to the second node; wherein the first node is a node visible to the external node outside the server chassis, and the second node is a node hidden relative to the external node.

[0021] In one or more embodiments of the present application, the network address of the first node includes a static network address and a dynamic network address; wherein the dynamic network address of the first node is statically allocated and / or obtained through the dynamic host configuration protocol; the network address of the second node includes a static network address.

[0022] In one or more embodiments of the present application, the Ethernet switch controller includes a first port, a second port, and a connector port; the first port is connected to a first node, the second port is connected to a second node, and the connector port is connected to a connector of a communication output terminal of the Ethernet switch controller; the second port is configured to be in the same virtual local area network; and / or, data isolation is performed between the second port and the connector port through port isolation of the local area network switch.

[0023] In one or more embodiments of the present application, the first node includes a motherboard node; the second node includes a network card node; the Ethernet switch controller includes a motherboard port, a network card port, a connector port and a spare port; the motherboard port is connected to the motherboard node; the network card port is connected to the network card node; the connector port is connected to the connector of the communication lead-out end of the Ethernet switch controller; and the spare port is used to connect a newly added chassis node or a chassis node migrated from a port of another Ethernet switch or a connector of the communication lead-out end.

[0024] In one or more embodiments of the present application, the external node is connected to the server chassis through a connector at a communication output end of the server chassis.

[0025] In one or more embodiments of the present application, the connector of the communication output terminal of the server chassis is directly visible to the outside.

[0026] In one or more embodiments of the present application, the server chassis includes a plurality of internal chassis nodes, and the plurality of internal chassis nodes communicate with each other through an Ethernet switch controller.

[0027] On the other hand, a computer device is provided, comprising one or more processors; and a memory associated with the one or more processors, the memory being used to store computer-readable instructions, which, when read and executed by the one or more processors, implement the following steps: an Ethernet switch controller located in a server chassis obtains a communication request; wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller; identifying a request subject and a target node of the communication request; wherein the target node is one of the plurality of chassis nodes; in response to the request subject being an external node outside the server chassis, authenticating the request subject, and in response to successful authentication, communicating with the target node via a first communication method; in response to the request subject being a chassis node, communicating with the target node via a second communication method.

[0028] On the other hand, a non-transitory computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by one or more processors, the following steps are implemented: an Ethernet switch controller located in a server chassis obtains a communication request; wherein the server chassis also includes multiple chassis nodes connected to the Ethernet switch controller; a request subject and a target node of the communication request are identified; wherein the target node is one of the multiple chassis nodes; in response to the request subject being an external node outside the server chassis, the request subject is authenticated, and in response to the authentication being successful, the request subject is communicated with the target node through a first communication method; in response to the request subject being a chassis node, the target node is communicated with the target node through a second communication method. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of an application scenario of one or more embodiments of the node management method for a server chassis of the present application;

[0030] FIG2 is a schematic diagram of the structure of one or more embodiments of a node management device for a server chassis of the present application;

[0031] FIG3 is a schematic structural diagram of an embodiment of a server chassis of the present application;

[0032] FIG4 is a flow chart of an embodiment of a node management method for a server chassis of the present application;

[0033] FIG5 is a flow chart of another embodiment of a node management method for a server chassis of the present application;

[0034] FIG6 is a schematic structural diagram of another embodiment of the server chassis of the present application;

[0035] 7 is a flow chart of another embodiment of the node management method of the server chassis of the present application;

[0036] FIG8 is a flow chart of another embodiment of a node management method for a server chassis of the present application;

[0037] FIG9 is a schematic diagram of the structure of one or more embodiments of the computer device of the present application. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the embodiments described herein are only used to explain this application and are not intended to limit this application.

[0039] In the related art, the communication between server chassis nodes usually has problems such as slow communication rate, poor stability and poor scalability. In one or more embodiments, server chassis communication is generally implemented based on the I2C bus, and the IPMB transmission rate is generally 100K to 400K, which is significantly lower than the network transmission rate of 100M or 1G. In addition, the I2C-based IPMB is prone to transmission anomalies due to path interference or software library problems. At the same time, the communication between two nodes may require an exclusive I2C bus. If multiple nodes access each other, a large amount of I2C bus resources will be required, which can easily lead to poor scalability within the server chassis.

[0040] In related technologies, communication between server chassis nodes can also occur through direct connections on the baseboard management controller (BMC) dedicated network port. This can lead to issues such as occupying the BMC dedicated network port and poor scalability. In one or more embodiments, the BMC dedicated port is typically an out-of-band management channel. If used for communication between internal server nodes, it can easily conflict with and affect out-of-band management functions. BMCs typically only include a single dedicated port and may not be able to directly communicate with multiple nodes.

[0041] To address the problem of unreasonable node management methods in server chassis in related technologies, the present application provides a node management method for a server chassis, a node management device for a server chassis, a server chassis, a computer device, and a computer-readable storage medium. This application is described in detail below.

[0042] Please refer to FIG1 , which is a schematic diagram of an application scenario of one or more embodiments of the node management method for a server chassis of the present application.

[0043] In one or more embodiments, an external node 10, such as a user terminal device, is communicatively connected to a server chassis 20. The external node 10 refers to a node located outside the server chassis 20. The external node 10 may be, but is not limited to, various personal computers, laptops, smartphones, tablet computers, and portable wearable devices. In one or more embodiments, the server chassis 20 may be an independent server. Multiple independent servers can form a server cluster. The server chassis 20, through its internal nodes, can be equipped with the capabilities of responding to service requests, providing services, and ensuring services.

[0044] In one or more embodiments, the external node 10 can be connected to the server chassis 20 via the connector 21 of the communication output terminal of the server chassis 20. For example, the connector 21 of the communication output terminal can be an RJ45 (Registered Jack 45) or the like, which helps to improve the stability of communication between the external node 10 and the server chassis 20. Furthermore, the server chassis 20 can have only the connector 21 of the communication output terminal directly visible to the outside.

[0045] Furthermore, the server chassis may include a chassis node and a node management device 22 of the server chassis.

[0046] A chassis node refers to a node located inside a server chassis. A chassis node may include multiple motherboard nodes 23 and at least one network card node 24. As shown in FIG1 , the chassis node of the server chassis 20 may include two motherboard nodes 23 and two network card nodes 24. It should be noted that the number of motherboard nodes 23 and network card nodes 24 shown in FIG1 is used as an example to illustrate the embodiment, and does not strictly limit the number of chassis nodes in the embodiment. For example, in one or more embodiments, the number of motherboard nodes 23 may be two, and the number of network card nodes 24 may be one; or there may be a greater number of motherboard nodes 23 and network card nodes 24, which will not be elaborated here.

[0047] For example, with the emergence of high-performance central processing units (CPUs) like Xeon processors (such as Birch Stream), single-node motherboard (one CPU) designs have become mainstream. However, in terms of server utilization efficiency, pairing a single-node server with a single Smart NIC for server management can be very wasteful from a TCO (Total Cost of Ownership) perspective. Consequently, designs have emerged, such as placing two single-node motherboards in a single chassis, with a Smart NIC placed inside. Using the Smart NIC's multihost functionality, one Smart NIC can manage both node motherboards.

[0048] At the same time, a design can be further developed, where one node is reserved for each Smart NIC. The server chassis then contains two motherboard nodes and two Smart NICs. As is well known, a Smart NIC can be considered a small server, equivalent to a node. This can be considered as two motherboard nodes and two NIC nodes within the server chassis, which presents significant challenges for overall server management.

[0049] The node management device 22 of the server chassis is connected to the chassis node and the external node outside the server chassis. The node management device of the server chassis can be as described in the embodiment below. The working principle can be referred to the node management method of the server chassis described below, which is not repeated here.

[0050] Please refer to FIG. 2 , which is a schematic diagram of the structure of one or more embodiments of a node management device for a server chassis of the present application.

[0051] In one or more embodiments, the node management device of the server chassis includes a connection interface 221 and an Ethernet switch controller 222 .

[0052] Connection interface 221 is used to connect to an external node. In one or more embodiments, connection interface 221 may be a connector on a communication output terminal of a server chassis; alternatively, connection interface 221 may be a port connecting an Ethernet switch controller to a connector on a communication output terminal, referred to as a connector port below, which is not limited here.

[0053] The Ethernet switch controller 222 is disposed in the server chassis and connected to the connection interface 221. The Ethernet switch controller 222 is configured to: receive a communication request. The server chassis also includes multiple chassis nodes connected to the Ethernet switch controller 221. The controller 222 identifies a request subject and a target node of the communication request. The target node is one of the multiple chassis nodes. If the request subject is an external node outside the server chassis, the controller communicates with the target node using a first communication method. If the request subject is a chassis node, the controller communicates with the target node using a second communication method.

[0054] In one or more embodiments, the Ethernet switch controller may be a LAN Switch (local area network switch) controller, etc., which is not limited here.

[0055] It can be seen that the node management device of the server chassis adds an Ethernet switch controller inside the server chassis, and uses the Ethernet switch controller to implement node management, so as to have flexible scalability, which is conducive to flexible management of the chassis nodes inside the server chassis. At the same time, in one or more embodiments, at least part of the bus resources can be released to help reduce the occurrence of insufficient bus resources. The chassis nodes in the server chassis are connected through the network, which is also conducive to improving data transmission speed and communication efficiency, thereby improving the node server management efficiency. At the same time, there are different response strategies for external nodes and chassis nodes as request subjects, and the external node will be authenticated when it is the request subject, which is conducive to improving the security of server chassis communication, and thus can improve the reliability of chassis node communication.

[0056] At the same time, one or more embodiments focus on the secure and flexible management of each management unit within a server, making only the connector at the communication output directly visible to external nodes. By configuring the Ethernet switch controller to determine whether a chassis node belongs to the first or second node and whether it can be presented externally, secure management can be achieved. Furthermore, each chassis node within the server chassis can also communicate with each other, enabling flexible management of internal nodes.

[0057] The definition of the server chassis node management device can be found in the definition of the server chassis node management method described later and will not be repeated here. Each module in the server chassis node management device described above can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the modules described above can be embedded in or independent of a processor in a computer device in hardware form, or stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0058] Please refer to Figure 3, which is a schematic diagram of the structure of an embodiment of a server chassis of the present application. The internal structure of the server chassis of the present application is described in detail below.

[0059] In one or more embodiments, the chassis node includes a plurality of first nodes and at least one second node, and the first node is connected to the second node.

[0060] Among them, the first node is a node visible to external nodes outside the server chassis, and the second node is a node hidden from external nodes. In one or more embodiments, by setting the first node visible to external nodes and the second node hidden from external nodes, the chassis nodes that can be exposed to the outside of the server chassis can be reduced, which is beneficial to improving the security of the server chassis, and can also reasonably plan the communication request delivery method to reduce the communication burden. At the same time, in one or more embodiments, the external node as the request subject will also be authenticated, which can reduce the risk of the server chassis establishing a communication connection with a risky external node, so as to reduce the risk of the server chassis being easily attacked by the network, thereby improving the reliability and security of the communication process, and further improving the reliability and stability of the server chassis.

[0061] Furthermore, the Ethernet switch controller may include a first port, a second port, and a connector port. The first port is connected to the first node. The second port is connected to the second node. The connector port is connected to a connector of a communication output terminal of the Ethernet switch controller.

[0062] In one or more embodiments, the second port can be configured to be in the same virtual local area network (VLAN); and / or, data can be isolated between the second port and the connector port through port isolation of a LAN switch, thereby enabling relatively reliable control of data and facilitating data security.

[0063] In one or more embodiments, the first node may be a motherboard node within a server chassis. The second node may be a network interface card (NIC) node within the server chassis. Accordingly, the Ethernet switch controller may include a motherboard port, a network interface card (NIC) port, and a connector port. In other words, the first port may include a motherboard port, and the second port may include a NIC port. The motherboard port is connected to the motherboard node. The NIC port is connected to the NIC node. The connector port is connected to a connector at a communication output terminal of the Ethernet switch controller.

[0064] Furthermore, the Ethernet switch controller may also include spare ports. These spare ports can be connected to newly added chassis nodes, chassis nodes migrated from ports on other Ethernet switches, or connectors on communication output terminals, thereby improving the scalability of the server chassis and facilitating the migration of chassis nodes within the server chassis. This, in turn, improves the scalability of node communication management and contributes to improving the reliability and stability of the server chassis.

[0065] Please refer to FIG4 , which is a flow chart of an embodiment of a node management method for a server chassis of the present application.

[0066] S301: An Ethernet switch controller disposed in a server chassis obtains a communication request; wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller.

[0067] In one or more embodiments, a communication request may be sent from an external node or chassis node to a chassis node of a server chassis. A communication request may be broadly understood to include an action requesting establishment of a communication connection, communication data, a service request, and the like, without limitation herein.

[0068] S302: Identify a request subject and a target node of a communication request; wherein the target node is one of a plurality of chassis nodes.

[0069] In one or more embodiments, a node that sends a communication request to an Ethernet switch controller is identified as the request subject, and a node that the communication request desires to communicate with is also identified as the target node.

[0070] S303: In response to the request subject being an external node outside the server chassis, the request subject is authenticated, and in response to successful authentication, the request subject communicates with the target node via a first communication method; in response to the request subject being a chassis node, the request subject communicates with the target node via a second communication method.

[0071] In one or more embodiments, in response to identifying that a requesting entity is an external node outside a server chassis, it is determined that the current communication request may pose a certain risk, and the requesting entity may be authenticated to verify whether the requesting entity has permission to communicate with the chassis node. In response to successful authentication of the external node as the requesting entity, it may be determined that the external node is trustworthy and communication with it is relatively reliable and low risk, so the requesting entity is allowed to communicate with the target node via the first communication method. In this way, when the external node communicates with the chassis node, the security and reliability of the communication process can be effectively improved.

[0072] At the same time, in response to identifying that the requesting subject is a chassis node inside the server chassis, that is, the communication occurs inside the server chassis, it can be considered that the risk of communication inside the server chassis is relatively small, and there is no need to authenticate the requesting subject. The requesting subject can communicate with the target node through the second communication method, which can reduce the authentication process and reduce the computational cost of the communication process, thereby improving communication efficiency.

[0073] By planning the response strategies for external nodes and chassis nodes as request subjects separately, it is possible to improve the communication efficiency of the server chassis while ensuring security and reliability.

[0074] In view of this, in one or more embodiments, an Ethernet switch controller is added within the server chassis and node management is implemented using the Ethernet switch controller. This provides flexible scalability, thereby facilitating flexible management of chassis nodes within the server chassis, while also improving data transmission speed and communication efficiency, thereby enhancing node server management efficiency. Furthermore, different response strategies are implemented for external nodes and chassis nodes as requesting entities, and when an external node is acting as a requesting entity, the external node is authenticated, thereby improving the security of server-chassis communications and, in turn, the reliability of chassis-node communications.

[0075] At the same time, in one or more embodiments, the chassis nodes inside the server chassis also communicate with each other through the Ethernet switch controller. In other words, in one or more embodiments, network communication is performed between chassis nodes located inside the same server chassis. Compared with the traditional bus communication method between chassis nodes in a server chassis, the network communication between chassis nodes in the node management method of one or more embodiments can significantly improve the communication rate, simplify the redundant operations generated when expanding / deleting chassis nodes, improve the processing efficiency when chassis nodes change, and help reduce the crowding out of the bus and / or BMC dedicated ports, reduce the risk of communication anomalies, and thus improve the scalability of node communication management, while helping to improve the reliability and stability of the server chassis.

[0076] 3 , in one or more embodiments, the plurality of chassis nodes include a plurality of first nodes and at least one second node, wherein the first nodes are nodes visible to external nodes and the second nodes are nodes hidden from external nodes.

[0077] That is, in one or more embodiments, to ensure communication security within the server chassis, chassis nodes are divided into an internal network and an external network. Communication between internal network devices can be authentication-free, while access to internal network devices from the external network requires authentication. This also reduces the number of chassis nodes with which external nodes can directly communicate, further improving communication security and reliability.

[0078] In one or more embodiments, the first node may include a motherboard node, the second node may include a network card node, and the Ethernet switch controller includes a network card port, a motherboard port, and a connector port.

[0079] Among them, the network card port is the port of the Ethernet switch controller connected to the network card node; the motherboard port is the port of the Ethernet switch controller connected to the motherboard node; the connector port is the port of the Ethernet switch controller connected to the connector of the communication lead-out end, and the connector of the communication lead-out end is used to connect to an external node.

[0080] Furthermore, the network card port is configured to be in the same virtual local area network (VLAN); the connector port is communicatively connected to the motherboard port; and / or, data isolation is performed between the network card port and the connector port via port isolation of the LAN switch.

[0081] That is, in one or more embodiments, considering the security of communication within the server chassis, chassis nodes are divided into an internal network and an external network. Communication between internal network devices may not require authentication, while access to internal network devices from the external network requires authentication. In one or more embodiments, the motherboard node may be used as the first node, and the network card node as the second node. In this way, by creating a virtual local area network and / or port isolation, data can be relatively reliably controlled, which is conducive to achieving data security.

[0082] In one or more embodiments, the server chassis can be configured to support two partitioning modes: virtual local area network (VLAN) creation and port isolation. The server chassis can obtain user configuration instructions and switch to the partitioning mode indicated by the configuration instructions. Alternatively, the server chassis can use reinforcement learning models and other methods to select a partitioning mode that is more suitable for the current scenario. This is not limited here.

[0083] Please refer to Figures 5 and 6 in combination. Figure 5 is a flow chart of another embodiment of the node management method of the server chassis of the present application, and Figure 6 is a structural diagram of another embodiment of the node management device of the server chassis of the present application.

[0084] In one or more embodiments, the network address of the first node includes a static network address and a dynamic network address, wherein the dynamic network address of the first node is statically allocated and / or obtained using the Dynamic Host Configuration Protocol. The network address of the second node includes a static network address.

[0085] Please continue to refer to Figure 5. The following describes in detail an implementation method in which, when the external node is the requesting subject and the target node is the second node, the requesting subject is authenticated and, in response to successful authentication, the communication with the target node via the first communication method is performed.

[0086] In one or more embodiments, in response to receiving a communication request from an external node, the Ethernet switch controller may send the communication request to one of the first nodes. The first node receiving the communication request may serve as a forwarding node. Because the target node is hidden from the external node and cannot directly communicate with the external node, the forwarding node means that the first node is not the target node of the communication request, but rather forwards the communication request to the second node that is the target node.

[0087] The forwarding node and / or the target node can authenticate the requesting entity and verify whether the external node acting as the requesting entity has access, communication, and other permissions. In other words, the chassis node authenticating the requesting entity can be the first node acting as the forwarding node; alternatively, the chassis node authenticating the requesting entity can be the second node acting as the target node; alternatively, the chassis node authenticating the requesting entity can be the first node acting as the forwarding node and the second node acting as the target node, with each node authenticating the requesting entity.

[0088] In one or more embodiments, the requesting subject may be authenticated by one or a combination of identity identification, key, seal, user biometrics, dynamic password, etc., which will not be described in detail here.

[0089] If the requesting entity passes authentication, the requesting entity can be considered relatively trustworthy and reliable, so the forwarding node can forward the communication request to the target node, allowing the target node to receive the communication request. If the requesting entity fails authentication, the communication request of the requesting entity is rejected and / or relevant information is fed back to the user.

[0090] In one or more embodiments, by dividing the first node and the second node, the number of chassis nodes exposed to the outside of the server chassis can be reduced, which is beneficial for improving the security of the server chassis and allowing for the rational planning of communication request delivery methods to reduce the communication burden. Furthermore, in one or more embodiments, the external node acting as the requesting subject is authenticated, which can reduce the risk of network attacks on the server chassis, thereby improving the reliability and security of the communication process and, in turn, the reliability and stability of the server chassis.

[0091] For example, the forwarding node and the target node may authenticate the requesting subject separately, thereby further improving the reliability of the authentication process through double authentication, which can help ensure the reliability and security of the communication process.

[0092] In one or more embodiments, in response to the Ethernet switch controller forwarding the communication request to the forwarding node, the forwarding node may verify the first identity identifier of the requesting entity. The first identity identifier may carry identity information verifiable by the forwarding node, such as a user login name and key, network address information, etc.

[0093] In response to the first identity identifier passing the verification, the forwarding node may communicate with the target node via the third communication mode. In response to the first identity identifier failing the verification, the forwarding node may reject the communication request of the requesting subject and / or provide feedback to the user that the requesting subject failed the verification of the first identity identifier.

[0094] In one or more embodiments, the third communication method may include: obtaining interface information of the request subject; querying the transmission configuration information to obtain the interface information of the target node that matches the interface information of the request subject; wherein the transmission configuration information includes the pre-configured interface information of each first node, second node and external node, as well as the interface information of the target node when each serves as the request subject; the forwarding node communicates with the target node based on the interface information of the target node.

[0095] That is to say, the communication method between the first node as a forwarding node and the second node as a target node may be different from the communication method between the first node as a requesting subject and the second node as a target node as described below. For example, by reasonably planning the communication transmission process inside the server chassis, the crowding out of the same communication resources by different communication scenarios can be reduced, which is conducive to improving the rationality of communication management between nodes, and thus conducive to improving the stability of the server chassis.

[0096] The forwarding node transmits the communication request from the requesting entity to the destination node via the third communication method. The destination node verifies the second identity of the requesting entity. If the second identity verifies successfully, the destination node determines that authentication is successful. If the second identity verifies unsuccessfully, the destination node may reject the communication request from the requesting entity and / or provide a user with feedback indicating that the second identity verification failed.

[0097] Furthermore, the first identity identifier and the verification of the forwarding node can be periodically updated at intervals of a first preset time length. The second identity identifier and the verification of the target node can be periodically updated at intervals of a second preset time length. At the same time, the second preset time length is greater than the first preset time length. In other words, the update frequency of the first identity identifier can be higher than the update frequency of the second identity identifier, so as to reasonably plan the update frequency of the first identity identifier and the second identity identifier, and reasonably balance the management of computing resources and the security and reliability of the server chassis. At the same time, by first authenticating the requesting subject with the first identity identifier with a higher update frequency, it is beneficial to improve the effectiveness of the authentication, and can screen out external nodes that do not have communication authority at an early stage, and can reduce the operation of secondary verification, so as to improve the communication response efficiency while reducing the communication computing cost.

[0098] Please refer to Figure 7, which is a flow chart of another embodiment of the node management method for a server chassis of the present application. The following describes in detail an implementation method for authenticating the requesting subject when an external node is the requesting subject and the target node is the first node, and then communicating with the target node via the first communication method in response to successful authentication.

[0099] In one or more embodiments, a connector port of an Ethernet switch controller receives a communication request, wherein the connector port is a port connected to an external node, and the Ethernet switch controller sends the communication request from the connector port to a port connected to a first node as a target node.

[0100] The target node authenticates the requesting entity in response to a communication request received through its port connected to the Ethernet switch controller. If the requesting entity passes the identity verification, the target node accepts the communication request. If the requesting entity fails the identity verification, the target node rejects the requesting entity's communication request and / or provides relevant information to the user.

[0101] In one or more embodiments, the external node as the requesting subject requests to communicate with the first node. The first node is a node visible to the external node, so the intervention of the second node hidden relative to the external node can be reduced, which is conducive to improving the reliability of the communication process.

[0102] Please refer to FIG8 , which is a flow chart of another embodiment of the node management method for a server chassis of the present application.

[0103] The following describes in detail an implementation method in which, when a chassis node is a requesting subject and the target node is also a chassis node, the requesting subject is authenticated, and in response to successful authentication, the requesting subject communicates with the target node through the first communication mode.

[0104] In one or more embodiments, a baseboard management controller provided in the requesting subject monitors the operating information of the requesting subject; wherein the operating information includes at least one of temperature information, power consumption information, and resource utilization.

[0105] The baseboard management controller processes the operation information to obtain communication data monitored by the baseboard management controller.

[0106] Furthermore, when the communication data transmission timing is suitable, the requesting subject may send the communication data to the Ethernet switch controller. In one or more embodiments, the communication data may include at least one of temperature information, power consumption information, and resource utilization.

[0107] The Ethernet switch controller broadcasts communication data carrying an authentication network address to the chassis node; wherein the authentication network address includes the network address of the requesting subject and / or the network address of the target node, and the target node is configured to obtain the communication data upon identifying the authentication network address.

[0108] The destination node acquires the communication data in response to identifying the network address.

[0109] It can be seen that in one or more embodiments, chassis nodes can communicate with each other through the network, which can significantly improve communication efficiency compared to the communication method through the internal bus of the server chassis, and is also beneficial to improving the security and stability of the server chassis. At the same time, communication management through the Ethernet switch controller can improve scalability, which in turn is beneficial to improving the flexibility of the node management method.

[0110] It should be understood that although the various steps in the flow charts of Figures 4-5 and Figures 7-8 are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless otherwise specified herein, the execution of these steps is not strictly limited in order, and these steps can be performed in other orders. Moreover, at least a portion of the steps in Figures 4-5 and Figures 7-8 may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0111] Please refer to FIG9 , which is a schematic diagram of the structure of one or more embodiments of the computer device of the present application.

[0112] In one or more embodiments, the computer device may be a server, and its internal structure diagram may be as shown in FIG9 .

[0113] The computer device includes one or more processors connected via a system bus, a memory managed by the one or more processors, and a network interface. The processor of the computer device is used to provide computing and control capabilities. The memory is used to store computer-readable instructions. The memory of the computer device includes a non-transitory storage medium and an internal memory. The non-transitory storage medium stores an operating system, computer-readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-transitory storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer-readable instructions are executed by the processor, a node management method for a server chassis is implemented.

[0114] Those skilled in the art will understand that the structure shown in Figure 9 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0115] In one or more embodiments, a computer device is provided, including a memory, one or more processors, and computer-readable instructions stored in the memory and executable on the processors. When the processors execute the computer-readable instructions, the following steps are implemented:

[0116] S301: An Ethernet switch controller disposed in a server chassis obtains a communication request; wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller.

[0117] S302: Identify a request subject and a target node of a communication request; wherein the target node is one of a plurality of chassis nodes.

[0118] S303: In response to the request subject being an external node outside the server chassis, the request subject is authenticated, and in response to successful authentication, the request subject communicates with the target node via a first communication method; in response to the request subject being a chassis node, the request subject communicates with the target node via a second communication method.

[0119] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-transitory computer-readable storage medium. When the computer-readable instructions are executed, they may include processes such as the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0120] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0121] The embodiments described above merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present application, and such modifications and improvements are all within the scope of protection of the present application.

Claims

1. A node management method for a server chassis, characterized in that: The node management method includes: An Ethernet switch controller disposed in a server chassis obtains a communication request; wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller; Identifying a request subject and a target node of the communication request; wherein the target node is one of the plurality of chassis nodes; In response to the request subject being an external node outside the server chassis, authenticating the request subject, and in response to successful authentication, communicating with the target node through a first communication method; or In response to the request subject being the chassis node, communicating with the target node through a second communication manner.

2. The node management method according to claim 1, characterized in that: The plurality of chassis nodes include a plurality of first nodes and at least one second node; wherein the first node is a node visible to the external node, and the second node is a node hidden from the external node; In response to the target node being the second node, authenticating the request subject, and in response to successful authentication, communicating with the target node through the first communication mode includes: The Ethernet switch controller sends the communication request to one of the first nodes, and the one of the first nodes serves as a forwarding node; The forwarding node and / or the target node authenticates the request subject; and In response to authentication being successful, the forwarding node forwards the communication request to the target node.

3. The node management method according to claim 2, characterized in that: The forwarding node and the target node authenticating the request subject include: The forwarding node verifies the first identity identifier of the request subject; In response to the first identity identifier passing the verification, the forwarding node communicates with the target node through a third communication mode; The target node verifies the second identity identifier of the request subject; and In response to the second identity identifier passing the verification, it is determined that the authentication is successful.

4. The node management method according to claim 3, characterized in that: The forwarding node communicating with the target node through the third communication mode includes: Obtaining interface information of the request subject; Querying transfer configuration information to obtain interface information of a target node that matches the interface information of the request subject; wherein the transfer configuration information includes pre-configured interface information of each of the first node, the second node, and the external node, as well as interface information of the target node when each node serves as the request subject; and The forwarding node communicates with the target node based on the interface information of the target node.

5. The node management method according to claim 3, characterized in that: The node management method includes: Periodically updating the first identity and the verification of the forwarding node at intervals of a first preset time; and Periodically updating the second identity and the verification of the target node at intervals of a second preset time length; The second preset duration is greater than the first preset duration.

6. The node management method according to claim 2, characterized in that: In response to the target node being the first node, authenticating the request subject, and in response to successful authentication, communicating with the target node through the first communication method includes: The connector port of the Ethernet switch controller receives the communication request; wherein the connector port is a port connected to the external node; The Ethernet switch controller sends the communication request from the connector port to the port connected to the target node; The target node authenticates the request subject in response to the communication request inputted by the port connected to the Ethernet switch controller; and In response to the request subject passing the identity authentication, the communication request is accepted.

7. The node management method according to claim 1, characterized in that: In response to the request subject being the chassis node, communicating with the target node through the second communication mode includes: The requesting subject sends the communication data to the Ethernet switch controller; The Ethernet switch controller broadcasts the communication data carrying the authentication network address to the chassis node; wherein the authentication network address includes the network address of the request subject and / or the network address of the target node, and the target node is configured to obtain the communication data upon identifying the authentication network address; and The target node obtains the communication data in response to identifying the network address.

8. The node management method according to claim 7, characterized in that: The communication data includes at least one of temperature information, power consumption information, and resource utilization; and the node management method includes: A baseboard management controller provided in the requesting subject monitors the operation information of the requesting subject; wherein the operation information includes at least one of temperature information, power consumption information, and resource utilization; and The baseboard management controller performs data processing on the operation information to obtain the communication data monitored by the baseboard management controller.

9. The node management method according to claim 7, characterized in that: The step of authenticating the request subject includes: determining a forwarding node for forwarding the communication request to the target node; and The request subject is authenticated by the forwarding node and the target node respectively.

10. A node management device for a server chassis, characterized in that: The node management device includes: a connection interface for connecting to an external node; and An Ethernet switch controller is provided in the server chassis and connected to the connection interface, and is used to: Obtaining a communication request; wherein the server chassis further comprises a plurality of chassis nodes connected to the Ethernet switch controller; Identifying a request subject and a target node of the communication request; wherein the target node is one of the plurality of chassis nodes; In response to the request subject being an external node outside the server chassis, communicating with the target node through a first communication method; or In response to the request subject being the chassis node, communicating with the target node through a second communication manner.

11. A server chassis, characterized in that: The server chassis includes: a chassis node, comprising a plurality of motherboard nodes and at least one network card node; and The node management device of the server chassis as claimed in claim 10 is connected to the chassis node and the external node outside the server chassis.

12. The server chassis according to claim 11, wherein: The chassis node includes a plurality of first nodes and at least one second node, wherein the first node is connected to the second node; The first node is a node visible to an external node outside the server chassis, and the second node is a node hidden from the external node.

13. The server chassis according to claim 12, wherein: The network address of the first node includes a static network address and a dynamic network address; wherein the dynamic network address of the first node is statically allocated and / or obtained through the Dynamic Host Configuration Protocol; The network address of the second node includes a static network address.

14. The server chassis according to claim 12, wherein: The Ethernet switch controller includes a first port, a second port, and a connector port; The first port is connected to the first node, the second port is connected to the second node, and the connector port is connected to a connector connected to a communication output terminal of the Ethernet switch controller; as well as The second port is configured to be in the same virtual local area network; And / or, data isolation is performed between the second port and the connector port through port isolation switched via a local area network.

15. The server chassis according to claim 12, wherein: The first node includes a mainboard node; the second node includes a network card node; The Ethernet switch controller includes a motherboard port, a network card port, a connector port, and a spare port; The mainboard port is connected to the mainboard node; the network card port is connected to the network card node; the connector port is connected to the connector of the communication lead-out end of the Ethernet switch controller; The idle port is used to connect to a newly added chassis node or a chassis node migrated from a port of another Ethernet switch or a connector of a communication lead-out terminal.

16. The server chassis according to claim 11, wherein: The external node is connected to the server chassis via a connector at a communication output end of the server chassis.

17. The server chassis according to claim 16, wherein: The connector of the communication lead-out end of the server chassis is directly visible to the outside.

18. The server chassis according to claim 11, wherein: The server chassis includes a plurality of internal chassis nodes, and the plurality of internal chassis nodes communicate with each other through the Ethernet switch controller.

19. A computer device comprising: one or more processors; as well as A memory associated with the one or more processors, the memory being used to store computer-readable instructions, wherein the computer-readable instructions, when read and executed by the one or more processors, implement the steps of the node management method according to any one of claims 1 to 9.

20. A non-transitory computer-readable storage medium having computer-readable instructions stored thereon, characterized in that: When the computer-readable instructions are executed by one or more processors, the steps of the node management method according to any one of claims 1 to 9 are implemented.

Images