JP2007299427A - Power control method, and system for achieving the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To secure a high security level in remote power control, and to execute system management having a high degree of freedom by determining whether to permit the remote power control by using attributes of a user carrying out the power control, and a group to which an assigned server belongs, and various kinds of other attributes. <P>SOLUTION: This power control method prevents a client from executing a remote power control request directly to a BMC existing on a server for processing the remote power control request from the outside, or a similar hardware device, but a management server 120 for collectively receiving the power control request from the client is installed instead. The management server authenticates the power control request received from the client by referring to various kinds of tables describing groups to which the user and the server belong to, and other attributes, and requests the remote power control to the server on behalf of the client only when authenticated. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to remote power control of a computer system.

  There is a power control technology that authenticates a requester of remote power control by a combination of a user ID and a password, and immediately determines whether or not the requested power control can be performed based on the result of successful authentication. Using this technology, a plurality or a single server is always kept in standby, and in response to a use request from a client, some or all of the resources of the waiting server are used exclusively by the client. When a system is configured to return the server used by the client to a standby state after the use is completed, as described in JP-A-2003-203189, when the client uses the server, the server is turned on. A server rental system for turning off the server can be configured.

  ACPI (Advanced Configuration and Power Interface) and IPMI (Intelligent Platform Management Interface) are existing technologies. Also, X.509 recommended by ITU-T (International Telecommunication Union Telecommunication Standardization Sector) exists as a standard for electronic key certificates.

JP 2003-203189 A

  The mechanism to allow remote control of blade servers, which are computers that are temporarily used in response to requests from client computers, and to allow clients to use blade server resources, has increased the number of clients using many blade servers. In connection with this, in the system configuration in which the power control of the blade server is performed, the following problems are solved, and the power control of the server computer at a location away from the client computer is facilitated.

  For the BMC (Baseboard Management Controller) of the component specified by IPMI used for remote power control, page 29 of "-IPMI-Intelligent Platform Management Interface Specification Second Generation v2.0 Document Revision 1.0" which is the IPMI specification It is introduced in. The BMC user authentication function has a hardware restriction that has only a simple function of storing a user ID and password combination and performing user authentication by comparing it, and there is no choice for the authentication method. A high security level cannot be secured.

  In addition, due to the above BMC restrictions, server allocation management that determines whether or not allocation and power control can be performed by grouping the user who performs power control with the server to be allocated, or by assigning multiple attributes. It is not possible to introduce a policy and perform system management with a high degree of freedom.

  Prevents control signals (including unauthorized power control requests and power control requests) from being sent directly to the BMC or similar hardware device that exists on the server and processes remote power control requests from the outside. Instead of setting up and installing devices, instead of installing a management server that centrally manages power control requests from clients, you can receive power control requests and authenticate power control requests on this management server. The management server takes over the power control only when As a result, it is possible to limit the entity that performs remote power control of the server to a reliable management server, and security can be ensured.

  In addition to the authentication of the power control request by the management server, the hardware control side that performs power control may authenticate the power control request by the management server. In the authentication performed by the management server, a combination of a user ID and a password may be simply received and authenticated as a user identifier, but the identity of the client user who made the power control request is guaranteed at a higher security level. For this purpose, a portable personal authentication device that uniquely identifies the user individual is connected to the client, and the user individual that corresponds to the X.509 format of the ITU-T recommendation installed on the personal authentication device is globally unique. If a personal certificate to be certified is transmitted together with a user identifier and authentication of the personal certificate is performed in addition to authentication by the user identifier, the user can be prevented from being forged by theft of the user ID and password.

  It is possible to easily control the power supply of a server computer located away from the client computer.

  Embodiments of the present invention will be described below.

  The best mode for carrying out the present invention will be described below in detail with reference to the drawings.

  FIG. 1 is an overall configuration diagram of a system that lends a blade server to a management server that performs user authentication and remote power control in response to a request from a client according to an embodiment of the present invention.

  The client 100 has a memory 101, a CPU 108, a USB (Universal Serial Bus) interface 109 that can connect a mouse, a keyboard, and a personal authentication device, and a video for connecting a display device and outputting screen information. An interface 110 and a NIC 111 are provided. Further, a remote control program 102, a power control request program 103, a user identifier generation program 104, and an OS 105 are stored on the memory 101.

  The remote control program 102 acquires the connection destination IP address 107 of the assigned blade server, connects to the remote control service 142 stored in the memory 141 of the blade server 140 and executed by the CPU 144, and connects to the video interface 110 of the client 100. A screen for controlling the blade server 140 is output on the connected display device, and the operation information of the mouse and keyboard connected to the USB interface 109 is transmitted to the remote control service 142, so that the user of the client 100 is GUI. The blade server 140 is controlled via (Graphical User Interface).

  The power control program 103 receives a power control instruction for the blade server 140 from the user of the client 100 and requests the management server 120 to execute the power control. The user identifier generation program 104 causes the user to input a user identifier that is input by the user and assigned to the individual, acquires the user identifier 106 that can uniquely identify the individual user, and stores it in the memory. . Further, the management server 120 has a connection destination IP address 107 of the assigned blade server that tabulates the connection destination IP address information of the remote control service on the blade server notified to the client 100 when the management server 120 assigns the blade server to the client 100. In FIG. 1, the client 100 is a so-called THIN client that does not include an HDD (Hard Disk Drive), but may include an HDD.

  The management server 120 includes a memory 121, a CPU 127, a USB interface 128 capable of connecting a mouse and a keyboard, an IDE (Integrated Drive Electronics) interface 129 for connecting an HDD, and an HDD 130 connected thereto. And a video interface 134 and a NIC 135 for connecting a display device and outputting screen information. The memory 121 stores a power control command 122, a power control program 123, a user authentication program 124, a request waiting program 125, and an OS 126. On the HDD 130, an allocation management table 131, a user management table 132, and a blade server management table 133 are stored.

  The blade server 140 is used to connect the memory 141, CPU 144, mBMC (mini-Baseboard Management Controller) 145 that omits some BMC functions, failure detection device 146, power control device 147, power supply 148, NIC 149, and HDD. IDE interface 150 and HDD 151 connected thereto.

  Here, the mBMC 145 conforms to the IPMI specification and performs power management according to an external request. The failure detection device 146 also monitors abnormalities by monitoring signals from temperature sensors and voltage sensors installed in the blade server, and has a function of returning the presence / absence of an abnormality in response to an inquiry from the outside. The power supply control device 147 has a function of controlling the power supply 148, and the power supply 148 supplies power supplied from the outside into the blade server. The NIC 149, the mBMC 145, and the power supply control device 147 are supplied with power from an auxiliary power supply (not shown in the drawing) different from the power supply 148, so that they always function even when the power supply 148 is off.

  Further, the memory 141 communicates with the OS 143 capable of controlling power supply in accordance with ACPI and the remote control program 102 on the client 100 to control the blade server 140 with respect to the remote control program 102. Remote control to send the client's 100 user information and control the blade server 140 by receiving the operation information of the mouse and keyboard connected to the client 100 from the client 100 and executing the operation. Service 142 is provided.

  The blade server 140 is also provided with a video interface for connecting a display device and outputting screen information, and an interface for connecting a keyboard and a mouse, and a power control command 122, a power control program 123, a user The authentication program 124, the request waiting program 125, and the OS 126 are stored in the memory 141, and the allocation management table 131, the user management table 132, and the blade server management table 133 are arranged on the HDD 151 and have the same configuration as the management server 120. By doing so, it can be used as the management server 120.

  The NIC 111 of the client 100 is connected to the IP network 160, the NIC 149 of the blade server 140 is connected to the IP network 164, and the IP network 160 and the IP network 164 are connected via the firewalls 161 and 163 and the router 162. . The router 162 is connected to the NIC 135 of the management server 120. The client 100, the management server 120, and the blade server 140 can perform bidirectional communication with each other. However, in order to prevent a malicious attacker from attacking the power control mechanism by means such as sending illegal messages, the firewall 161 sends packets sent from the IP network 160 side to the blade server group. Packets that have characteristics that affect power control (for example, if multiple IP addresses are assigned to NIC 149 of blade server 140 and received packets are separated on the OS side and power control side, the power control IP It can be set to filter and discard packets destined for addresses. Note that the communication method in the network between the IP network 160, the IP network 164, the router 162, and the NIC 135 may be wireless or wired.

  FIG. 2 is a detailed example of the blade server management table 133 on the HDD 130 of the management server 120. The blade server management table 133 has columns for blade server management number, blade server IP address, and blade server group. The blade server management number column contains information that uniquely identifies the blade server. The blade server IP address column contains the IP address assigned to the NIC of the blade server. The connection destination IP address when 102 communicates with the remote control service 142, and the group identifier representing the group to which each blade server belongs are registered in the column of the blade server group. Here, each blade server always belongs to one group.

  By grouping, it is possible to manage computers used according to user attributes such as departments and sections to which a plurality of users belong. Also, if there is a difference in the performance of each blade server, for example, the blade server belonging to group 1 is classified as high performance, the blade server belonging to group 2 is classified as low performance, or the applications stored in the blade server differ. For example, a blade server belonging to group 1 is classified as a graphics dedicated machine with a graphic application installed, and a blade server belonging to group 2 is classified as a word processing software or a business processing machine with spreadsheet software installed. It can be carried out.

  By grouping blade servers to be used in this way and performing power management in association with them, the power management user or administrator mistakenly operates the power of blade servers other than the group to which the user belongs. Disappears.

  FIG. 3 is a detailed example of the user management table 132 on the HDD 130 of the management server 120. The user management table 132 has columns for a user identifier, a user group, and a user authority. In the user identifier column, user identifiers that can uniquely identify users for all users who have the right to use the blade server from the client are registered. In the user group group column, a group identifier that designates a group of blade servers that are permitted to perform power management for the user corresponding to the user identifier registered in the user identifier column of the same row is registered. . In the user authority column, the user authority corresponding to the user identifier registered in the user identifier column in the same row with respect to power control is registered. There are two types of user authority: general user and administrator. A user with general user authority is assigned to the assignment management table 131 among blade servers that belong to the same group as their own group. Although it is possible to request power control only for blade servers that have their own user identifiers as possible user identifiers, users with administrator privileges are blade servers belonging to the same group as their own group Any blade server can request power control.

  FIG. 4 is a detailed example of the allocation management table 131. The assignment management table has columns for blade server management number, assignable user identifier, assignment status, power status, and failure status. A management number for uniquely identifying a blade server is registered in the management number column for the blade server, and a user identifier for a user that can be allocated to the blade server is registered in the user identifier column for the assignable user. There may be a plurality of users that can be assigned to the blade server. In this case, the user identifier of each user is registered. FIG. 4 shows that the blade server with management number 5 can be assigned to a plurality of users a, b, and c.

  However, assignment of a blade server means that one blade server is occupied by one user, and while the blade server is assigned to one of the assignable users, other users are assigned A blade server is not assigned redundantly. Conversely, it is possible for a single user to assign and use multiple blade servers. FIG. 4 shows that the user a can assign blade servers with management numbers 1, 3, and 5.

  When NULL is registered instead of the user identifier in the user identifier column, the blade server is not assigned to any user. The assignment status column stores information indicating whether the blade server is assigned to the client by the management server (not assignable) or not assigned (assignable). The power status column stores information indicating the power status of the blade server (on or off or unknown = information cannot be acquired for some reason). The failure presence / absence column stores a state where the failure detection device 146 of the blade server has detected an abnormality and a state of absence when it has not detected. The information on the power status and failure status columns is periodically updated by the management server request waiting program 125 by inquiring of the blade server mBMC 145 and failure detection device 146, respectively. There is no need to manually change this information according to the actual situation.

  Note that the administrator of the management server can view and edit the blade server management table 133, the user management table 132, and the assignment management table 131. If an assignable user identifier is temporarily rewritten to NULL and the problem with the blade server is resolved, the user identifier in the assignment management table 131 is returned to the state before rewriting. It is possible to prevent a user from being assigned to a suspected blade server. In addition, when the administrator of the management server is expected to use more users than the number of existing servers, the assignment table 131 is rewritten so that servers are preferentially assigned to users belonging to a specific group. It is possible to perform dynamic system management such as changing.

  The user of the client 100 can call the GUI screen 500 shown in FIG. 5 by executing the power control request program 103 after executing the user identifier generation program 104 and storing the user identifier 106 in the memory 101. The GUI screen 500 includes an information display / selection panel 501, a power-on button 502, a shutdown button 503, a forced power-off button 504, a reset button 505, and a message display area 507. Further, the information display / selection panel 501 has a part for displaying blade server management number, assignment status, power supply status, and failure information for each blade server that can be assigned to a user.

  The information displayed on the information display / selection panel 501 for the blade server management number, allocation status, power status, and information on the presence / absence of failure is the same as the content of the blade server management table 133, user management table 132, and allocation management table 131. These are output when the user having the user identifier a calls the GUI screen 500 in the state illustrated in FIG. 2, FIG. 3, and FIG. 4, respectively. From this content, it can be seen that the user having the user identifier a is assigned to the blade server corresponding to the management numbers 1 and 3 and can be used exclusively. The power supply control request program 103 periodically transmits the user identifier 106 to the management server 120, inquires about the information, and updates the display information displayed on the information display / selection panel 501.

  The information display / selection panel also displays a blade server that is a target of power operation when the user operates the power by pressing the power on button 502, the shutdown button 503, the forced power off 504, or the reset button 505. The radio button 506 which is a user interface for exclusively selecting one of a plurality of selection items is designated. The power-on button 502 is for instructing to turn on the blade server, and the shutdown button 503 is for instructing to turn off the power after the OS on the blade server is normally terminated. The button 504 instructs to immediately turn off the power without performing normal termination processing of the OS running on the blade server, and the reset button 505 is normal termination of the OS running on the blade server. Instructs execution of hardware initialization without performing processing.

  FIG. 6 shows processing performed by the client 100 and the management server 120 when the user makes a power control request on the client 100. First, on the GUI screen 500 of the power control request program 103 on the client 100, when the user presses the power on button 502, the shutdown button 503, the forced power off button 504, or the reset button 505, the power control request program 103 Is the power control type information corresponding to the pressed button, the blade server management number that uniquely identifies the blade server that is the target of the power operation selected by the radio button 506, and the individual user who requested the power control. A power control request message including a user identifier 106 that uniquely identifies the message is generated and transmitted 602 to the management server. The request waiting program 125 on the management server receives the message 603 of the power control request, extracts the user identifier 106 embedded in the message, and passes it to the user authentication 604. The user authentication 604 inquires whether the passed user identifier 106 exists in the user identifier column of the user management table 132. If the user identifier passed in the user identifier column exists, the user authentication 604 If it does not exist, it is determined 605 that the user authentication has failed.

  The client user identifier, which is an identifier for the user to access the client, and the user identifier, which is the identifier for the user to access the blade server, may be the same identifier. Using the client identifier used by the administrator, it is possible to control the blade server corresponding to another user identifier used by another user.

  The user authentication 604 can be extended to ensure a higher security level. For example, a personal authentication device equipped with a personal certificate such as an electronic certificate is distributed to each user, the personal authentication device is connected to the USB interface 109, and the user identifier generation program 103 on the client 100 is The request waiting program of the management server that has received the power control request, obtained a personal certificate stored in the server, uses this as a user identifier, and asks the certificate authority for the received personal certificate to check whether the user has been forged. A higher security level can be secured by taking measures such as confirming.

  In addition, identification information such as the MAC (Media Access Control) address and IP (Internet Protocol) address of the client used by the user is used for user authentication for power control, or a unique machine ID is assigned to each client. By using this machine ID for user authentication for power control, not only the user identifier but also the power control request from the client used by the user, power control cannot be performed, and the user can be impersonated A higher security level can be ensured.

  When the user authentication fails, the request waiting program 125 on the management server transmits a result code (failure) for the power control request to the client 606 and ends 607. On the other hand, when the user authentication is successful, the blade server that can uniquely identify the power control type information corresponding to the pressed button and the blade server that is the target of the power operation from the power control request message Check the allocation management table 131, user management table 132, and blade server management table 133 that the management server has to check whether the requested power control can be executed on the target blade server by extracting the management number. Determine whether to accept / reject the request for power control request 608.

  In the request acceptance / request rejection determination 608, the request waiting program 125 on the management server includes the power control target described in the blade server management table 133 in the group to which the user who made the power control request described in the user management table 132 belongs. If the group that belongs to the blade server is not included, the power control request is rejected. On the other hand, if the group that belongs to the blade server that is the target of power control described in the blade server management table 133 is included in the group that belongs to the user who made the power control request described in the user management table 132, the power control request The user's authority is acquired from the user management table 132 using the user identifier as a search key. If it is an administrator, the power control request is provisionally accepted, and if it is a general user, it can be assigned to the blade server that is the target of power control If the user identifier is acquired from the allocation management table 131 and matches the user identifier of the user who made the power control request, the power control request is provisionally accepted, otherwise the power control request is rejected.

  Further, the request waiting program 125 determines whether to accept the power control request provisionally received from the authority of the user who made the power control request, the type of power control, and the status of the blade server allocation management table 131. decide. First, when the user who makes the power control request has the authority of the manager, the power supply control request is accepted regardless of the power on, shutdown, forced power off, or reset. On the other hand, if the user who made the power control request is a general user, the power on request is shut down only when the allocation status is unallocated, the power status is off, and there is no failure. For forced power off / reset requests, the request is accepted only if the assigned status is assigned, the power status is on, and there is no failure. Otherwise, the request is rejected. To do.

  If the request waiting program 125 on the management server determines that the request is rejected as described above, the request waiting program 125 does not perform power supply control, but transmits a result code (failure) to the client and ends. On the other hand, if the request acceptance is determined, the power control program 123 is caused to execute 610 the requested power control process. Thereafter, the power control program 123 obtains the result of power control and determines whether the power control is successful or unsuccessful 611. If the power control program 123 fails, the result code (failure) for the power control request is transmitted to the client. And exit 607.

  On the other hand, if the power control is successful, the table update process 612 is performed. In this table update 612, if the power-on is successful, the assignment status in the assignment management table 131 is updated to assignment, and if the shutdown or forced power-off is successful, the assignment status in the assignment management table 131 is changed to unassigned. To do. After that, the request waiting program 125 sends the result code (success) and the management number and IP address of the blade server assigned from the blade server management table 133 to the client when newly assigned by power-on. Exit 614. The power control request program 103 on the client 100 creates a power control request and sends it to the management server 602, receives the power control result from the management server 615, and newly assigns the blade server in the table update 616 If there is, the IP address is added to the connection IP address 107 of the blade server, a message corresponding to the result of the power control is output 617 to the message display area 507 on the GUI screen 500, and the process ends 618.

  FIG. 7 shows a power control processing flow when the administrator of the management server 120 executes the power control command 122 on the CUI (Character User Interface) provided by the OS 126 in order to manually control the power of the blade server 140. It represents. First, when the power control command 122 is executed 701 on the management server 120, the power control command obtains the execution authority information of the executor from the OS 126, 702, and whether the executor has the authority of the OS 126 administrator. Make a decision 703. If the executor does not have OS 126 administrator authority, it is assumed that the user does not have authority to execute the power control command, and the power control command 122 outputs an error on the CUI provided by OS 126. Exit 705. On the other hand, if the executor has the OS 126 administrator authority in 703, the power control command 122 assumes that the user has the authority to execute the power control command, and performs power control processing on the power control program 123. If the result is unsuccessful 706, an error is output on the CUI provided by the OS 126 and finished 709, and if successful, a success message is output on the CUI provided by the OS 126 711 And finish 712.

  FIG. 8 shows a flow of processing in which the power control program 123 on the management server 120 performs remote power control on the mBMC 145 and the OS 143 on the blade server 140. First, the power supply control program 123 performs an IPMI command generation process 802 that converts a power supply control instruction from the request waiting program 125 or the power supply control command 122 into an IPMI command. The IPMI command generated here is the chassis control command described on page 358 of the IPMI specification "-IPMI-Intelligent Platform Management Interface Specification Second Generation v2.0 Document Revision 1.0". The requested contents are “Power Up” for instructing power on for a power on request, “Power Down” for instructing power off for a forced power off request, and “Reset instructing” for a reset request. “Hard Reset” and “Soft Shutdown” are specified for shutdown request. The power supply control program 123 executes an IPMI command transmission 803 that transmits the generated IPMI command to the mBMC 145 on the blade server. The mBMC 145 on the blade server 140 receives the IPMI command and starts the power control process 804. The mBMC 145 on the blade server 140 confirms whether or not the content of the received IPMI command is “Soft shutdown” in which it is necessary to execute power-off after executing the OS termination process 805.

  Here, in the case of a “Soft Shutdown” request, the mBMC 145 notifies the OS 143 of a power button pressing event using ACPI in order to instruct the OS to start the shutdown. This power button press event is notified when the user presses the power button for more than 4 seconds, as introduced on page 63 of "Advanced Configuration and Power Interface Specification Revision 3.0", which is the ACPI specification. However, here, the mBMC 145 notifies the OS 143 to execute “Soft shutdown”. OS 143 detects this event and executes the shutdown process selected by the administrator in advance in the power control setting of OS 143 as the process for the power button press event 808. When it is safe to turn off the power, mBMC Instruct 809 to turn off the power for 809 and stop 810.

  On the other hand, the mBMC that has notified the OS of the power button press event in 806 that received the “Soft shutdown” request waits for the power-off instruction from the OS, and when the power-off instruction is received from the OS, the power controller 147 turns off the power. A signal is transmitted to cut off the power supply from the power supply 148 of the blade server 140. In the conditional branch 805, if the IPMI command sent from the power control program is not “Soft shutdown”, the mBMC transmits a signal corresponding to the requested content to the power control device 147 to execute the request. Thereafter, the mBMC 145 on the blade server 140 transmits 815 the result of the executed power control to the power control program 123 on the management server 120 and ends 816. Further, the power control program 123 on the management server 120 receives 817 the result of power control from the mBMC 145 and ends the process 818.

  The BMC user authentication function has a hardware restriction that has only a simple function of storing a user ID and password combination and performing user authentication by collating them, and power control is performed only with the BMC of the blade server. When request authentication is performed, it is not possible to deal with unauthorized access to make a power control request directly to the BMC. On the other hand, according to this embodiment, a power management request from a client is collectively received and managed by a reliable management server. By performing remote power control for the blade server after the server authenticates the power control request, sufficient authentication can be performed for the power control request.

  In order to further increase the security level, the management server 120 can be authenticated by the authentication function of the BMC 145 of the blade server 140. When the management server 120 transmits a power control command to the blade server, identification information indicating the management server 120 is transmitted together with the power control command. The BMC 145 accepts only a power control command from a predetermined management server. As the identification information of the management server 120, the IP address or MAC address of the management server can be used.

  In this embodiment, it is assumed that the management server is located at the same location as the blade server. However, even if the management server is located at a location away from the blade server, security can be ensured by authenticating the management server. improves. Even when there are a plurality of management servers, flexible power management can be performed by authenticating each management server.

  Since the authentication function of the blade server's BMC is simple, the management server authenticates the user who uses the client, and the authentication of the management server The BMC of the blade server can be done easily.

  In this example, it is assumed that simple authentication of BMC is used. However, even if a management controller such as BMC can perform strong and robust authentication, this authentication should be performed. Can be used.

  In addition, due to the above BMC restrictions, server allocation management that determines whether or not allocation and power control can be performed by grouping the user who performs power control with the server to be allocated, or by assigning multiple attributes. The system can be introduced to manage the system with a high degree of freedom.

  When the management server performs remote power control, it not only authenticates the user, but also determines whether power control is possible based on the registered user information, the group to which it belongs, the power status of the blade server, and whether there is a blade server failure. Therefore, the degree of freedom of setting the server allocation policy is increased for the system administrator.

  The above-described embodiments can be changed or combined as appropriate without departing from the spirit of the present invention.

It is an example of the system block diagram concerning embodiment of this invention. It is an example of the figure showing the blade server management table which the management server in this embodiment has. It is an example of the figure showing the user management table which the management server in this embodiment has. It is an example of the figure showing the allocation management table which the management server in this embodiment has. It is an example of the figure showing the GUI screen of the power supply control request program in this embodiment. It is an example of the flowchart of the power supply control in this embodiment. It is an example of the flowchart of the power supply control in this embodiment. It is an example of the flowchart of the power supply control in this embodiment.

Explanation of symbols

100 Client 120 Management server 140 Blade server 131 Allocation management table 132 User management table 133 Blade server management table 145 mBMC
147 Power supply control device 148 Power supply 500 GUI screen of power supply control request program

Claims (15)

A power control method for a blade server in a system having a server composed of a plurality of blade servers, a client for operating the blade server, and a management server for managing the server,
The management server has information indicating a correspondence relationship between a blade server user identifier for identifying a user who uses the blade server and the blade server,
The client transmits a first power control request including a client user identifier for identifying a user who uses the client and information for specifying the blade server to the management server;
The management server that has received the first power control request has information indicating that the blade server user identifier corresponding to the client user identifier is associated with information for identifying the blade server. Judgment by
When the blade server user identifier and the information specifying the blade server are associated with each other, the management server sends a second power control request to the blade server specified based on the information specifying the blade server. Send
The blade server that has received the second power supply control request controls the power supply of the blade server based on the received second power supply control request. The blade server has a management controller;
The power supply according to claim 1, wherein the management controller receives the second power control request, and the management controller controls a power control device of the blade server and performs power control of the blade server. Control method. The management server has authority information regarding the authority of the user associated with the client user identifier,
The management server determines whether the user having the client user identifier included in the first power control request has authority based on the authority information;
2. The second power control request is transmitted to a blade server identified based on information identifying the blade server when a user having the client user identifier has authority. Or the power supply control method of 2. The plurality of blade servers of the server are classified into a plurality of groups,
The management server has information indicating a correspondence relationship between the blade server and a group to which the blade server belongs, and the group is associated with the client user identifier permitted to control power of the blade server belonging to the group. And
The management server, when the blade server identified based on the information identifying the blade server belongs to a group associated with the client user identifier included in the first power control request, The second power control request is transmitted to the identified blade server.
The power supply control method according to any one of claims 1 to 3. The first power control request is a request to turn off or restart the blade server, and the power state of the blade server acquired through the management controller of the blade server is on. 5. The power control method according to claim 1, wherein in some cases, the management server transmits the second power control request to the identified blade server. 6. The power control according to claim 1, wherein the information specifying the blade server includes at least one of a MAC (Media Access Control) address or an IP (Internet Protocol) address of the blade server. Method. The second power control request includes information for specifying the management server,
The management controller that has received the second power control request executes the power control request for the blade server having the management controller based on information for identifying the management server included in the second power control request. The power supply control method according to claim 2, wherein whether or not to perform the determination is determined.   The power management method according to claim 1, wherein the management server is a part of a plurality of blade servers constituting the server. A system comprising a server composed of a plurality of blade servers, a client for operating the blade server, and a management server for managing the server,
The client
A remote operation unit for transmitting operation information input to the input device to the blade server;
A display unit for displaying screen information received from the blade server;
A power control request issuing unit that creates a first power control request including a client user identifier for identifying a user who uses the client and information for specifying the blade server, and transmits the first power control request; Have
The management server
A storage device for storing information indicating a correspondence relationship between a blade server user identifier for identifying a user who uses the blade server and the blade server;
A request receiving unit for receiving the first power control request;
Determination that determines that the blade server user identifier corresponding to the client user identifier included in the first power control request is associated with the information specifying the blade server based on the information indicating the correspondence relationship A processing unit;
Power control for transmitting a second power control request to the blade server identified based on the information identifying the blade server when the blade server user identifier is associated with the information identifying the blade server A command issuing unit,
The blade server
A remote operation service unit that receives operation information received from the client, operates the blade server, and transmits screen information to the client;
A management controller for controlling the power control device of the blade server;
A power control device that controls the power of the blade server based on the second power control request. The management server
Having authority information relating to the user's authority associated with the user identifier;
The determination processing unit determines whether the user having the client user identifier included in the first power control request has authority based on the authority information,
The power control command issuing unit transmits the second power control request to a blade server identified based on information identifying the blade server when a user having the client user identifier has execution authority. The system according to claim 9. The plurality of blade servers of the server are classified into a plurality of groups,
The management server
Information indicating a correspondence relationship between the plurality of blade servers and a group to which the blade server belongs, and the group is associated with the client user identifier allowed to control power of the blade server belonging to the group;
The management server, when the blade server identified based on the information identifying the blade server belongs to a group associated with the client user identifier included in the first power control request, The second power control request is transmitted to the identified blade server.
The system according to claim 9 or 10, characterized in that 12. The system according to claim 9, wherein the information specifying the blade server includes at least one of a MAC (Media Access Control) address and an IP (Internet Protocol) address of the blade server. The management controller of the blade server determines whether to execute the power control request of the blade server having the management controller based on information specifying the management server included in the second power control request 13. A system according to claim 9-12.   The system according to claim 9, wherein the management server is a part of a plurality of blade servers configuring the server. A management server that manages blade servers,
A storage device for storing information indicating a correspondence relationship between a user who uses the client and the blade server;
A request receiving unit that receives a first power control request that includes a client user identifier that identifies a user who uses the client, and information that identifies the blade server;
Determination that determines that the blade server user identifier corresponding to the client user identifier included in the first power control request is associated with the information specifying the blade server based on the information indicating the correspondence relationship A processing unit;
Power control for transmitting a second power control request to the blade server identified based on the information identifying the blade server when the blade server user identifier is associated with the information identifying the blade server A command issuing unit;
A management server characterized by comprising:

Images