CN115934619A - Asset management method and related device for equipment cabinet server - Google Patents

Asset management method and related device for equipment cabinet server Download PDF

Info

Publication number
CN115934619A
CN115934619A CN202211168681.3A CN202211168681A CN115934619A CN 115934619 A CN115934619 A CN 115934619A CN 202211168681 A CN202211168681 A CN 202211168681A CN 115934619 A CN115934619 A CN 115934619A
Authority
CN
China
Prior art keywords
server
cabinet
signal
server node
bit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211168681.3A
Other languages
Chinese (zh)
Inventor
温瑞军
万侃然
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XFusion Digital Technologies Co Ltd
Original Assignee
XFusion Digital Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by XFusion Digital Technologies Co Ltd filed Critical XFusion Digital Technologies Co Ltd
Priority to CN202211168681.3A priority Critical patent/CN115934619A/en
Publication of CN115934619A publication Critical patent/CN115934619A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Computer And Data Communications (AREA)

Abstract

The application discloses an asset management method and a related device of a cabinet server. The cabinet can be divided into a plurality of installation positions according to the height. And each installation position of the cabinet can be fixedly provided with a signal transmitter. The cabinet can control the signal transmitter on each mounting position to send out signals. When the server node installed at the installation site receives the signal, the server node may transmit equipment information of the server to the cabinet in response to the signal. After receiving the device information of the server node, the cabinet may bind the device information of the server node to the installation location. Thus, when the manager can quickly determine the installation position of the server.

Description

Asset management method and related device for cabinet server
Technical Field
The application relates to the technical field of the Internet of things, in particular to an asset management method and a related device of a cabinet server.
Background
With the continuous development of the internet of things industry, many enterprises need to use a large number of servers, and managers can use cabinets to place the servers. One unit (U) of the international servers is equal to 4.445 cm, in the cabinet, the cabinet can be divided into one or more U bits according to height, each U bit has a height of about 4.445 cm, and the servers can be placed in the cabinet and occupy one or more U bits of the cabinet. In order to manage the IT assets such as the server, the manager needs to quickly and accurately determine the corresponding relationship of the U bit of the server in the cabinet.
The server and the cabinet can be connected by cables with fixed wire sequences. After connection, the corresponding relation between the server and the U bit is recorded manually. In this way, the manager can quickly find the location of the server in the cabinet.
However, by adopting the method, the cable connection between the server and the cabinet requires a fixed line sequence, and the operation and maintenance are inconvenient.
Disclosure of Invention
The application provides an asset management method and a related device of a cabinet server, which realize asset management of the cabinet server.
In a first aspect, the present application provides a rack server, including: a cabinet, a plurality of signal transmitters, at least one server node, and at least one signal receiver; the equipment cabinet comprises a plurality of installation positions, each installation position is provided with a signal transmitter, and each installation position is used for installing a server node; the equipment cabinet is connected with the plurality of signal transmitters and is used for controlling each signal transmitter to send out a signal; each server node is provided with a signal receiver and is connected with the signal receiver arranged on the server node; the equipment cabinet is used for binding the installation position with the equipment information of the server node.
Therefore, when a manager can quickly determine the installation position of any server node installed in the cabinet, asset management is facilitated.
In one possible implementation, the signal transmitter and the signal receiver in the same installation position are located on the same horizontal line, and the signal receiver is arranged on the side, close to the signal transmitter, of the server node.
Therefore, the success rate of the signal receiver for receiving the signal sent by the signal transmitter can be improved.
In one possible implementation manner, the cabinet comprises a processor, an input/output expansion module and a mounting plate; the mounting plate is provided with a plurality of signal transmitters, and the position of each signal transmitter corresponds to the position of one mounting position of the cabinet; the processor is connected with the mounting plate through the input/output expansion module.
In another possible implementation manner, the cabinet includes a processor, an input/output expansion module, and a plurality of mounting plates, the processor is connected to the plurality of mounting plates through the input/output expansion module, each mounting plate is provided with a signal transmitter, and the position of each mounting plate corresponds to the position of one mounting position of the cabinet.
In a possible implementation manner, the signal receiver on the server node is connected with a baseboard management controller of the server node, and the baseboard management controller is used for being connected with the cabinet.
In one possible implementation, the signal transmitter includes: one or more of a visible light emitter, a light emitting diode, or an infrared emitter, and/or a signal receiver comprising: one or more of a light sensitive receiver or an infrared signal receiver.
In one possible implementation manner, the device information of the server node includes: one or more of a device name of the server node, a product serial number, SN, identification of the server node, a media access control, MAC, address of the server node, and an internet protocol, IP, address of the server node.
In a second aspect, the present application provides another rack server, comprising: a cabinet, a plurality of signal receivers, at least one server node, and at least one signal transmitter; the equipment cabinet comprises a plurality of installation positions, each installation position is provided with a signal receiver, and each installation position is used for installing a server node; the cabinet is connected with a plurality of signal receivers; each server node is provided with a signal emitter and is connected with the signal emitter arranged on the server node; the cabinet is used for controlling the signal emitter on each server node to send out signals; the server node is used for sending the equipment information of the server node to the cabinet; the equipment cabinet is used for binding the installation position with equipment information of the server node in response to the signal.
In one possible implementation, the signal receiver is located on the same horizontal line with the signal transmitter in the same installation position, and the signal transmitter is disposed on a side of the server node close to the signal transmitter.
In one possible implementation manner, the cabinet comprises a processor, an input/output expansion module and a mounting plate; the mounting plate is provided with a plurality of signal receivers, and the position of each signal receiver corresponds to the position of one mounting position of the cabinet; the processor is connected with the mounting plate through the input/output expansion module.
In another possible implementation manner, the cabinet includes a processor, an input/output expansion module, and a plurality of mounting plates, the processor is connected to the plurality of mounting plates through the input/output expansion module, each mounting plate is provided with a signal receiver, and the position of each mounting plate corresponds to the position of one mounting position of the cabinet.
In a possible implementation manner, the signal transmitter on the server node is connected with a baseboard management controller of the server node, and the baseboard management controller is used for being connected with the cabinet.
In one possible implementation, the signal transmitter includes: one or more of a visible light emitter, a light emitting diode, or an infrared emitter, and/or a signal receiver comprising: one or more of a light-sensitive receiver or an infrared signal receiver.
In one possible implementation, the device information of the server node includes: one or more of a device name of the server node, a product serial number, SN, identification of the server node, a media access control, MAC, address of the server node, and an internet protocol, IP, address of the server node.
In a third aspect, the present application provides an asset management method for a rack server, including: the cabinet controls a signal emitter arranged at the installation position to send out a signal; if the same installation position is provided with the server node, the signal receiver arranged on the server node receives the signal, and the server node responds to the signal and sends equipment information of the server node to the cabinet, wherein the same installation position is the installation position where the signal transmitter sending the signal is located; the equipment cabinet receives the equipment information of the server node and binds the equipment information of the server node with the same installation position.
In a possible implementation manner, the number of the installation positions is multiple, each installation position is provided with one signal emitter, and the cabinet controls the multiple signal emitters to emit signals according to a first sequence.
In one possible implementation manner, the signal receiver on the server node is connected with a baseboard management controller of the server node, wherein the signal receiver on the server node transmits the received signal to the baseboard management controller, and the baseboard management controller transmits the device information of the server node to the cabinet in response to the signal.
In one possible implementation, the signal transmitter includes: one or more of a visible light emitter, a light emitting diode, or an infrared emitter, and/or a signal receiver comprising: one or more of a light sensitive receiver or an infrared signal receiver.
In one possible implementation, the device information of the server node includes: one or more of a device name of the server node, a product serial number, SN, identification of the server node, a media access control, MAC, address of the server node, and an internet protocol, IP, address of the server node.
In a fourth aspect, the present application provides another method for asset management of a rack server, including: under the condition that the server node is installed at the installation position of the cabinet, the cabinet sends a transmitting instruction to the server node; responding to the transmitting instruction, the server node controls a signal transmitter arranged on the server node to send out a signal; the server node sends the equipment information of the server node to the cabinet; the equipment cabinet receives equipment information of the server node; if the signal receiver arranged at the installation position receives the signal, the cabinet responds to the signal and binds the equipment information of the server node with the same installation position, wherein the same installation position is the installation position where the signal receiver for receiving the signal is located.
In a possible implementation manner, the installation positions are multiple, and each installation position is provided with one signal receiver; the rack sends the transmission instructions to each server node in a second order in the case that at least two server nodes are installed in at least two installation locations.
In a possible implementation manner, the signal transmitter on the server node is connected to a baseboard management controller of the server node, wherein the baseboard management controller receives a transmission instruction sent by the cabinet, and in response to the transmission instruction, the baseboard management controller controls the signal transmitter on the server node to send a signal, and the baseboard management controller sends the device information of the server node to the cabinet.
In one possible implementation, the signal transmitter includes: one or more of a visible light emitter, a light emitting diode, or an infrared emitter, and/or a signal receiver comprising: one or more of a light-sensitive receiver or an infrared signal receiver.
In one possible implementation manner, the device information of the server node includes: one or more of a device name of the server node, a product serial number, SN, identification of the server node, a media access control, MAC, address of the server node, and an internet protocol, IP, address of the server node.
In a fifth aspect, an embodiment of the present application provides a computer storage medium, which includes computer instructions, and when the computer instructions are executed on a rack server, the rack server executes the asset management method of the rack server in any possible implementation manner of the third aspect or the fourth aspect.
In a sixth aspect, an embodiment of the present application provides a computer program product, which, when running on a rack server, causes the rack server to execute the asset management method of the rack server in any possible implementation manner of the third aspect or the fourth aspect.
Advantageous effects of the second aspect to the sixth aspect can be referred to the advantageous effects of the first aspect.
Drawings
Fig. 1A is a schematic architecture diagram of a rack server 10 according to an embodiment of the present disclosure;
fig. 1B is a schematic view of a cabinet 100 according to an embodiment of the disclosure;
fig. 2A is a schematic hardware structure diagram of a cabinet 100 according to an embodiment of the present disclosure;
fig. 2B is a schematic hardware structure diagram of a server 200 according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating a positional relationship between a mounting board, a light emitting diode and a light sensor according to an embodiment of the present disclosure;
FIG. 4 is a schematic structural diagram of a mounting plate according to an embodiment of the present disclosure;
FIG. 5 is a schematic structural diagram of another mounting plate provided in the embodiments of the present application;
fig. 6 is a schematic flowchart of a process of binding device information of a server and a U bit where the server is located according to an embodiment of the present application;
fig. 7 is a schematic flowchart of another process for binding device information of a server and a U bit where the server is located according to the embodiment of the present application;
fig. 8 is a schematic flowchart of an asset management method of a rack server according to an embodiment of the present application;
FIG. 9 is a schematic flowchart of an asset management method for a rack server according to an embodiment of the present application;
fig. 10 is a schematic diagram of hardware module interaction of the rack server 10 executing an asset management method according to an embodiment of the present application;
fig. 11 is a schematic functional module diagram of a rack server 10 according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be described in detail and clearly with reference to the accompanying drawings. Wherein in the description of the embodiments of the present application, "/" indicates an inclusive meaning, for example, a/B may indicate a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.
In the following, the terms "first", "second" are used for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of this application, a "plurality" means two or more unless indicated otherwise.
The following describes an architecture of a rack server provided in an embodiment of the present application.
As shown in fig. 1A, the rack server 10 includes a rack 100, one or more servers (also referred to as server nodes in the embodiments of the present application), one or more signal transmitters, and one or more signal receivers. Wherein the one or more servers may include server 200. Cabinet 100 may be divided into one or more mounting bits, which may be U bits, e.g., U bit 1, U bit 2, U bit 3, and U bit 4, among others. Wherein, the height of each U bit can be 4.445 cm, i.e. 1U equals 4.445 cm. "U" is a unit indicating an external size of the server and is an abbreviation of unit, and a specific size indicated by 1U is determined by the Electronic Industries Association (EIA). It will be understood by those skilled in the art that the actual dimensions of the "U" may be subject to variation during actual manufacturing, or that the particular dimensions of the "U" may be determined by other alternative server external dimensioning units or organizations, without limitation. In some embodiments, a cabinet management board 110 may be further disposed in the cabinet 100 for managing the U-position of the cabinet 100 and the servers disposed in the U-position, and so on.
Server 200 may be placed in cabinet 100 and occupy one of the U-bits in cabinet 100, e.g., server 200 may be placed in U-bit 4 of cabinet 100. It should be noted that, in the embodiment of the present application, the server 200 may be an independent server or a server node, such as a rack server, a blade server, a tower server, and the like. In some embodiments, the server 200 may also be a server unit in a server.
Cabinet 100 may establish a communication connection with server 200. The communication connection may be a wired connection, and in some embodiments, the communication connection may also be a wireless connection, which is not limited herein.
Server 200 may send device information for server 200, which may include identification information, to enclosure 100 via the communication connection. Wherein the identification information may comprise any one or more of: a device name, a Serial Number (SN) number, a Media Access Control (MAC) address, and an Internet Protocol (IP) address, among others. In some embodiments, the device information may include, in addition to the identification information, any one or more of the following: model information, factory hours, maintenance cycles, maintenance records, and the like.
After cabinet 100 receives the device information of server 200 sent by server 200, the location information of server 200 may be determined, and the location information of server 200 includes the U bit where server 200 is located in cabinet 100. The cabinet 100 may store correspondence between the device information of the server 200, the location information of the server 200, the device information of the server 200, and the location information of the server 200.
It is understood that when other servers (e.g., the server 300 and the server 310) are also included in the cabinet server 10, the cabinet 100 may also establish a communication connection with the other servers and store the correspondence between the device information of the server and the location information of the server.
It should be noted that the cabinet 100 may be the cabinet 100 shown in fig. 1A or fig. 1B, or may be a cabinet of another form. In addition, the cabinet 100 may be a single cabinet as shown in fig. 1A or fig. 1B, and in some embodiments, the cabinet 100 may also be a compound cabinet or a room composed of a plurality of cabinets, which is not limited herein.
Cabinet 100 and server 200 may use Near Field Communication (NFC) based U bit identification method to bind server 200 and the U bit where server 200 is located. However, the NFC-based U-bit identification method requires additional NFC tags to be added to the cabinet 100 and an NFC identifier (reader) to be added to the server 200, which results in high implementation cost. And the service life of the NFC tag and the nfcreater is not long.
The embodiment of the application provides an asset management method of a cabinet server. A signal transmitter (e.g., a visible light emitter, a light emitting diode, or an infrared emitter, etc.) may be fixedly disposed at each mounting location of cabinet 100. One or more servers are mounted in the cabinet 100, and each server is provided with a signal receiver (e.g., a light sensor, an infrared signal receiver, etc.). The cabinet can control the signal transmitter on each mounting position to send out signals according to a first sequence. When a server, such as server 200, installed at the installation site receives the signal, server 200 may send equipment information for server 200 to the cabinet in response to the signal. After receiving the device information of the server 200, the rack may bind the device information of the server 200 with the installation site. Thus, when the manager can quickly determine the installation position of any one of the servers installed in the cabinet 100, the asset management is facilitated. Moreover, when the server 200 is connected with the cabinet 100 by cables, the cable connection between the server 200 and the cabinet 100 has no fixed line sequence, and the operation and maintenance of hardware are flexible.
In the following embodiments of the present application, an asset management method of a rack server and a related apparatus provided in the embodiments of the present application will be described by taking an example in which a signal transmitter is a light emitting diode and a signal receiver is a light-sensitive sensor. It is understood that in the embodiment of the present application, the light emitting diode may be replaced by another signal transmitter (e.g., a visible light transmitter or an infrared transmitter), and correspondingly, the light-sensitive sensor may be replaced by a corresponding signal receiver (e.g., an infrared receiver, etc.), which is not limited herein.
The following describes a hardware structure of a cabinet 100 provided in an embodiment of the present application.
As shown in fig. 2A, cabinet 100 may include: processor 101, memory 102, mounting board 103, power module 104, and management network switch 105. Wherein:
the processor 101 may be used to read and execute computer readable instructions. In particular implementations, the processor 101 may mainly include a controller, an operator, and a register. The controller is mainly responsible for decoding the instruction and sending out control signals (such as control signal 1, control signal 2, and the like) for the operation corresponding to the instruction. The arithmetic unit is mainly responsible for storing register operands, intermediate operation results and the like temporarily stored in the instruction execution process. In a specific implementation, the hardware architecture of the processor 101 may be an Application Specific Integrated Circuit (ASIC) architecture, a MIPS architecture, an ARM architecture, or an NP architecture, etc. In some embodiments, some or all of the processors 101 may be provided in the cabinet 100 in the form of a cabinet management board (e.g., the cabinet management board 110 shown in fig. 1A).
Memory 102 is coupled to processor 101 for storing various software programs and/or sets of instructions. In particular implementations, memory 102 may include high speed random access memory, and in some embodiments, memory 102 may also include non-volatile memory. The memory 102 may store a communication program that may be used to communicate with the cabinet 100 or other devices. In other embodiments, the memory 102 may also store an operating system, such as an embedded operating system like uCOS, vxWorks, RTLinux, etc. The memory 102 may be used to store device information of the server 200, location information of the server 200, correspondence of the device information and the location information of the server 200, and the like.
Mounting plate 103 may include one or more mounting locations (also referred to herein as U-locations) corresponding to one or more U-locations of cabinet 100, each U-location having a height of about 4.445 centimeters. In some embodiments, a light emitting diode is disposed in each U-site of the mounting board 103, which can be lit or extinguished. The board 103 may be used to receive a control signal 1 sent by the processor 101. In some embodiments, mounting board 103 may also be used to turn on or off the light emitting diodes on mounting board 103 in response to the control signal 1.
In other embodiments, a light sensor (e.g., a brightness sensor) is disposed in each U-position of the mounting board 103. The light sensor can be used to sense whether the led on the server 200 or other servers is in a light state. In this case, the mounting board 103 may also be used to send the sensing result to the processor 101.
A power module 104, which may be used to provide system power for the cabinet 100 and supply power to each module of the cabinet 100; the support cabinet 100 receives a charging input, etc. The power module 104 may include a Power Management Unit (PMU) and a battery. The power supply management unit can receive external charging input; the electrical signals input by the charging circuit are provided to the battery for charging, and the electrical signals provided by the battery may also be provided to other modules in the cabinet 100 to prevent the battery from being overcharged, overdischarged, shorted, or overcurrent. In some embodiments, power module 104 may also include a wireless charging coil for wirelessly charging cabinet 100. In addition, the power management unit can also be used for monitoring parameters such as battery capacity, battery cycle number, battery health state (electric leakage and impedance) and the like.
The management network switch 105 may be configured to establish a communication connection with a server (e.g., server 200) and receive device information of the server sent by one or more servers (e.g., server 200). The management network switch 105 may establish a communication connection with the server 200 by using a wired connection such as a cable connection. In some embodiments, the management network switch 105 may also establish a wireless communication connection with the server 200.
Optionally, in some embodiments, cabinet 100 may also include keys, sensors (not shown in fig. 2A), and the like. The key can be a physical key or a touch key (used in cooperation with the touch sensor) and the like, and is used for triggering operations such as startup, shutdown and reset. The touch sensor can detect touch operations of a user, such as single click, double click, multiple click, long press, repeated press and the like, and can also perform user fingerprint identification so as to authenticate the identity of the user in service scenes such as security sensitivity and the like.
It is understood that cabinet 100 shown in fig. 2A is merely an example, and that cabinet 100 may have more or fewer components than shown in fig. 2A, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 2A may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The following describes a hardware configuration of the server 200 according to an embodiment of the present application.
As shown in fig. 2B, the server 200 may include: one or more network device processors 201, memory 202, communication interface 203, transmitter 205, receiver 206, coupler 207, sensor module 209, and Baseboard Management Controller (BMC) 210, optionally, server 200 may also include antenna 208. These components may be connected by a bus 204 or otherwise, as illustrated in FIG. 2B by a bus. Wherein:
the communication interface 203 may be used for the server 200 to communicate with other communication devices, for example with electronic devices used by consumers of items. Specifically, the communication interface 203 may be a 3G communication interface, a Long Term Evolution (LTE) (4G) communication interface, a 5G communication interface, a WLAN communication interface, a WAN communication interface, or the like. Not limited to wireless communication interfaces, the server 200 may also be configured with a wired communication interface 203 to support wired communication.
In some embodiments of the present application, the transmitter 205 and the receiver 206 may be considered as one wireless modem. The transmitter 205 may be configured to transmit signals output by the network device processor 201. Receiver 206 may be used to receive signals. In the server 200, the number of the transmitters 205 and the receivers 206 may be one or more. The antenna 208 may be used to convert electromagnetic energy in the transmission line to electromagnetic energy in free space, or vice versa. The coupler 207 may be used to multiplex the mobile communications signal for distribution to a plurality of receivers 206. It is to be appreciated that the antenna 208 of the network device can be implemented as a large-scale antenna array.
The memory 202 is coupled to the network device processor 201 for storing various software programs and/or sets of instructions. In particular, the memory 202 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
The memory 202 may store an operating system (hereinafter referred to as a system), such as an embedded operating system like uCOS, vxWorks, RTLinux, etc. The memory 202 may also be used to store an implementation program on the side of the server 200 in the asset management method of the rack server provided in one or more of the following embodiments of the present application.
In embodiments of the present application, the network device processor 201 may be configured to read and execute computer readable instructions. In particular, the network device processor 201 may be used to invoke programs stored in the memory 202.
In some embodiments, the server 200 may include a sensor module 209 that may include one or more light-sensitive sensors (e.g., a brightness sensor). The sensor module 209 may be configured to sense whether the light emitting diode in the U-position corresponding to the position of the server 200 in the cabinet is in a light emitting state, and send a sensing result to the bmc 210.
In other embodiments, the server 200 may replace the sensor module 209 with a light emitting diode or other signal emitter (not shown in FIG. 2B). For example, in the case of replacing the sensor module 209 with a light emitting diode, the server 200 may be configured to receive the control signal 2 sent by the processor 101 and determine whether to light or extinguish the light emitting diode based on the control signal 2.
The bmc 210 may be configured to receive a sensing result of the sensor module 209. Baseboard management controller 210 can be connected to sensor module 209. When the sensor module 209 senses that the light emitting diode in the U-bit corresponding to the position of the server 200 in the cabinet is in a light emitting state, the bmc 210 may be configured to send the device information of the server 200 to the management network switch 105 in the cabinet 100. Baseboard management controller 210 may also be used to connect to cabinet 100 when server 200 is connected to cabinet 100 using a cable.
It is to be understood that the server 200 shown in fig. 2B is merely an example, and that the server 200 may have more or fewer components than shown in fig. 2B, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 2B may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The following describes a schematic positional relationship among the mounting board 103, the light emitting diode, and the light sensor provided in the embodiment of the present application.
As shown in fig. 3, a mounting board 103 is disposed in the cabinet 100, and the mounting board 103 may be divided into one or more U bits according to height, for example, U bit 1, U bit 2, U bit 3, U bit 4, and U bit 5, where the one or more U bits correspond to the one or more U bits that are divided according to height by the cabinet 100. At least one light emitting diode is disposed on each U-site of the mounting board 103. For example, a light emitting diode 301 is disposed on U bit 1, a light emitting diode 302 is disposed on U bit 2, a light emitting diode 303 is disposed on U bit 3, a light emitting diode 304 is disposed on U bit 4, a light emitting diode 305 is disposed on U bit 5, and so on. Meanwhile, one or more servers are also placed in the cabinet 100, such as a server 200 placed in U1 of the cabinet 100, and so on. The server 200 is provided with a light sensor 306 on a side adjacent to the mounting board 103. That is, the light-sensitive sensor 306 may sense that the corresponding led 301 is in a light-emitting state or a light-off state, for example, when the cabinet 100 controls the led 301 on U position 1 to emit light, the server 200 on U position 1 of the cabinet 100 may sense that the led 301 is in a light-emitting state through the light-sensitive sensor 306. When cabinet 100 controls light emitting diode 301 on U position 1 to go out, server 200 on U position 1 of cabinet 100 may sense that light emitting diode 301 is in the off state through light sensor 306.
Similarly, if other servers are placed on other U bits (e.g., U bit 2, U bit 3, U bit 4, etc.) of the cabinet 100, the other servers may determine whether the light emitting diode corresponding to the U bit where the server is located is in a light emitting state through the light sensor arranged on the server.
Preferably, the light emitting diode on the mounting plate and the light sensor arranged on the server on the corresponding U-position can be on the same horizontal line.
In addition, optionally, as shown in fig. 3, baffles 307 may be further disposed on the mounting plate between different U positions. Therefore, the light sensor on the server 200 can be prevented from sensing the light emitted by the light emitting diode on other U positions to influence the sensing result.
It should be noted that in some embodiments, a light sensor may be disposed on each U bit of the mounting board 103, and a light emitting diode may be disposed on the server 200. In this case, whether the server 200 is placed on the U-site or not and whether the led on the server 200 is turned on or not may be sensed by the light sensor on the mounting board 103.
The following describes a schematic structural diagram of the mounting plate 103 provided in the embodiment of the present application.
In some embodiments, the mounting plate 103 may use a full plate design.
As shown in fig. 4, the mounting board 103 may include a whole board 400, and a general-purpose input/output (GPIO) expansion module 410, one or more light emitting diodes such as a light emitting diode 401, a light emitting diode 402, a light emitting diode 403, a light emitting diode 404, a light emitting diode 405, and the like are disposed in the whole board 400. The whole board 400 may be divided into a plurality of U-bits according to height, and each U-bit of the whole board 400 is provided with a light emitting diode. For example, a light emitting diode 401 is disposed on U bit 1, a light emitting diode 402 is disposed on U bit 2, a light emitting diode 403 is disposed on U bit 3, a light emitting diode 404 is disposed on U bit 4, a light emitting diode 405 is disposed on U bit 5, and so on. Each light emitting diode is connected with a GPIO expansion module 410, and the GPIO expansion module 410 is connected with a cabinet management board. In this embodiment, a part or all of the processors 101 of the cabinet 100 are disposed on the cabinet management board. The GPIO expansion module 410 may receive the control signal 1 sent by the cabinet management board, and control the lighting or lighting-off of the light emitting diodes on the entire board 400 based on the control signal 1 and the corresponding relationship between the pins of the GPIO expansion module 410 and the U bits. Taking the led 401 on U bit 1 as an example, when the GPIO extension module 410 receives the control signal 1 indicating to light the led 401 corresponding to U bit 1, in response to the control signal 1, the GPIO extension module 410 may light the led 401 on U bit 1 through the pin corresponding to U bit 1 on the GPIO extension module 410.
In other embodiments, the mounting plate 103 may also be a discrete single plate design.
As shown in fig. 5, the board 103 may include a GPIO expansion module 500 and one or more boards, such as board 510, board 520, board 530, board 540, and board 550. Each board is provided with a light emitting diode, and each board corresponds to one U bit of the cabinet 100. For example, as shown in fig. 5, a single board 510 corresponds to U bit 1 of the cabinet 100, and a light emitting diode 501 is disposed on the single board 510; the single board 520 corresponds to U position 2 of the cabinet 100, and the light emitting diode 502 is disposed on the single board 520; the single board 530 corresponds to U bit 3 of the cabinet 100, and the light emitting diode 503 is disposed on the single board 530; the single board 540 corresponds to U-bit 4 of the cabinet 100, and the light emitting diode 504 is disposed on the single board 540; the single board 550 corresponds to U bit 5 of the cabinet 100, and the light emitting diode 505 is disposed on the single board 550, and so on. Each single board is connected with the GPIO expansion module 500, and the GPIO expansion module 500 is connected with the cabinet management board. The GPIO expansion module 500 may receive the control signal 1 sent by the cabinet management board, and control the on/off of the leds on the board based on the control signal 1 and the correspondence between the pins of the GPIO expansion module 500 and the respective U bits. The specific manner of the GPIO extension module 500 controlling the light emitting diodes to be turned on or off may refer to the related description in the embodiment shown in fig. 4.
It should be understood that the structure of the mounting plate 103 shown in fig. 4 and 5 is only an example, and in the embodiment of the present application, other mounting plate designs (for example, a combination of a whole plate and a separate single plate, etc.) may also be adopted, and the present application is not limited thereto.
It should be noted that, when the light-sensitive sensor is disposed on the mounting board 103 and the light-emitting diode is not disposed, the mounting board 103 may also adopt a whole board design or a discrete single board design, and the specific structure may refer to the related content in the embodiment shown in fig. 4 or fig. 5, and is not described herein again. In addition, in the embodiment of the present application, the light emitted by the light emitting diode may be visible light or invisible light. The brightness of the light-emitting diode in the light-emitting state and the size of the light-emitting diode are not limited.
In other embodiments, the light emitting diode and the light sensor in the above embodiments may also be replaced by an infrared emitting device and an infrared receiving device, respectively, and the cabinet management board controls the infrared emitting device to turn on or off.
In one possible implementation, the mounting board 103 may also be integrally connected to the cabinet management board 110, and the application is not limited thereto.
A specific process for binding the device information of the server and the U bit where the server is located provided in the embodiment of the present application is described below.
Taking the U bit 1 of the cabinet 100 as an example, as shown in fig. 6, a specific process for binding the device information of the server and the U bit where the server is located may include the following steps:
s601, the cabinet 100 lights the led on U position 1.
Cabinet 100 may sequentially illuminate diodes on different U-bits in a first order. The first sequence may be a sequence in which all U bits in the cabinet 100 are arranged from top to bottom, may also be a sequence in which all U bits in the cabinet 100 are arranged from bottom to top, and may also be another sequence in which all U bits in the cabinet 100 can be traversed, which is not limited herein.
Take five U bits, i.e., U bit 1, U bit 2, U bit 3, U bit 4, and U bit 5, of the cabinet 100 as an example:
when the first order is U bit 1, U bit 2, U bit 3, U bit 4, and U bit 5, the cabinet 100 may first turn on the leds on U bit 1 based on the first order, while keeping the leds on the other U bits off. After lighting the led on U bit 1, the cabinet 100 may light the led on U bit 2 and extinguish the led on U bit 1 after performing step S605 described below.
When the first sequence is U bit 5, U bit 4, U bit 3, U bit 2, and U bit 1, the cabinet 100 may sequentially turn on the light emitting diodes on U bit 5, U bit 4, U bit 3, U bit 2, and U bit 1 based on the first sequence, and when the light emitting diode on any one of the U bits is in a light emitting state, the light emitting diodes on the other U bits all keep in a light off state.
S602, the server 200 recognizes that the led on U bit 1 is in a light emitting state.
Since the server 200 is located on the U position 1 of the cabinet 100, when the cabinet 100 lights the led on the U position 1, the light sensor on the server 200 can sense the led on the U position 1 to emit light.
S603, server 200 sends the device information of server 200 to cabinet 100.
When server 200 senses that the led on U bit 1 is in a light emitting state, server 200 may send device information of server 200 to cabinet 100, where the device information of server 200 may include identification information, and the identification information may include any one or more of a device name, an SN address, a MAC address, and an IP address.
In some embodiments, the device information of the server 200 may further include any one or more of the following: model information of the server 200, factory time, maintenance period, maintenance record, and the like.
S604, the cabinet 100 determines the location information of the server 200, and the location information of the server 200 is used to indicate the U bit of the server 200 in the cabinet 100.
After cabinet 100 receives the device information of server 200, it may determine that the server placed in U bit 1 of cabinet 100 is server 200 based on that the led in U bit 1 is in the light-emitting state, that is, it is determined that the location information of server 200 is: server 200 is placed in U bit 1 of cabinet 100.
In some embodiments, cabinet 100 may also determine that U bit of server 200 located in cabinet 100 is U bit 1 based on the light emitting diode lit in step S601 being the light emitting diode on U bit 1.
S605, the rack 100 stores the correspondence between the device information and the location information of the server 200 and the device information and the location information of the server 200.
For example, the cabinet 100 may store the device information of the server 200, the location information of the server 200, and the corresponding relationship between the two in the form of table 1 below.
TABLE 1 correspondence of device information and location information for a server
Server identification U position
192.168.0.112 U bit 1
As shown in Table 1, table 1 may include a server identification column that may be used to prompt for identification information of the server, such as an IP address, MAC address, etc., and a U-bit column that may be used to prompt for location information of the server, i.e., the U bit in which the server is located in cabinet 100, such as U bit 1. As can be seen from table 1, the IP address of the server 200 is 192.168.0.112, and the location of the server 200 is U bit 1 in the cabinet 100.
For another example, the cabinet 100 may also store the device information of the server 200, the location information of the server 200, and the correspondence relationship between the two in the form of the following table 2.
Table 2 correspondence between device information and location information of server
Figure BDA0003862602810000111
As shown in table 2, table 2 may include a server identification column, a factory time column, a maintenance record column, and a U-bit column, where the server identification column may be used to prompt identification information of the server, for example, an IP address of 192.168.0.112, the factory time column may be used to prompt factory time of the server, and the maintenance record column may be used to prompt maintenance records of the server. The U-bit column may be used to prompt location information of the server, i.e., the U-bit, e.g., U-bit 1, where the server is located in cabinet 100. As can be seen from table 1, the IP address of the server 200 is 192.168.0.112, the factory time is 2019, 9 and 27 days, and the location of the server 200 is U bit 1 in the cabinet 100. Two maintenance records are provided for the server 200, and one maintenance record shows that the server 200 has performed routine maintenance once in 2021 year, 1 month and 1 day. Another maintenance record shows that server 200 has overhauled for circuit failure problems at 30 days 6 months 2022.
Further illustratively, when a plurality of servers (including the server 200) are placed in the cabinet 100, the cabinet 100 may also have correspondence between the device information and the location information of the plurality of servers.
TABLE 3 correspondence between device information and location information of a server
Server identification U position
192.168.0.112 U bit 1
113.89.35.188 U bit 2
As shown in Table 3, table 3 may include a server identification column that may be used to prompt identification information of the server, such as an IP address, SN address, MAC address, etc., and a U-bit column that may be used to prompt location information of the server, i.e., the U-bit in which the server is located in cabinet 100. As can be seen from Table 3, the server having IP address 192.168.0.112 is located at U bit 1 in the cabinet 100, and the server having IP address 113.89.35.188 is located at U bit 2 in the cabinet 100.
It should be noted that table 1, table 2 and table 3 are only examples, and in this embodiment, when storing the correspondence between the device information and the location information of the server 200, the cabinet 100 may store more or less device information of the server 200 than in table 1 and table 2, for example, the device model, the device name and the maintenance period of the server 200.
Thus, when the manager of the server needs to find the server 200, the specific location of the server 200 in the cabinet 100 can be determined by looking up the location information of the server 200 stored in the cabinet 100 based on any item of the device information of the server 200 (e.g., IP address, MAC address, device name, etc.). Moreover, the cost is low by adopting the method, in addition, the cable connection between the server 200 and the cabinet 100 does not need to adopt fixed line sequence connection, and the hardware operation and maintenance are flexible.
In some embodiments, when the cabinet 100 lights the leds on the other U-bit than U-bit 1, taking U-bit 3 as an example, if another server, such as the server 300, is placed on U-bit 3, the server 300 may also perform the steps performed by the server 200 in the embodiment shown in fig. 6, send the identification information of the server 300 to the cabinet 100 when sensing the leds on U-bit 3 to emit light, determine the location information of the server 300 as U-bit 3 of the cabinet 100 by the cabinet 100, and store the corresponding relationship between the location information of the server 300 and the identification information of the server 300. If no other server is placed on U bit 3, i.e. U bit 3 of the cabinet 100 is idle, the cabinet 100 may light up the leds on the next U bit based on the first sequence after waiting for a certain time (e.g. 15 seconds or 30 seconds).
With the above method, after the cabinet 100 sequentially lights up the leds on all the U-bits based on the first order, the cabinet 100 may store the location information of all the servers placed in the cabinet 100. Even with many servers in cabinet 100, an administrator can quickly find the location of any of the many servers.
In some embodiments, cabinet 100 may maintain the status of the leds on one U-bit while illuminating the leds on the other U-bit. Taking lighting the led on U bit 1 as an example, in addition to the led on U bit 1, the cabinet 100 may keep the led that was previously in the lighting state, and keep the led that was previously in the extinguishing state. In this case, the server 200 may sense the state change of the light emitting diode through the light sensor, and when the light sensor senses that the light emitting diode on the corresponding U bit changes from the off state to the light emitting state, that is, senses that the light emitting diode is turned on, the server 200 sends the identification information of the server 200 to the cabinet 100.
Note that the following description is given. The embodiment of the application does not limit the brightness, the color and the like of the light emitting diode.
The embodiment of the application also provides another specific flow for binding the device information of the server and the U bit where the server is located.
Taking the server 200 located in the U position 1 of the cabinet 100 as an example, as shown in fig. 7, when the light emitting diode is disposed on the server 200 and the cabinet 100 is disposed with the light sensor, another specific process for binding the device information of the server and the U position where the server is located may include the following steps:
s701, the cabinet 100 sends an illumination signal to the server 200 for instructing the server 200 to illuminate the light emitting diode on the server 200.
Cabinet 100 may send the illumination signals to the servers (including server 200) disposed in cabinet 100 in a second order. The second order is the ordering of all servers placed in cabinet 100. The present application does not limit the specific ranking results. The control signal 2 in the above embodiment may include a lighting signal.
S702, the server 200 lights the light emitting diode on the server 200 in response to the lighting signal.
S703, the cabinet 100 determines that the U-bit of the light sensor sensing the light emitting of the led is the sensing result.
After the led on the server 200 is lit, the light sensor disposed on the U position 1,U position 1 of the cabinet 100 in which the server 200 is located can sense the led is lit. That is, cabinet 100 may determine that the sensing result is U bit 1.
S704, server 200 sends the device information of server 200 to cabinet 100.
The device information of the server 200 may refer to the related description in step S603 shown in fig. 6 described above.
In some embodiments, server 200 may send equipment information for server 200 to cabinet 100 after receiving the illumination signal. In other embodiments, server 200 may also send the equipment information of server 200 to cabinet 100 before receiving the lighting signal sent by cabinet 100, which is not limited herein.
S705, the cabinet 100 determines the location information of the server 200 based on the sensing result, and the location information of the server 200 is used for indicating the U bit where the server 200 is located in the cabinet 100.
The location of server 200 is used to indicate that the U bit in cabinet 100 where server 200 is located is U bit 1.
The cabinet 100 may determine that the U bit of the server 200 located in the cabinet 100 is U bit 1 based on the object of the lighting signal sent by the cabinet 100 in step S701 and the sensing result.
In other embodiments, in the case that server 200 sends the identification information of server 200 to cabinet 100 in response to the lighting signal, cabinet 100 may also determine that U bit of server 200 in cabinet 100 is U bit 1 based on the identification information sent by server 200 and the sensing result.
S706, cabinet 100 stores the correspondence between the device information and the location information of server 200 and the device information and the location information of server 200.
The specific way for the cabinet 100 to store the device information and the location information of the server 200 and store the corresponding relationship between the device information and the location information of the server 200 may refer to the related description in step S605 in the embodiment shown in fig. 6, and details are not repeated here.
When a server (e.g., the server 300) other than the server 200 is placed in the cabinet 100, taking the server 300 located at the U-slot 3 as an example, the server 300 may also perform the steps performed by the server 300 in the embodiment shown in fig. 7 after receiving the lighting signal, so as to light the light emitting diode on the server 300. When the cabinet 100 senses the light emitting diode to emit light through the light-sensing sensor on the U bit 3, the cabinet 100 may determine the location information of the server 300 as the U bit 3 of the cabinet 100 based on the sensing result, and store the corresponding relationship between the location information of the server 300 and the device information of the server 300, and between the location information of the server 300 and the device information.
Similarly, in the embodiment shown in fig. 7, when the light emitting diode on one of the servers placed in the cabinet 100 emits light, the cabinet 100 may control the light emitting diodes on the other servers to be in the off state, and in other embodiments, the light emitting diodes on the other servers may also be in the same state as the previous state, which may specifically refer to the relevant content in the embodiment shown in fig. 6, and details are not described here.
The following describes a specific flow of an asset management method of a rack server according to an embodiment of the present application.
As shown in fig. 8, a specific process of the asset management method of the rack server may include the following steps:
s801, the cabinet 100 starts U-bit identification and determines the lighting sequence of the U-bit.
After the cabinet 100 is powered on, U-bit identification is started to determine the lighting sequence of the U-bits. In some embodiments, cabinet 100 may also initiate U-bit identification in response to an administrator input, or the like.
The U-bit lighting order is the order of all U bits (or all U bits with servers placed) on the cabinet 100. The U-site illumination sequence may be used to indicate the sequence in which cabinet 100 illuminates the leds on different U-sites.
S802, the cabinet 100 determines, based on the U-bit lighting sequence, that the U bit where the next diode to be lit is located is the U bit to be identified.
If cabinet 100 has just started U-bit identification, cabinet 100 may determine, based on the U-bit lighting order, that the first U-bit in the U-bit lighting order is the U-bit to be lit.
For example, taking U-bit lighting order of U-bit 1, U-bit 2, U-bit 3, U-bit 4, and U-bit 5 as an example, when cabinet 100 starts U-bit identification, cabinet 100 may determine U-bit 1 as the U-bit to be identified.
If cabinet 100 has completed identifying one or more U bits, cabinet 100 may determine a new U bit to be identified based on the U bit lighting order and the current U bit to be identified.
Further illustratively, still taking the U-bit lighting order as U-bit 1, U-bit 2, U-bit 3, U-bit 4, and U-bit 5 as an example, in the case that the current U-bit to be identified is U-bit 3, that is, in the case that the cabinet server 10 has just completed identifying U-bit 3, the cabinet 100 may determine that the next U-bit to be lit 4 is a new U-bit to be identified based on the U-bit lighting order.
And S803, the cabinet 100 lights the light emitting diode on the U position to be identified.
After determining the U-bit to be identified, cabinet 100 may illuminate the light emitting diode on the U-bit to be identified.
S804, the server identifies that the light-emitting diode on the U bit to be identified is in a light-emitting state.
The servers in steps S804 to S807 are servers on which U bits to be recognized are placed, and it should be noted that when U bits to be recognized are changed, the servers in steps S804 to S807 are servers on which new U bits to be recognized can only be placed strangely at last.
S805, the server sends the equipment information of the server to the cabinet 100.
S806, the cabinet 100 determines the location information of the server, and the location information of the server is used for indicating the U bit of the server in the cabinet 100.
S807, the cabinet 100 stores the correspondence between the device information and the location information of the server and the device information and the location information of the server.
For specific contents of step S803 to step S807, reference may be made to the related descriptions in step S601 to step S605 shown in fig. 6, which are not repeated herein.
S808, the cabinet 100 extinguishes the LEDs on the U position to be identified.
Step S808 is an optional step.
In other embodiments, the cabinet 100 may also control the lighting time of the leds on the U-bit to be identified, and extinguish the leds on the U-bit to be identified after the leds are lit for a certain time (e.g., the first time).
S809, the cabinet 100 determines whether the U bit to be identified is the last U bit to be identified based on the U bit lighting sequence.
For example, taking U-bit lighting order of U-bit 1, U-bit 2, U-bit 3, U-bit 4, and U-bit 5 as an example, in the case that the current U-bit to be identified is U-bit 3, the cabinet 100 may determine that there are other U-bits after U-bit 3 based on the U-bit lighting order. In the case that the current U bit to be identified is U bit 5, cabinet 100 may determine that there are no other U bits after U bit 5 based on the U bit lighting order.
When the cabinet 100 determines that the U bit to be identified is the last U bit, the cabinet 100 performs the following step S810, and ends the U bit identification.
When the cabinet 100 determines that the U bit to be identified is not the last U bit, the cabinet 100 performs the above steps S802 to S809, re-determines a new U bit to be identified, and identifies the new U bit to be identified.
S810, the cabinet 100 finishes the U bit identification.
Another method for managing assets of a rack server provided in the embodiments of the present application is described below.
As shown in fig. 9, another specific process of the asset management method of the rack server may include the following steps:
s901, the cabinet 100 starts U bit identification and determines the lighting sequence of the servers.
Cabinet 100 may begin U-bit identification after power up to determine the server lighting sequence. In some embodiments, cabinet 100 may also initiate U-bit identification in response to an administrator input, or the like.
The server lighting sequence is a sequence of all servers placed in the cabinet 100, and is used to instruct the cabinet server 10 to light the leds on different servers.
S902, the rack 100 determines the server of the next lit diode as the server to be bound based on the server lighting sequence.
If cabinet 100 begins U-bit identification, cabinet 100 may determine that the first server in the server lighting sequence is the server to be bound based on the server lighting sequence.
For example, taking the server lighting sequence as server 200, server 300, and server 310 as an example, when cabinet 100 just starts U-bit identification, cabinet 100 may determine that server 200 is a server to be bound.
If cabinet 100 has completed the identification of one or more U bits, then cabinet 100 may determine a new server to bind based on the server lighting order and the current server to bind.
Further illustratively, still taking the example that the server lighting order is the server 200, the server 300 and the server 310, in the case that the current server to be bound is the server 200, that is, in the case that the rack server 10 has just completed the identification of the U bit where the server 200 is located, the rack 100 may determine that the next server 300 to be lit is the new server to be bound based on the server lighting order.
And S903, the cabinet 100 sends a lighting signal to the server to be bound, and the lighting signal is used for indicating the server to be bound to light the light emitting diode.
And S904, responding to the lighting signal, and lighting the light emitting diode on the server to be bound by the server to be bound.
S905, the cabinet 100 determines that the U bit where the light sensor sensing the light emitting of the light emitting diode is located is a sensing result.
S906, the to-be-bound server sends the device information of the to-be-bound server to the cabinet 100.
S907, the cabinet 100 determines the location information of the servers to be bound based on the sensing result, and the location information of the servers is used for indicating the U bits of the servers in the cabinet 100.
S908, the cabinet 100 stores the device information and the location information of the server to be bound, and the device information and the location information of the server to be bound.
For the specific contents of step S903 to step S908, reference may be made to the related descriptions in step S701 to step S706 shown in fig. 7, which are not described herein again.
And S909, the server to be bound extinguishes the light emitting diode on the server to be bound.
The to-be-bound server may control the light emitting time of the light emitting diode, and after the light emitting diode continues to emit light for a certain time (e.g., a second time), the to-be-bound server may extinguish the light emitting diode.
In other embodiments, after the cabinet 100 determines the location information of the server to be bound, an off instruction may be sent to the server to be bound, and the server to be bound may also receive and respond to the off instruction sent by the cabinet 100 to turn off the light emitting diode.
S910, the cabinet 100 judges whether the server to be bound is the last server based on the server lighting sequence.
For example, taking the server lighting sequence as the server 200, the server 300 and the server 310 as an example, in the case that the current server to be bound is the server 200, the cabinet 100 may determine that there are other servers after the server 200 based on the server lighting sequence. In the case where the current server to be bound is server 310, cabinet 100 may determine that no other servers exist after server 310 based on the server lighting order.
When the cabinet 100 determines that the server to be bound is the last server, the cabinet 100 performs the following step S911, and ends the U-bit identification.
When the cabinet 100 determines that the server to be bound is not the last server, the cabinet 100 performs the steps S902 to S910, re-determines a new server to be bound, and identifies the U bit where the new server to be bound is located.
S911, the cabinet 100 finishes the U-bit identification.
Fig. 10 illustrates a hardware module interaction diagram of the rack server 10 executing the asset management method of the rack server according to the embodiment of the present application.
The following describes hardware module interaction during the process of the rack server 10 executing the asset management method of the rack server, taking the server 200 placed in U bit 1 to identify U bit 1 as an example.
After determining that U-bit to be identified is U-bit 1, cabinet management board 110 in cabinet 100 (or processor 101 of cabinet 100) may send an illumination signal to board 103 in cabinet 100 to instruct board 103 to illuminate the light emitting diode on U-bit 1.
The mounting board 103, after receiving the lighting signal sent by the cabinet management board 110, lights the led on U bit 1 in response to the lighting signal.
After the led on U bit 1 is turned on, the sensor module 209 in the server 200 may sense that the led is turned on and send the light sensing information to the bmc 210 in the server 200, where the light sensing information is used to notify the bmc 210 that the led on U bit of the server 200 is in a turned on state.
The baseboard management controller 210, after receiving the exposure information, can send the device information of the server 200 to the management network switch 105.
The management network switch 105 may send the device information of the server 200 sent by the baseboard management controller 210 to the cabinet management board 110 of the cabinet 100.
The cabinet management board 110 may determine the location information of the server 200 based on the device information of the server 200 and the U-bit to be identified, that is, the server 200 is located on U-bit 1 of the cabinet 100.
After U bit 1 is identified, cabinet server 100 may update the U bit to be identified, and repeat the above process to complete the identification of other U bits in cabinet 100, which is not described herein again.
It should be noted that, in other embodiments, the light emitting diodes may also be disposed in the server 200, and the light sensor may be disposed on the mounting plate 103 of the cabinet 100 corresponding to the U position. In this case, cabinet management board 110 may send an illumination signal to baseboard management controller 210 of server 200, in response to which baseboard management controller 210 may control light-emitting diodes on server 200 to emit light, and cabinet 100 may determine location information of server 200 according to the light exposure result of mounting board 103, which will not be described in detail herein.
It is to be understood that the above-mentioned interaction of the hardware modules of the rack server 10 shown in fig. 10 to perform the asset management method of the rack server is only an example, and the modules in the rack server 10 may also adopt other interaction manners, and the present application is not limited thereto.
The following describes functional modules of the rack server 10 provided in the embodiment of the present application.
As shown in fig. 11, the rack server 10 may include a management module 11, a lighting module 12, a management network switching module 13, an information base 14, a brightness perception module 15, and a server management module 16. Wherein, the management module 11, the lighting module 12, the management network exchange module 13 and the information base 14 are located in the cabinet 100, and the brightness perception module 15 and the server management module 16 are located in the server 200.
The management module 11 may send a control signal (e.g., control signal 1, control signal 2, etc.) to the lighting module, and control the light emitting diodes in the lighting module 12 to be turned on or off. The management module 11 may also receive the device information of the server 200 transmitted by the management network switching module 13, and the like. The management module 11 may also determine location information of the server 200, for example, determine location information of the server 200 based on the device information of the server 200 and the states of the light emitting diodes in the lighting module 12, or determine location information of the server 200 based on the device information of the server 200 and the control signal, and the like. The management module 11 may transmit the location information of the server 200 and the device information of the server 200 to the information repository 14.
The lighting module 12 may receive the control signal sent by the management module 11, and control the light emitting diodes in the lighting module 12 to be turned on or off based on the control signal.
The management network switching module 13 may receive the device information of the server 200 transmitted by the server management module 16. The management network switching module 13 may transmit the received device information of the server 200 to the management module 11.
The information repository 14 may receive and store the correspondence relationship between the location information of the server 200, the device information of the server 200, the location information of the server 200, and the device information of the server 200, which are transmitted by the management module 11.
The brightness sensing module 15 may determine a sensing result based on one or more light emitting diodes in a lighting state in the lighting module 12, and transmit the sensing result to the server management module 16.
The server management module 16 may receive the sensing result sent by the brightness sensing module 15, and send the device information of the server 200 to the management network switching module 13.
It should be noted that in other embodiments, the lighting module 12 may be located in the server 200, and the brightness sensing module 15 may be located in the cabinet 100. In this case, the brightness sensing module 15 determines a sensing result based on one or more light emitting diodes in a lighting state in the lighting module 12, and transmits the sensing result to the management module 11.
It is understood that the above-mentioned structure of the functional modules of the rack server 10 shown in fig. 11 is only an example, and the rack server 10 may further include more or less functional modules than those shown in fig. 11, and the present application is not limited thereto.
It should be noted that, in any of the above embodiments of the present application, the light emitting diode may also be replaced by another signal emitter, and the light-sensitive sensor may also be replaced by another signal receiver, which is not limited herein.
The embodiments of the present application can be combined arbitrarily to achieve different technical effects.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the present application are generated, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.
In short, the above description is only an example of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements and the like made in accordance with the disclosure of the present invention are intended to be included within the scope of the present invention.

Claims (13)

1. A rack server comprising a rack, a plurality of signal transmitters, at least one server node, and at least one signal receiver;
the cabinet comprises a plurality of installation positions, each installation position is provided with one signal transmitter, and each installation position is used for installing one server node;
the cabinet is connected with the signal transmitters and is used for controlling each signal transmitter to send out a signal;
each server node is provided with one signal receiver and is connected with the signal receiver which is arranged on the server node;
the signal transmitter and the signal receiver in the same installation position correspond to the position of the signal receiver when at least one server node is installed in at least one installation position, the signal receiver is used for receiving the signal sent by the signal transmitter in the same installation position, the server node in the same installation position is used for responding to the signal and sending the equipment information of the server node to the cabinet, and the cabinet is used for binding the installation position with the equipment information of the server node.
2. The cabinet server of claim 1, wherein the signal transmitter is located at the same horizontal line as the signal receiver in the same mounting location, and the signal receiver is disposed on a side of the server node adjacent to the signal transmitter.
3. The cabinet server of claim 1, wherein the cabinet comprises a processor, an input/output expansion module, and a mounting plate; the mounting plate is provided with a plurality of signal transmitters, and the position of each signal transmitter corresponds to the position of one mounting position of the cabinet; the processor is connected with the mounting plate through the input/output expansion module;
or the like, or a combination thereof,
the rack includes treater and input \ output expansion module and a plurality of mounting panel, the treater passes through input \ output expansion module is with a plurality of the mounting panel is connected, every be equipped with one on the mounting panel signal transmitter, and every the position of mounting panel with one of rack the position of installation position is corresponding.
4. The cabinet server of claim 1, wherein the signal receiver on the server node is connected to a baseboard management controller of the server node, the baseboard management controller being configured to connect to the cabinet.
5. The cabinet server of any one of claims 1-4, wherein the signal transmitter comprises:
one or more of a visible light emitter, a light emitting diode, or an infrared emitter, and/or the signal receiver comprises: one or more of a light sensitive receiver or an infrared signal receiver.
6. The cabinet server of any of claims 1-4, wherein the device information of the server node comprises:
one or more of a device name of the server node, a product Serial Number (SN) identification of the server node, a Media Access Control (MAC) address of the server node, and an Internet Protocol (IP) address of the server node.
7. A rack server comprising a rack, a plurality of signal receivers, at least one server node, and at least one signal transmitter;
the cabinet comprises a plurality of installation positions, each installation position is provided with one signal receiver, and each installation position is used for installing one server node;
the cabinet is connected with a plurality of signal receivers;
each server node is provided with one signal emitter and is connected with the signal emitter which is arranged on the server node;
the cabinet is used for controlling the signal transmitter on each server node to send out signals;
the server node is used for sending equipment information of the server node to the cabinet;
wherein, in the case that at least one of the server nodes is installed in at least one of the installation sites, the signal receiver in the same installation site corresponds to the position of the signal transmitter, the signal receiver is used for receiving the signal sent by the signal transmitter in the same installation site, and the cabinet is used for binding the installation site with the equipment information of the server node in response to the signal.
8. An asset management method of a rack server, comprising:
the cabinet controls a signal emitter arranged at the installation position to send out a signal;
if a server node is installed in the same installation position, a signal receiver arranged on the server node receives the signal, and the server node responds to the signal and sends equipment information of the server node to the cabinet, wherein the same installation position is the installation position where the signal transmitter which sends the signal is located;
and the equipment cabinet receives the equipment information of the server node and binds the equipment information of the server node with the same installation position.
9. The method of claim 8, wherein the plurality of mounting locations are provided, each mounting location is provided with one of the signal emitters, and the cabinet controls the plurality of signal emitters to emit signals according to a first sequence.
10. The method of claim 8 or 9, wherein the signal receiver on the server node is connected to a baseboard management controller of the server node, wherein the signal receiver on the server node sends the received signal to the baseboard management controller, and wherein the baseboard management controller sends equipment information of the server node to the cabinet in response to the signal.
11. An asset management method of a rack server, comprising:
the method comprises the steps that under the condition that a server node is installed at an installation position of a cabinet, the cabinet sends a transmitting instruction to the server node;
responding to the transmitting instruction, the server node controls a signal transmitter arranged on the server node to send out a signal; the server node sends equipment information of the server node to the cabinet;
the equipment cabinet receives equipment information of the server node;
and if the signal receiver arranged at the installation position receives the signal, the cabinet responds to the signal and binds the equipment information of the server node with the same installation position, wherein the same installation position is the installation position where the signal receiver for receiving the signal is located.
12. The method of claim 11, wherein said mounting locations are plural, each of said mounting locations having one of said signal receivers;
and under the condition that at least two server nodes are installed in at least two installation positions, the cabinet sends a transmitting instruction to each server node according to a second sequence.
13. The method of claim 11 or 12, wherein the signal transmitter on the server node is connected to a baseboard management controller of the server node, wherein the baseboard management controller receives a transmission instruction sent by the cabinet, and in response to the transmission instruction, the baseboard management controller controls the signal transmitter on the server node to send a signal, and the baseboard management controller sends the equipment information of the server node to the cabinet.
CN202211168681.3A 2022-09-24 2022-09-24 Asset management method and related device for equipment cabinet server Pending CN115934619A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211168681.3A CN115934619A (en) 2022-09-24 2022-09-24 Asset management method and related device for equipment cabinet server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211168681.3A CN115934619A (en) 2022-09-24 2022-09-24 Asset management method and related device for equipment cabinet server

Publications (1)

Publication Number Publication Date
CN115934619A true CN115934619A (en) 2023-04-07

Family

ID=86649610

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211168681.3A Pending CN115934619A (en) 2022-09-24 2022-09-24 Asset management method and related device for equipment cabinet server

Country Status (1)

Country Link
CN (1) CN115934619A (en)

Similar Documents

Publication Publication Date Title
US11336522B2 (en) Information handling system physical component inventory to aid operational management through near field communication device interaction
JP6491291B2 (en) System for determining device location data in a data center
US20160073276A1 (en) Information Handling System Physical Component Maintenance Through Near Field Communication Device Interaction
CN109587005B (en) Connection detection method and device, computer equipment and readable storage medium
WO2012013130A1 (en) Method and system for managing server information data
US8055887B2 (en) Dynamically updating barcode data
CN101554092A (en) Method and apparatus for replacing a device in a network
RU2010143856A (en) METHOD AND DEVICE FOR AUTOMATIC SELECTION OF APPLICATIONS IN ELECTRONIC DEVICE USING MULTIPLE DETECTION ADMINISTRATORS
US8397053B2 (en) Multi-motherboard server system
CN1972212A (en) Kvm switch supporting ipmi communications with computing devices
CN107193763B (en) Information processing method and electronic equipment
JP2012146235A (en) Installation position information management system, rack, management object device and installation position information management method
US20210329755A1 (en) Navigational dynamic lighting
CN114356725B (en) Case management system
CN107885542A (en) All-in-one start-up and shut-down control method, electronic equipment, storage medium, control system
US20100323668A1 (en) Device status notification method, apparatus, and notification system
CN110740609A (en) Server information processing method and device for internet data center and controller
CN115934619A (en) Asset management method and related device for equipment cabinet server
CN112860327A (en) CPU port switching method, device, equipment and readable medium
JP2008003917A (en) Management method for rack-mounted device
KR101849709B1 (en) Modular bmc system
CN209821817U (en) Electronic equipment and cluster server system
CN109901954B (en) Storage device and resource management method
JP6191376B2 (en) Server installation position management system, server installation position management method, and program
CN111835902A (en) Device testing method and device, electronic device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination