JP2011227841A - Computer system and identifier management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To increase the using efficiency of all WWN for rewrite by automatically executing distribution or collection as necessary concerning the management method of a WWN for rewrite applied to an FC-HBA.SOLUTION: An exclusive WWN management server manages the state of the distribution of a WWN for a rewrite applied to an FC-HBA in a batch, and when WWN distribution to the FC-HBA becomes necessary, a management module which manages the FC-HBA requests the WWN distribution to the WWN management server, and receives the WWN from the WWN management server, and applies it to the FC-HBA. On the other hand, when the WWN applied to the FC-HBA becomes unnecessary, the management module requests WWN collection to the WWN management server, and returns the WWN to the WWN management server. Exclusive data are used for the communication of the request between the management module and the WWN management server, and between the management module and the BMC.

Description

  The present invention relates to a computer system and an identifier management method for managing an identifier (WWN for rewriting) assigned to an FC-HBA mounted on a server chassis constituting the computer system.

  One of OS boot methods in a computer system is a SAN (Storage Area Network) boot in which a computer system and an external storage device are connected to boot from the external storage device.

  To implement SAN boot, the logical unit of the storage device in which the OS is installed using the WWN (World Wide Name), which is a unique ID assigned to the FC (Fibre Channel) port mounted on the computer There is a method of associating the WWN and permitting access from the FC port having the WWN.

  Here, by rewriting the WWN information assigned to the FC port of the computer, it becomes possible to access another logical unit of the storage apparatus. This access destination control is used when, for example, a failure occurs in a certain computer and the environment before the failure is constructed in another computer. Non-Patent Document 1 discloses that the access destination to the logical unit of the storage apparatus can be controlled by rewriting the WWN information assigned to the FC port.

Integrated Service Platform BladeSymphony BS2000 User's Guide Chapter 6 System Web Console Server Chassis Management Additional WWN List Screen (BS2000UG-08, Japanese 8th Edition / December 2009, pp.429-430)

  In order to use the SAN, it is necessary to uniquely assign an identifier WWN to the FC-HBA (Host Bus Adapter) used for communication between the storage apparatus and the server.

  Currently, WWN is configured to distribute a certain amount in advance to product vendors. In addition, the WWN distributed to the vendor is a system in which the vendor distributes a predetermined amount to the product purchaser in advance.

  The WWN is a 48-bit numerical value and is finite. As the use of SAN expands, there is concern that WWN will be consumed in large quantities in the future. For example, when rewriting WWN information, it is necessary to distribute in advance two WWNs, a WWN before rewriting and a WWN after rewriting, to one FC-HBA before and after rewriting the WWN information. Since two WWNs are not used simultaneously, for example, if rewriting does not occur, only the WWN before rewriting is used, and the WWN after rewriting is not used. That is, there is a problem that the WWN is not used effectively and a large amount of unused WWN is consumed. Moreover, since WWN is limited, there is a concern that WWN will be exhausted due to mass consumption of WWN.

  Therefore, an object of the present invention is to provide a management method for improving the utilization efficiency of the WWN for rewriting in order to solve the above-described problems.

  To achieve the above object, a computer system and an identifier management method according to the present invention include a plurality of server modules each having a management controller, a first adapter, and a second adapter, and the first system. A storage device connected to the server module via an adapter, a management module connected to the server module via a second adapter, and a first identifier uniquely assigned to the first adapter; And a WWN management unit that manages a second identifier that is rewritably assigned to the first adapter.

  The management controller includes a first request communication information update unit that updates request communication information transmitted to and received from the management module, and a first storage unit that stores the received request communication information. The WWN management unit includes: a second request communication information update unit that updates request communication information transmitted to and received from the management module; a second storage unit that stores the received request communication information; WWN management information for managing the distribution status of the second identifier, and the management module includes a third adapter connected to the second adapter, an identifier used in the first adapter, and the Identifier setting information for managing the correspondence with the first adapter, a request communication information creation unit for creating request communication information to be transmitted and received between the management controller or the WWN management unit and the management module; And a third storage unit for storing request communication information serial reception.

  The requested communication information includes, as a request type, distribution of the second identifier from the WWN management unit to the management module, collection of the second identifier from the management module to the WWN management unit, One of the assignment of the second identifier from the management module to the management controller and the return of the second identifier from the management controller to the management module are included.

  Then, when new request communication information is stored in the third storage unit, the management module confirms the request type of the request communication information, and controls the second identifier according to the request type.

  In other words, a computer system comprising a computer mounted with an FC-HBA and a server chassis equipped with a management module for managing the computer and a server for managing the WWN connected to the management module. When a WWN for rewriting is assigned, a server that manages the WWN for the assigned WWN collectively manages the distribution status, and automatically distributes the WWN in response to a request from the management module. When the assigned WWN is no longer needed, the WWN is automatically collected in response to a request from the management module. Requests between modules such as distribution and collection are made using requested communication information, which is dedicated communication data.

  According to the present invention, the second identifier is distributed from the WWN management unit to the management module, the second identifier is collected from the management module to the WWN management unit, and the second identifier is given from the management module to the management controller. Alternatively, transmission / reception of request communication information having one of the request types of the return of the second identifier from the management controller to the management module is performed between the management controller and the management module and between the management module and the WWN management unit. Since the management module manages the status of the second identifier (rewrite WWN) in the system using the requested communication information, it automatically distributes or collects the second identifier as necessary. Thus, it is not necessary to distribute the second identifier (rewrite WWN) to all FC-HBAs as in the past. That is, according to the present invention, it is possible to efficiently use a limited number of second identifiers in the computer system, and the concern of mass consumption of WWNs is eliminated.

System configuration diagram of Example 1 Details of request communication data WWN management server module configuration Details of the WWN management table Details of the data structure of the WWN management configuration file Details of the module configuration of the management module Details of data structure of WWN setting table WWN distribution request opportunity list details WWN collection request opportunity list details BMC module configuration details Processing flow executed by the request communication data update unit of the WWN management server for the request communication data stored in the WWN request storage unit Processing flow of operations performed by the request communication data update unit of the WWN management server in response to a WWN distribution request Processing flow of operations performed by the request communication data update unit of the WWN management server in response to a WWN collection request Processing flow executed by the BMC request communication data update unit for the request communication data stored in the WWN request storage unit Processing flow of operations performed by the BMC request communication data update unit in response to a WWN return request Processing flow of operations performed by the BMC request communication data update unit in response to a WWN assignment request Processing flow executed by the request communication data creation unit of the management module for the request communication data stored in the WWN request storage unit Process flow of operations for WWN collection performed by the request communication data creation unit of the management module Process flow of operations for WWN collection performed by the request communication data creation unit of the management module Processing flow of operations for WWN distribution performed by the request communication data creation unit of the management module Processing flow of operations for WWN distribution performed by the request communication data creation unit of the management module System configuration diagram of Example 2 Details of the module configuration of the WWN management mechanism in Example 2 System configuration diagram of Example 3 Details of the module configuration of the management module in the third embodiment Details of the data structure of the WWN setting table in the third embodiment

<Example 1>
FIG. 1 shows a system configuration diagram of a computer system to which the present invention is applied. The system device according to the first embodiment includes a WWN management server 101, a server chassis 102, and a storage device 103 that is an example of a storage device.

  A network interface card (NIC) 108 built in the WWN management server 101 is connected to an external module (the management module 106 in the example of FIG. 1) via a network switch (NW-SW) 104. By connecting the NIC 108 to the network, data communication can be performed with another module (for example, the management module 106 having the NIC 107) that incorporates the NIC. Further, the WWN management server 101 has a function of responding to requests for WWN distribution and WWN collection received from connected external modules by managing the WWN for rewriting distributed to itself and its state. In addition, the WWN management server 101 includes a memory for storing programs and data and a CPU for executing the programs.

  The server chassis 102 has a management module 106 mounted thereon. The NIC 107 built in the management module 106 is connected to the WWN management server 101 via the NW-SW 104. The management module 106 is connected to other modules installed in the server chassis 102, and has a function of monitoring and operating each module. In addition, the management module 106 includes a memory for storing programs and data, and a CPU for executing the programs. Further, the server chassis 102 can be equipped with a plurality of server modules, and forms a blade server. In the example of FIG. 1, the server chassis 102 has N server modules including server modules 110 and 120 mounted thereon.

  The server modules 110 and 120 have basically the same configuration and include BMC (Baseboard Management Controller) 111 and 121 which are examples of so-called management controllers. The server modules 110 and 120 incorporate FC-HBAs 113 and 123, a memory for storing programs and data, a CPU for executing the programs, and the like.

  FC-HBAs 113 and 123 are first adapters and may be compatible with hot plugs.

  The NICs 112 and 122 that are the second adapters built in the server modules 110 and 120 are connected to the NIC 107 that is the third adapter built in the management module 106. The NICs 112 and 122 are connected to the BMCs 111 and 121 in the server modules 110 and 120.

  The FC-HBAs 113 and 123 are connected to the storage apparatus 103 via a fiber channel switch (FC-SW) 105, and for example, an OS held in the storage apparatus 103 can be used. FC-HBAs 113 and 123 are assigned WWNs 115 and 125 as identification information. The WWNs 115 and 125 can acquire and rewrite values from the BMC 111. In addition, the FC-HBAs 113 and 123 hold orgWWNs (original WWNs) 114 and 124 as first identifiers indicating original WWNs assigned to the FC-HBAs 113 and 123, separately from the WWNs 115 and 125. The orgWWNs 114 and 124 can acquire values from the BMC 111. Hereinafter, a rewriting WWN having a value different from that of the orgWWN is referred to as an addWWN (additional WWN) as a second identifier. If addWWN is not assigned, the values of orgWWNs 114 and 124 are written in WWNs 115 and 125, respectively.

  FIG. 2 shows details of requested communication data 201, which is an example of requested communication information. The request communication data 201 is transmitted / received between the management module 106 and the WWN management server 101 or between the management module 106 and the BMC 111.

  The request communication data 201 includes a request type 202, a request processing result 203, an FC-HBA type 204, an FC-HBA number 205, a WWN type 206, a WWN 207, a request source 208, and a request destination 209. Further, the request communication data 201 is created by a module that makes a request, and the data content is updated, new data is stored, and the like as necessary.

  The request type 202 stores, for example, one of the following (a) to (d) as the type of operation requested. (a) A WWN distribution request to the WWN management server 101. (b) A WWN collection request to the WWN management server 101. (c) Request to assign WWN to FC-HBA to BMC111. (d) Request to return WWN to BMC111 to FC-HBA. The request processing result 203 stores the processing result of the request (for example, any of unprocessed, successful, or failed). The FC-HBA type 204 stores a physical FC-HBA indicating the type of the target FC-HBA or a logical FC-HBA. The FC-HBA number 205 stores the number of the target FC-HBA (for example, an installed slot number). The WWN type 206 stores orgWWN or addWWN indicating the type of WWN assigned to the target FC-HBA. The WWN 207 stores a WWN value corresponding to the request content. The request source 208 stores the connection destination (IP address in the example of FIG. 2) of the module that created and sent the request communication data 201. The request destination 209 stores the connection destination (IP address in the example of FIG. 2) of the module that is the transmission destination of the request communication data 201.

  FIG. 3 shows a module configuration of the WWN management server 101. The WWN management server 101 includes a NIC 108, a WWN management table 301 that is an example of WWN management information, a WWN management setting file 302, a WWN request storage unit 303 that is an example of a second storage unit, and a second request communication information update unit A request communication data updating unit 304, which is an example.

  The WWN management table 301 stores WWNs distributed and managed to the WWN management server 101 and the status of the WWNs, and is used for the purpose of managing the WWNs. The WWN management setting file 302 has a policy of selecting WWNs distributed by the WWN management server 101. The WWN request storage unit 303 first stores the request communication data 201 received by the NIC 108 built in the WWN management server 101 in the form of a queue in the WWN request storage unit 303, and sequentially processes requests. Used in. The storage state of the request communication data 201 in the WWN request storage unit 303 is monitored by the WWN management server 101. The request communication data update unit 304 of the WWN management server has a function of processing a request regarding the WWN to the WWN management server 101, such as a function of updating the content of the request communication data 201 stored in the WWN request storage unit 303.

  FIG. 4 shows details of the WWN management table 301. The WWN management table 301 includes a WWN 401 column, a distribution destination 402 column, an FC-HBA type 403 column, and an FC-HBA number 404 column.

  The WWN 401 stores all the addWWN distributed to the WWN management server 101 and the orgWWN of the FC-HBA under management. The operation of adding an element to the WWN management table 301 and storing the value in the WWN 401 is performed by the administrator of the WWN management server 101. The elements of the table are arranged in ascending or descending order with respect to the value of WWN 401 (stored in ascending order in the example of FIG. 4).

  The distribution destination 402 indicates the connection destination (IP address in the example of FIG. 4) of the module that requested the WWN distribution, and stores the request source 208 of the processed request communication data 201. If undistributed, the fact is stored. The FC-HBA type 403 indicates whether the WWN 401 is assigned to a physical FC-HBA or a logical FC-HBA, the FC-HBA type 204 of the processed request communication data 201. Stored. The FC-HBA number 404 indicates a number for identifying the FC-HBA in the module of the distribution destination 402 (in the example of FIG. 4, the mounting slot number), and stores the FC-HBA number 205 of the processed request communication data 201. If undistributed, this is stored.

  FIG. 5 shows details of the data structure of the WWN management setting file 302. The WWN management setting file 302 includes a distribution WWN selection policy 501.

  The distribution WWN selection policy 501 describes a criterion for selecting a WWN to be distributed by the WWN management server 101. This selection criterion is edited by the administrator of the WWN management server 101, and for example, one of the following (a) to (c) is described. (a) Use WWNs in ascending order. (b) Use WWNs in descending order. (c) Describe the WWN value in ascending or descending order, and use the described WWN as the starting point in ascending or descending order.

  In the distribution WWN selection policy 501, it is not essential to describe the criteria such as (a) to (c). When the content is empty, the WWN management server 101 distributes the WWN distributed according to the criteria of (a). May be selected.

  FIG. 6 shows the details of the module configuration of the management module 106. The management module 106 includes a NIC 112, a WWN setting table 601 that is an example of identifier setting information, a WWN distribution request opportunity list 602, a WWN collection request opportunity list 603, a request communication data creation unit 604 that is an example of a request communication information creation unit, And a WWN request storage unit 605 which is an example of a third storage unit.

  The WWN setting table 601 stores WWN settings to be assigned to each FC-HBA. The WWN distribution request trigger list 602 is a list in which triggers for executing a request for assigning a WWN to an FC-HBA are described. The WWN collection request opportunity list 603 is a list in which an opportunity to execute a request for collecting the WWN assigned to the FC-HBA is described. The requested communication data creation unit 604 provides a WWN for the management module 106, such as a function for creating the requested communication data 201 when an event described in the WWN distribution request opportunity list 602 or the WWN collection request opportunity list 603 occurs. It has a function to process requests. The WWN request storage unit 605 first stores the request communication data 201 received by the NIC 112 built in the management module 106 in the form of a queue in the WWN request storage unit 605, and is used for the purpose of sequentially processing requests. To do.

  FIG. 7 shows details of the data structure of the WWN setting table 601. The WWN setting table 601 includes an FC-HBA number 701 column, a WWN type 702 column, and a WWN703 column. The WWN type 702 and WWN 703 are updated when the server module 110 including the FC-HBA 113 is inserted or removed, or when the administrator of the management module 106 refers to or changes the WWN setting.

  The FC-HBA number 701 stores the number of the FC-HBA installed in the server module 110 managed by the management module 106 (in the example of FIG. 7, the installation slot number).

  The WWN type 702 stores orgWWN or addWWN indicating the type of WWN to be assigned. If the FC-HBA is not installed, this is stored in the WWN type 702. When addWWN is stored, it indicates that the WWN distributed from the WWN management server 101 is assigned. If orgWWN is stored, it indicates that orgWWN is being used.

  The WWN 703 stores the value of the assigned WWN. If the FC-HBA is not installed, this is stored in WWN703.

  FIG. 8 shows details of the WWN distribution request opportunity list 602. The WWN distribution request trigger list 602 is a list in which triggers for executing a request when assigning a WWN to the FC-HBA 111 are described. In the example of FIG. 8, six items 801 to 806 are held, but an administrator of the management module 106 including the WWN distribution request opportunity list 602 can add items as necessary.

  FIG. 9 shows details of the WWN return request opportunity list 603. The WWN return request trigger list 603 is a list in which triggers for executing a request for collecting the WWN assigned to the FC-HBA 111 are described. In the example of FIG. 9, six items 901 to 906 are held, but an administrator of the management module 106 including the WWN return request opportunity list 603 can add items as necessary.

  FIG. 10 shows details of the module configuration of the BMC 111. The BMC 111 includes a WWN request storage unit 1001 that is an example of a first storage unit, and a request communication data update unit 1002 that is an example of a first request communication information update unit. The WWN request storage unit 1001 first stores the request communication data 201 received by the NIC 112 connected to the BMC 111 in the form of a queue in the WWN request storage unit 1001, and uses it for the purpose of sequentially processing requests. . The request communication data update unit 1002 of the BMC has a function of processing a request regarding the WWN to the BMC 111, such as a function of updating the content of the request communication data 201 stored in the WWN request storage unit 1001.

  FIG. 11 shows a processing flow executed by the request communication data update unit 304 of the WWN management server 101 for the request communication data 201 stored in the WWN request storage unit 303, and monitors the WWN request storage unit 303. The process starts from step S1101.

  The request communication data update unit 304 of the WWN management server 101 confirms the presence or absence of the request communication data 201 in the WWN request storage unit 303 (S1102). In the first embodiment, the management module 106 transmits request communication data 201 to the WWN management server 101 as necessary.

  When the request communication data 201 does not exist in the WWN request storage unit 303 (S1103), the WWN request communication data update unit 304 of the WWN management server 101 continues to monitor the WWN request storage unit 303. On the other hand, when the request communication data 201 exists in the WWN request storage unit 303 (S1103), the WWN request communication data update unit 304 of the WWN management server 101 extracts the first request communication data 201 from the WWN request storage unit 303, and requests The type 202 is confirmed (S1104).

  When the request type 202 is WWN distribution (S1105), the WWN request communication data update unit 304 of the WWN management server 101 performs WWN distribution request processing S1201 shown in FIG. 12 (S1106). When the request type 202 is WWN collection (S1105), the WWN request communication data update unit 304 of the WWN management server 101 performs WWN collection request processing S1301 shown in FIG. 13 (S1107). If the request type 202 is neither the WWN distribution nor the WWN collection described above (S1105), an error process is performed because the process is not performed by the WWN request communication data update unit 304 of the WWN management server 101 (S1108).

  Then, any one of S1106, S1107, and S1108 corresponding to the content of the request type 202 is performed, and the process returns to the monitoring of the WWN request storage unit 303.

  FIG. 12 shows a processing flow of the operation of the WWN request communication data update unit 304 of the WWN management server 101 in response to the WWN distribution request. This is a detailed processing flow of items executed in S1106, and processing for distributing a WWN from the WWN management server 101 is started from step S1201.

  The requested communication data update unit 304 of the WWN management server 101 searches the WWN management table 301 for a WWN in which the distribution destination 402 has not been distributed (S1202, S1203).

  The search order refers to the distribution WWN selection policy 501 of the WWN management setting file 302, and is, for example, one of the following (a) to (c). (a) When using WWNs in ascending order, search in ascending order of the value of WWN401. (b) When using WWNs in descending order, search in descending order of the value of WWN401. (c) When a specific WWN value is described in combination with an ascending order or descending order and used from the WWN in ascending order or descending order, search is performed from the described WWN to the order in which the value of WWN 401 is small or large. If the number does not exist, the search is performed from the WWN closest to the WWN described together in ascending or descending order.

  When the WWN corresponding to the search condition of S1202 is found, the request communication data update unit 304 of the WWN management server 101 sets the distribution destination 402 of the WWN 401 of the WWN management table 301 to the request source 208 of the request communication data 201 (FIG. 2). In the example, it is updated to IP address), FC-HBA type 403 is updated to FC-HBA type 204 of request communication data 201, and FC-HBA number 404 is updated to FC-HBA number 205 of request communication data 201 (S1204 ). In the first embodiment, the request source 208 is the management module 106.

  Next, the request communication data update unit 304 of the WWN management server 101 successfully updates the request processing result 203 of the request communication data 201 retrieved in S1104, and updates the WWN 207 to the WWN found in S1202 and S1203 (S1205). .

  Next, the request communication data 201 updated in S1205 is sent to the management module 106 (S1207), and the process is terminated (S1208).

  On the other hand, when the WWN corresponding to the search condition of S1202 cannot be found, the request communication data update unit 304 of the WWN management server 101 updates the request processing result 203 of the request communication data 201 to failure (S1206).

  Next, the request communication data 201 updated in S1206 is sent to the management module 106 (S1207), and the process is terminated (S1208).

  FIG. 13 shows a processing flow of the operation of the requested communication data update unit 304 of the WWN management server 101 in response to the WWN collection request. This is a detailed process flow of the items executed in S1107, and the process for the WWN management server 101 to collect the returned WWN starts from step S1301.

  The requested communication data update unit 304 of the WWN management server 101 searches for a WWN in which the WWN 207 of the requested communication data 201 extracted in S1104 matches the WWN 401 of the WWN management table 301 (S1302, S1303).

  When a WWN corresponding to the search condition of S1302 is found, the requested communication data update unit 304 of the WWN management server 101 sets the distribution destination 402, FC-HBA type 403, and FC-HBA number 404 of the WWN 401 to an undistributed state. (S1304).

  Next, the request communication data update unit 304 of the WWN management server 101 successfully updates the request processing result 203 of the request communication data 201 extracted in S1104 (S1305).

  Next, the request communication data update unit 304 of the WWN management server sends the request communication data 201 updated in S1305 to the management module 106 (S1307), and ends the processing (S1308).

  On the other hand, when the WWN corresponding to the search condition of S1302 cannot be found, the request communication data update unit 304 of the WWN management server 101 updates the request processing result 203 of the request communication data 201 to failure (S1306).

  Next, the request communication data update unit 304 of the WWN management server 101 sends the request communication data 201 updated in S1306 to the management module 106 (S1307), and ends the processing (S1308).

  FIG. 14 shows a processing flow executed by the request communication data update unit 1002 of the BMC 111 for the request communication data 201 stored in the WWN request storage unit 1001, and a step of monitoring the WWN request storage unit 1001 is shown. Start from S1401.

  The request communication data update unit 1002 of the BMC 111 confirms the presence or absence of the request communication data 201 in the WWN request storage unit 1001 (S1402). In the first embodiment, the management module 106 transmits request communication data 201 to the BMC 111 as necessary.

  When the request communication data 201 does not exist in the WWN request storage unit 1001 (S1403), the request communication data update unit 1002 of the BMC 111 continues to monitor the WWN request storage unit 1001. On the other hand, when the request communication data 201 exists in the WWN request storage unit 1001 (S1403), the request communication data update unit 1002 of the BMC 111 extracts the first request communication data 201 from the WWN request storage unit 1001 and confirms the request type 202. (S1404).

  When the request type 202 is WWN assignment (S1405), the request communication data update unit 1002 of the BMC 111 performs the WWN assignment request processing S1601 shown in FIG. 16 (S1406). When the request type 202 is WWN return (S1405), the request communication data update unit 1002 of the BMC 111 performs the WWN return request processing S1501 shown in FIG. 15 (S1407). If the request type 202 is neither the above-mentioned WWN assignment nor WWN return (S1405), error processing is performed (S1408) because it is not processing performed by the request communication data update unit 1002 of the BMC 111.

  Then, any one of S1406, S1407, and S1408 corresponding to the content of the request type 202 is performed, and the process returns to the monitoring of the WWN request storage unit 1001.

  FIG. 15 shows a processing flow of the operation of the request communication data update unit 1002 of the BMC 111 in response to the WWN return request. This is a detailed processing flow of the items executed in S1407, and processing for returning the addWWN assigned to the FC-HBA 113 is started from step S1501.

  The request communication data update unit 1002 of the BMC 111 refers to the FC-HBA type 204 and the FC-HBA number 205 of the request communication data 201 received in S1501, and identifies the FC-HBA 113 that is the target of the WWN return request (S1502 , S1503).

  Next, when the FC-HBA 113 can be identified, the mounting state of the FC-HBA 113 is confirmed (S1504, S1505).

  When the installation of the FC-HBA 113 is confirmed in S1504 and S1505, the WWN 115 of the FC-HBA 113 is rewritten to the orgWWN 114 (S1506).

  Next, when the rewriting of S1506 is successful (S1507), the FC-HBA 113 is activated (S1508).

  Next, after S1508, the BMC request communication data update unit 1002 successfully updates the request processing result 203 of the request communication data 201 received in S1501 (S1509).

  Then, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1509 to the management module 106 (S1512) and ends the process (S1513).

  When the FC-HBA 113 cannot be identified in S1502 and S1503, the request communication data update unit 1002 of the BMC 111 updates the request processing result 203 of the request communication data 201 received in S1501 to failure (S1511).

  Next, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1511 to the management module 106 (S1512) and ends the process (S1513).

  In addition, when the installation of the FC-HBA 113 cannot be confirmed in S1504 and S1505 (that is, when it is confirmed that the FC-HBA 113 is not installed), the request communication data update unit 1002 of the BMC 111 receives the request processing result 203 of the request communication data 201 received in S1501 Is successfully updated (S1509).

  Next, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1509 to the management module 106 (S1512) and ends the process (S1513).

  If the rewriting of the WWN 115 of the FC-HBA 113 to the orgWWN 114 fails in S1506 and S1507, the activation of the FC-HBA 113 is stopped (S1510).

  Next, the request communication data update unit 1002 of the BMC 111 updates the request processing result 203 of the request communication data 201 received in S1501 to failure (S1511).

  Next, the request communication data update unit 1002 of BMC sends the request communication data 201 updated in S1511 to the management module 106 (S1512) and ends the process (S1513).

  FIG. 16 shows a processing flow of the operation of the request communication data update unit 1002 of the BMC 111 in response to the WWN grant request. This is a detailed process flow of the items executed in S1406, and the process for assigning the distributed addWWN to the FC-HBA 113 starts from step S1601.

  The request communication data update unit 1002 of the BMC 111 refers to the FC-HBA type 204 and the FC-HBA number 205 of the request communication data 201 received in S1601, and identifies the FC-HBA 113 that is the target of the WWN assignment request (S1602 , S1603).

  Next, when the FC-HBA 113 is specified, the request communication data update unit 1002 of the BMC 111 rewrites the WWN 115 of the FC-HBA 113 (S1604). The value after rewriting is the WWN 207 of the request communication data 201 received in S1601.

  Next, when the rewriting of S1604 is successful (S1605), the FC-HBA 113 is activated (S1606).

  Next, the request communication data update unit 1002 of the BMC 111 successfully updates the request processing result 203 of the request communication data 201 received in S1601 (S1607).

  Next, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1607 to the management module 106 (S1610) and ends the process (S1611).

  If the FC-HBA 113 cannot be identified in S1602 and S1603, the request communication data update unit 1002 of the BMC 111 updates the request processing result 203 of the request communication data 201 received in S1601 to failure (S1609).

  Next, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1609 to the management module 106 (S1610) and ends the process (S1611).

  If rewriting fails in S1605, the activation of the FC-HBA 113 is stopped (S1608).

  Next, the request communication data update unit 1002 of the BMC 111 updates the request processing result 203 of the request communication data 201 received in S1601 to failure (S1609).

  Next, the request communication data update unit 1002 of the BMC 111 sends the request communication data 201 updated in S1609 to the management module 106 (S1610) and ends the process (S1611).

  FIG. 17 shows a processing flow executed by the request communication data creation unit 604 of the management module 106 for the request communication data 201 stored in the WWN request storage unit 605, and processing for monitoring the WWN request storage unit 605 Starts from step S1701.

  The request communication data creation unit 604 of the management module 106 checks whether or not the request communication data 201 exists in the WWN request storage unit 605 (S1702).

  When the request communication data 201 does not exist in the WWN request storage unit 605 (S1703), the request communication data creation unit 604 of the management module 106 continues to monitor the WWN request storage unit 605. On the other hand, when the request communication data 201 exists in the WWN request storage unit 605 (S1703), the request communication data creation unit 604 of the management module 106 extracts the first request communication data 201 from the WWN request storage unit 605 and determines the request type. 202 is confirmed (S1704).

  When the request type 202 is WWN distribution (S1705), WWN distribution request processing is performed from S2005 shown in FIG. 20 (S1706). When the request type 202 is WWN collection (S1705), processing of the WWN collection request is performed from S1904 shown in FIG. 19 (S1707). When the request type 202 is WWN assignment (S1705), the processing of the WWN assignment request is performed from S2104 shown in FIG. 21 (S1708). When the request type 202 is WWN return (S1705), the processing of the WWN return request is performed from S1805 shown in FIG. 18 (S1707).

  Then, any one of S1706, S1707, S1708, and S1709 corresponding to the content of the request type 202 is performed, and the process returns to the monitoring of the WWN request storage unit 605.

  18 and 19 show a processing flow for WWN collection executed by the request communication data creation unit 604 of the management module 106 when any of the behaviors managed in the WWN collection request opportunity list 603 occurs. The operation starts from step S1801.

  The request communication data creation unit 604 of the management module 106 creates request communication data 201 for requesting the return of the WWN 115 for the FC-HBA 113 that is the WWN collection target (S1802). In the request communication data 201 created in S1802, specifically, the WWN return is stored in the request type 202, the unprocessed is stored in the request processing result 203, and the FC-HBA 113 type is stored in the FC-HBA type 204. The installed slot number is stored in the FC-HBA number 205, the WWN type 702 of the WWN setting table 601 is stored in the WWN type 206, the WWN 703 is stored in the WWN 207, and the request source 208 itself (management module 106) The connection destination of the BMC 111 on which the FC-HBA 113 is mounted is stored in the request destination 209.

  Next, the request communication data creation unit 604 of the management module 106 sends the created request communication data 201 to the BMC 111 (S1803).

  Next, the request communication data creation unit 604 of the management module 106 receives the response (S1512) of the request communication data 201 implemented by the BMC 111 as described above with reference to FIG. 15, and receives the WWN request in S1709 of FIG. The retrieval of the requested communication data 201 from the storage unit 605 is completed (S1804).

  Next, the request communication data creation unit 604 of the management module 106 confirms the request processing result 203 of the request communication data 201 received in S1804 (S1805, S1806).

  If the request processing result 203 of S1805 and S1806 is not successful, error processing (S1907) is performed and the processing is terminated (S1908).

  On the other hand, if the request processing result 203 of S1805 and S1806 is successful, the WWN type 702 of the FC-HBA number 701 corresponding to the FC-HBA 113 that is the WWN collection target is confirmed in the WWN setting table 601 (S1807, S1808).

  If the WWN type 702 in S1807 and S1808 is orgWWN, the process ends (S1908).

  On the other hand, when the WWN type 702 of S1807 and S1808 is addWWN, the request communication data creation unit 604 of the management module 106 creates request communication data 201 for requesting the collection of the WWN 703 of the corresponding FC-HBA number 701 in S1807. (S1901). In the request communication data 201 created in S1901, specifically, WWN collection is stored in the request type 202, unprocessed is stored in the request processing result 203, and the FC-HBA 113 type is stored in the FC-HBA type 204. The installed slot number is stored in FC-HBA number 205, addWWN is stored in WWN type 206, WWN703 is stored in WWN207, the connection destination of itself (management module 106) is stored in request source 208, The connection destination of the WWN management server 101 is stored in the request destination 209.

  Next, the request communication data creation unit 604 of the management module 106 sends the request communication data 201 created in S1901 to the WWN management server 101 (S1902).

  Thereafter, the request communication data creation unit 604 of the management module 106 receives the response (S1307) of the request communication data 201 executed by the WWN management server 101 as described above with reference to FIG. 13, and in S1707 of FIG. Then, the retrieval from the WWN request storage unit 605 is completed (S1903).

  Next, the request processing result 203 of the request communication data 201 received in S1903 is confirmed (S1904, S1905).

  If the request processing result 203 of S1904 and S1905 is successful, the WWN type 702 of the corresponding FC-HBA number 701 in S1807 is updated to orgWWN and WWN703 is updated to the value of orgWWN114 (S1906), and the process is terminated (S1908). . That is, the processing in S1906 realizes synchronization between the identifier in the WWN setting table 601 of the management module 106 and the identifier in the WWN 115 of the FC-HBA 113.

  On the other hand, if the request processing result 203 of S1904 and S1905 is not successful, error processing (S1907) is performed and the processing is terminated (S1908).

  FIGS. 20 and 21 show processing flows for WWN distribution executed by the request communication data creation unit 604 of the management module 106 when any of the trigger behaviors managed in the WWN distribution request trigger list 602 occurs. The operation starts from step S2001.

  The request communication data creation unit 604 of the management module 106 creates request communication data 201 for requesting distribution of the WWN for the FC-HBA 113 to which the WWN is to be assigned (S2002). In the request communication data 201 created in S2002, specifically, WWN distribution is stored in the request type 202, unprocessed is stored in the request processing result 203, and the FC-HBA 113 type is stored in the FC-HBA type 204. , The installed slot number is stored in FC-HBA number 205, addWWN is stored in WWN type 206, the connection destination of itself (management module 106) is stored in request source 208, and the WWN management server is stored in request destination 209 Stores 101 connection destinations.

  Next, the management module 106 sends the created request communication data 201 to the WWN management server 101 (S2003).

  Next, the management module 106 receives the response (S1207) of the request communication data 201 executed by the WWN management server 101 as described above with reference to FIG. 12, and receives the response from the WWN request storage unit 605 in S1706 of FIG. The retrieval of the requested communication data 201 is completed (S2004).

  Next, the request communication data creation unit 604 of the management module 106 confirms the request processing result 203 of the request communication data 201 received in S2004 (S2005, S2006).

  If the request processing result 203 of S2005 and S2006 is not successful, error processing (S2106) is performed and the processing is terminated (S2107).

  On the other hand, if the request processing result 203 of S2005 and S2006 is successful, the WWN type 702 of the FC-HBA number 701 corresponding to the FC-HBA 113 subject to WWN assignment is updated to addWWN, and the requested communication data received in S2004 for WWN703 The WWN 207 is updated to 201 (S2007).

  Next, the request communication data creation unit 604 of the management module 106 creates request communication data 201 that requests the distribution of the distributed WWN to the FC-HBA 113 (S2101). In the request communication data 201 created in S2101, specifically, WWN assignment is stored in the request type 202, unprocessed is stored in the request processing result 203, and the FC-HBA 113 type is stored in the FC-HBA type 204. Store the slot number in FC-HBA905, addWWN in WWN type, store WWN703 updated in S2007 in WWN207, store the connection destination of itself (management module 106) in request source 208, The connection destination of the BMC 111 on which the FC-HBA 113 is mounted is stored in the request destination 209.

  Next, the request communication data creation unit 604 of the management module 106 sends the request communication data 201 created in S2102 to the BMC 111 (S2102).

  Thereafter, the request communication data creation unit 604 of the management module 106 receives the response (S1610) of the request communication data 201 implemented by the BMC 111 as described above with reference to FIG. 16, and in step S1708 of FIG. The retrieval from the request storage unit 605 is completed (S2103).

  Next, the request processing result 203 of the request communication data 201 received in S2103 is confirmed (S2104, S2105).

  If the request processing result 203 of S2104 and S2105 is successful, the process ends (S2107).

  On the other hand, if the request processing result 203 of S2104 and S2105 is not successful, error processing (S2106) is performed and the processing is terminated (S2107).

  As described above, in the system according to the first embodiment, the WWN management server 101 collectively manages the rewrite WWN (addWWN) used in the computer system. Further, the management module 106 creates request communication data for controlling the collection, distribution, return, and assignment of the rewrite WWN, and based on the request type stored in the request communication data, the management module-between the WWN management servers and the management module- Since the rewrite WWN (addWWN) is transferred between the BMCs of the server module, a computer system can be constructed with only a limited number of rewrite WWNs (addWWN) than the FC-HBA installed in the server module. In other words, unused rewrite WWNs (addWWN) can be automatically collected in an undistributed state, so it is not necessary to prepare rewrite WWNs (addWWN) as many as the number of FC-HBAs. As a result, a computer system that efficiently uses a finite number of rewrite WWNs (addWWN) can be realized.

<Example 2>
FIG. 22 shows an overall view of an apparatus according to the second embodiment to which the present invention is applied. The difference from the first embodiment shown in FIG. 1 is that the management module 2206 holds the function of the WWN management server 101 as the WWN management mechanism 2201 itself. Further, the request destination 209 of the requested communication data 201 sent out by the management module 2206 is the WWN management server 101 in the second embodiment, but the WWN management mechanism 2201 in the second embodiment. Other configurations are the same as those in the first embodiment.

  FIG. 23 shows a module configuration of the WWN management mechanism 2201 held by the management module 2206.

  Similar to the WWN management server 101 in the first embodiment, the WWN management mechanism 2201 has a WWN management table 301, a WWN management setting file 302, a WWN request storage unit 303, and a request communication data update unit 304 of the WWN management server. Yes. That is, the WWN management mechanism 2201 has the same function as the WWN management server.

  As described above, the WWN management mechanism 2201 may be disposed in the management module 2206 in the server chassis 2202.

<Example 3>
FIG. 24 shows a general view of an apparatus according to a third embodiment to which the present invention is applied. The difference from the first embodiment shown in FIG. 1 is that the virtual machine system is operating on the server module installed in the server chassis 2402.

  The virtual machine system is managed by the hypervisors 2430 and 2440. The virtual computer system also includes logical computers 2431, 2434, 2441, 2444, logical FC-HBAs 2432, 2435, 2442, 2445, logical WWNs 2433, 2436, 2443, 2446, and WWN switches 2437, 2447.

  In the example of FIG. 24, two virtual machines are configured per hypervisor, but a configuration with a larger number of N is possible. The WWN switches 2437 and 2447 are mechanisms for mutually converting the logical WWN and FC-HBA WWN.

  In the configuration of FIG. 24, “when a hypervisor adds a logical FC-HBA” is added to the WWN distribution request opportunity list 602 of the management module 2406, and “hypervisor is a logical FC-HBA” is added to the WWN collection request opportunity list 603. Is added ”.

  When these triggers occur, the management module 2406 sends request communication data 201 for requesting WWN grant / WWN return with the request destination 209 as a hypervisor. The hypervisor that has received the request communication data 201 performs the processing illustrated in FIG. 15 or FIG. 16 in the same manner as the BMC that has received the request communication data 201.

  FIG. 25 shows the details of the module configuration of the management module 2406 in the third embodiment shown in FIG. The management module 2406 includes a NIC 2412, a WWN setting table 2501, a WWN distribution request list 502, a WWN collection request opportunity list 603, a request communication data creation unit 604, and a WWN request storage unit 605.

  The difference between the management module 106 of the first embodiment and the management module 2406 of the third embodiment is the difference in the data structure of the WWN setting table. Specifically, the data structure of the WWN setting table 601 in FIG. 7 is different from the data structure of the WWN setting table 2501 in FIG.

  FIG. 26 shows details of the data structure of the WWN setting table 2501. The WWN setting table 2501 includes an FC-HBA type 2601 column, an FC-HBA number 2602 column, a WWN type 2603 column, and a WWN 2604 column.

  The FC-HBA type 2601 indicates the type of FC-HBA managed by the management module 2406, and stores either a physical FC-HBA or a logical FC-HBA. Note that FC-HBA number 2602 is the same use as FC-HBA number 701 shown in FIG. 7, WWN type 2303 is the same use as WWN type 702 shown in FIG. 7, and WWN2604 is the same use as WWN703 shown in FIG. ,used.

  As described above, according to the present invention, the distribution status of addWWN to be assigned to the FC-HBA is managed, and communication is performed using request communication data that is dedicated communication data, so that the WWN management server can be used as necessary. However, it is possible to automatically distribute and collect the WWN for rewriting, and it becomes unnecessary to prepare addWWN statically for all FC-HBAs. Therefore, the use efficiency of addWWN can be increased, and finite WWN exhaustion can be prevented.

  101: WWN management server 102: Server chassis 103: Storage device 104: Network switch (NW-SW) 105: Fiber channel switch (FC-SW) 106: Management module 107, 108, 112, 122: Network interface card (NIC), 110, 120: Server module, 111, 121: BMC, 113, 123: FC-HBA, 114, 124: orgWWN, 115, 125: WWN,

Claims (13)

A plurality of server modules having a management controller, a first adapter, and a second adapter;
A storage device connected to the server module via the first adapter;
A management module connected to the server module via the second adapter;
A WWN management unit that manages a second identifier that is rewritably assigned to the first adapter, different from the first identifier that is uniquely assigned to the first adapter;
The management controller has a first request communication information update unit that updates request communication information that is transmitted to and received from the management module, and a first storage unit that stores the received request communication information.
The WWN management unit includes: a second request communication information update unit that updates request communication information transmitted to and received from the management module; a second storage unit that stores the received request communication information; WWN management information for managing the distribution status of the second identifier,
The management module includes: a third adapter connected to the second adapter; identifier setting information for managing correspondence between an identifier used in the first adapter and the first adapter; and the management controller Or a request communication information creation unit that creates request communication information that is transmitted and received between the WWN management unit and the management module, and a third storage unit that stores the received request communication information.
The requested communication information includes, as a request type, distribution of the second identifier from the WWN management unit to the management module, collection of the second identifier from the management module to the WWN management unit, and the second identifier. Either one of assignment of an identifier from the management module to the management controller or return of the second identifier from the management controller to the management module;
The management module, when new request communication information is stored in the third storage unit,
Confirm the request type of the request communication information,
A computer system that controls the second identifier according to the request type. The first adapter is FC-HBA,
The second adapter is a NIC;
The computer system according to claim 1, wherein the identifier is a WWN. The WWN management unit is a WWN management server,
The computer system according to claim 1, wherein the plurality of server modules and the management module are mounted on a server chassis.   The computer system according to claim 1, wherein the WWN management unit is a WWN management mechanism included in the management module. When the management module detects a distribution request for the second identifier to the first adapter,
Creating request communication information in which the request type is distribution of the second identifier from the WWN management unit to the management module;
Sending request communication information whose request type is distribution to the WWN management unit;
When the WWN management unit receives request communication information in which the request type is distribution,
Referring to the WWN management information, search for a second identifier that can be assigned,
If there is a second identifier that can be allocated, the second identifier that can be allocated is stored in the request communication information;
Transmitting request communication information storing the second assignable identifier to the management module;
When the management module receives the request communication information storing the second assignable identifier,
Update the identifier corresponding to the first identifier of the distribution request target of the second identifier in the identifier setting information to the assignable second identifier,
Create request communication information whose request type is the assignment of the second identifier that can be assigned from the management module to the management controller,
Sending the request communication information that the request type is grant to the management controller;
When the management controller receives request communication information in which the request type is grant,
Referring to the request communication information in which the request type is grant, identify the first adapter that is the distribution request target of the second identifier,
The computer system according to claim 1, wherein the assignable second identifier is stored in the distribution request target first adapter. When the management module detects a collection request for the second identifier assigned to the first adapter,
Creating request communication information in which the request type is a return of the second identifier from the management controller to the management module;
Sending request communication information whose request type is return to the management controller,
When the management controller receives request communication information in which the request type is return,
Storing the first identifier in the first adapter to be collected;
Request communication information storing a request processing result indicating success or failure of storage of the first identifier is transmitted to the management module,
When the management module receives the request communication information storing the request processing result, the management module refers to the request processing result,
If the request processing result is not successful, the process ends as an error,
If the request processing result is successful, confirm the identifier of the first adapter of the collection request target managed in the identifier setting information,
If the identifier of the first adapter managed in the identifier setting information is the first identifier, the process is terminated,
When the identifier of the first adapter managed in the identifier setting information is a second identifier,
Create request communication information whose request type is the collection of the second identifier assigned to the first adapter of the collection request target,
Sending request communication information whose request type is collection to the WWN management unit;
When the WWN management unit receives request communication information whose request type is collection,
Referring to the WWN management information, search for the second identifier of the collection request target,
2. The computer system according to claim 1, wherein the distribution state corresponding to the second identifier of the collection request target of the WWN management information is set to undistributed. A plurality of server modules having a management controller, a first adapter, and a second adapter, a storage device connected to the server module via the first adapter, and the second adapter via the second adapter An identifier management method in a computer system comprising a management module connected to a server module,
The computer system includes a WWN management unit that manages a second identifier that is rewritably assigned to the first adapter, different from a first identifier that is uniquely assigned to the first adapter,
Distribution of the second identifier from the WWN management unit to the management module between the management controller and the management module and between the management module and the WWN management unit, and management of the second identifier Any one request among collection from the module to the WWN management unit, assignment of the second identifier from the management module to the management controller, or return of the second identifier from the management controller to the management module Request communication information having a type is sent and received,
When the management module receives new request communication information,
Confirm the request type of the request communication information,
An identifier management method comprising controlling the second identifier according to the request type. The management controller has a first request communication information update unit that updates request communication information that is transmitted to and received from the management module, and a first storage unit that stores the received request communication information.
The WWN management unit includes a second request communication information update unit that updates request communication information transmitted to and received from the management module, and a second storage unit that stores the received request communication information.
The management module includes: a third adapter connected to the second adapter; identifier setting information for managing correspondence between an identifier used in the first adapter and the first adapter; and the management controller Or a request communication information creation unit that creates request communication information that is transmitted and received between the WWN management unit and the management module, and a third storage unit that stores the received request communication information.
The management module, when new request communication information is stored in the third storage unit,
Confirm the request type of the request communication information,
8. The identifier management method according to claim 7, wherein the second identifier is controlled according to the request type. The first adapter is FC-HBA,
The second adapter is a NIC;
The identifier management method according to claim 7, wherein the identifier is a WWN. The WWN management unit is a WWN management server,
8. The identifier management method according to claim 7, wherein the plurality of server modules and the management module are mounted on a server chassis.   8. The identifier management method according to claim 7, wherein the WWN management unit is a WWN management mechanism included in the management module. When the management module detects a distribution request for the second identifier to the first adapter,
Creating request communication information in which the request type is distribution of the second identifier from the WWN management unit to the management module;
Sending request communication information whose request type is distribution to the WWN management unit;
When the WWN management unit receives request communication information in which the request type is distribution,
Referring to the WWN management information, search for a second identifier that can be assigned,
If there is a second identifier that can be allocated, the second identifier that can be allocated is stored in the request communication information;
Transmitting request communication information storing the second assignable identifier to the management module;
When the management module receives the request communication information storing the second assignable identifier,
Update the identifier corresponding to the first identifier of the distribution request target of the second identifier in the identifier setting information to the assignable second identifier,
Create request communication information whose request type is the assignment of the second identifier that can be assigned from the management module to the management controller,
Sending the request communication information that the request type is grant to the management controller;
When the management controller receives request communication information in which the request type is grant,
Referring to the request communication information in which the request type is grant, identify the first adapter that is the distribution request target of the second identifier,
8. The identifier management method according to claim 7, wherein the assignable second identifier is stored in the distribution request target first adapter. When the management module detects a collection request for the second identifier assigned to the first adapter,
Creating request communication information in which the request type is a return of the second identifier from the management controller to the management module;
Sending request communication information whose request type is return to the management controller,
When the management controller receives request communication information in which the request type is return,
Storing the first identifier in the first adapter to be collected;
Request communication information storing a request processing result indicating success or failure of storage of the first identifier is transmitted to the management module,
When the management module receives the request communication information storing the request processing result, the management module refers to the request processing result,
If the request processing result is not successful, the process ends as an error,
If the request processing result is successful, confirm the identifier of the first adapter of the collection request target managed in the identifier setting information,
If the identifier of the first adapter managed in the identifier setting information is the first identifier, the process is terminated,
When the identifier of the first adapter managed in the identifier setting information is a second identifier,
Create request communication information whose request type is the collection of the second identifier assigned to the first adapter of the collection request target,
Sending request communication information whose request type is collection to the WWN management unit;
When the WWN management unit receives request communication information whose request type is collection,
Referring to the WWN management information, search for the second identifier of the collection request target,
8. The identifier management method according to claim 7, wherein the distribution status corresponding to the second identifier of the collection request target of the WWN management information is undistributed.

Images