JP2001014147A - Acting system for setup - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a management console act for setting up the software of plural clients as an agent. SOLUTION: The plural clients 100-102 and a disk system 105 provided with logical units (LUs) 106-108 for storing the software to be executed in the clients 100-102 are connected through the loop 110 of an SAN(storage area network) and the management console 109 is connected to the loop 110. The management console 109 is provided with a maintenance control part 10 (50, 70) and sets up the software by activating a setup disk 103 in place of the clients 100-102 to the logical units (LUs) 106-108 respectively monopolized by the clients 100-102. Even when the number of the clients is increased or the dispersion of the clients is advanced due to the diffusion of fiber channels, the setup work of the software is easily performed and a work cost is reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a setup agency system, and more particularly, to a setup agency system in which software of a plurality of clients is set up on behalf of a management console.

[0002]

2. Description of the Related Art FIG. 23 is a conceptual diagram of a network system in which a plurality of clients and a plurality of storages for storing software executed by the clients are mutually connected via a network. This network system is a typical CSS (Client Server System)
In the form of a plurality of clients 100 to 102,
It is connected to logical units (LUs) 106 to 108 of a disk system 105 under the server 111 via a LAN (Local Area Network) 104. For example, a logical unit (LU) exclusively owned by the client 100
The software is set up on the setup disk 103 by the operator from the client 100.
Start and go.

[0003]

In the above-described conventional software setup, an operator exclusively performs setup for each client. Therefore, there is a problem that the setup work requires time and effort due to an increase in the number of clients. In particular, a fiber channel loop capable of transmitting 10 km of light between nodes (FC-AL: Fi
With the spread of bre Channel Arbitrated Loop), there is a problem that remoteization of a client to a client is promoted, and the cost of software setup work is increased due to client distribution. Therefore, an object of the present invention is to provide a setup proxy system in which software of a plurality of clients is set up on behalf of a management console.

[0004]

SUMMARY OF THE INVENTION In a first aspect, the present invention relates to a fiber channel loop interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A set-up agent system connected to a management console for setting up the software on behalf of the client, wherein a loop ID assigning means for assigning a loop ID of the client to the management console at the time of loop initialization of a fiber channel; A client registry holding unit that acquires and holds a registry in which information on a client machine name, a user name, and hardware / software type and version is registered; and a machine name, a user name, hardware / software of the management console. Management console registry holding means for acquiring and holding a registry in which information relating to the type and version of the management console is registered, registry comparing means for comparing the registry of the client and the management console, and information missing in the registry of the management console. Supplementary information adding means for virtually creating and adding, setup data management information holding means for holding a version as setup data management information, and comparing the software version in the client registry with the setup data version Version comparing means, setup executing means for executing setup, and client access inhibiting means for inhibiting access from the client to the storage. At the time of setup, suppress access that hinders setup from the client to the storage, mount the storage under the management console so that setup can be performed from the management console, assign a loop ID of the client to the management console, Since the management console has a registry equivalent to that of the client, the registry of the client is reflected in the registry of the management console, software is set up from the management console, and the software is assigned to the management console after the setup is completed. Returning a loop ID to the client, separating the storage from the subordinate of the management console, and releasing the inhibition of access to the storage from the client. Provide a to-up agency system. In the setup substitution system according to the first aspect, the management console performs the setup by transferring the loop ID of the setup target client to the self on the fiber channel loop and mounting the loop ID on the storage owned by the setup target client. This allows the management console to set up the software on behalf of the setup target client.

In a second aspect, the present invention provides a network for interconnecting a plurality of clients having different types of operation systems and a plurality of storages storing software executed by the clients. What is claimed is: 1. A system for connecting a management console for performing a setup on behalf of said client, comprising: an operation system type recognizing means for recognizing a type of an operation system of said client; Comprises a management console registry creating means for reflecting the registered registry in the registry of the management console, and a setup executing means for executing the setup, using the respective means, Recognizing the type of the operation system of the client, and reflecting the registry related to the operation system of the client in the registry of the management console so that the management console performs setup on the same type of operation system as the client; Starts up an operation system of the same type as the client and executes the setup of the operation system. In the setup agency system according to the second aspect, the management console checks the type of the operation system of the client to be set up, starts the same operation system by itself, and performs the setup by reflecting the registry of the client to be set up to itself. . This allows the management console to set up the operation system on behalf of the setup target client.

In a third aspect, the present invention provides a method for setting up the software to the clients in a network loop interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. What is claimed is: 1. A setup proxy system comprising a management console connected in place, a version search unit for searching whether the software of the plurality of clients is the same version, a setup target client determination unit for determining a setup target client, and a setup A batch processing means for setting up a batch processing means, wherein each of the means is used to set up a client to be set up from the management console by using an existing software version as a key when setting up the software. Determined by ropes, and batching to run setup continuously provides setup agent system, characterized in that setting up the software of the same version of a plurality of set-up target client continuously. In the setup substitution system according to the third aspect, the management console checks the software version of the client, sets a plurality of clients having the same version of software as set-up target clients, performs batch processing, and performs continuous setup. . This allows the management console to
On behalf of multiple setup target clients,
You can set up the software in order.

[0007] In a fourth aspect, the present invention relates to a network loop for interconnecting a plurality of clients and a plurality of storages storing software executed by the clients, and setting the software setup to the clients. A setup proxy system comprising a management console connected in place, comprising virtual client means for operating an operation system of the client on the management console as a virtual client, and executing software of a plurality of setup target clients by multitasking. A setup agency system characterized by setting up is provided. 4th above
In the setup agency system of the aspect of the above, the management console starts up the operation systems of a plurality of setup target clients as virtual clients and performs setup by multitasking. This allows the management console to set up software in parallel on behalf of a plurality of setup target clients.

In a fifth aspect, the present invention provides a method for setting up the software to the clients in a network loop interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A setup agency system in which a management console is connected in place of the management console, wherein an image volume holding unit for holding an image volume of a setup disk such as a CD-ROM in a storage X at the time of setting up a storage A, and operation stopped due to a failure or the like. Version recognition means for recognizing the version of the operation system and software of the new storage A 'which has been replaced with the storage A, and a setup for executing the setup of the storage A' using the storage X when the version is old. The management console holds an image volume of a setup disk such as a CD-ROM in the storage X, and the operating system and the version of the exchanged storage A ′ are stored in the storage X. Is provided, the setup data of the storage A 'is executed using the image volume of the storage X, and the setup proxy system is provided. In the setup substitution system according to the fifth aspect, the image volume of the setup disk is held in the storage X when the storage A is set up, and the image volume held in the storage X when the storage A is replaced with the storage A ′. , The management console sets up software for the storage A '. This allows the management console to set up the software on behalf of the setup target client.

When the storages A, B,... Are sequentially set up, an image volume of a setup disk such as a CD-ROM is held in a high-speed storage X such as an HDD at the same time as the storage A is set up. By performing the setup after B using the storage X, the setup work can be sped up.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring now to the drawings, a first embodiment of the present invention will be described.
The fifth to fifth embodiments will be described. Note that the present invention is not limited by this.

FIG. 22 is a conceptual diagram of a setup substitution system according to the first to third embodiments of the present invention. The setup agency system 1 includes a plurality of clients 100 to 102 and the clients 100 to 102.
System 105 having logical units (LU) 106 to 108 for storing software to be executed by
And a SAN (Storage Area Network) loop 110
, And a management console 109 is connected to the loop 110. The management console 1
Reference numeral 09 includes a maintenance control unit 10 (first embodiment), 50 (second embodiment), and 70 (third embodiment) in addition to the configuration of a normal computer. For the logical units (LU) 106, 107, and 108 exclusively owned by 101 and 102, the setup disk 103 is started on behalf of the clients 100, 101, and 102 to perform software setup work.

-First Embodiment- In a first embodiment, the clients 101, 102, 1
03 corresponds to the logical units (LU) 106, 10
The case where the version of the OS or application included in each of the servers 7 and 108 is upgraded from the management console 109 will be described with reference to FIGS.

FIG. 1 is a block diagram showing the configuration of the maintenance control unit 10 according to the first embodiment. The maintenance control unit 10 includes a loop ID assignment unit 11,
Management console registry holding unit 12, client registry holding unit 13, registry comparing unit 14, supplementary information creating and adding unit 15, program version comparing unit 1
6, a setup data management information holding unit 17, a setup execution unit 18, a logical unit (LU) mount / unmount execution unit 19, and a client access suppression unit 20. The loop ID assigning unit 11
Corresponds to the client 10 shown in FIG.
In order to substitute for 0, 101, and 102, the loop ID of the clients 100, 101, and 102 is temporarily assigned as the loop ID of the management console 109. The management console registry holding unit 12 stores the machine name, the user name, and the like of the management console 109 in order to return to the original registry after the management console 109 performs setup on behalf of the clients 100, 101, and 102.
A registry in which the types and versions of hardware / software are registered is temporarily saved and held in a buffer. The client registry holding unit 13 stores the management console 109 in the client 100, 101, 10
2. Clients 100 and 10 required to take over
A registry in which the machine names, user names, and hardware / software types and versions 1, 102 are registered from the clients 100, 101, and 102, and temporarily stored in a buffer. The registry comparison unit 14
Registry of Management Console 109 and Client 10
Compare with the registries obtained from 0, 101 and 102.
The supplementary information creating and adding unit 15 simulates the missing information in the registry of the management console 109 by the registry comparing unit 14 and adds the information to the registry of the management console 109. The program version comparing unit 16 compares the version of the program to be set up with the version of the program that has already been set up. The setup data management information holding unit 17 temporarily stores management information in the setup data in a buffer. The setup execution unit 18
Do the setup work. The logical unit (LU) mount / unmount execution unit 19 manages the logical units (LU) 106, 107, and 108 occupied by the clients 100, 101, and 102 on the management console 10.
9 or clients 100, 101,
It returns to the subordinate of 102. The client access suppressing unit 20 includes clients 100, 101, and 102.
Stops access to the logical units (LU) 106, 107, and 108 during setup.

FIG. 2 is a block diagram showing details of the loop ID allocating section 11. As shown in FIG. The loop ID assigning unit 11 is a client for the fiber channel.
A client loop ID receiving unit 30 that reads the loop IDs of 0, 101, and 102, and a management console loop ID receiving unit 3 that reads the loop ID of the management console 109
1 and a loop I of the clients 100, 101 and 102
D and a loop ID exchange unit 32 for exchanging loop IDs of the management console 109 with each other;
A client loop ID transmitting unit 33 that transmits the loop IDs of the management console 109 and the management console 109 to the clients 100 and 10.
1 and 102, and a management console loop ID transmitting unit 34 for transmitting the information to the control console loop ID transmitting unit 102.

FIG. 3 is a block diagram showing details of the registry comparing unit 14. As shown in FIG. This registry comparison unit 14
Is a registry receiving unit 35 of the management console that receives a registry including information such as the connection hardware environment of the management console 109, and the clients 100 and 10.
A registry receiving unit 36 of a client that receives a registry containing information such as a connection hardware environment of the client 102 and the information on hardware such as a peripheral device and a machine name of the management console 109 from a registry of the management console 109. A hardware resource search unit 37 of the management console for searching for information on the machine names and user names of the clients 100, 101 and 102 and information on hardware such as peripheral devices from the registry of the clients 100, 101 and 102. A hardware resource search unit 38; a hardware resource comparison unit 39 for comparing the hardware resources of the management console 109 with the hardware resources of the clients 100, 101 and 102; Minute information (information of the configuration is different from the part)
And a same information extracting unit 41 that extracts the same information (information of the part having the same configuration) of the hardware resource information.

FIG. 4 shows the supplementary information creating and adding unit 15.
FIG. 4 is a block diagram showing the details of. The supplementary information creation and addition unit 15 includes a virtual hardware resource (supplementary information) creation unit 42 that creates a virtual hardware resource based on the difference information of the hardware resources extracted by the registry comparison unit 14, An original hardware resource (existing information) holding unit 43 for temporarily holding the same information of the hardware resources extracted by the registry comparing unit 14, the virtual hardware resources (supplementary information) and the original hardware resources (existing information). Information) to create a new registry, and the management console 1
09, and a new registry transmission unit 45 for transmitting the data to the new registry 09.

Next, the operation according to the first embodiment will be described with reference to the flowcharts of FIGS. The operation in FIG. 5 is performed when the management console 109 in FIG.
It is started by starting setup processing using the setup disk 103 such as (200). In step 201, the client access suppression unit 20 suppresses all accesses from the clients 100, 101, and 102 to the disk system 105. Step 20
In the second, the logical unit (LU) mount / unmount execution unit 19 executes the client 100, 101, 102
Manages the logical units (LU) 106, 107, and 108 of the disk system 105 exclusively owned by
To mount. In step 203, the management console 109 registers the registries of the clients 100, 101, 102 with the logical units (LU) 106, 107, 1.
08, the client registry holding unit 13
To hold. In step 204, the management console 10
9 holds its own registry in the management console registry holding unit 12. In step 205, the management console 109 assigns the loop ID of the client 100 (or 101, 102) to the management console 109 by the loop ID assignment unit 11 (the management console loop ID reception unit 31, the loop ID exchange unit 32, the client ID). Along with the loop ID transmission unit 33), the loop ID of the management console 109 is allocated to the client 100 (or 101, 102) (client loop I).
D receiving unit 30, loop ID exchanging unit 32, and management console loop ID transmitting unit 34). In step 206,
The registry of the management console 109 held by the management console registry holding unit 12 is received by the registry information receiving unit 35 of the management console, and the hardware resource search unit 37 of the management console sends the machine name, user name, and peripheral device of the management console 109 S connected as
Retrieve hardware information such as CSI card. Also,
The registry of the client 100 (or 101, 102) held by the client registry holding unit 13 is
The client's registry information receiving unit 36 receives the client's hardware resource searching unit 38, and the client's hardware resource searching unit 38 receives the machine name and user name of the client 100 (or 101, 102) and hardware information such as a SCSI card connected as a peripheral device. Search for. Further, the hardware resource comparison unit 39 compares the hardware resource of the management console 109 with the client 100 (or 10).
1, 102).

Referring to FIG. 6, in step 207, the difference information extracting unit 40
If there is insufficient hardware resource in the management console 109 in step 102), the process proceeds to step 208,
If not, proceed to step 210. In step 208,
The virtual hardware resource (supplementary information) creation unit 42 of the supplementary information creation and addition unit 15 converts the dummy information of the hardware resource (for example, a SCSI card or a video card) that is lacking in the management console 109 into a virtual hardware resource. (Copied from the hardware resource of the client 100 (or 101 or 102)). Then, the registry combining unit 44 combines the virtual hardware resource with the original hardware resource of the management console 109 held in the original hardware resource (existing information) holding unit 43 to create a new registry. In step 209,
The new registry transmission unit 45 transmits the synthesized registry to the management console 109.

In step 210, the management console 10
From 9, only the management information in the setup data is read and held in the buffer of the setup data management information holding unit 17. In step 211, the client 100 stored in the client registry
The version information of the OS or the application registered in the registry (or 101 or 102) is compared with the version information of the OS or the application stored in the setup data management information storage unit 17. Proceed, if equal, step 21
Go to 9.

In step 212, a setup is executed. In step 213, the registry of the client 100 (or 101, 102) is read and held again in the buffer of the client registry holding unit 13, and the registry of the management console 109 is read and held again in the buffer of the management console registry holding unit 12. Next, the loop ID assignment unit 11 assigns the loop ID assigned to the management console 109 to the client 100 (or 101, 102), and assigns the loop ID assigned to the clients 100, 101, 102 to the management console 109. That is,
Return to the original loop ID. In step 214, the logical units (LU) 106, 107, 108 are unmounted from the management console 109. In step 215,
The inhibition of access to the disk system 105 by the client 100 (or 101 or 102) is released. In step 216, if the OS has been set up, the process proceeds to step 217. If the application has been set up, the setup process ends. In step 217, the OS is booted. Then, the setup process ends.

In step 219, the client 100 is stored again in the buffer of the client registry holding unit 13.
The registry of (or 101, 102) is read and held, and the registry of the management console 109 is again read and held in the buffer of the management console registry holding unit 12. Next, in the loop ID assignment unit 11,
The loop ID assigned to the management console 109 is assigned to the client 100 (or 101, 102), and the loop ID assigned to the clients 100, 101, 102 is assigned to the management console 109.
That is, the original loop ID is restored. In step 220,
The logical units (LU) 106, 107, and 108 are unmounted from the management console 109. Step 22
1, the client 100 (or 101, 102)
Of the disk system 105 is released. Then, the setup process ends.

Now, an OS and an application are set up for a logical unit (LU) 106 exclusively owned by the client 100, and then the client 101
It is assumed that the same setup is performed for the logical unit (LU) 107 exclusively used by the. Conventionally, one worker moves from the client 100 to the client 101 and performs the same work, or two workers perform the same work separately, but in a SAN environment network based on Fiber Channel, When the client 100 and the client 101 are arranged at a long distance, it is not easy to move. On the other hand, using two workers doubles the human cost. On the other hand, according to the first embodiment, one operator only needs to sequentially select and set up the logical units (LU) 106 and 107 from one management console 109. Therefore, no movement is required.
Also, human costs can be reduced.

Second Embodiment In the second embodiment, the clients 101, 102, 1
FIGS. 7 to 12 and FIG. 22 show cases in which the logical unit (LU) 03 has different Windows-based OSs (NT, 95, 98) in the corresponding logical units (LU) 106, 107, and 108, respectively, and performs each setup from the management console 109. This will be described with reference to FIG.

FIG. 7 is a block diagram showing the configuration of the maintenance control unit 50 according to the second embodiment. The maintenance control unit 50 includes a loop ID assignment unit 11,
Client registry holding unit 13, program version comparing unit 16, setup data management information holding unit 1
7. Setup execution unit 18, Logical unit (LU)
The system includes a mount / unmount execution unit 19, a client access suppression unit 20, an OS type recognition unit 51, and a management console registry holding / creating unit 52. Elements having the same reference numbers as in the first embodiment have the configuration described in the first embodiment. The OS type recognition unit 51 recognizes whether the OS of the clients 100, 101, and 102 is Windows NT or Windows 95. The management console registry holding / creating unit 52 temporarily holds, in a buffer, a registry in which the machine name, user name, hardware / software type and version of the management console 109 are registered, and creates a new registry required for setup. Create

FIG. 8 is a block diagram showing details of the OS type recognition section 51. The OS type recognizing unit 51 receives an OS-related registry receiving unit 53 that receives information about the type and version of the OS in the registry received from the clients 100, 101, and 102, and an OS identifier search that searches for an identifier indicating the type of the OS. A set-up unit 54, a setup data OS management information receiving unit 55 that receives OS management information from the management information of the setup data, and an OS that compares the types of the OSs of the clients 100, 101, and 102 with the types of the OSs to be set up. The comparing unit 56 and the OS management information of the OS to be set up are stored in the management console 1
09, and an OS management information transmission unit 57 that transmits the OS management information to the OS 09.

FIG. 9 is a block diagram showing details of the management console registry holding / creating unit 52. This management console registry holding / creating unit 52
An OS management information receiving unit 58 that receives OS management information such as the type and version of the OS from the type recognition unit 51, and an OS-related registry creation that creates an OS-related registry required for the management console 109 to recognize the corresponding OS Part 59
A management console registry receiving unit 62 for receiving an original registry of the management console 109; a management console loop ID transmitting unit 61 for transmitting loop ID information from the original registry of the management console 109; an OS-related registry and a management console The registry synthesizing unit 6 which synthesizes 109 original registries
0 and the newly created registry is added to the management console 109.
And a new registry transmission unit 63 for transmitting to the new registry.

Next, the operation according to the second embodiment will be described with reference to the flowcharts of FIGS. The operation in FIG. 10 is performed when the management console 109 in FIG.
-It is started by starting a setup process using a setup disk 103 such as a ROM (30)
0). Steps 301 to 305 are the same processing as steps 201 to 205 described in the first embodiment. However, the management console registry holding unit 2 of the first embodiment is replaced by a management console registry holding / creating unit 52. In step 306, the OS identification unit 51
The related registry receiving unit 53 extracts the OS related information from the client registry held in the client registry holding unit 13. Then, the OS identifier search unit 54 searches for the type and language of the OS of the client.

Referring to FIG. 11, in step 307, the process proceeds to step 308 if the language of the OS of the client searched in step 306 is not Japanese, and to step 309 if the language is Japanese. In step 308, O
The S comparing unit 56 checks the OS management information of the setup data received from the setup data OS management information receiving unit 55 with the OS of the client searched in the step 306.
If the languages match, the process proceeds to step 309, and if they do not match, the process proceeds to step 323 in FIG.

In step 309, the OS management information in the setup data is checked, and the OS to be set up is checked.
If is not Windows NT, go to step 310
If it is owsNT, go to step 311. In step 310, the OS management information in the setup data is checked. If the OS to be set up is Windows 95, the process proceeds to step 312;
Proceed to 3.

In step 311, the management information of Windows NT is stored in the management console registry
The management console 10 received by the S management information receiving unit 58, created in the registry by the OS-related registry creating unit 59, and received by the management console registry receiving unit 62.
9 by the registry synthesizing unit 60. Then, the process proceeds to step 314.

In step 312, the management information of Windows 95 is stored in the management console registry
The management console 10 received by the S management information receiving unit 58, created in the registry by the OS-related registry creating unit 59, and received by the management console registry receiving unit 62.
9 by the registry synthesizing unit 60. Then, the process proceeds to step 314.

In step 313, the management information of Windows 98 is stored in the management console registry
The management console 10 received by the S management information receiving unit 58, created in the registry by the OS-related registry creating unit 59, and received by the management console registry receiving unit 62.
The new registry is created by adding it to the 9 original registries by the registry synthesizing unit 60. Then, the process proceeds to step 314.

In step 314, the new registry created is transmitted from the new registry transmitting unit 63 to the management console 1.
09. In step 315, only the version information of the setup data from the management console 109 is read and held in the buffer of the setup data management information holding unit 17.

In step 316 of FIG. 12, the version information of the OS registered in the registry of the client 100 (or 101 or 102) held in the buffer of the client registry holding unit 13 and the setup data management information holding unit 17 Is compared with the version information of the OS stored in the buffer. If the values are not equal, the process proceeds to step 317;

In step 317, the setup is executed. In step 318, the registry of the client 100 (or 101, 102) is read and held again in the buffer of the client registry holding unit 13, and the registry of the management console 109 is read again in the buffer of the management console registry holding / creating unit 52. And the loop ID assigning unit 11 assigns the loop ID of the management console 109 to the client 100 (or 101, 102), and assigns the loop ID of the client 100 (or 101, 102) to the management console 1.
09. That is, the state before the setup is returned. In step 319, the logical unit (LU) 1
06 (or 107, 108) to the management console 109
Unmount from. In step 320, the inhibition of access to the disk system 105 by the client 100 (or 101, 102) is released. Step 3
At 21, the OS is booted. Then, the setup process ends.

In step 323, the client 100 is stored again in the buffer of the client registry holding unit 13.
(Or 101, 102) to read and hold the registry, and the management console registry holding / creating unit 5
2, the registry of the management console 109 is read and held again in the buffer 2, and the loop ID of the
(Or 101, 102), and client 1
A loop ID of 00 (or 101, 102) is assigned to the management console 109. That is, the state before the setup is returned. In step 324, the logical unit (LU) 106 (or 107, 108) is unmounted from the management console 109. In step 325,
The inhibition of access to the disk system 105 by the client 100 (or 101 or 102) is released. Then, the setup process ends.

For example, the OS of the client 100 connected to the SAN loop 110 is Windows NT 4.0 Japanese, the OS of the client 101 is Windows 95 English, and the OS of the client 102 is Windows 98
Assuming that you have an OS environment that is a Japanese version, the CD-ROM media you want to set up is Wi-
If it is the latest revision of ndows NT 4.0 Japanese version,
The management console 109 executes Windows only for the logical unit (LU) 106 exclusively used by the client 100.
Perform NT 4.0 Japanese version setup. Therefore, only by exchanging the CD-ROM media to be set up, a different type of O
S can be set up and work efficiency can be improved.

Third Embodiment In the third embodiment, the clients 101, 102, 1
03 corresponds to the logical units (LU) 106, 10
7 and 108 have the same version of applications, and the management console 109 continuously performs batch processing of version upgrades of these applications.
This will be described with reference to FIGS.

FIG. 13 is a block diagram showing the configuration of the maintenance control unit 70 according to the third embodiment. The maintenance control unit 70 includes an all client registry holding unit 71, an application version searching unit 72,
Setup target / non-target client division unit 73, loop ID assignment unit 74, management console registry holding / creating unit 75, setup data management information holding unit 1
7. Setup execution unit 18, Logical unit (LU)
A mount / unmount execution unit 19 and a client access suppression unit 20 are provided. Elements having the same reference numbers as in the first embodiment have the configuration described in the first embodiment. The all-client registry holding unit 71 temporarily stores, in a buffer, a registry in which the machine name, user name, hardware / software type and version of all clients used for the application version search are registered. The application version search unit 72 searches for the same version of an application. The setup target / non-target client division unit 73 specifies a client to be set up. The loop ID allocating unit 74 performs the processing shown in FIG.
Clients 100, 1 directly connected to AN loop 110
A new loop ID is assigned to the setup target client out of 01 and 102. The management console registry holding / creating unit 75 temporarily holds, in a buffer, a registry in which the machine name, user name, hardware / software type and version of the management console 109 are registered, and stores a new registry required for setup. create.

FIG. 14 is a block diagram showing details of the application version search section 72. The application version search unit 72 receives a setup request application type and version identifier receiving unit 76 for receiving information on the type and version of the application from the setup management information holding unit 17, and a client possession from the buffer of the all client registry holding unit 71. All client application type and version identifier receiving units 77 that receive information on the type and version of the application being executed, a setup request OS, a comparison and classification unit 78 that compares the setup request application with the current environment, an OS to be set up, The same version application determination unit 79 as a setup target for determining an application.

FIG. 15 is a block diagram showing details of the setup target / non-target client division unit 73. As shown in FIG. The setup target / non-target client division unit 73 includes a setup target client loop ID transmission unit 80 that transmits a loop ID of a client determined as a setup target to the loop ID assignment unit 74,
A setup batch file creation unit 81 that creates a batch file for setting up the same version of the application to be set up collectively, and a client logical unit (LU) unmount that issues an instruction to unmount the client logical unit (LU) from the management console 109 And an instruction issuing unit 82.

FIG. 16 shows the loop ID assigning section 74.
FIG. 4 is a block diagram showing the details of. The loop ID assigning unit 74 determines whether the loop I
Loop I of setup target client receiving D
D receiving unit 83 and the loop I of all the clients that receive the loop IDs of all the clients on the SAN loop 110
D receiving unit 86, a new loop ID creating unit 84 for creating a loop ID newly assigned to the setup target client, a new loop ID sending unit 85 for sending a new loop ID to the setup target client, and setup of the setup target client Previous original loop ID and new loop ID used during setup
And a loop ID management map 87 for registering the relationship.

Next, an operation according to the third embodiment will be described with reference to the flowcharts of FIGS. The operation in FIG. 17 is performed when the management console 109 in FIG.
-It is started by starting a setup process using a setup disk 103 such as a ROM (40)
0). In step 401, since the management console 109 becomes the setup host during the setup, the client 100
2 to all access to the disk system 105. In step 402, the clients 100-1
The logical units (LU) 106 to 108 of the disk system 105 occupied by the 02 are mounted on the management console 109 by the logical unit (LU) mount / unmount execution unit 19 of the maintenance control unit 70. In step 403, the management console 109
Register the 00-102 registry as a logical unit (LU)
From 106 to 108, the data is read and held in the client registry holding unit 13 which is a buffer. In step 404, only the management information in the setup data from the management console 109 is stored in the setup data management information holding unit 1.
7 is read and held. In step 405, based on the type and version of the application received by the setup request application type and version identifier reception unit 76 from the setup data management information storage unit 17, the all client registry storage unit 71
From the various application types and versions received by the client application type and version identifier receiving unit 77, the same one is selected by the comparison and classification unit 78. In step 406, the same version application determination unit 79 to be set up performs
The client to be set up is, for example, the client 100 where the same version of the application is found,
101 is determined. In step 407, the version information of the application of the setup target client is compared with the version information of the application held in the buffer of the setup data management information holding unit 17, and if they are not the same, the process proceeds to step 408 in FIG. In this case, the process proceeds to step 420 in FIG.

In step 408 of FIG. 18, the loop IDs of the setup target clients 100 and 101 are received by the loop ID reception unit 83 of the setup target clients, and the loop IDs received by the loop ID reception units 86 of all the clients are used. In the new loop ID creation unit 84, the setup target clients 100 and 101
, A new loop ID is created, and the new and old loop IDs are associated with each other and registered in the loop ID management map 87. In step 409, the new loop ID transmission unit 85 transmits the new loop ID to the setup target clients 100 and 101. In step 410, the client logical unit (LU) unmount instruction issuing unit 82
Sends an instruction to the logical unit (LU) mount / unmount execution unit 19 to unmount the logical units (LU) 106 to 108 of the clients 100 to 102 from the management console 109. In step 411,
A batch file is created by the setup batch file creation unit 81 so that the setup program can be started continuously for the logical units (LU) 106 and 107 of the setup target clients 100 and 101. In step 412, the logical unit (LU) 106 of the setup target client 100 is mounted on the management console 109 again. In step 413,
The setup is executed by the setup execution unit 18 for the logical unit (LU) 106 of the setup target client 100. In step 414, the logical unit (LU) 1 of the setup target client 100
After completing the setup for the client 06, the logical unit (LU) 106 of the client 100 to be set up is unmounted from the management console 109, and the logical unit (L
U) 107 is mounted on the management console 109 again. In step 415, the setup execution unit 18 performs setup on the logical unit (LU) 107 of the setup target client 101. In step 416, after completing the setup for the logical unit (LU) 107 of the setup target client 101, the logical unit (LU) 107 of the setup target client 101 is unmounted from the management console 109. In step 417, the setup target clients 100, 1 are determined from the loop ID management map 87.
The loop ID before setup 01 is searched, assigned to the clients 100 and 101 to be set up, and returned to the state before setup. In step 418, the inhibition of access to the disk system 105 by the clients 100 and 101 is released. Then, the setup processing ends (419).

At step 420 in FIG. 18, the logical units (LU) 106 to 108 are unmounted in order to disconnect them from the management console 109 without performing setup. In step 421, the clients 100 to 10
The inhibition of access to the second disk system 105 is released. Then, the setup process ends (41).
9).

For example, the logical units (LU) 106 and 107 exclusively owned by the clients 100 and 101 are assigned to the micro units.
If it is assumed that the application Word 5.0 of the soft company is installed, and the setup is performed from the management console 109 using the setup disk 103 of Word 6.0, the setup disk 103 is first activated. Then, a client having Word is searched from all the clients 100 to 103 on the SAN loop 110.
Next, a client having the same version or older than the setup disk 103 is selected, and a setup target client is specified. For example, Client 1
00 and 101 are the targets. And in batch processing,
Logical unit (LU) of clients 100 and 101
The same setup process is continuously performed for 106 and 107. As described above, a system having high management performance can be realized by continuously performing the same setup work in a batch.

Fourth Embodiment In a fourth embodiment, the clients 101, 102, 1
03 corresponds to the logical units (LU) 106, 10
FIG. 1 shows a case in which applications having the same version are provided in the storage consoles 7 and 108, and the management console 109 simultaneously processes the upgrades of these applications.
This will be described with reference to FIG.

FIG. 19 is a conceptual diagram of a setup substitution system according to the fourth embodiment. The setup agency system 4 includes logical units (LUs) 106 to 1
Disk system 105 with 08, management console 1
09, the virtual clients 112 to 114 operating by emulating the client OS, the local HDD 115 of the management console 109, and a plurality of Cs.
It comprises a setup disk 116 such as a D-ROM.

The virtual clients 112 to 114
This is emulation software that can start another OS among the OSs of the management console 109. That is, Ma
Software “V” to run Windows OS on cintosh OS
Another Windows O on Windows OS, such as “irtual PC”
Emulation software that runs S. The virtual client 112 is a logical unit (LU) 10
6, the virtual client 113 mounts the logical unit (LU) 107, the virtual client 114 mounts the logical unit (LU) 108, and the OS of each of the virtual clients 112 to 114
Start up an installer such as Windows setup.exe to perform setup. Setup disk 106
Prepares several virtual clients, and transmits setup data to the logical units (LU) 106 to 108 using a CD-ROM changer or the like.

According to the fourth embodiment, a large-scale CD-RO
By providing a plurality of setup disks with an M changer or the like, a mode in which a large amount of setup is executed overnight can be realized.

-Fifth Embodiment-In the fifth embodiment, a logical unit (LU) is generated due to a failure or the like.
A case in which the disk system performs setup using its own environment when the configuration inside the disk system changes due to replacement of the disk drive will be described with reference to FIGS. 20 and 21.

FIG. 20 is a configuration diagram of a setup substitution system according to the fifth embodiment. The setup proxy system 5 includes a loop 110, S
Clients 100 to 102 such as PCs connected on the loop 110 of the AN, a management console 109 for setting up an OS and an application in place of the clients 100 to 102, and a CD-RO used for the setup
M, etc. setup disk 103, disk system 91, logical units (LU) 106 to 108, logical unit (LU) 9 having a setup data image
2. It comprises a replaced logical unit (LU) 93 and a maintenance control unit 90 that manages and operates the setup process.

Next, based on the flowchart of FIG.
An operation according to the fifth embodiment will be described. FIG.
The operation (a) is performed when the management console 109 in FIG.
For upgrading S and applications, CD-
It is started by starting a setup process using the setup disk 103 such as a ROM (500).
In step 501, the management console 109 sends the logical units (LU) 106, 10 of the disk system 91.
7 and 108 are mounted under the subordinate, and the setup is executed according to the procedure described in the first embodiment. Step 50
In 2, the maintenance control unit 90 transfers the image volume of the setup disk 103 to the logical unit (L
U) Copy to 92 and hold. Then, the first setup is completed (503).

The operation shown in FIG. 21B is started in the second and subsequent setups (504). In step 505, the maintenance control unit 90 compares the logical unit (LU) 92 having the setup data image with the other logical units (LU) 106 to 108, and determines whether the OS or the application is older than the setup data of the logical unit (LU) 92. If found, the process proceeds to step 506, and if not found, the setup process ends (508). In step 506, the management console 109 mounts the logical unit (LU) 92 as a setup device. In step 507, the management console 109 mounts the logical unit (LU) found in step 505 (for example, the replaced logical unit (LU) 93), and executes the setup according to the procedure described in the first embodiment. Then, the setup processing ends (508).

In the fifth embodiment, maintenance of the OS and applications can be performed only in the disk system 91 when a logical unit (LU) replacement occurs. In this method, the setup itself can be speeded up by putting the setup data in a high-speed device such as an HDD in the disk system 91.

[0056]

According to the setup proxy system of the present invention, the software of a plurality of clients can be set up on behalf of the management console. Therefore, even if the number of clients increases, and even if the distribution of clients advances due to the spread of Fiber Channel, software setup work can be easily performed,
Work costs can be reduced.

[Brief description of the drawings]

FIG. 1 is an internal structural diagram of a maintenance control unit according to a first embodiment of the present invention.

FIG. 2 is an internal structural diagram of a loop ID assignment unit according to the first embodiment of the present invention.

FIG. 3 is an internal structural diagram of a registry comparing unit according to the first embodiment of the present invention.

FIG. 4 is an internal structural diagram of a supplementary information creation and addition unit according to the first embodiment of the present invention.

FIG. 5 is a flowchart illustrating a setup proxy process according to the first embodiment of the present invention.

FIG. 6 is a flowchart continued from FIG. 5;

FIG. 7 is an internal structural diagram of a maintenance control unit according to a second embodiment of the present invention.

FIG. 8 is an internal structure diagram of an OS type recognition unit according to a second embodiment of the present invention.

FIG. 9 is an internal structural diagram of a management console registry holding / creating unit according to the second embodiment of the present invention.

FIG. 10 is a flowchart illustrating a setup proxy process according to a second embodiment of the present invention.

FIG. 11 is a continuation of the flowchart in FIG. 10;

FIG. 12 is a flowchart continued from FIG. 11;

FIG. 13 is an internal structural diagram of a maintenance control unit according to a third embodiment of the present invention.

FIG. 14 is an internal structural diagram of an application version search unit according to a third embodiment of the present invention.

FIG. 15 is an internal structural diagram of a setup target / non-target client division unit according to the third embodiment of the present invention.

FIG. 16 is a loop ID according to the third embodiment of the present invention;
It is an internal structure figure of an allocation part.

FIG. 17 is a flowchart illustrating a setup proxy process according to a third embodiment of the present invention.

FIG. 18 is a flowchart continued from FIG. 17;

FIG. 19 is a conceptual diagram of a setup agency system according to a fourth embodiment of the present invention.

FIG. 20 is a conceptual diagram of a setup agency system according to a fifth embodiment of the present invention.

FIG. 21 is a flowchart illustrating a setup proxy process according to a fifth embodiment of the present invention.

FIG. 22 is a conceptual diagram of a setup agency system according to first, second, and third embodiments of the present invention.

FIG. 23 is a conceptual diagram of a conventional network system.

[Explanation of symbols]

10. Maintenance control unit, 11 Loop ID assigning unit, 12 Management console registry holding unit, 1
3 ··· Client registry holding unit, 14 ·· Registry comparison unit, 15 ·· Supplementary information creation and addition unit, 16 ·
A program version comparison unit, 17 a setup data management information holding unit, 18 a setup execution unit,
19-Logical unit (LU) mount / unmount execution unit, 20-Client access suppression unit, 30
.. A client loop ID receiving unit, 31 a management console loop ID receiving unit, 32 a loop ID exchanging unit
33: Client loop ID transmission unit, 34: Management console loop ID transmission unit, 35: Registry information reception unit of management console, 36: Registry information reception unit of client, 37: Hardware resource search of management console , 38, a client hardware resource search unit, 39, a hardware resource comparison unit, 40, a difference information extraction unit, 41, an identical information extraction unit, 42, creation of virtual hardware resources (supplementary information) , 43... Original hardware resource (existing information) holding unit, 44... Registry synthesizing unit, 45... New registry sending unit, 50.
1. OS type recognition unit, 52 management console registry holding / creating unit, 53 OS related registry receiving unit, 54 OS identifier searching unit, 55 setup data OS management information receiving unit, 56 OS comparison unit, 57
··· OS management information transmission unit, 58 ··· OS management information reception unit, 59 ··· OS related registry creation unit, 60 ··· Registry synthesis unit, 61 ··· Management console loop ID transmission unit, 62 ··· Reception of management console registry Part, 63
A new registry transmission unit, 70 a maintenance control unit, 71 an all client registry holding unit, 72
An application version search unit, 73 a setup target / non-target client division unit, 74 a loop ID assigning unit, 75 a management console registry holding / creating unit, 76 a setup request application type and version identifier receiving unit; 77 ··· All client application type and version identifier receiving section, 78 ··· Comparison / classification section, 79 ··· Set-up identical version application determining section, 80 ··· Setup target client loop ID transmitting section, 81 ·
-Setup batch file creation unit, 82-Client logical unit (LU) unmount instruction issuing unit, 83-Loop I of setup target client
D receiving section, 84 new loop ID creating section, 85 new loop ID transmitting section, 86 loop ID receiving sections of all clients, 87 loop ID management map, 90
Maintenance control unit, 91 · · disk system, 92
..Logical unit (LU) having setup data image, 93. ・ Replaced logical unit (LU),
100 to 102 client, 103 setup disk, 104 LAN, 105 disk system, 106 to 108 logical unit (L
U), 109 management console, 110 SAN
111, server, 112 to 114, virtual client, 115, local HDD, 116, setup disk

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Ikuya Yagisawa 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Inside Hitachi, Ltd.System Development Laboratory Co., Ltd. (72) Inventor Yasuyuki Ajimatsu 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Co., Ltd. Inside Hitachi System Development Laboratory (72) Akira Yamamoto 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture, Japan Hitachi, Ltd. System Development Laboratory (72) Inventor Hideki Kamimaki 1099, Ozenji, Aso-ku, Kawasaki, Kanagawa Prefecture F-term in Hitachi, Ltd. System Development Laboratory (Reference) 5B076 AA01 5B089 GA21 GA23 GB02 HA06 JA34 JB07 KA13 KB04 KB06 KB09 LB10 LB14

Claims (5)

[Claims] 1. A management console for setting up the software on behalf of the clients is connected to a fiber channel loop interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A loop ID allocating means for allocating a loop ID of the client to the management console in a fiber channel loop initialization, a machine name of the client,
A client registry holding unit that acquires and holds a registry in which information relating to a user name, hardware / software type and version is registered, and a machine name, a user name, hardware / software type and version of the management console. Management registry holding means for acquiring and holding a registry in which information about the management console is registered, a registry comparison means for comparing the client and the registry of the management console, and virtually creating information missing in the registry of the management console Supplementary information adding means for adding and adding, setup data management information holding means for holding a version as setup data management information, software version and setup data version in the client registry And version comparison means for comparing,
A setup execution unit for executing setup, and a client access inhibiting unit for inhibiting access to the storage from the client, wherein the setup from the client to the storage is performed at the time of software setup using the units. The storage is mounted under the management console so as to prevent access to be hindered and can be set up from the management console, and a loop ID of the client is provided.
Is assigned to the management console, the management console has a registry equivalent to the client, so that the registry of the client is reflected in the registry of the management console, the software is set up from the management console, and after the setup is completed, A setup substitute system, wherein a loop ID assigned to the management console is returned to the client, the storage is separated from the subordinate of the management console, and access suppression from the client to the storage is released. 2. The software is set up on behalf of the clients in a network interconnecting a plurality of clients having different types of operation systems and a plurality of storages storing software to be executed by the clients. A setup proxy system connected to a management console, comprising: an operation system type recognizing means for recognizing the type of the operation system of the client; and a registry in which information on the type and version of the operation system of the client is registered. A management console registry creating means for reflecting the result in the registry of the management console; and a setup executing means for executing the setup. The management console recognizes the type of the application system, and reflects the registry related to the operation system of the client in the registry of the management console so that the management console performs setup on the same type of operation system as the client. A setup agency system, characterized in that the same kind of operation system as above is started and the operation system is set up. 3. A management console for setting up the software on behalf of the clients is connected to a network interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A setup agent system, comprising: a version search unit that searches whether the software of the plurality of clients is the same version; a setup target client determination unit that determines a setup target client; and a setup batch processing unit that batches setup. Using the above means, at the time of software setup, using the existing software version as a key to search and determine the client to be set up from the management console; Setup proxy system that batching, characterized in that setting up the software of the same version of a plurality of set-up target client continuously to perform to. 4. A management console for setting up the software on behalf of the clients is connected to a network interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A setup agent system, comprising: virtual client means for operating an operation system of the client on the management console as a virtual client, and setting up software of a plurality of setup target clients by multitasking. . 5. A management console for setting up the software on behalf of the clients is connected to a network interconnecting a plurality of clients and a plurality of storages storing software executed by the clients. A setup agency system, wherein an image volume of a setup disk such as a CD-ROM is stored in a storage X when the storage A is set up.
Means for storing an image volume holding means, a version recognizing means for recognizing an operation system and software version of a new storage A 'which has been replaced with a storage A which has been shut down due to a failure or the like. And a setup execution unit for executing setup of the storage A ′ using the storage unit. The management console holds an image volume of a setup disk such as a CD-ROM in the storage X by using each of the units. A setup in which the version of the operation system or the application of A 'is older than the setup data of the storage X, and if the version is older, the setup of the storage A' is executed using the image volume of the storage X Line system.