Board information management system and method for managing board information

Abstract

To provide a technique which can automatically and collectively manage information including system information in operation for all boards equipped in a control server product.SOLUTION: A board information management system includes a CPU board and at least one board connected to the CPU board and manages board information as information for each of the at least one board. The CPU board acquires board information of each of the at least one board from the board, creates a table which collects the acquired board information of the boards, and stores the created table in a storage region in the CPU board.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a technology for automatically managing various types of information related to a board mounted on a control server product. [Background technology]

[0002] Control server products often have various boards (hereinafter referred to as "boards") installed in their housings to achieve the required functions and performance. For this reason, in order to properly maintain and operate a control server product, it is essential to properly manage each of the various boards installed in the control server product, for example, by grasping the necessary information and monitoring the status.

[0003] However, management of the boards installed in control server products has traditionally been done entirely manually, which has meant that control server product administrators have had to spend a lot of time and effort managing these boards, and the possibility of human error during the work cannot be eliminated, leading to concerns that the boards may not be managed properly.

[0004] In this context, various technologies have been proposed for automatically acquiring information and monitoring the status of boards mounted on control server products in operation (for example, Patent Documents 1 and 2). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 9-237243 [Patent Document 2] Japanese Patent Application Laid-Open No. 2009-294766 Summary of the Invention [Problem to be solved by the invention]

[0006] The technology described in Patent Document 1 aims to improve the maintainability of various boards and disk units installed in a system by collecting information indicating the installation status and individual information of the boards and disk units. However, the information that can be collected by the technology described in Patent Document 1 is limited to information that was recorded in advance when the boards or disk units were manufactured, i.e., information that was recorded before the boards or disk units were put into operation. For example, if an error occurs while the board or disk unit is in operation, information related to the error, such as the content or time of the error, cannot be collected. Therefore, for example, if the board or disk unit is later used in another system, information related to such errors must be managed separately and manually.

[0007] Furthermore, the technology described in Patent Document 2 aims to improve the maintainability of multiple Digital Signal Processor (DSP) cards by having a host CPU connected to the multiple DSP cards via a VME bus on a backplane collect operational status information about the DSPs installed in each DSP card. However, while the technology described in Patent Document 2 can determine whether each of the multiple DSP cards is in a normal state (whether there is an abnormality), it cannot confirm the specific details of the error even if the DSP card is in an abnormal state. Therefore, for example, if the DSP card is later used in another system, information about such errors must be managed separately and manually.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a technology that can automatically and centrally manage information, including running system information, for all boards installed in a control server product. [Means for solving the problem]

[0009] The board information management system according to the present invention includes a CPU board and one or more boards connected to the CPU board, and is a system that manages board information, which is information about each of the one or more boards. The CPU board acquires the board information of each of the one or more boards from the board, creates a table that summarizes the acquired board information for each board, and stores the created table in a storage area within the CPU board.

[0010] Other problems and solutions disclosed in the present application will be made clear in the detailed description and drawings. [Effects of the Invention]

[0011] According to the present invention, it is possible to automatically and collectively manage information including information about the running system for all boards mounted on a control server product. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a board information management system. [Figure 2] FIG. 2 is a diagram illustrating an example of functional blocks of a board information management system. [Figure 3] FIG. 10 is a diagram showing an example of the flow of data when information on each board is stored in a storage area of ​​a CPU board. [Figure 4] FIG. 10 is a diagram showing an example of the flow of data when error information that has occurred on each board is stored in a storage area on the CPU board. [Figure 5] FIG. 10 is a diagram showing an example of the flow of data when information about each board is written back to the board. DETAILED DESCRIPTION OF THE INVENTION

[0013] In the following description, a "CPU board" may refer to the main board and / or system board of the control server product, on which one or more processors are implemented as system controller chips that control the system. The at least one processor is typically a microprocessor device, such as a CPU (Central Processing Unit), but may also be another type of processor device, such as a GPU (Graphics Processing Unit). The at least one processor may be a single-core or multi-core processor. The at least one processor may also be a processor core. The at least one processor may also be a broader processor device, such as a circuit that is a collection of gate arrays written in a hardware description language to perform some or all of the processing (e.g., a Field-Programmable Gate Array (FPGA), a Complex Programmable Logic Device (CPLD), or an Application Specific Integrated Circuit (ASIC)).

[0014] In the following description, the term "board" may refer to various expansion boards and / or dedicated boards for the control server product, which are connected to the CPU board so as to be able to communicate with each other.

[0015] Also, in the following description, a "storage area" may be one or more persistent storage devices and may include one or more memories.

[0016] In the following description, a "persistent storage device" may refer to one or more persistent storage devices. A persistent storage device may typically be a non-volatile storage device (e.g., an auxiliary storage device) made of flash memory, and specifically may be, for example, a solid state drive (SSD), a non-volatile memory express (NVMe) drive, or a storage class memory (SCM). A persistent storage device may also be a hard disk drive (HDD).

[0017] In the following description, the term "memory" refers to one or more memory devices, typically a primary storage device. At least one of the memory devices may be a volatile memory device or a non-volatile memory device.

[0018] In the following description, the term "storage device" may refer to at least memory of a persistent storage device.

[0019] In the following description, a "communication unit" may be one or more communication interface devices, which may be one or more I / O (Input / Output) interface devices or may include one or more I / O (Input / Output) interface devices.

[0020] In the following description, an "interface device" may refer to one or more interface devices. The one or more interface devices may be at least one of one or more I / O (Input / Output) interface devices and one or more communication interface devices. In this case, the one or more I / O (Input / Output) interface devices may be interface devices for at least one of an I / O device and a remote display computer. The I / O (Input / Output) interface device for the display computer may be one or more communication interface devices. The at least one I / O device may be a user interface device, for example, either an input device such as a keyboard and a pointing device, or an output device such as a display device. On the other hand, in this case, the one or more communication interface devices may be one or more homogeneous communication interface devices (e.g., one or more NICs (Network Interface Cards)) or two or more heterogeneous communication interface devices (e.g., a NIC and an HBA (Host Bus Adapter)).

[0021] In the following description, functions may be described using the expression "yyy unit." However, the function may be realized by one or more computer programs executed by a processor, by one or more hardware circuits (e.g., FPGAs or ASICs), or by a combination thereof. When a function is realized by a program executed by a processor, the specified processing is performed using a storage area and / or a communication unit, etc., as appropriate, and therefore the function may be considered to be at least a part of the processor. Processing described using a function as the subject may be processing performed by a processor or a CPU board equipped with the processor. A program may be installed from a program source. The program source may be, for example, a computer that distributes the program or a computer-readable recording medium (e.g., a non-transitory recording medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0022] In the following explanation, a process may be described using a "program" as the subject, but the process described using a program as the subject may also be a process performed by a processor or a CPU board equipped with that processor. Two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0023] Hereinafter, the present embodiment will be described in detail with reference to the drawings.

[0024] In the following description, the same or similar components will be designated by common reference numerals, and redundant description may be omitted.

[0025] Furthermore, when there are multiple elements having the same or similar functions, the multiple elements may be described by using the same reference numeral with different subscripts to distinguish between them. On the other hand, when there is no need to distinguish between the multiple elements, the subscripts may be omitted.

[0026] (Configuration example of board information management system 100) First, an example of the configuration of a board information management system 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram that schematically shows an example of the configuration of the board information management system 100. Note that Fig. 1 is a diagram that focuses on parts necessary for explanation, and therefore unnecessary parts are omitted from the illustration.

[0027] The board information management system 100 of this embodiment is a computer system that can automatically and centrally manage information, including running system information, for all boards 1 installed in a control server product, and is realized by a computer or server having the configurations described below.

[0028] In the following description of this embodiment, the board information management system 100 is assumed to be realized by a single general-purpose computer or server equipped with one or more processors, one or more storage devices, one or more interface devices, and wired or wireless communication lines (none of which are shown) connecting them.

[0029] That is, the board information management system 100 has a storage device made up of a persistent storage device and a memory, an interface device, and a processor connected to them.

[0030] The persistent storage device is an auxiliary storage device made up of a nonvolatile storage element such as a flash memory. Specific examples of persistent storage devices include a solid state drive (SSD) and a hard disk drive (HDD). The persistent storage device stores at least a board information management program. This board information management program is a computer program for implementing the functions required for the board information management system 100. Execution of the board information management program by a processor performs various processes, which will be described later with reference to FIGS. 3 to 5.

[0031] The board information management program may be configured from a device driver, an operating system, various application programs located at higher levels than these, and a library that provides common functions to these programs.

[0032] Memory is a primary storage device that mainly consists of volatile memory elements such as RAM (Random Access Memory). Memory temporarily stores data representing various information read from persistent storage devices and various data obtained through interface devices.

[0033] The processor is a processor device such as a CPU (Central Processing Unit) and various co-processors. This processor loads the board information management program into memory and executes it, thereby performing overall control of the board information management system 100 itself and also managing a control unit (not shown) that performs various processes such as calculation processing and determination processing.

[0034] The interface devices include communication interface devices that connect to a communication network and communicate with other devices, terminals, etc., and I / O (Input / Output) interface devices.

[0035] As shown in FIG. 1, the board information management system 100 having such a hardware configuration includes a CPU board 5 and one or more boards 1a, 1b, 1c, . . . 1n (hereinafter, when referring to them collectively or when no particular distinction is made, they will be collectively referred to as "board 1") that are connected to the CPU board 5 so as to enable data communication with each other.

[0036] The CPU board 5 includes an information acquisition unit 6 that acquires information from each board 1, and a storage area 7 that stores the acquired information.

[0037] In the board information management system 100 according to this embodiment, the storage area 7 of the CPU board 5 is implemented using an SSD (Solid State Drive), but this storage area 7 provided on the CPU board 5 may also be implemented using other types of persistent storage devices.

[0038] On the other hand, each board 1 also has a storage area 2 for storing various information related to the board 1 (hereinafter also referred to as "board information").

[0039] In the board information management system 100 according to this embodiment, the storage areas 2 of each board 1 are implemented using flash memory, but these storage areas 2 provided on each board 1 may also be implemented using other types of persistent storage devices.

[0040] Furthermore, the type of each board 1 and the number of boards 1 connected to the CPU board 5 are not limited and can be set arbitrarily.

[0041] With this configuration, the board information management system 100 collects information about all boards 1 in the storage area 7 of the CPU board 5.

[0042] When the information acquisition unit 6 of the CPU board 5 acquires the board information stored in the storage area 2 of each board 1, it creates a table in the storage area 7 of the CPU board 5 that records each piece of acquired board information. Then, after performing an error check on each piece of board information, it records it in the corresponding record in the table. In this way, the board information of each board 1 is consolidated in the storage area 7 of the CPU board 5.

[0043] As a result, the user of the board information management system 100 can collectively manage the board information relating to all the boards 1 by appropriately referring to the storage area 7 of the CPU board 5.

[0044] Next, an example of blocks of various functions provided in the board information management system 100 according to this embodiment will be described with reference to Fig. 2. Note that each block described below does not represent a hardware configuration, but represents a functional block.

[0045] FIG. 2 is a functional block diagram illustrating a configuration for storing board information of each board 1 in the storage area 7 of the CPU board 5. As shown in FIG.

[0046] The information acquisition unit 6 and storage area 7 shown in FIG. 2 are the same as the information acquisition unit 6 and storage area 7 shown in FIG.

[0047] As shown in Figure 2, the information acquisition unit 6 of the CPU board 5 has the following functional blocks: a communication unit 8 that communicates with each board 1 using a method such as I2C communication; a total operating time calculation unit 9 that calculates the total operating time of each board 1; a table creation unit 10 that compiles the board information of each board 1 into a table; a communication unit 12 that performs system communication with each board 1 using a method such as PCIe communication; and an error content determination unit 13 that identifies the content of the error from information about an error that has occurred in the system communication.

[0048] As shown in FIG. 2, each board 1 has a controller 11, such as a LAN controller, that controls communication (for example, PCIe communication) used in the system of the board 1.

[0049] FIG. 3 is a diagram showing an example of the data flow when information on each board 1 is stored in the storage area 7 of the CPU board 5. As shown in FIG.

[0050] The board information transmitted from the board 1 to the CPU board 5 includes the serial number, REV, operation start date and time, and unique information.

[0051] Furthermore, the unique information can be arbitrarily set and used when there is information that the user wishes to manage.

[0052] The board information is transmitted from the storage area 2 to the CPU board 5 by the communication unit 8 when the system is started up.

[0053] The serial number and REV are transmitted from the communication unit 8 to the table creation unit 10.

[0054] The operation start date and time is transmitted to the total operation time calculation unit 9, which calculates the total operation time from the operation start date and time and the current time information held by the CPU board 5, and transmits the operation start date and time and the total operation time to the table creation unit 10.

[0055] The table creating unit 10 creates a management table from the transmitted information that compiles the serial number, REV, operation start date and time, total operation time, mounting slot, and unique information.

[0056] The mounting slot is determined based on the location where the communication unit 8 is communicating.

[0057] A management table is created for all boards 1 and stored in the storage area 7.

[0058] This allows the user of the board information management system 100 to collectively manage the board information relating to all boards 1 by appropriately referring to the storage area 7 of the CPU board 5.

[0059] FIG. 4 is a diagram showing an example of the flow of data when error information occurring on each board 1 is stored in the storage area 7 of the CPU board 5. In FIG.

[0060] When an error occurs in the communication (eg, PCIe communication) used in the system on the board 1, error information is transmitted from the controller 11 (eg, LAN controller) to the communication unit 12 and the error content determination unit 13 in this order.

[0061] Therefore, the error content determining unit 13 determines the content of the error based on the information of the error that has occurred, and transmits the determined content to the table creating unit 10 .

[0062] At this time, the current time information held by the CPU board 5 is also transmitted to the table creation unit 10 as the date and time of the error occurrence.

[0063] The table creating unit 10 creates an error management table that lists the date and time when an error occurred, the content of the error, and the installation slot.

[0064] The installation slot is determined based on the location where the communication unit 12 is communicating.

[0065] In this way, by creating an error management table on each board 1 and storing it in the storage area 7, the user of the board information management system 100 can refer to the storage area 7 of the CPU board 5 as appropriate when an error occurs and understand how the board 1 behaved while in operation.

[0066] Because both the management table and the error management table contain information about the mounting slot, it is possible to check the information in the management table and the error management table together for each board 1. Therefore, by referencing these tables, it is possible to manage all boards 1 collectively.

[0067] FIG. 5 is a diagram showing an example of the data flow when information about each board 1 in the management table and error management table stored in the storage area 7 of the CPU board 5 is written back to the board 1.

[0068] The data written back is information that will be utilized when reusing, and therefore only the information of the board 1 itself will be written back.

[0069] The management table and error management table stored in the storage area 7 are transmitted to the communication unit 8 and written into the storage area 2 of the board 1 .

[0070] By referring to the storage area 2, it is possible to check the information of the replaced board 1 (maintenance part) itself, which can be useful when considering the use of the board in another product.

[0071] By performing this type of control on all connected boards 1, it becomes possible to manage all boards 1 in a centralized manner, and it becomes possible to store information that can be used when reusing maintenance parts for other products.

[0072] The above-described embodiment of the present invention can be summarized as follows.

[0073] (1) The board information management system 100 includes a CPU board 5 and one or more boards 1 connected to the CPU board 5, and is a system that manages board information, which is information about each of the one or more boards 1. The CPU board 5 acquires the board information of each of the one or more boards 1 from the board 1, creates a table that summarizes the acquired board information for each board 1, and saves the created table in a storage area 7 within the CPU board 5. In this way, the board information management system 100 can automatically and collectively manage board information, including running system information, for all boards 1 installed in a control server product.

[0074] (2) The board information includes the serial number of the board 1. In this way, the board information management system 100 can automatically and collectively manage board information, including serial numbers, for all boards 1 mounted on the control server product.

[0075] (3) The CPU board 5 calculates the total operating time for each of the one or more boards 1 and stores the calculated total operating time for each board 1 in the table as board information for that board 1. In this way, the board information management system 100 can automatically and collectively manage board information, including total operating time, for all boards 1 mounted on the control server product. As a result, the user of the board information management system 100 can properly understand when to perform maintenance or replacement on that board 1, enabling efficient maintenance work on the control server product.

[0076] (4) The CPU board 5 acquires error information for each of the one or more boards 1, determines the error content representing the nature of the error from the acquired error information, and saves the acquired error information and the determined error content in a table. In this way, the board information stored in the table in the storage area 7 of the CPU board 5 includes information about the running system, such as the error content and the time the error occurred. As a result, the user of the board information management system 100 can understand the operations and behavior of each board 1 while the control server product is running.

[0077] (5) The CPU board 5 writes the board information of each board 1 stored in the table back to the storage area 2 of the corresponding board 1. In this way, the board information management system 100 can store information that can be used when reusing the board 1 as a maintenance component. As a result, the user of the board information management system 100 can effectively reuse each board 1 as a maintenance component.

[0078] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the spirit of the present invention.

[0079] The above-described embodiments, examples, and modifications are merely examples, and the present invention is not limited to these details as long as the features of the invention are not impaired. Furthermore, although various embodiments, examples, and modifications have been described above, the present invention is not limited to these details. Other aspects that can be considered within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention.

[0080] In the above figures, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily show all the control lines and information lines that are actually implemented. For example, it can be assumed that almost all components are actually connected to each other.

[0081] The layout of each functional unit of the board information management system 100 described above is merely an example. The layout of each functional unit can be changed to an optimal layout in terms of the performance, processing efficiency, communication efficiency, etc. of the hardware and software provided in the board information management system 100. [Explanation of symbols]

[0082] 100: Board information management system 1... Board connected to CPU board 2...Storage area within the board (Flash) 5...CPU board 6…Information acquisition section 7...Storage area on the CPU board (SSD) 8...Communication section inside the CPU board (I2C) 9...Total operating time calculation section 10...Table creation section 11... Controller inside the board 12...Communication section inside the CPU board (PCIe) 13...Error content determination section

Claims

1. A board information management system including a CPU board and one or more boards connected to the CPU board, the system managing board information which is information about each of the one or more boards, The CPU board includes: obtaining board information for each of the one or more boards; Creating a table summarizing the board information of each board acquired; The created table is stored in a storage area in the CPU board. Board information management system.

2. The board information management system according to claim 1 , wherein the board information includes a serial number of the board.

3. The CPU board includes: calculating a cumulative operating time for each of the one or more boards; storing the calculated total operating time of each board in the table as board information of the board; The board information management system according to claim 1 .

4. The CPU board includes: obtaining error information for each of the one or more boards; determining an error content representing the content of the error from the acquired error information; The acquired error information and the determined error content are stored in the table. The board information management system according to claim 1 .

5. 5. The board information management system according to claim 1, wherein the CPU board writes back the board information of each board stored in the table to the storage area of ​​the corresponding board.

6. 1. A board information management method in which a computer including a CPU board and one or more boards connected to the CPU board manages board information, which is information about each of the one or more boards, comprising: The CPU board includes: obtaining board information from each of the one or more boards; Creating a table summarizing the board information of each board acquired; The created table is stored in a storage area in the CPU board. How to manage board information.

Images