Computing system and network device management method
By setting up a substrate management controller with external and internal network interfaces in the processing unit, the problem of unable to remote management of network switches to achieve remote management and monitoring of network exchangers, improved the management efficiency of data centers, Essence
Patent Information
- Application Number
- CN202210351507.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-10-28
- Filing Date
- 2022-04-02
- Publication Date
- 2025-01-28
- Estimated Expiration
- 2042-04-02
AI Technical Summary
The prior art cannot implement remote management of network switches because network switches are generally unable to connect directly to external networks.
By setting up the first substrate management controller (BMC) in the processing unit, the BMC has an external network interface and internal network interface. Performance management.
The remote management of the network switch is realized, allowing users to configure and monitor the network switch from the remote end, and improve the management efficiency of the data center.
Smart Images

Figure CN116055347B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to communication between a processing device and a network device; more particularly, to a system and method for remotely managing a network switch via a processing device. Background Art
[0002] Servers are used extensively in high-demand applications, such as network-based systems or data centers. The emergence of cloud computing applications has increased the demand for data centers. Data centers contain numerous servers that store data and run applications, accessed by users from remotely connected computing devices. A typical data center consists of physical racks with associated power and communication connections. Each rack can house multiple computing and storage servers. Generally, each server includes hardware components such as a processing unit, memory devices, network interface cards, power supplies, network switches, and other specialized hardware. The processing unit typically includes a baseboard management controller (BMC) that manages the operation of the hardware components and supports components such as the power supply and fans. The BMC of the processing unit can be directly connected to an external network, allowing users to remotely access the processing unit for out-of-band management. Network switches also typically include their own BMC. However, network switches are often unable to directly connect to an external network to enable remote access. Therefore, there is a pressing need for systems and methods for remote management of network switches. Summary of the Invention
[0003] The term "embodiment" and similar words, such as "implementation," "configuration," "aspect," "example," and "option," are intended to refer broadly to all subject matter of the present disclosure and the appended claims. Statements containing such words should be understood as not limiting the subject matter described in this specification or as limiting the meaning or scope of the appended claims. The embodiments covered by this disclosure are defined by the appended claims, not by this section. This section provides a general overview of the various aspects of the disclosure and introduces some of the concepts that will be further described in the "Implementation Methods" section. This section is not intended to identify key or essential features of the claimed subject matter. This section is also not intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire disclosure, any or all of the drawings, and each claim.
[0004] According to certain aspects of the present disclosure, a computing system is provided, comprising a processing unit and a network device. The processing unit comprises a first baseboard management controller (BMC), an external network interface coupled to the first BMC, and a first internal network interface coupled to the first BMC. The network device comprises a second BMC and a second internal network interface coupled to the second BMC. The second internal network interface of the network device is connected to the first internal network interface of the processing unit. The first BMC is configured to transmit data between an external network and the second BMC via the external network interface, the first internal network interface, and the second internal network interface.
[0005] In some implementations, the data includes one or more management requests associated with the network device, and the first BMC is configured to receive the one or more management requests from the external network via the external network interface.
[0006] In some implementations, the first BMC is configured to transmit the one or more management requests to the second BMC via the first internal network interface and the second internal network interface.
[0007] In some implementations, the second BMC is configured to generate at least one response to the one or more management requests, and transmit the at least one response to the first BMC via the first internal network interface and the second internal network interface.
[0008] In some implementations, the first BMC is configured to transmit the one or more responses to the one or more management requests to an external network via an external network interface.
[0009] In some implementations, the first internal network interface includes a first physical layer (PHY) circuit and a first Reduced Media Independent Interface (RMII) connection connecting the first PHY circuit to the first BMC.
[0010] In some implementations, the second internal network interface includes a second PHY circuit and a second RMII connection connecting the second PHY circuit to the second BMC.
[0011] In some implementations, the first PHY circuit of the processing unit and the second PHY circuit of the network device are connected to each other via a wired connection.
[0012] In some implementations, the wired connection is an Ethernet connection.
[0013] In some implementations, the external network interface of the processing unit includes a network interface card (NIC) and an RMII connection coupling the NIC to the first BMC.
[0014] In some implementations, the NIC of the processing unit is coupled to an external network via a wired connection or a wireless connection.
[0015] In some implementations, the first BMC includes a first data interface and a second data interface. The first data interface of the first BMC forms part of the external network interface. The second data interface of the first BMC forms part of the first internal network interface.
[0016] In some implementations, the first BMC includes a data bridge located between the first data interface and the second data interface to transmit data between the external network interface of the processing unit and the first internal network interface of the processing unit.
[0017] In some implementations, the processing unit includes a first serial communication interface, and the network device includes a second serial communication interface coupled to the first serial communication interface via an integrated circuit bus (I2C) connection.
[0018] In some implementations, the second BMC is configured to transmit a media access control (MAC) address of the network device to the first BMC via the first and second serial communication interfaces.
[0019] In some implementations, the network device is a network switch.
[0020] According to certain aspects of the present disclosure, a method for managing a network device is provided, comprising receiving a management request from an external network on a first baseboard management controller (BMC) of a processing unit. The method further comprises transmitting the management request from the first BMC of the processing unit to a second BMC of the network device via an internal network. The method further comprises generating, by the second BMC of the network device, a response to the management request. The method further comprises transmitting the response to the management request from the second BMC of the network device to the first BMC of the processing unit via the internal network. The method further comprises transmitting the response to the management request from the first BMC of the processing unit to the external network.
[0021] In some embodiments, the method further includes generating a virtual data bridge between a first data interface of a first BMC of the processing unit and a second data interface of the first BMC of the processing unit. The method further includes receiving a unique identifier associated with the network device on the first BMC of the processing unit. The method further includes outputting the management request on the second data interface in response to receiving a management request on the first data interface and determining that the management request includes the unique identifier. The first data interface is connected to an external network, and the second data interface is connected to a second BMC of the network device via an internal network.
[0022] In some implementations, the method further includes receiving a response to the management request on a second data interface of the first BMC of the processing unit. The method further includes outputting the response to the management request on a first data interface of the first BMC of the processing unit.
[0023] In some implementations of the method, the network device is a network switch.
[0024] The above content in this section is not intended to represent every embodiment or every aspect of the present disclosure. On the contrary, the above content in this section only provides examples for some of the novel aspects and features described in this specification. The above features and advantages, as well as other features and advantages of the present disclosure, will be understood after reading the detailed description of the representative embodiments and modes for implementing the present invention below, and reading them together with the accompanying drawings and appendix claims. The additional aspects of the present disclosure will be understood by those skilled in the art of the present disclosure after reading the embodiments in the "Implementation Methods" below and reading them together with the drawings. A brief description of these drawings is shown in the "Brief Description of Drawings" section below. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The present disclosure and its advantages and figures are best understood after reading the following description of representative embodiments in conjunction with the accompanying drawings. These drawings are merely representative embodiments and should not be construed as limiting the scope of the embodiments or claims.
[0026] Figure 1 is a block diagram showing a system for remotely managing network devices using a separate processing device according to certain aspects of the present disclosure;
[0027] Figure 2 A flow chart showing a method according to certain aspects of the present disclosure, wherein Figure 1 The system shown performs remote management of network devices;
[0028] Figure 3 is a diagram showing, according to certain aspects of the present disclosure, Figure 1 The network packet flow of the system shown.
[0029] The numbers in the figure are explained as follows:
[0030] 100: Operational System
[0031] 102: Chassis
[0032] 104: External network
[0033] 106: Internal network connection
[0034] 108:Sequence Connection
[0035] 110: Processing unit
[0036] 112: Motherboard
[0037] 114: Network Interface Card (NIC)
[0038] 116: Physical layer (PHY) circuit
[0039] 118: Baseboard Management Controller (BMC)
[0040] 119A: First data interface
[0041] 119B: Second data interface
[0042] 120A: First Reduced Media Independent Interface (RMII) connection
[0043] 120B: Second RMII connection
[0044] 122: External network interface
[0045] 124: Internal network interface
[0046] 126:Data Bridging
[0047] 128: Serial communication interface
[0048] 130: Network switch
[0049] 132: Network switch board
[0050] 134:BMC
[0051] 135:Data interface
[0052] 136:PHY circuit
[0053] 138:RMII connection
[0054] 140: Internal network interface
[0055] 142: Serial communication interface
[0056] 200:Method
[0057] 202, 204, 206, 208, 210: Step 302: User
[0058] 304: Network Interface Card (NIC)
[0059] 306,308:BMC
[0060] 310, 312, 314: inbound data flow
[0061] 316, 318, 320: outbound data flow DETAILED DESCRIPTION
[0062] Network systems (such as servers) include baseboard management controllers (BMCs), which enable the system to be remotely accessed and managed via an external network connection (also known as out-of-band management). The BMCs can be used to monitor various components in the system and perform tasks such as rebooting and shutting down the system. However, some network devices in such systems are not able to provide remote management capabilities through direct connections to the external network. This document discloses systems and methods for remotely managing network devices using BMCs from various devices.
[0063] Each embodiment is described with reference to the drawings in the appendix, in which the same reference numerals in different drawings are used to represent similar or equivalent elements. The drawings are not necessarily drawn to scale and are only used to illustrate the aspects and features of the present disclosure. The various specific details, relationships and methods described herein are used to provide a complete understanding of certain aspects and features of the present disclosure, and those skilled in the art to which the present disclosure belongs will recognize that such aspects and features can be implemented without such specific details, or can be implemented with other relationships and methods. In some examples, for the sake of clarity of the drawings, known structures or operations are not illustrated in detail. The embodiments disclosed herein need not be limited to the operations or event sequences described, as some operations can be performed in different orders and / or simultaneously with other operations or events. In addition, not all of the operations or events described must implement certain aspects or features of the present disclosure.
[0064] In this section, unless otherwise expressly indicated, words in the singular include the plural, and vice versa, where appropriate. The word "include" means "including but not limited to." In addition, words indicating similarity, such as "about," "near," "substantially," "approximately," etc., may be used in this section to mean "located at," "close to," "near," "within a 3-5% error range," "within an allowable manufacturing error range," or a logical combination of the above words. Similarly, words such as "vertical" or "horizontal" are intended to include "within a 3-5% error range" in the vertical or horizontal direction, respectively. In addition, words indicating direction, such as "top," "bottom," "left," "right," "above," and "below," are intended to refer to equivalent directions as depicted in the referenced drawings; to be read in the context of the referenced object or component, such as in the position in which the object or component is normally used; or to be read in other ways as described herein.
[0065] Figure 1A computing system 100 is shown for remotely managing network devices. The computing system 100 can be a computing server, a storage server, or any other computing system with a network connection. The computing system 100 includes a housing 102, a processing unit 110 disposed within the housing 102, and a network switch 130 disposed within the housing 102. The processing unit 110 is configured to perform the primary computing functions of the computing system 100. The processing unit 110 includes a motherboard 112 and various components disposed on the motherboard 112. The various components disposed on the motherboard 112 include a central processing unit (not shown), a network interface card (NIC) 114, a physical layer (PHY) circuit 116, and a baseboard management controller (BMC) 118. The BMC 118 of the processing unit 110 is also referred to as a first BMC in this disclosure. The motherboard 112 may include or be connected to various other components (not shown), including memory devices (e.g., random access memory (RAM), flash memory storage devices, etc.), other computer chips (e.g., a northbridge chip, a southbridge chip, etc.), various input / output interfaces, a power supply, a fan module, temperature sensors, etc. The BMC 118 typically includes its own processing unit and memory devices. The processing unit of the BMC 118 may be configured to execute firmware stored in the memory devices of the BMC 118. The BMC 118 is configured to manage the operation of the processing unit 110. For example, the BMC 118 may monitor the temperature and voltage of the processing unit 110 and adjust the operation of any component as needed.
[0066] BMC 118 also enables remote access to processing unit 110 via NIC 114. Remote access by a user (e.g., an information technology (IT) technician) allows the user to remotely reboot or shut down processing unit 110, monitor various components of processing unit 110, and more. This type of remote management is also referred to as out-of-band management. BMC 118 includes a first data interface 119A connected to NIC 114 via a first Reduced Media-Independent Interface (RMII) connection 120A. In some implementations, first data interface 119A is an Ethernet interface. NIC 114 (which may include an Ethernet port, a Universal Serial Bus (USB) port, a wireless transceiver, etc.) is configured to connect to external network 104. NIC 114, first data interface 119A of BMC 118, and first RMII connection 120A together form an external network interface 122 of processing unit 110. External network interface 122 connects processing unit 110 to external network 104, allowing users to remotely access BMC 118 for out-of-band management of processing unit 110.
[0067] The processing unit 110 also includes an internal network interface 124 that allows the processing unit 110 to connect to the network switch 130. The internal network interface 124 includes the second data interface 119B of the BMC 118, the PHY circuit 116, and a second RMII connection 120B. The second RMII connection 120B connects the second data interface 119B of the BMC 118 to the PHY circuit 116. The PHY circuit 116 is a circuit (e.g., an integrated circuit) that facilitates data transmission between the processing unit 110 and the network switch 130. Generally speaking, the PHY circuit 116 includes a physical port for receiving data signals from the network switch 130 and circuitry required to translate the data signals into a format that can be transmitted to the BMC 118. In some implementations, the PHY circuit includes an Ethernet port for connecting the processing unit 110 and the network switch 130. Therefore, the internal network interface 124 enables the processing unit 110 to communicate with the network switch 130.
[0068] The network switch 130 includes a network switch board 132 and various components configured on the network switch board 132. These components (not shown) may include computing components (e.g., processing units, complex programmable logic devices, etc.), fans, power supplies, support circuits, etc. The network switch 130 also includes multiple input / output interfaces (e.g., Ethernet ports). These input / output interfaces can be used to connect various devices to the network switch 130, such as other components of the computing system 100, other systems similar to the computing system 100, other devices, etc. The network switch 130 and any devices connected to the network switch 130 (e.g., the processing unit 110) are interconnected in an internal network.
[0069] The network switch board 132 also includes a BMC 134 and a PHY circuit 136. The BMC 134 may be similar to the BMC 118 of the processing unit 110 and may be used to monitor the performance of various components of the network switch 130. The BMC 134 of the network switch 130 is also referred to as a second BMC in this disclosure. The PHY circuit 136 may be similar to the PHY circuit 116 of the processing unit 110 and facilitates data transmission between the processing unit 110 and the network switch 130. The PHY circuit 136 may include a physical port (e.g., an Ethernet port) similar to the PHY circuit 116 of the processing unit 110. The BMC 134 includes a data interface 135 (which in some embodiments is an Ethernet interface) connected to the PHY circuit 136 via an RMII connection 138. The data interface 135 of the BMC 134, the PHY circuit 136, and the RMII connection 138 together form the internal network interface 140 of the network switch 130.
[0070] The internal network interface 140 of the network switch 130 is connected to the internal network interface 124 of the processing unit 110 via the internal network connection 106 between the PHY circuit 116 and the PHY circuit 136. In some implementations, the internal network connection 106 is a wired connection (e.g., via an Ethernet cable or a USB cable). In some implementations, the internal network connection 106 is a wireless connection.
[0071] In some implementations, the PHY circuit 136 forms part or all of the input / output interface of the network switch 130. In such implementations, the PHY circuit 136 typically includes multiple physical ports (e.g., Ethernet ports). One of these ports is used to connect the network switch 130 to the processing unit 110. The remaining ports are then used to interconnect any other required components in the internal network.
[0072] Although the network switch 130 includes a BMC 134 and various input / output interfaces (e.g., an Ethernet interface), the BMC 134 is typically not configured to allow out-of-band management via the BMC 134 and PHY circuitry 136. Therefore, while the network switch 130 can connect to the internal network via the PHY circuitry 136, the network switch 130 cannot directly connect to the external network 104 to allow remote access and out-of-band management. Instead, the BMC 118 of the processing unit 110 serves as an intermediary between the external network 104 and the BMC 134 of the network switch 130.
[0073] The firmware executed by the BMC 118 may include instructions that implement a data bridge 126 between the first data interface 119A and the second data interface 119B. In some implementations, the data bridge 126 is a virtual data bridge. In such implementations, the firmware causes the BMC 118 to re-route data from the external network 104 that is intended for the network switch 130 but is received by the BMC 118. If the BMC 118 receives data on the first data interface 119A that is intended for the BMC 134 of the network switch 130, the BMC 118 outputs the data on the second data interface 119B. Because the second data interface 119B is connected to the BMC 134 of the network switch 130, data from the external network 104 that is intended for the network switch 130 can reach the BMC 134, even though the network switch 130 is not directly connected to the external network 104.
[0074] Generally speaking, the data received from the external network 104 includes one or more out-of-band management requests. For example, such management requests may include a request to restart the network switch 130, a request to shut down the network switch 130, a request to adjust the operation of one or more fan modules of the network switch 130, etc. When the BMC 134 receives a management request, it may perform a desired task (e.g., restart the network switch 130) and / or generate a response to the management request. For example, the management request may include a status request. The response to the status request may include information related to the status of the network switch 130 and / or the status of various components of the network switch 130.
[0075] In some implementations, the response to the management request is performed after the desired task is completed and may include confirmation of the task's completion. For example, if BMC 134 receives a request to reboot network switch 130, BMC 134 may reboot network switch 130 and then generate a confirmation message confirming the completion of the reboot process. BMC 134 may transmit the confirmation message to BMC 118 via internal network interface 124, internal network interface 140, and internal network connection 106. BMC 118 receives the response to the management request on second data interface 119B and may output the response on first data interface 119A for transmission to external network 104. Thus, the response may be transmitted to external network 104 via external network interface 122 of processing unit 110.
[0076] In some implementations, a management request to the network switch 130 includes a unique identifier, indicating that the management request is intended for the network switch 130, rather than the processing unit 110 (or any other component). When the BMC 118 receives the management request from the external network 104, the BMC 118 is configured to check whether the management request includes the unique identifier. If the management request is determined to include the unique identifier of the network switch 130, the BMC 118 transmits the management request to the network switch 130. In some implementations, the unique identifier is the media access control (MAC) address of the network switch 130.
[0077] To route management requests (and / or other data) intended for network switch 130, BMC 118 must know the unique identifier (e.g., MAC address) of network switch 130. Therefore, the unique identifier may be transmitted to BMC 118 during configuration of computing system 100 and stored by BMC 118. BMC 118 may then compare the unique identifier included in a received management request with the stored unique identifier of network switch 130. In the illustrated embodiment, BMC 118 includes serial communication interface 128, and BMC 134 includes serial communication interface 142. Serial communication interface 128 and serial communication interface 142 may be interconnected via serial link 108, which in some embodiments is an integrated circuit (IC) bus. BMC 134 may transmit the unique identifier of network switch 130 to BMC 118 via serial communication interfaces 128 and 142 and serial link 108. In some cases, BMC 118 and BMC 134 do not know each other's Internet Protocol (IP) addresses and cannot communicate with each other via internal network connection 106 until the MAC address of network switch 130 is transmitted to BMC 118 via serial communication interfaces 128 and 142 and serial connection 108. However, in other implementations, BMC 134 may transmit a unique identifier of network switch 130 to BMC 118 via internal network interfaces 124 and 140 and internal network connection 106.
[0078] In the illustrated embodiment, the computing system 100 includes a network switch 130 connected to the processing unit 110, enabling out-of-band management of the network switch 130. However, any suitable network device including the network switch 130 may be used. In these embodiments, the network device includes a BMC, which may be coupled to the BMC 118 of the processing unit 110 via the internal network connection 106. Communication between the external network 104 and the network device for out-of-band management is generally performed in the same manner as communication with the network switch 130.
[0079] Figure 2This flowchart illustrates a method 200 for remotely managing a network device (e.g., network switch 130). In step 202, a processing unit's BMC (e.g., BMC 118 of processing unit 110) receives a management request. The management request may be received from an external network (e.g., external network 104). In step 204, the management request is transmitted from the processing unit's BMC to the network device's BMC (e.g., BMC 134 of network switch 130). In some implementations, the management request is transmitted to the network device's BMC via an internal network connection (e.g., internal network connection 106). In step 206, the network device's BMC generates a response to the management request. In some implementations, the response is a confirmation signal confirming that the desired task (e.g., restart or shutdown) has been completed. In other implementations, the response includes information related to the status of the network device and / or components within the network device. In step 208, the response to the management request is transmitted from the network device's BMC to the processing unit's BMC. In some implementations, the response to the management request is transmitted via an internal network. In step 210, the response to the management request is transmitted from the BMC of the processing unit to the external network.
[0080] In some embodiments, method 200 may include additional steps. For example, in some embodiments, the BMC of the processing unit includes a first data interface (e.g., first data interface 119A) connected to an external network, and a second data interface (e.g., second data interface 119B) of the BMC connected to the network device via an internal network connection. Method 200 may include generating a virtual data bridge between the first data interface and the second data interface of the BMC of the processing unit. The management request may be received on the first data interface and output on the second data interface. In such embodiments, method 200 may further include receiving a response to the management request on the second data interface of the BMC of the processing unit, and outputting the response to the management request on the first data interface of the BMC of the processing unit.
[0081] In some implementations, method 200 includes receiving a unique identifier (e.g., a MAC address) of a network device at a baseboard management (BMC) of a processing unit. In such implementations, the BMC may determine whether the management request includes the unique identifier of the network device. If the management request is received at the first data interface and is determined to include the unique identifier of the network device, the BMC of the processing unit may output the management request at the second data interface.
[0082] Figure 33 is a diagram illustrating the flow of network packets through computing system 100. In inbound data flow 310, network interface card (NIC) 304 receives a first set of one or more network packets from user 302 via an external network. NIC 304 may be a NIC of a processing unit, such as NIC 114 of processing unit 110. NIC 304 has an external network interface that connects NIC 304 to the external network. Generally, the first set of one or more network packets includes one or more management requests to be sent to BMC 308. BMC 308 may be a BMC of a network device, such as BMC 134 of network switch 130. The first set of one or more network packets typically includes a unique identifier associated with BMC 308. In some implementations, the unique identifier is a MAC address. The NIC 304 implements a filter (eg, a MAC filter) to determine a desired destination of the first set of one or more network packets based on the unique identifier, so that the NIC 304 may forward the first set of one or more network packets to the identified destination.
[0083] In inbound data flow 312, NIC 304 forwards the first set of one or more network packets to BMC 306 of the processing unit. BMC 306 may be the same as or similar to BMC 118 of processing unit 110. Generally, BMC 306 receives the first set of one or more network packets on a first data interface (which may be a first Ethernet network interface) and outputs the first set of one or more network packets on a second data interface (which may be a second Ethernet network interface). In inbound data flow 314, BMC 306 transmits the first set of one or more network packets from the second data interface to BMC 308 of the network device. BMC 308 may be the same as or similar to BMC 134 of network switch 130. BMC 308 may have a data interface that receives the first set of one or more network packets. Generally, the processing unit and the network device have interconnected internal network interfaces, allowing BMC 306 to communicate with BMC 308.
[0084] BMC 308 is configured to receive the first set of one or more network packets (which may include one or more management requests) and generate a second set of one or more network packets in response. The second set of one or more network packets may include confirmation of any actions taken, status updates, etc. In outbound data flow 316, BMC 308 transmits the second set of one or more network packets from the data interface of BMC 308 to the second data interface of BMC 306 via the internal network interface of the network device and processing unit. In outbound data flow 318, BMC 306 transmits the second set of one or more network packets from the first data interface of BMC 306 to NIC 304. Finally, in outbound data flow 320, NIC 304 transmits the second set of one or more network packets to user 302 via the external network interface of NIC 304.
[0085] Although one or more embodiments of the present disclosure have been illustrated and described, equivalent modifications or improvements will occur to those skilled in the art upon reading and understanding this specification and the accompanying drawings. In addition, although a particular feature of the present disclosure may be disclosed in only one of several embodiments, that feature may be combined with other features in one or more other embodiments if desired or advantageous for any given or specific application.
[0086] Although various embodiments of the present disclosure have been described above, it should be noted that these embodiments are presented for illustrative purposes only and are not intended to be limiting. Numerous modifications may be made to the disclosed embodiments based on the disclosure herein without departing from the spirit and scope of the present disclosure. Therefore, the breadth and scope of the present disclosure should not be limited to any of the foregoing embodiments. Rather, the scope of the present disclosure is to be defined by the appended claims and their equivalents.
Claims
1. A computing system, comprising: A processing unit, comprising a first baseboard management controller (BMC), an external network interface, and a first internal network interface, wherein the external network interface and the first internal network interface are coupled to the first BMC, the first BMC comprises a first data interface and a second data interface, and a virtual data bridge is provided between the first data interface and the second data interface; A network device, comprising a second BMC and a second internal network interface, wherein the second internal network interface of the network device is connected to the first internal network interface of the processing unit; The first BMC is configured to transmit data between the external network and the second BMC via the external network interface, the first internal network interface, and the second internal network interface, wherein the data includes one or more management requests. wherein the first data interface is connected to the external network, and the second data interface is connected to the second BMC of the network device via the internal network; wherein the first BMC of the processing unit is used to receive a unique identification code, the unique identification code being associated with the network device; In response to receiving the one or more management requests on the first data interface, and the one or more management requests being determined to include the unique identification code, the first BMC of the processing unit outputs the management request on the second data interface. 2 . The computing system of claim 1 , wherein the one or more management requests are associated with the network device, and wherein the first BMC is configured to receive the one or more management requests from the external network via the external network interface. 3 . The operating system of claim 1 , wherein the second BMC is configured to generate at least one response to the one or more management requests, and transmit the at least one response to the first BMC via the first internal network interface and the second internal network interface. 4 . The computing system of claim 1 , wherein the first BMC is configured to transmit at least one response to the one or more management requests to the external network via the external network interface. 5 . The operating system of claim 1 , wherein the first data interface of the first BMC forms a portion of the external network interface, and the second data interface of the first BMC forms a portion of the first internal network interface.
6. The computing system of claim 1, wherein the processing unit comprises a first serial communication interface, and the network device comprises a second serial communication interface, the second serial communication interface being coupled to the first serial communication interface via an integrated circuit bus (I2C) connection.
7. A network device management method, the network device management method comprising: On a first baseboard management controller (BMC) of the processing unit, receiving a management request from an external network; transmitting the management request from the first BMC of the processing unit to the second BMC of the network device via the internal network; The second BMC of the network device generates a response to the management request; Transmitting the response to the management request from the second BMC of the network device to the first BMC of the processing unit via the internal network; transmitting the response to the management request from the first BMC of the processing unit to the external network; generating a virtual data bridge between a first data interface of the first BMC of the processing unit and a second data interface of the first BMC of the processing unit; receiving, on the first BMC of the processing unit, a unique identification code associated with the network device; as well as In response to receiving the management request on the first data interface and the management request being determined to include the unique identification code, outputting the management request on the second data interface; The first data interface is connected to the external network, and the second data interface is connected to the second BMC of the network device via the internal network.
Citation Information
Patent Citations
Data transmission system applied to electronic equipment with multiple servo units
TWI301939B