JP2016099883A - Communication apparatus, management terminal, branding application method, and computer program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a server device and the like that enable the application of branding without requiring revision of BMC FW.SOLUTION: A communication apparatus comprises: reading means that, when receiving a request of reading a file referred to by a management module managing the self communication apparatus in accordance with an object-oriented management schema that is mounted on a BMC and manages a non-homogeneous device from a management terminal with which the communication apparatus can communicate, reads the file from a prescribed storage place in the BMC and returns it to the management terminal; and update means that, when receiving the file updated using unique information corresponding to a branding destination of the self communication apparatus from the management terminal, updates the file in the storage place by using the updated file.SELECTED DRAWING: Figure 1

Description

  The present invention discloses a technique for updating brand information.

  A CIM (Common Information Model) is adopted as a standard schema that enables management information to be exchanged in a network environment including devices of various vendors.

  The CIM schema is an object-oriented management schema for managing non-homogeneous devices, and obtains information about devices in the network and designates a class to be called by the management program in order to execute management operations.

  In the CIM environment, a management target is managed by a remote terminal equipped with a CIM application. The CIM application has a function of transmitting a CIM management request for executing a management operation related to a management target to the management target (server device).

  The server device managed in response to the CIM management request acquires hardware management information and transmits it to the CIM application by using a SMASH-CLP (Systems Management Architecture for Server Hardware (SMASH) Command Line Protocol) module or the like. To do.

  SMASH is defined by DMTF (Distributed Management Task Force) and defines a command line protocol for exchanging with the CIM infrastructure and a profile for hardware management. The SMASH-CLP module (hereinafter simply referred to as “SMASH-CLP”) enables SSH (Secure Shell) -based connection between a remote terminal and hardware to be managed. As a module for performing hardware management in response to a CIM management request in this way, there is, for example, a WS-MAN (Web Service Management) module (hereinafter simply referred to as “WS-MAN”) in addition to SMASH-CLP.

  CIM is mainly composed of a CIM object manager (hereinafter referred to as “CIMOM”), a CIM provider, and a CIM repository when VMware (registered trademark) of VMware is adopted as an OS (Operation System) of a server. .

  A CIM provider is a mechanism that provides a management connection to device drivers and hardware. CIM providers include add-on CIM providers provided by hardware vendors including server manufacturers and hardware device vendors, in addition to standard CIM providers provided by VMware.

  By creating a CIM provider, hardware vendors can provide the monitoring and management functions of the devices that they provide.

  The server that has received the CIM management request from the CIM application acquires management information from the hardware to be managed by the CIM provider. The CIMOM receives management information from the CIM provider and provides the information to the CIM application via the SMASH-CLP, WS-MAN, or the like.

  The CIM application receives the above information to manage and monitor the hardware.

  With such a CIM schema, hardware mounted on servers of various vendors can be monitored by a remote terminal on a standard basis.

  The CIM repository is a storage area used by CIMOM, and information (CIM class information) related to CIM-compliant classes (hereinafter referred to as “CIM classes”), correspondence between CIM class information and CIM providers, etc. Is stored.

  Here, the function that enables hardware monitoring from a remote terminal as described above is implemented in a system management controller (BMC) in the server device. That is, a BMC FW (Firmware) operating in the BMC has functions such as the above-described SMASH-CLP, WS-MAN, CIMOM, CIM provider, and CIM repository.

  Here, the BMC FW can be mounted in accordance with an original equipment manufacturer (OEM). That is, a function according to the specification of the OEM destination can be incorporated into the BMC FW.

  In the DMTF standard, a definition file that defines commands that can be used by SMASH-CLP and a CIM repository referenced by CIMOM store unique information according to the specifications of the OEM destination (vendor).

  The definition file defines related classes and usable commands for each target (UFCT: User Friendly class Tag) which is a simple name of the CIM class. As commands, standard commands that can be executed by SMASH-CLP and OEM commands are defined. The OEM command is a vendor-specific command other than the standard command.

  The CIM repository may include vendor-specific information (brand information).

  As described above, since the definition file and the CIM repository include vendor-specific information, it is necessary to implement vendor-specific information (branding application) in the BMC.

  Patent Document 1 discloses, for example, a technique in which an apparatus participates in a CIM network environment and can interface with a management application that issues a management-related request as a CIM API (Application Programming Interface). This technology reduces the need to provide device vendors with improved methods to develop CIM providers that provide device specific APIs to implement the CIM API.

  Non-Patent Document 1 describes details of the CIM schema established by DMTF.

JP 2009-266245 A

http://dmtf.org/standards/cim Search on November 10, 2014

  As described above, the definition file that defines commands that can be used by the SMASH-CLP includes vendor-specific commands, and therefore can be defined or updated only after the OEM destination is determined. Therefore, it is necessary to create or update the definition file after determining the OEM destination and to revise the BMC FW.

  In addition, the CIM repository referred to by CIMOM cannot be dynamically created according to the OEM destination. This is because an environment for compiling and generating a CIM repository requires a large capacity, and it is difficult to incorporate the environment into the BMC due to the BMC capacity constraints. Therefore, the CIM repository cannot be dynamically created according to the OEM destination, and it is necessary to create a CIM repository and update the BMC FW in order to update the brand information after the OEM destination is determined.

  The above-mentioned Patent Document 1 discloses a method of developing a CIM provider that provides a device-specific API, but does not disclose a technique for applying branding without requiring revision of the BMC FW.

  The present invention has been made in view of the above problems, and has as its main object to provide a communication device and the like that can be applied for branding without requiring revision of the BMC FW.

  The first communication device of the present invention is a management capable of communicating a read request of a file referred to by a management module that manages its own device in accordance with an object-oriented management schema that is implemented in a BMC and manages a non-homogeneous device. When received from a terminal, the file is read from a predetermined storage location in the BMC and returned to the management terminal, and the file updated from the management terminal with unique information according to the branding destination of the own device And updating means for updating the file at the storage location with the updated file.

  A first management terminal according to the present invention includes a transmission / reception unit that transmits / receives information to / from a communication device that is installed in a BMC and that has a management module that manages the device according to an object-oriented management schema that manages a non-homogeneous device. The communication device transmits a read request for a file referred to by the management module to the communication device via the transmission / reception unit, and the file received in response to the read request corresponds to a branding destination of the communication device. And a branding file creating means for updating with the unique information.

  The first branding application system according to the present invention is capable of communicating with a communication device that includes a management module that is installed in a BMC and that manages its own device in accordance with an object-oriented management schema that manages non-homogeneous devices. A management terminal, and when the communication device receives a read request for a file referred to by a management module from the management terminal, the communication device reads the file from a predetermined storage location in the BMC and returns it to the management terminal. And a updating unit that updates the file at the storage location with the updated file when the file updated with the unique information corresponding to the branding destination of the device is received from the management terminal. The management terminal includes a transmitting / receiving means for transmitting / receiving information to / from the communication device; The communication device transmits a read request for the file referred to by the management module to the communication device via the transmission / reception unit, and the file received in response to the read request includes the unique information corresponding to the branding destination of the communication device. And a branding file creation means to be updated.

  The first branding application method of the present invention can communicate a read request of a file referred to by a management module that manages the own device in accordance with an object-oriented management schema that is implemented in the BMC and manages a non-homogeneous device. Upon receiving from the management terminal, the file is read from a predetermined storage location in the BMC and returned to the management terminal, and the file updated with unique information corresponding to the branding destination of the own device is received from the management terminal. Then, the file in the storage location is updated with the updated file.

  This object is also achieved by a computer program that implements the communication device, management terminal, or branding application method having the above-described configurations by a computer, and a computer-readable storage medium that stores the computer program. Is done.

  According to the present invention, there is an effect that branding can be applied without requiring revision of the BMC FW.

It is a figure which shows the structure of the server system which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the file which comprises the CIM repository with which the server apparatus which concerns on the 1st Embodiment of this invention is provided. It is a figure which shows an example of the definition file with which the server apparatus which concerns on the 1st Embodiment of this invention is provided. It is a block diagram which shows the structure of the branding information control part with which the server apparatus which concerns on the 1st Embodiment of this invention is provided, and a management terminal. It is a figure which shows an example of the file format table which the branding information control part with which the server apparatus which concerns on the 1st Embodiment of this invention is provided contains. It is a figure which shows an example of the file storage location table which the branding information control part with which the server apparatus which concerns on the 1st Embodiment of this invention is provided contains. It is a figure which shows the operation | movement in which the server apparatus which concerns on the 1st Embodiment of this invention implements branding application according to the request | requirement from a management terminal. It is a figure which shows the structure of the communication apparatus which concerns on the 2nd Embodiment of this invention. It is a figure which illustrates the hardware constitutions of the apparatus which concerns on each embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

First Embodiment FIG. 1 is a block diagram showing a configuration of a server system 1000 according to a first embodiment of the present invention. The server system 1000 includes a server device 100, a remote terminal 200, and a management terminal 300.

  The server device 100 is managed and monitored by the remote terminal 200 according to the CIM schema. The remote terminal 200 includes a CIM application that transmits a CIM management request for executing a management operation related to a management target to the server device 100.

  The management terminal 300 performs settings related to branding application (details will be described later) in the server device 100. The management terminal 300 is connected to the server device 100 via a USB (Universal Serial Bus) IF (Interface) and transmits / receives information.

  The management terminal 300 also transmits / receives information to / from server apparatuses 100-2 to 100-n (n is a natural number) connected via a network via a LAN (Local Area Network) IF.

  The server apparatus 100 includes a BMC 110 that is a system management controller. The BMC 110 is equipped with the following functions by the BMC FW that controls the BMC 110. That is, the BMC 110 includes the functions of the SMASH-CLP 111, the WS-MAN 112, the CIMOM 113, the CIM providers 114-1 to 114-n (n is a natural number), the definition file 115, and the CIM repository 116.

  The BMC 110 also includes a branding information control unit 120, an IF 130 including a USB IF and a LAN IF.

  The SMASH-CLP 111 and WS-MAN 112 installed in the BMC 110 manage the interface with the remote terminal 200 via the CIM instance.

  The remote terminal 200 can access the SMASH-CLP 11 using the SSH protocol, and can access the WS-MAN 112 using the HTTP (Hypertext Transfer Protocol).

  When the CIMOM 113 acquires a CIM management request from the remote terminal 200 via the SMASH-CLP 111 or the WS-MAN 112, the CIMOM 113 refers to the class information regarding the class for acquiring the management information corresponding to the request from the CIM repository 116. Then, the CIMOM 113 calls the CIM provider 114-i (i = 1 to n: n is a natural number) corresponding to the class information defined in the CIM repository 116. The CIM management request includes creation, modification, deletion, etc. of a CIM instance. In this embodiment, a CIM instance is an entity of CIM class data collected regarding hardware to be managed.

  In response to the CIM management request, the CIM provider 114-i creates and changes a CIM instance related to hardware to be managed. The CIM provider 114-i exists for each CIM class supported by the BMC 110.

  The CIMOM 113 passes the CIM instance acquired from the CIM provider 114-i to the SMASH-CLP 111 or the WS-MAN 112. The SMASH-CLP 111 or the WS-MAN 112 acquires or changes the CIM instance from each CIM provider via the CIMOM 113. The SMASH-CLP 111 or the WS-MAN 112 transmits a CIM instance to the remote terminal 200, so that the hardware monitoring is performed by the remote terminal 200.

  Here, the CIM repository 116 referred to by the CIMOM 113 when acquiring the CIM instance stores the CIM class supported by the BMC 110 and CIM property information defined by the CIM class. FIG. 2 is a diagram illustrating an example of files constituting the CIM repository 116. As shown in FIG. 2, the CIM repository defines class information.

  In FIG. 2, for example, the CIM class A is defined by the standard property 1 to the standard property n and the OEM property 1 to the OEM property n. As described above, the definition of the class information includes a standard property defined by the CIM standard and an OEM property. In the present embodiment, the OEM property indicates a property including a vendor name (brand information).

  A tag indicating that the file is a file constituting the CIM repository is inserted in advance at the head of the file constituting the CIM repository 116.

  On the other hand, the definition file 115 is a file included in the configuration file defined by the standard of SMASH-CLP111. The configuration file describes setting information related to the operation of the SMASH-CLP 111. The definition file 115 defines commands that can be used by the SMASH-CLP 111 among the setting information.

  FIG. 3 is a diagram illustrating an example of the definition file 115. As shown in FIG. 3, the definition file 115 defines a CIM class related to a target (UFCT), which is a simple name of the CIM class, and a command executable on each target. The definition of the command includes standard commands of SMASH-CLP 111 supported by the target and OEM commands different for each vendor other than the standard commands. DMTF stipulates that the vendor name is included in the name of the OEM command.

  Also, in the definition file 115, a tag indicating that the file is a definition file of a command that can be executed on the target is inserted at the beginning of the file.

  FIG. 4 is a block diagram illustrating a configuration of the branding information control unit 120 and the management terminal 300 included in the server apparatus 100 illustrated in FIG. In response to a request from the management terminal 300, the branding information control unit 120 performs branding application.

  Here, branding application refers to a process of applying information (for example, inserting a vendor name) according to a vendor destination to information different for each vendor included in the definition file 115 and the CIM repository 116.

  4, the branding information control unit 120 includes a control unit 121, a reading unit 122, a file verification unit 123, a file format conversion unit 124, a file update unit 125, a BMC revision information 126, a file format table 127, and a file storage. A location table 128 is provided.

  The management terminal 300 also includes an input / output IF 310, a branding file creation unit 311, a transmission / reception unit 312, and an IF 313 including a USB IF and a LAN IF.

  The branding information control unit 120 transmits and receives requests and files to and from the management terminal 300 via the IF 130 provided in the BMC 110 and the IF 313 of the management terminal 300.

  An outline of each component of the branding information control unit 120 will be described.

  The control unit 121 of the branding information control unit 120 controls the request and file received via the IF 130 or the entire branding information control unit 120. The reading unit 122 reads a branding file in response to a branding file read request from the management terminal 300. The branding file refers to a definition file 115 including vendor-specific information such as a vendor name and a file constituting the CIM repository 116.

  The file verification unit 123 verifies the branding file acquired from the management terminal 300. Specifically, the file verification unit 123 verifies that the file is a branding file by detecting tag data for the branding file transmitted from the management terminal 300 via the IF 130. Further, the file verification unit 123 verifies that the file is not broken by performing a CRC check on the received branding file. The file verification unit 123 can prevent branding from being applied by a broken file or a file that is not a branding file.

  The file format conversion unit 124 converts the branding file into a file format corresponding to (supported by) BMC revision. Specifically, the file format conversion unit 124 reads information on the file format corresponding to the current BMC revision from the file format table 127 and converts the received branding file into a file format corresponding to the BMC revision. .

  The file update unit 125 applies the updated branding file to a predetermined storage location corresponding to the current BMC revision. Specifically, the file update unit 125 reads a file storage location corresponding to the current BMC revision from the file storage location table 128, and the file in the format converted by the file format conversion unit 124. Update by exclusive control.

  The BMC revision information 126 includes information indicating the current BMC revision, for example, information such as “1.0” and “2.0”.

  The file format table 127 includes file format information corresponding to the BMC revision. FIG. 5 is a diagram illustrating an example of the file format table 127. The file storage location table 128 stores associations between BMC revisions and branding file storage locations. FIG. 6 is a diagram illustrating an example of the file storage location table 128.

  Next, an outline of each component of the management terminal 300 will be described.

  The input / output IF 310 receives an instruction from the operator, that is, accepts an OEM destination vendor name or branding application execution request, or displays a branding application execution propriety message. The branding file creation unit 311 creates a branding file to be transmitted to the server device 100. The transmission / reception unit 312 transmits / receives requests, branding files, and the like to / from the server apparatus 300 via the IF 313.

  Next, the operation for implementing branding will be described. FIG. 7 is a diagram illustrating an operation in which the branding information control unit 120 implements branding application in response to a request from the management terminal 300. With reference to FIG. 7, the operation of implementing branding will be described.

  When the input / output IF 310 of the management terminal 300 acquires the vendor name as the OEM destination from the operator, the input / output IF 310 notifies the branding file creation unit 311 of the vendor name and sends a branding file acquisition request to the server device via the transmission / reception unit 312. 100 (S101).

  The branding file acquisition request is notified to the branding information control unit 120 of the server device 100. The branding information control unit 120 notifies the request to the reading unit 122 by the control unit 121. The reading unit 122 reads the branding file, that is, the definition file 115 and the CIM repository 116 from the branding file storage location with reference to the file storage location table 128 (S102). The control unit 121 returns the read branding file to the management terminal 300 via the IF 130 (S103).

  In the branding file creation unit 311, the management terminal 300 searches the received branding file for data having different information for each vendor (hereinafter also referred to as “OEM data”). Here, in the definition file 115 and the CIM repository 116 shown in FIGS. 2 and 3, the data indicated by “A” is OEM data. The branding file creation unit 311 inserts the vendor name acquired from the input / output IF 310 into the retrieved OEM data (S104).

  Subsequently, when a branding application request is input to the input / output IF 310 from the operator, the branding file creation unit 311 sends the branding application request and the created (updated) branding file to the server apparatus 100 via the transmission / reception unit 312. (S105).

  The server apparatus 100 receives the branding application request and the branding file via the IF 130. The control unit 121 of the branding information control unit 120 notifies the file verification unit 123 of an instruction to verify the received branding file.

  The file verification unit 123 performs a CRC check on the received branding file and verifies the validity (S106). Further, the file verification unit 123 verifies whether or not a tag indicating that the file is a branding file, that is, a command definition file or a CIM repository file is inserted in the received branding file ( S106). The file verification unit 123 notifies the control unit of the verification result.

  As a result of the verification, when the branding file is broken or when the tag is not inserted in the branding file (No in S107), the control unit 121 gives an error to the branding application request received from the management terminal 300. Return (S108). When receiving the error, the input / output IF 310 displays an error message (S109). In response, the operator stops the implementation of branding.

  On the other hand, as a result of the verification, if the validity of the branding file can be confirmed (Yes in S107), the control unit 121 notifies the file format conversion unit 124 of an instruction to convert the format of the received branding file.

  In response to the notification, the file format conversion unit 124 reads the current BMC revision information from the BMC revision information 126 and also reads the file format information corresponding to the revision from the file format table 127. Then, the file format conversion unit 124 converts the received branding file into the read file format (S110).

  Subsequently, the control unit 121 notifies the file update unit 125 of an instruction to update the definition file 115 and the CIM repository 116 using the format-converted branding file.

  In response to the notification, the file update unit 125 reads the storage location of the definition file 115 and the CIM repository 116 from the file storage location table 128 and updates the file stored in the location with the branded file converted in the format. (S111).

  As described above, according to the first embodiment, the management terminal 300 sets the IFs 313 and 130 to the BMC 110 on which the definition file 115 including different information for each vendor and the CIM repository 116 are installed in the server apparatus 100. The branding file is requested to be read through. In the branding file creation unit 311, the management terminal 300 updates information that is different for each vendor included in the branding file received in response to the request with information (for example, vendor name) input by the operator. The management terminal 300 transmits the updated branding file to the server device 100. The BMC 110 of the server apparatus 100 updates the definition file 115 and the CIM repository 116 with the received branding file by the branding information control unit 120.

  By adopting the above configuration, according to the first embodiment, the brand information (OEM data) mounted on the BMC 110 can be updated by the management terminal 300, so a new OEM destination has been added. In this case, there is an effect that it is possible to implement branding without requiring revision of the BMC FW.

  In addition, when the definition file 115 or the CIM repository 116 is out of order or when the BMC is replaced, only the branding file can be updated by connecting the management terminal 300 to the server device 100. Therefore, unnecessary update is unnecessary and maintenance is performed. The effect that time can be shortened is obtained.

  Further, by connecting the management terminal 300 to a plurality of server devices via a LAN during production of the server device, it becomes possible to implement branding of a plurality of server devices at once without revising the BMC FW. . Since the branding application time (file update time) is significantly shorter than the BMC FW update time, the production cost can be greatly reduced.

Second Embodiment FIG. 8 is a diagram illustrating a configuration of a communication apparatus 400 according to a second embodiment of the present invention. As illustrated in FIG. 8, the communication device 400 includes a reading unit 410 and an updating unit 420.

  When the reading unit 410 receives a read request for a file referenced by a management module that manages its own device in accordance with an object-oriented management schema that is implemented in the BMC and manages a non-homogeneous device, from the communicable management terminal, The file is read from a predetermined storage location in the BMC and returned to the management terminal.

  When the update unit 420 receives a file updated with unique information corresponding to the branding destination of the own device from the management terminal, the update unit 420 updates the file in the storage location with the updated file.

  Note that the object-oriented management schema for managing non-homogeneous devices corresponds to the CIM schema in the first embodiment. The management module also corresponds to SMASH-CLP, WS-MAN, and CIMOM.

  By adopting the above configuration, according to the second embodiment, since the branding file stored in the communication device can be updated from the management terminal, it is possible to apply the branding without requiring the revision of the BMC FW. An effect is obtained.

  Note that each unit of the server apparatus 100 and the management terminal 300 illustrated in FIG. 1 and the like is realized by hardware resources illustrated in FIG. 9 includes a CPU (Central Processing Unit) 10, a RAM (Random Access Memory) 11, a ROM (Read Only Memory) 12, an external connection interface 13, and a storage medium 14. The CPU 10 controls the overall operation of the server apparatus 100 and the management terminal 300 by reading various software programs (computer programs) stored in the ROM 12 or the storage medium 14 into the RAM 11 and executing them. That is, in each of the above embodiments, the CPU 10 executes a software program for executing each function (each unit) included in the server device 100 and the management terminal 300 while appropriately referring to the ROM 12 or the storage medium 14.

  Moreover, in each embodiment mentioned above, about the case where the function shown to each block in the server apparatus 100 shown in FIG. 1 etc. and the management terminal 300 is implement | achieved by a software program as an example which CPU10 shown in FIG. 9 performs. explained. However, some or all of the functions shown in each block shown in FIG. 1 and the like may be realized as hardware.

  Further, in the present invention described by taking each embodiment as an example, after the computer program capable of realizing the functions described above is supplied to the server apparatus 100 and the management terminal 300, the CPU 10 stores the computer program in the RAM 11. This can be achieved by reading and executing the above.

  The supplied computer program may be stored in a computer-readable storage device such as a readable / writable memory (temporary storage medium) or a hard disk device. In such a case, the present invention can be understood as being configured by a code representing the computer program or a storage medium storing the computer program.

  The present invention can be applied to, for example, a server apparatus that employs CIM as a standard specification schema for managing hardware.

10 CPU
11 RAM
12 ROM
13 External Connection Interface 14 Storage Medium 100, 100-2 to 100-n Server Device 110 BMC
111 SMASH-CLP
112 WS-MAN
113 CIMOM
114-1 to 114-i CIM provider 115 definition file 116 CIM repository 120 branding information control unit 121 control unit 122 reading unit 123 file verification unit 124 file format conversion unit 125 file update unit 126 BMC revision information 127 file format table 128 file storage Location table 130, 313 IF
200 Remote terminal 300 Management terminal 310 Input / output IF
311 Branding file creation unit 312 Transmission / reception unit

Claims (9)

When a read request for a file referred to by a management module that manages a self-device in accordance with an object-oriented management schema that is implemented in a BMC (Baseboard Management Controller) and manages a non-homogeneous device is received from a communicable management terminal, Reading means for reading the file from a predetermined storage location in the BMC and returning it to the management terminal;
And a updating unit configured to update the file in the storage location with the updated file when receiving the file updated with the unique information corresponding to the branding destination of the own device from the management terminal. The communication apparatus according to claim 1, further comprising: format conversion means for converting the updated file received from the management terminal into a file format supported by the BMC. The communication device according to claim 1, wherein the file includes a definition of a command that can be executed by the management module. The communication apparatus according to any one of claims 1 to 3, wherein the file includes a definition of a class supported by the BMC. The communication apparatus according to any one of claims 1 to 4, wherein the object-oriented management schema includes a CIM (Common Information Model). A transmission / reception unit that transmits / receives information to / from a communication device that includes a management module that manages the device itself in accordance with an object-oriented management schema that is implemented in the BMC and manages a non-homogeneous device;
A request to read a file referred to by the management module is transmitted to the communication device via the transmission / reception means, and the file received in response to the read request is unique to the branding destination of the communication device. A management terminal equipped with a branding file creation means to update with information. A communication device equipped with a management module that manages the device itself in accordance with an object-oriented management schema that is implemented in the BMC and manages a non-homogeneous device; and a management terminal that can communicate with the communication device.
The communication device
Upon receiving a file read request referred to by the management module from the management terminal, the file is read from a predetermined storage location in the BMC and returned to the management terminal;
When receiving the file updated with the unique information corresponding to the branding destination of its own device from the management terminal, the update terminal comprises the update means for updating the file in the storage location with the updated file,
The management terminal
Transmitting / receiving means for transmitting / receiving information to / from the communication device;
A request to read a file referred to by the management module is transmitted to the communication device via the transmission / reception means, and the file received in response to the read request is unique to the branding destination of the communication device. Branding application system with branding file creation means to update with information. When a read request for a file referred to by a management module that manages its own device in accordance with an object-oriented management schema that is implemented in a BMC and manages a non-homogeneous device is received from a communicable management terminal, the file is stored in the BMC Read out from a predetermined storage location in, and returns to the management terminal,
A branding application method, wherein when the file updated with the unique information corresponding to the branding destination of the own device is received from the management terminal, the file in the storage location is updated with the updated file. When a read request for a file referred to by a management module that manages its own device in accordance with an object-oriented management schema that is implemented in a BMC and manages a non-homogeneous device is received from a communicable management terminal, the file is stored in the BMC A process of reading from the predetermined storage location and returning to the management terminal;
When receiving the file updated with the unique information according to the branding destination of the own device from the management terminal, the process of updating the file in the storage location by the updated file,
A computer program that is executed by a computer.

Images