Patent ID: 12242838

DESCRIPTION OF EMBODIMENTS

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Among the constituent elements disclosed herein, those having the same function are denoted by the same reference numerals, and a description thereof is omitted. It should be noted that the embodiments disclosed herein are illustrative examples as means for implementing the present invention, and should be appropriately modified or changed depending on a configuration and various conditions of an apparatus to which the present invention is applied, and the present invention is not limited to the following embodiments. Furthermore, it should be noted that all of the combinations of features described in the following embodiments are not necessarily essential to the solution of the present invention.

First Embodiment

Hereinafter, a non-limiting example will be described in which a server management apparatus according to the present embodiment is implemented in a central server apparatus, which may be located in a central data center or the like that constitutes a core network, connects to respective nodes that constitute a network virtualization infrastructure to collect information from bare metal servers deployed in a large number of accommodating stations distributed in a mobile network, diagnoses the bare metal servers by analyzing the collected information to generate a structured file in a readable format that includes information on the bare metal server and a server status flag indicating whether or not any of the bare metal server and the hardware components included in the bare metal server has abnormality, and instructs the bare metal server that has no abnormality to install an OS and virtualization software by referring to the structured file.

However, the present embodiment is not limited thereto. The server management apparatus according to the present embodiment may be implemented in any server apparatus that is deployed elsewhere than the central data center and constitutes the backhaul network relaying a Radio Access Network (RAN) to the core network or the core network itself.

The server management apparatus according to the present embodiment may also be implemented in any of the nodes that constitutes the network virtualization infrastructure.

According to the present embodiment, a bare metal server refers to a general-purpose server apparatus that is deployed in the accommodating station, or the like, in the mobile network and is capable of constituting the network virtualization infrastructure, but before the OS is installed.

<Network Configuration of Mobile Network System>

FIG.1is a conceptual diagram illustrating an exemplary network configuration of a mobile network system including a server management apparatus according to the present embodiment.

The mobile network100shown inFIG.1includes a base station101, a plurality of accommodating stations102, a Regional Data Center (RDC)103, and a Central Data Center (CDC)104.

The mobile network100according to the present embodiment may be a virtualized network constructed on a virtualization infrastructure. In the mobile network100, the physical network is virtualized, and end-to-end network functions across the RAN, the backhaul network, and the core network are realized on general-purpose servers or cloud using virtualization software.

The mobile network100may be a 4G network or a 5G network, or any other generation of mobile communication system, as long as the mobile network can be implemented in the virtualization infrastructure.

Referring toFIG.1, the base station101includes an antenna, a Remote Radio Head (RRH), a Radio Interface Unit (RIU), which is a line termination device, and the like, and transmits and receives radio signals to and from the UE (not shown) via the antenna of the base station101.

The base station101is an edge node that constitutes the RAN of the mobile network100. The base station101receives an attach request from the UE, and connects the UE to the core network via the fronthaul network and the backhaul network to relay data transmission and voice calls between the UE and the Internet105.

The UE may be a mobile terminal such as a smartphone, a cell phone, a tablet, or a Personal Computer (PC), a mobile device such as a vehicle, or a terminal with built-in equipment such as a sensor, and its type is not limited thereto, as long as the UE is capable of mobile communication via the base station101.

The accommodating station102is an edge data center that accommodates a plurality of base stations101, home networks, or enterprise networks via the fronthaul network constituted with fiber optic cables, or the like.

In order to relay the radio access request to the core network, the accommodating station102bears functions of a Distributed Unit (DU), which is a radio signal processing unit, and a Central Unit (CU), which is a data processing unit. Those DU and CU may be a virtualized vDU and a virtualized vCU, respectively.

The RDC103accommodates a plurality of accommodating stations102distributed in the target area via the backhaul network constituted with optical fiber cables, or the like, and bears functions of a firewall and a Network Address Translation (NAT), which is an IP address translation function.

The CDC104accommodates one or a plurality of RDCs103via the backhaul network, and bears functions of the core network such as an Evolved Packet Core (EPC) and an IP Multimedia Subsystem (IMS).

The core network is a high-capacity backbone network that is used by the mobile network100as the central role of communications, and connects between line concentrators, hub stations, and operators.

It should be noted that the number of base stations101, accommodating stations102, RDC103, and CDC104are not limited to the number shown inFIG.1. For example, althoughFIG.1shows one RDC103and one CDC104, respectively, there may be a plurality of RDCs103and CDCs104, respectively.

FIG.2is a block diagram illustrating an exemplary relationship between the virtualization infrastructure of the mobile network system inFIG.1and the server management apparatus according to the present embodiment.

Referring toFIG.2, the Network Function Virtualization Infrastructure (NFVI)21is an infrastructure for network virtualization and includes physical resources, virtualization layers, and virtualized resources. The physical resources include hardware resources such as computing, storage, and transmission resources.

The virtualization layer is constituted with a hypervisor or the like, which virtualizes the physical resources and provides the virtualized physical resources to the Virtualized Network Function (VNF)22. The virtualized resources are the virtualized resources that are provided to the VNF22.

In other words, the NFVI21is an infrastructure that allows the hardware resources, which are physical resources that realize computing, storage, transmission, and the like, to be handled flexibly as virtualized hardware resources virtualized by the virtualization layer such as the hypervisor.

A plurality of general-purpose servers constituting the NFVI21inFIG.2may be deployed in each of the accommodating station102, the RDC103, and the CDC104. The number, arranging positions, wirings, and the like, of the general-purpose servers to be deployed in each of the accommodating station102, the RDC103, and the CDC104are predetermined based on the type of the accommodating station and the data center. The plurality of general-purpose servers deployed in the same station are connected to each other in a communicable manner.

The VNF22is a set of virtualized network functions that are deployed on the physical resources and the virtualized resources and correspond to respective applications running on a virtual machine (VM) on the general-purpose servers, respectively, so as to realize the network functions by software. Each of the VNFs22may have an Element Manager (EM), which is a management function of the VM.

A Management and Orchestration (MANO)23has a management function and an orchestration function of the virtualized environment constituted with the NFVI21and the VNFs22. The MANO23includes a Virtualized Infrastructure Manager (VIM)231, a VNF Manager (VNFM)232, and a NVF Orchestrator (NVFO)233.

The VIM231performs operation and management of the physical resources and the virtualized resources used by the VNF22.

The VNFM232allocates a set of network functions of each of the VNFs22on physical and virtualized resources and performs the lifecycle management of each of the VNFs22. The set of network functions to be deployed include communication functions, service application functions, and data transfer protocols necessary to provide respective services. It should be noted that the VNFM232may be a dedicated VNFM that is dedicated to each of the VNFs22, or otherwise may be a general-purpose VNFM that is provided for two or more VNFs22.

The NFVO233performs the orchestration of respective resources of the NFVI21, the deployment of the set of network functions of the VNFs22, and integrated operation and management of the entire system. This NFVO233performs the processing corresponding to instructions issued from an Operation Support System (OSS)/Business Support System (BSS)24.

The OSS/BSS24is a system that monitors and manages service instances corresponding to applications provided to end users, which are the uppermost layer of the virtualized network. The OSS is, for example, the system required to constitute and operate respective service instances. The BSS is a system required for billing, customer information management, and the like.

The server management apparatus1is connected to the NFVI21, the OSS/BSS24, and the MANO23in a communicable manner, and performs the bare metal server diagnosis processing according to the present embodiment.

It should be noted that, althoughFIG.2illustrates an example in which the server management apparatus1is implemented in a separate node, independent from the nodes of the virtualization infrastructure, the present embodiment is not limited thereto. For example, the server management apparatus1may be implemented as a part of MANO23, or alternatively implemented as a part of an OSS/BSS24.

<Functional Configuration of Server Management Apparatus>

FIG.3is a block diagram illustrating an exemplary functional configuration of the server management apparatus according to the first embodiment.

Among the functional modules of the slicing controller apparatus1shown inFIG.3, as for the functions that are implemented by software, those functions may be implemented by storing the program to provide the functions of each functional module in a ROM or other memory, and the allowing a CPU to read the programs into a RAM to execute the programs. As for the functions that are implemented in hardware, for example, a dedicated circuit may be automatically generated on a Field Programmable Gate Array (FPGA) from the programs to provide the function of respective function modules by using a predetermined compiler. Alternatively, it is also possible to form a Gate Array circuit in the same way as an FPGA and implement it by hardware. Yet alternatively, those functions may be implemented an Application Specific Integrated Circuit (ASIC). The configuration of the functional blocks shown inFIG.3is no more than an example, and multiple functional blocks may constitute a single functional block, or any of the functional blocks may be divided into blocks that perform multiple functions.

Referring toFIG.3, the server management apparatus1includes a server information acquisition unit11, an analysis unit12, a structured file generation unit13, a diagnosis unit14, an installation instructing unit15, an input/output unit16, a structured file storage unit17, and a task folder18.

The server information acquisition unit11acquires, from a large number of bare metal servers3deployed in a plurality of accommodating stations102, respectively, information on each of the bare metal servers and the hardware components constituting the bare metal server, and supplies the acquired information on the bare metal server and the hardware components (hereinafter also simply referred to as “bare metal server information”) to the analysis unit12.

More particularly, the server information acquisition unit11requests each of bare metal servers3to send information on the bare metal server concerned and the hardware components thereof, using, as a key, an identifier of a control board of the bare metal server3, for example, an IP address, and receives the bare metal server information sent from the bare metal server3in response to the transmission request.

The Intelligent Platform Management Interface (IPMI) commands, the Redfish API, and the like, are interfaces that allow an external apparatus to obtain the hardware status of the respective bare metal servers3by remotely issuing commands. The server information acquisition unit11may remotely issue those IPMI commands, or the like, to the bare metal servers3and receive the response to the commands from respective bare metal servers3.

The IPMI is capable of acquiring the status of each of bare metal servers3and the hardware components thereof through a single interface, regardless of the differences in or existence of the processor, the BIOS (Basic Input Output System), and the OS of the bare metal server3. In addition, the IPMI is operable on the bare metal server3even when the bare metal server3is powered off.

The server information acquisition unit11may issue the IPMI commands to a large number of bare metal servers3deployed in a plurality of the accommodating stations102at once, or alternatively may issue the IPMI commands to one or a plurality of bare metal servers3individually. In addition, periodic issuance of the IPMI commands may be scheduled in advance and converted into tasks to be executed at the scheduled timing, and the tasks may be registered in the task folder18. The server information acquisition unit11may also receive the bare metal server information sent from each of the bare metal servers3periodically or when a certain event occurs.

The analysis unit12analyzes the bare metal server information supplied from the server information acquisition unit11and supplies the analyzed bare metal server information to the structured file generation unit13and the diagnosis unit14.

The structured file generation unit13generates a structured file from the analyzed bare metal server information supplied from the analysis unit12and stores the generated structured file in the structured file storage unit17.

The structured file generated by the structured file generation unit13is a structured file that hierarchically stores, in a readable format, the bare metal server information, that is, information on the bare metal server and the hardware components thereof. More detailed structure of the structured file will be described later with reference toFIGS.7and8.

The diagnosis unit14diagnoses the bare metal server3by referring to the analyzed bare metal server information supplied from the analysis unit12.

More particularly, the diagnostic unit14generates a bare metal server status flag by referring to the information indicating the status of the bare metal server and the status of the hardware components included in the bare metal server information.

In other words, the diagnosis unit14determines whether or not any of the bare metal server and the hardware components thereof has an abnormality, and when it is determined that any of the bare metal server and the hardware components has an abnormality, sets the generated bare metal server status flag to ON. The bare metal server status flag generated by the diagnostic unit14is stored in the structured file of the bare metal server3concerned. The bare metal server status flag may be described in a header of the structured file.

The installation instructing unit15instructs the bare metal server3to install the OS and the virtualization software on the bare metal server3.

More particularly, the installation instructing unit15reads out the structured file of each bare metal server3stored in the structured file storage unit17, and, referring to the bare metal server status flag described in the structured file, extracts, from among all the bare metal servers that may be subject to the installation of the OS and the virtualization software, a bare metal server of which bare metal status flag is not set to ON, in other words, a bare metal server that is determined to have no abnormality. The installation instructing unit15sends, to one or a plurality of bare metal servers that are determined to have no abnormality, an instruction to install the OS and the virtualization software to the bare metal server concerned.

The input/output unit16provides an interface for instructing and inputting various commands and parameters, which operate the server management apparatus1or to be input to the bare metal server3, to the server management apparatus1. The input/output unit16also provides a Graphical User Interface (GUI) for displaying and outputting the execution results of the server diagnosis processing performed by the server management apparatus1via an output device such as a display device of an operation terminal19connected to the server management apparatus1.

The input/output unit16is capable of reading out the structured file of the bare metal server3stored in the structured file storage unit17, displaying the structured file on the display device of the operation terminal19, and also allowing a user to edit the displayed structured file. The input/output unit16is yet also capable of allowing various tasks, which are stored in the task folder18and to be executed by a large number of bare metal servers3deployed in a plurality of accommodating stations102, to be displayed on the display device of the operation terminal19so as to allow the user to register new tasks or edit the registered tasks.

The structured file storage unit18is constituted with a non-volatile storage device such as a Hard Disk Drive (HDD) or a Solid State Drive (SSD), and stores the structured file generated by the structured file generation unit13. The structured file storage unit18may be an external storage device of the server management apparatus1, or alternatively an internal storage device or a memory.

The task folder18stores various tasks to be executed by a large number of bare metal servers3deployed in a plurality of accommodating stations102. Each of the tasks includes scripts describing a plurality of commands to be issued to the bare metal servers3, and information such as schedules for executing the commands or scripts.

FIG.4is a block diagram illustrating an exemplary equipment configuration in the accommodating station that constitutes the mobile network system inFIG.1.

Referring toFIG.4, the accommodating station102includes a Top of Rack (TOR)41, a vDU42, a vCU43, and a Mobile Back-Haul (MBH) router44.

The TOR41includes a rack, which houses the network equipment of the accommodating station102, and switches. The TOR41accommodates respective network devices in the rack and provides wiring to the network devices accommodated in the rack. The TOR41also accommodates the fronthaul network from the base stations101, which is constituted with fiber optic cables.

The vDU42is a virtualized radio signal processing unit, and the vCU43is a virtualized data processing unit. The vDU42and the vCU43may be implemented in one or a plurality of general-purpose servers, respectively.

The MBH router44connects the data center network of the accommodating station102to the core network via the backhaul network.

It should be noted that the configuration shown inFIG.4merely denotes the logical nodes of the network in the accommodating station102, and does not necessarily correspond to the physical arrangement of switches, servers, and routers. Also, the number of the TOR41, the vDU42, the vCU43, and the MBH routers44may be determined as appropriate depending on the number of the base stations101accommodated by the accommodating station102, the functions borne by the virtualized network, the required throughput, or the like.

When a plurality of sets of the TOR41, the vDU42, the vCU43, and the MBH routers44are installed, the network of the accommodating station102may be made redundant by splitting signals from the base station101and inputting the split signals to a plurality of TORs41. In order to split the signals from the base station101, for example, a splitter such as a Planar Lightwave Circuit (PLC) splitter may be used to split the signals from the base station101.

The server management apparatus1according to the present embodiment performs the diagnosis processing of the bare metal servers, each of which is deployed in the accommodating station102and bears the functions of the vDU, vCU and the like shown inFIG.4. The server management apparatus1may also perform the diagnosis processing of the bare metal servers, each of which is deployed in the RDC103and the CDC104, similarly to the bare metal servers deployed in the accommodating station102.

FIG.5is a block diagram illustrating an exemplary hardware configuration of the bare metal server deployed in the accommodating station102inFIG.4, with a motherboard of the bare metal server being situated in the center.

Referring toFIG.5, a motherboard (i.e., control board)5of the bare metal server3may include a Baseboard Management Controller (BMC)51, a Network Interface Card (NIC) Controller52, a NIC53, a Redundant Arrays of Inexpensive Disks (RAID) controller54, a non-volatile memory55, a main memory56, and a Central Processing Unit (CPU)57. The BMC51is connected to respective hardware components shown inFIG.5via a system bus.

The motherboard5is an electronic circuit control board that mounts the main components of a computer of the bare metal server. The motherboard5may also be equipped with various chipsets, expansion slots, and connectors for connecting power supplies and various disk drives.

The BMC51is constituted with a microprocessor and, using the IPMI (Intelligent Platform Management Interface), provides an interface for sending and receiving commands to external devices such as the server management apparatus1.

The BMC51monitors each of the hardware components52to59shown inFIG.5and sends various information including the status of the bare metal server3and respective hardware components to the server management apparatus1in response to the IPMI commands from the server management apparatus1or autonomously. The BMC51also obtains an SEL log56of each of the hardware components and writes the SEL log56to the non-volatile memory55.

The NIC controller52controls the operation of the NIC53that provides the interface to the Local Access Network (LAN) communication network.

The RAID controller54controls the operation of the RAID disks54athat combines a plurality of HDDs to store data redundantly as one virtual HDD.

The non-volatile memory55is a non-volatile memory that is directly accessible by the BMC51. The non-volatile memory55stores the SEL log56and information on a replaceable Field Replaceable Unit (FRU) of the motherboard5, or the like.

The memory56is a volatile memory that operates as a main memory and a work area for the CPU57.

The CPU57is a processor that comprehensively controls the operation of the server that mounts the motherboard5.

The SEL log58is an event log recorded by the BMC51. The BMC51monitors the status of the bare metal server3and each of the hardware components of the bare metal server3, and records the obtained normal or abnormal status in the SEL log58.

The IPMI command is capable of reading and clearing the SEL log58, and also adding an event to the SEL log58.

According to the present embodiment, the diagnosis unit14may set the bare metal server status flag by analyzing the SEL log included in the bare metal server information acquired by the server information acquisition unit11.

The system sensor59detects the status of each of the hardware components of the bare metal server3, such as sensors detecting the status of the power supply, fans, temperature sensors, or the like, and outputs the detected sensor signals to the BMC51. The system sensor59may further include various control circuits such as power ON/OFF and reset.

According to the present embodiment, the server management apparatus1remotely issues the IPMI commands to the respective bare metal servers3using the IP address of the BMC51mounted on the motherboard5of the bare metal server3as the key. The BMC51of the bare metal server3receives the IPMI command and, in response to the received IPMI command, sends various information to the server management apparatus1indicating the identifier, version, status, and the like of the bare metal server3and respective hardware components thereof.

<Bare Metal Server Diagnosis Processing>

FIG.6is a flowchart illustrating an exemplary detailed processing procedure of the bare metal server diagnosis processing performed by the server management apparatus according to the first embodiment.

The bare metal server diagnosis processing shown inFIG.6may be started when a command for status inquiry, such as an IPMI command, is issued to the bare metal server3in the accommodating station102. This command issuance may be automatically executed by registering a task for executing a script containing a series of commands in the scheduler in the task folder18in advance, and reading the registered executable task by the server information acquisition unit11of the server management apparatus1to execute the read out executable task accordingly. Alternatively, the command issuance may be manually executed by an operator inputting the commands from a command line of the operation terminal19of the server management apparatus1.

In step S1, the server information acquisition unit11of the server management apparatus1remotely issues the command for status inquiry, such as the IPMI command, to each of a large number of the bare metal servers3deployed in a plurality of accommodating stations102using the IP address of the BMC51as a key.

The BMC51of the motherboard5of the bare metal server3sends the information on the bare metal server3and the information on each of the hardware components to the server information acquisition unit11in response to the issued command. The server information acquisition unit11receives the bare metal server information sent from the BMC51.

The bare metal server information received in step S1may include information on the bare metal server3, such as the IP address of the BMC51, the serial number of the bare metal server3, or the like. The bare metal server information received in step S1may also include information on the hardware components of the bare metal server3, such as the power ON/OFF status, the fan status and the temperature of the bare metal server3, the firmware version of the BMC51, the status of the NIC53, the status of the RAID54, the status and size of the memory56and the CPU57, the drive allocation status and model, and the like. The bare metal server information received in step S1may also include the SEL log58.

In step S2, the analysis unit12of the server management apparatus1analyzes the bare metal server information acquired by the server information acquisition unit11in step S1, and supplies the analyzed bare metal server information (i.e., analysis results) to the structured file generation unit13and the diagnosis unit14.

In step S3, the diagnosis unit14of the server management apparatus1performs the diagnosis of the bare metal server3based on the analysis results acquired in step S2.

More particularly, the diagnosis unit14generates the bare metal server status flag, and refers to the analyzed bare metal server information acquired in step S2to determine whether or not there is any abnormality in the bare metal server3itself or in any of hardware components of the bare metal server3. When any of the bare metal server3and the hardware components has an abnormality, the diagnosis unit14sets the bare metal server status flag to ON.

It should be noted that the bare metal server status flag is set to OFF when there is no abnormality in either the bare metal server3or any of the hardware components, in other words, when the bare metal server3is determined to be normal, and the initial value of the bare metal server status flag is OFF. When there is an abnormality in any of the bare metal server3and respective hardware components, the bare metal server status flag may allow a plurality of values to be set, which is capable of identifying a source component where the abnormality occurred and/or error codes.

In step S4, the structured file generation unit13of the server management apparatus1generates a structured file from the analyzed bare metal server information output from the analysis unit12in step S2and the bare metal server status flag output from the diagnosis unit14in step S3, and stores the generated structured file in the structured file storage unit17.

Referring toFIGS.7and8, a non-limiting example of a format of the structured file generated by the structured file generation unit13in step S4will be described in detail.

FIG.7is a schematic diagram illustrating an exemplary description of a header of the structured file generated by the structured file generation unit13of the server management apparatus1according to the present embodiment.

Referring toFIG.7, the structured file is a file in a text format (.txt) as a readable format (i.e., human-readable format), and has the header shown inFIG.7. Alternatively, the structured file generation unit13may use the character strings71to82shown inFIG.7as a file name of the generated structured file. Describing the character strings71to82shown inFIG.7as file names also falls within one embodiment of the header of the structured file.

The character string “72b6” denotes an identifier71that identifies the bare metal server3, and in the example ofFIG.7, a part of the IP address of the BMC51of the bare metal server3is described. The identifier71of the BMC51of the bare metal server3may be a key of the structured file. The identifier71may describe, for example, all or a part of the IP address or the MAC address of the BMC51.

The character string “ServerInfo” denotes an information type72that the structured file describes, and in the example ofFIG.7, it indicates information on a server.

The character string “D52BQ” denotes the vendor's model name73of the bare metal server3.

The character string “PowerOn” denotes the power status of the bare metal server3, and in the example ofFIG.7, it indicates that the power is on.

The character string “FaultLED-00” is the bare metal server status flag75that indicates whether the bare metal server3has an abnormality or is normal, and in the example ofFIG.7, the value of “00” indicates that the bare metal server3has no abnormality, in other words, the bare metal server3is normal.

The character string “3A11.BT20” denotes the BIOS version76of the bare metal server3. The character string “4.78.22” denotes the version77of the BMC51.

The character string “RAID ‘51.12.0-3186’. 0-3186′” denotes the version78of the RAID card (controller)54.

The character string “BBUOK” denotes the backup battery status79of the RAID54a, and in the example ofFIG.7, it indicates that the BBU is in a normal state.

The character string “Mem384” denotes the size81of the memory56, and in the example inFIG.7, it indicates that the memory size is 384 GB.

The character string “QTFCR202100BB” denotes the serial number 82 of the bare metal server3.

The character string “2021-03-24_19_07_23” denotes the time stamp83at which the various data of71to82were obtained.

According to the present embodiment, as shown inFIG.7, the structured file generation unit13generates the header of the structured file by adding a plurality of values of the bare metal server information of the bare metal server3. The structured file generation unit13generates the header of the structured file such that the header includes the bare metal server status flag75in the structured file.

The structured file generation unit13may generate the header, from among the bare metal server information, mainly from the identification information, the version information, and the status information of the bare metal server3itself.

The header layout shown inFIG.7is no more than an example, and the structured file generation unit13may describe all or a part of the hardware component information in the header from among the bare metal server information acquired in step S2. Also, the structured file generation unit13may generate the header of the structured file from a subset of the bare metal server information and hardware component information acquired in step S2.

FIG.8is a schematic diagram illustrating an exemplary bare metal server information described in the body of the structured file inFIG.7.

Referring toFIG.8, the structured file80describes, in the order from top to bottom, the BMC IP address (“BMC IP”), the bare metal server status flag (“FaultLED”), the server serial number, the power ON/OFF status, the firmware version of the BMC51, the BIOS version, and the memory size. Those descriptions are shared in common with the descriptions in the header shown inFIG.7.

Furthermore, the structured file80also includes the status of the memory56, the status and size of the PCIE card, which is an expansion card inserted into a slot on the motherboard5, the BIOS configuration attributes, the status and the memory size of the RAID controller54, the status and the capacity of each drive, the detailed status of the BBU, the status of the power supply unit, the SEL log58, and values detected by various system sensors59.

Those values are mainly information about the hardware components of the bare metal server3, such as their identifiers, the capacities, and statuses, which are not described in the header shown inFIG.7.

As described above, according to the present embodiment, the structured file generation unit13describes, in the header of the structured file, the identifier, the version and the status of the bare metal server3itself, those of which are the major bare metal server information from among the bare metal server information acquired in step S2. In addition, the structured file generation unit13describes, in the body of the structured file, the information of the hardware components of the bare metal server3and the detailed information of the information of the bare metal server3itself described in the header from among the bare metal server information acquired in step S2. In this way, according to the present embodiment, the bare metal server information is hierarchically stored in the header and the body of the structured file so as to generate a structured file in which the bare metal server information is stored in a structured manner.

Therefore, an operator who monitors a large number of bare metal servers3via the operation terminal19can browse a large number of structured files stored in the structured file storage unit17in a list format, or the like, and can easily and visually recognize the status of each bare metal server3from the character strings described in the header or the file name of the structured file.

For example, in response to a request input by the operator via an operation terminal19, it makes it possible to perform the display control to sort, from among a plurality of columns71to83of the header in a large number of structured files, one or a plurality of columns of the header specified in the input request to output the sorted columns on the display device. The header of the structured file has columns that contain values indicating the status of the bare metal server3and the hardware components. As a result, it makes it possible to easily perform the diagnosis of a large number of bare metal servers3by simply sorting a part of columns of the header of the structured file.

In addition, it makes it possible to provide a generic tool that extracts items of the bare metal server status flag75and other desired bare metal information from character strings described in the header or the file name of the structured file, and sorts the extracted items, regardless of the difference in the vendors, the server models, the installed OS, BIOS, or the like.

The server management apparatus1may also periodically collect the bare metal server information from all of the bare metal servers3connected to the server management apparatus1via the server information acquisition unit11, for example, at regular intervals every day, and automatically perform diagnosis of all bare metal servers3based on the collected bare metal server information.

More particularly, the diagnosis unit14of the server management apparatus1extracts the bare metal servers3that have the values of the bare metal server status flag (FaultLED) is other than “00” among all of the bare metal servers3. Furthermore, the diagnostic unit14may add the information on the source of the abnormality, which indicates which hardware component has caused the abnormality, to the analysis results by the analysis unit12for the extracted bare metal servers3, and output them to the display device of the operation terminal19or the like.

The operator can visually recognize the information on the source of the abnormality, which indicates which hardware component has caused the abnormality, which is output to the operation terminal19, and appropriately and easily determine the operational commands to be issued, such as a power cycle (power OFF/ON), disable/enable a given setting, a firmware upgrade/downgrade, or the like, to the bare metal server3that indicates the abnormality.

It should be noted that the formats of the structured file shown inFIGS.7and8is no more than exemplary, and the present embodiment is not limited thereto. For example, the contents of the file shown inFIG.8, that is, the details of the bare metal server information and the hardware component information, may be described in a non-human-readable format such as binary codes, as long as the file name or the header of the structured file is described in human-readable strings.

Furthermore, the header of the structured file shown inFIG.7may also include the identifiers of the accommodating station102where the bare metal server3is deployed and the corresponding data centers103and104thereto.

Returning back toFIG.6, in step S5, the installation instructing unit15of the server management apparatus1reads out the structured files stored in the structured file storage unit17and extracts the bare metal server3of which bare metal server status flag75is not set to ON. The installation instructing unit15sends an instruction to install the OS and the virtualization software to the extracted bare metal servers3, in other words, normal bare metal servers3that satisfy the conditions to install the OS and the virtualization software, respectively.

It is also possible to automatically execute the transmission of the instruction of the OS installation to a plurality of bare metal servers3at once. For example, the command to execute the installation can be written in a script in advance, and the script execution task can be registered in the task folder18to be started at a predetermined schedule. Thus, it makes it possible to automatically execute the task with the list of the bare metal servers3extracted in step S5as a parameter.

As described above, according to the present embodiment, the server management apparatus acquires information on each of bare metal servers and information on hardware components included in the bare metal server from a plurality of bare metal servers deployed in a plurality of accommodating stations, respectively, using the identifier of a control board of the bare metal server as a key, analyzes the acquired information, and generates a bare metal server status flag from the information of the bare metal server and the hardware components.

Furthermore, the server management apparatus further generates a structured file in a readable format that stores the acquired bare metal server information and hardware component information in a hierarchical manner, and describes the generated bare metal server status flag in a header of the structured file.

This allows servers to be deployed expeditiously with higher accuracy in a large-scale network constructed on the virtualization infrastructure. In particular, the information on bare metal servers, hardware components, and status flags indicating whether or not any of the bare metal server and the hardware components thereof has abnormality are stored in the structured file in a readable format. Therefore, it makes it possible to easily and arbitrarily extract and process the information necessary for diagnosis and deployment of a large number of bare metal servers even in a multi-vendor environment. As a result, it makes it possible to contribute to the efficiency and automation of the construction and operation of the network virtualization infrastructure.

Second Embodiment

Hereinafter, referring now toFIGS.9and10, the server management apparatus according to a second embodiment will be described in detail solely with respect to aspects that differ from those of the first embodiment above.

The present embodiment determines whether or not the firmware needs to be updated before installing the OS or the virtualization software on the bare metal server deployed in the accommodating station, and describes information indicating whether or not the firmware needs to be updated in the header of the structured file.

In order to construct network virtualization infrastructures in a plurality of accommodating stations102, respectively, it is required to update the firmware of the bare metal servers as necessary, and to install the OS and the virtualization software on the bare metal servers with the appropriately updated firmware. The present embodiment describes, in the header of the structured file, information indicating whether or not the firmware update is required for each of a large number of bare metal servers deployed in a plurality of accommodating stations, thereby enabling the unified or centralized management of the firmware update.

FIG.9is a block diagram illustrating an exemplary functional configuration of the server management apparatus1according to the second embodiment.

Referring toFIG.9, the server management apparatus1includes a server information acquisition unit11, an analysis unit12, a structured file generation unit13, a firmware update determination unit141, a firmware update instructing unit151, an input/output unit16, a structured file storage unit17, and a task folder18.

The server information acquisition unit11, the analysis unit12, the structured file generation unit13, the input/output unit16, the structured file storage unit17, and the task folder18of the server management apparatus1are similar to those of the above first embodiment shown inFIG.3.

According to the present embodiment, the firmware update determination unit141refers to the analyzed bare metal server information supplied from the analysis unit12to determine whether or not to update the firmware of the bare metal server3concerned.

More particularly, the firmware update determination unit141refers to the information indicating the firmware version of the bare metal server included in the bare metal server information to determine whether or not the firmware version described in the bare metal server information satisfies the prerequisites for the OS to be installed, and generates a firmware update flag indicating whether or not the firmware of the bare metal server3needs to be updated.

In other words, the firmware update determination unit141sets the generated firmware update flag to ON when the firmware of the bare metal server3is determined to be updated. The firmware update flag generated by the firmware update determination unit141is stored in the structured file of the bare metal server3concerned. This firmware update flag may be described in the header of the structured file.

The firmware update determination unit141may also refers to the information on the hardware components included in the bare metal server information to determine whether or not to update the firmware of any of the hardware components of the bare metal server3.

In this case, the firmware update determination unit141determines whether or not the firmware version of each of the hardware components of the bare metal server3satisfies the prerequisites of the OS to be installed, and when it is determined that the firmware of any of the hardware components needs to be updated, the firmware update determination unit141may generate a second firmware update flag indicating whether or not the firmware of the hardware component concerned needs to be updated. Alternatively, the firmware update determination unit141may, instead of generating the second firmware update flag, add a value indicating the firmware update of the hardware component concerned to a part of the firmware update flag of the bare metal server3.

The firmware update instructing unit151instructs the bare metal server3to update the firmware prior to the installation of the OS and the virtualization software on the bare metal server3. Subsequent to instructing the firmware update, the firmware update instructing unit151may further instruct the bare metal server to install the OS and the virtualization software on the bare metal server3.

More particularly, the firmware update instructing unit151reads out the structured files of respective bare metal servers3stored in the structured file storage unit17, refers to the firmware update flag described in the structured file, and extracts the bare metal server of which firmware update flag is set to ON, in other words, the bare metal server for which the firmware is required to be updated. The firmware update instructing unit151sends an instruction to each of the extracted bare metal servers, of which firmware is determined to be required to be updated, to update the firmware prior to the installation of the OS and the virtualization software. Here, the term “firmware update” includes both a normal update and an upgrade with functional enhancements.

FIG.10is a flowchart illustrating an exemplary detailed processing procedure of the firmware update processing of the bare metal server performed by the server management apparatus according to the second embodiment.

Referring toFIG.10, steps S1and S2are similar to the steps S1and S2of the first embodiment shown inFIG.6.

Subsequent to step S2, in step S31, the firmware update determination unit14of the server management apparatus141determines whether or not the firmware of the bare metal server3needs to be updated based on the analysis results acquired in step S2. More particularly, the firmware update determination unit141generates the firmware update flag, refers to the analyzed bare metal server information acquired in step S2to determine whether or not the firmware of the bare metal server3needs to be updated, and when it is determined that the firmware needs to be updated, set the firmware update flag to ON.

It should be noted that the firmware update flag is set to OFF when the firmware of the bare metal server3does not need to be updated, and the initial value of the firmware update flag is OFF. When any firmware of any of the bare metal server3and respective hardware components needs to be updated, the firmware update status flag may allow a plurality of values to be set, which is capable of identifying the component where the firmware update is required.

Referring toFIG.7, the header of the structured file may include the firmware update flag instead of or in addition to the firmware version77of the BMC51of the bare metal server3. The firmware version77included by the header of the structured file is also one embodiment of the information that indicates whether or not the firmware needs to be updated.

Returning back toFIG.10, step S4is similar to step S4of the first embodiment shown inFIG.6.

Subsequent to step S4, in step S51, the firmware update instructing unit151of the server management apparatus1reads out the structured file stored in the structured file storage unit17and extracts the bare metal server3of which firmware update flag is set to ON. The firmware update instructing unit151sends an instruction to update the firmware to the extracted bare metal server3, in other words, the bare metal server3for which the firmware is to be updated, prior to the installation of the OS and the virtualization software.

It is also possible to automatically execute sending of the firmware update instructions to a plurality of bare metal servers3at once. For example, the commands to execute the firmware update is described in a script in advance, and the script execution task is registered in the task folder18to be started on a predetermined schedule. Thus, the task can be automatically executed with the list of the bare metal servers3extracted in step S51as a parameter.

As described above, according to the present embodiment, the server management apparatus acquires information on the bare metal server and hardware components included in the bare metal server concerned from a plurality of bare metal servers deployed in a plurality of accommodating stations, using the identifier of the control board of the bare metal server as the key. The server management apparatus further analyzes the acquired information to generate a firmware update flag.

The server management apparatus yet further generates a structured file in a readable format that hierarchically stores the acquired bare metal server information and hardware component information, which includes a header describing the generated firmware update flag.

Therefore, it makes it possible to update the firmware in the servers expeditiously with higher accuracy in a large-scale network constituted by the virtualization infrastructure. In particular, since the structured file according to the present embodiment stores the information on bare metal servers, hardware components, and the firmware update flag indicating whether or not the firmware needs to be updated in a readable format, it makes it possible to easily and arbitrarily extract and process the information necessary to update and deploy the firmware of a large number of bare metal servers even in a multi-vendor environment. As a result, it makes it possible to contribute to the efficiency and automation of the construction and operation of the network virtualization infrastructure.

<Hardware Configuration of Server Management Apparatus>

FIG.11is a block diagram illustrating a non-limiting example of the hardware configuration of the server management apparatus1according to the present embodiment.

The server management apparatus1according to the present embodiment may be implemented in any single or a plurality of computers or any other processing platform. The server management apparatus1may be implemented in a general-purpose server device that constitutes a cloud, or otherwise in a dedicated server device.

Referring toFIG.11, although an example of the server management apparatus1being implemented in a single computer is shown, alternatively, the server management apparatus1according to the present embodiment may be implemented in a computer system including a plurality of computers. The plurality of computers may be intercommunicatively connected by a wired or wireless network.

As shown inFIG.11, the server management apparatus1may include a CPU111, a ROM112, a RAM113, an HDD114, an input unit115, a display unit116, a communication I/F117, and a system bus118. The server management apparatus1may also be equipped with an external memory.

The CPU (Central Processing Unit)111controls entire operations of the server management apparatus1in a comprehensive manner, and controls the operations of respective components112to117via the system bus118, which serves as a data transmission path.

The ROM (Read Only Memory)112is a non-volatile memory that stores the control programs and the like necessary for the CPU111to execute the processing.

Those programs may be stored in a non-volatile memory such as an HDD (Hard Disk Drive)114, an SSD (Solid State Drive), or removable storage media (not shown).

The RAM (Random Access Memory)113is a volatile memory and functions as a main memory, a work area, or the like of the CPU111. In other words, the CPU111loads the necessary programs and the like from the ROM112into the RAM113and executes the programs to realize various functional operations.

The HDD114stores, for example, various data and information necessary for the CPU111to perform processing using the programs. In addition, the HDD114stores, for example, various data and various information and the like obtained by the CPU111performing the processing using the programs and the like.

The input unit115is constituted with a pointing device such as a keyboard or a mouse.

The display unit116is constituted with a monitor such as a liquid crystal display (LCD). The display unit116may provide a GUI (Graphical User Interface) that is used to input instructions to the server management apparatus1for various parameters used in the bare metal server diagnosis processing, communication parameters used in communication with other devices, or the like.

The communication I/F117is an interface that controls communication between the server management apparatus1and external devices.

The functions of at least some of the components of the server management apparatus1shown inFIGS.3and9may be realized by the CPU111executing the programs. However, at least some of the functions of the components of the server management apparatus1shown inFIGS.3and9may be operated by a dedicated hardware. In this case, the dedicated hardware operates based on the control of the CPU111.

Although certain embodiments have been described above, the embodiments described are merely illustrative and are not intended to limit the scope of the present invention. The apparatus and methods described herein may be embodied in other forms than those described above. In addition, without departing from the scope of the present invention, omissions, substitutions, and modifications may be made to the above embodiments as appropriate. Such omissions, substitutions, and modifications fall within the scope of the appended claims and equivalents thereof, and fall within the technical scope of the present invention.

REFERENCE SIGNS LIST

1: Server Management Apparatus;3: Bare Metal Server;5: Motherboard;11: Server Information Acquisition Unit;12: Analysis Unit;13: Structured File Generation Unit;14: Diagnosis Unit;15: Installation Instructing Unit;16: Input/Output Unit;17: Structured File Storage Unit;18: Task Folder;19: Operation Terminal;21: NFVI;22: VNF;23: MANO;24: OSS/BSS;41: TOR;42: vDU;43: vCU;44: MBH Router;51: BMC;52: NIC Controller;53: NIC;54; RAID Controller;54a: RAID;55: Non-volatile Memory;56: Memory;57: CPU;58: SEL Log;59: System Sensor;80; Structured File;100: Mobile Network;101: Base Station;102: Accommodating Station;103: RDC;104: CDC;105: Internet;111: CPU;112: ROM,113: RAM,114: HDD;115: Input Unit;116: Display Unit;117: Communication I/F;118: System Bus;141: Firmware Update Determination Unit;15: Firmware Update Instructing Unit