JP2021089587A - Tool execution program, information processing device, and tool execution method - Google Patents

Abstract

To provide a tool execution terminal that can easily identify a failure occurrence cause in connection to a server.SOLUTION: In an information processing system 100, a tool execution terminal 1 receives a list of user identifiers, as input from an operator 4, and receives a logon script from a virtual machine (VM) 202. The tool execution terminal executes the logon script by a virtual desktop and collects logs output from the virtual machine. The tool execution terminal identifies an identifier of a user who failed in connection to the virtual machine by referring to a database and comparing an identifier of a user who succeeded in connection to the virtual machine with identifiers of multiple users who connect to the virtual machine. Based on connection information related to the user who succeeded in connection to the virtual machine, a list for identifying the reason why the users who failed in connection to the virtual machine cannot connect to the virtual machine is output.SELECTED DRAWING: Figure 3

Description

The present invention relates to a tool execution program, an information processing device, and a tool execution method.

In a Virtual Desktop Infrastructure (VDI) environment or Server Based Computing (SBC) environment, even if a single terminal does not cause a failure when connecting to a server, a failure occurs when multiple terminals connect to a server multiple times. There are cases where it occurs.

For example, if you release an environment to end users that has no problem even if you check the single connection after changing the settings during maintenance during operation, problems due to multiple connections may occur.

Therefore, before the release, the operation is confirmed by multiple connections.

Special Table 2016-535890 International Publication No. 2010/109681 Japanese Unexamined Patent Publication No. 2016-31720

FIG. 1 is a block diagram illustrating a first example of a multiple connection operation in a related example.

The information processing system 600a shown in FIG. 1 includes a plurality of (three in the illustrated example) servers 7 and a plurality of (three in the illustrated example) operating terminals 8.

Each server 7 deploys the hypervisor 701. Each hypervisor 701 deploys a plurality of (three in the illustrated example) Virtual Machine (VM) 702.

The user 9 connects to a plurality of VM702s at the same time zone by the operation terminal 8.

However, in order to confirm the operation by multiple connections, after preparing a plurality of operation terminals 8 as connection sources (see reference numeral A1) or preparing a large number of users 9 to operate (see reference numeral A2), to some extent. It takes time to check the operation of.

FIG. 2 is a block diagram illustrating a second example of the multiple connection operation in the related example.

The information processing system 600b shown in FIG. 2 includes a plurality of (three in the illustrated example) servers 7, a plurality of (three in the illustrated example) operating terminals 8, and one management terminal 6.

Each server 7 deploys the hypervisor 701. Each hypervisor 701 deploys a plurality of (three in the illustrated example) VM702.

The user 9 connects to a plurality of VM702s at the same time zone via the operation terminal 8 by the management terminal 6 on which the performance measurement tool is installed.

When checking the operation using the performance measurement tool, it is difficult to operate unless the operator has the skill to use the tool (see code B1), and it may be necessary to install an agent etc. in the environment to be tested. Therefore, it is not easy to apply it to the environment in which the customer is operating.

One aspect is aimed at facilitating the identification of the cause of failure in the connection to the server.

In one aspect, the tool executor connects to the virtual machine by comparing to the computer the identifiers of the users who have successfully connected to the virtual machine and the identifiers of multiple users who connect to the virtual machine. To identify the identifier of the user who failed, and to identify the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine based on the connection information related to the user who succeeded in connecting to the virtual machine. Output the list and execute the process.

On one side, it is easy to identify the cause of failure in connecting to the server.

It is a block diagram explaining the 1st example of the multiple connection operation in a related example. It is a block diagram explaining the 2nd example of the multiple connection operation in the related example. It is a block diagram which shows typically the configuration example of the information processing system in one example of Embodiment. It is a block diagram which shows typically the hardware configuration example of the tool execution terminal shown in FIG. It is a block diagram which shows typically the software structure example in the information processing system shown in FIG. It is a block diagram explaining the verification process of multiple connection in the tool execution terminal shown in FIG. It is a table exemplifying the user ID list information in the tool execution terminal shown in FIG. It is a table exemplifying the log file information in the tool execution terminal shown in FIG. It is a table which shows 1st example of the join log file information in the tool execution terminal shown in FIG. It is a table which shows the 2nd example of the join log file information in the tool execution terminal shown in FIG. It is a table which shows the 3rd example of the join log file information in the tool execution terminal shown in FIG. It is a table which shows the 4th example of the join log file information in the tool execution terminal shown in FIG. It is a flowchart explaining the script execution process in the tool execution terminal shown in FIG. It is a flowchart explaining the logon script processing in the tool execution terminal shown in FIG. It is a flowchart explaining the log combination processing in the tool execution terminal shown in FIG.

Hereinafter, one embodiment will be described with reference to the drawings. However, the embodiments shown below are merely examples, and there is no intention of excluding the application of various modifications and techniques not specified in the embodiments. That is, the present embodiment can be variously modified and implemented without departing from the spirit of the present embodiment.

Further, each figure does not mean that it includes only the components shown in the figure, but may include other functions and the like.

Hereinafter, since the same reference numerals indicate the same parts in the drawings, the description thereof will be omitted.

[A] Example of Embodiment [A-1] System Configuration Example FIG. 3 is a block diagram schematically showing a configuration example of the information processing system 100 in the example of the embodiment.

The information processing system 100 shown in FIG. 1 includes a tool execution terminal 1, a plurality of (three in the illustrated example) servers 2, and a plurality of (three in the illustrated example) operation terminals 3.

Each server 2 deploys the hypervisor 201. Each hypervisor 201 deploys a plurality of (three in the illustrated example) VM202s.

The operator 4 is connected to each of the plurality of VM202s by the operation terminal 3.

The tool execution terminal 1 connects to a plurality of VM 202s at the same time zone, and detects the presence or absence of a failure.

FIG. 4 is a block diagram schematically showing a hardware configuration example of the tool execution terminal 1 shown in FIG.

As shown in FIG. 4, the tool execution terminal 1 is an example of an information processing device, and includes a CPU 11, a memory 12, a display control unit 13, a storage device 14, an input interface (I / F) 15, a read / write processing unit 16, and communication. It is equipped with an I / F17. The server 2 and the operation terminal 3 may also have the same hardware configuration as the tool execution terminal 1.

The memory 12 is an example of a storage unit, and is an example of a storage device including a Read Only Memory (ROM) and a Random Access Memory (RAM). A program such as a Basic Input / Output System (BIOS) may be written in the ROM of the memory 12. The software program of the memory 12 may be appropriately read and executed by the CPU 11. Further, the RAM of the memory 12 may be used as a primary recording memory or a working memory.

The display control unit 13 is connected to the display device 130 and controls the display device 130. The display device 130 is a liquid crystal display, an Organic Light-Emitting Diode (OLED) display, a Cathode Ray Tube (CRT), an electronic paper display, or the like, and displays various information to an operator or the like. The display device 130 may be combined with an input device, for example, a touch panel.

The storage device 14 is an example device for reading, writing, and storing data, and for example, a Hard Disk Drive (HDD), a Solid State Drive (SSD), or a Storage Class Memory (SCM) may be used. The storage device 14 may store the user ID list information, the log file information, and the combined log file information, which will be described later, using FIGS. 6 to 12, respectively.

The input I / F 15 may be connected to an input device such as a mouse 151 or a keyboard 152 to control an input device such as the mouse 151 or the keyboard 152. The mouse 151 and the keyboard 152 are examples of input devices, and the operator 4 performs various input operations via these input devices.

The read / write processing unit 16 is configured so that the recording medium 160 can be attached. The read / write processing unit 16 is configured to be able to read the information recorded on the recording medium 160 while the recording medium 160 is attached. In this example, the recording medium 160 is portable. For example, the recording medium 160 is a flexible disk, an optical disk, a magnetic disk, a magneto-optical disk, a semiconductor memory, or the like.

The communication I / F 17 is an interface for enabling communication with an external device.

The CPU 11 is a processing device that performs various controls and calculations, and realizes various functions by executing an Operating System (OS) or a program stored in the memory 12.

The device for controlling the operation of the entire tool execution terminal 1 is not limited to the CPU 11, and may be, for example, any one of MPU, DSP, ASIC, PLD, and FPGA. Further, the device for controlling the operation of the entire tool execution terminal 1 may be a combination of two or more types of CPU, MPU, DSP, ASIC, PLD and FPGA. MPU is an abbreviation for Micro Processing Unit, DSP is an abbreviation for Digital Signal Processor, and ASIC is an abbreviation for Application Specific Integrated Circuit. PLD is an abbreviation for Programmable Logic Device, and FPGA is an abbreviation for Field Programmable Gate Array.

FIG. 5 is a block diagram schematically showing a software configuration example in the information processing system 100 shown in FIG.

The VM 202 shown in FIG. 3 activates the Active Directory 210 and functions as a user ID registration unit 211, a group policy setting unit 212, and a group policy allocation unit 213.

The user ID registration unit 211 registers the user ID of the user who performed the logon operation as a preliminary preparation for the verification process of multiple connections.

The group policy setting unit 212 executes the logon script 221 on the virtual desktop 220 as a preliminary preparation for the verification process of multiple connections. The logon script 221 outputs the logon record to the tool execution terminal 1, waits for a certain period of time, and then logs off.

The group policy allocation unit 213 allocates a group policy to the logon test user as a preliminary preparation for the verification process of multiple connections.

The tool execution terminal 1 functions as a script execution unit 111, a user ID list creation unit 112, an Agent installation unit 113, and a log aggregation execution unit 114. Further, the tool execution terminal 1 holds a result log 141 and a tool execution result 142 for each ID (in other words, an identifier) as an output result of the verification process of multiple connections. The result log 141 may be referred to as connection information.

The user ID list creation unit 112 creates user ID list information, which will be described later, using FIG. 7 as a preliminary preparation for the verification process of multiple connections.

The Agent installation unit 113 installs an Agent for executing the multiple connection verification process for each VM 202 as a preliminary preparation for the multiple connection verification process.

As an operation of the multiple connection verification process, the script execution unit 111 repeats as many times as the number of user IDs, specifies the user IDs, and starts the Agent in the VM202.

In other words, the script execution unit 111 functions as an example of an execution unit that executes multiple connections for each of the plurality of VM 202 by the identifiers of the plurality of users.

As an operation of the multiple connection verification process, the log aggregation execution unit 114 aggregates the result log 141 for each ID output by the logon script 221 in the virtual desktop 220 and compares it with the user ID in the user ID list information. Then, the log aggregation execution unit 114 identifies the logon failure ID, and outputs the tool execution result 142 indicating the user ID that could not be logged on and the user ID that could be logged on.

In other words, the log aggregation execution unit 114 compares the ID of the user who succeeded in connecting to the VM202 with the ID of a plurality of users who connect to the VM202, and the ID of the user who failed to connect to the VM202. It functions as an example of a specific part that identifies. Further, the log aggregation execution unit 114 outputs a tool execution result 142 for identifying the reason why the user who failed to connect to the VM202 cannot connect to the VM202 based on the result log 141 relating to the user who succeeded in connecting to the VM202. It functions as an example of the output unit.

The log aggregation execution unit 114 has a result log 141 relating to a user who has successfully connected to the VM202 and a result log 141 relating to a user who has failed to connect to the VM202, and a result log relating to a user who has successfully connected to the VM202. Only 141 may function as an example of a receiving unit receiving from the VM202.

FIG. 6 is a block diagram illustrating a multiple connection verification process in the tool execution terminal 1 shown in FIG.

The operator 4 inputs a list of test user IDs to the tool execution terminal 1 (see reference numeral C1), and assigns a logon script 221 to each test user ID in the tool execution terminal 1 (see reference numeral C2).

The tool execution terminal 1 receives a list of user IDs as input from the operator 4 (see reference numeral C3). Further, the tool execution terminal 1 receives the logon script 221 from the VM202 (see reference numeral C4).

In the core logic, the tool execution terminal 1 collects the log output from the VM202 (see reference numeral C5), refers to the database, and compares the collected log with the user ID list (see reference numerals C6 and C8). Then, the tool execution terminal 1 creates a list of users for whom the logon script 221 has not been executed (see reference numeral C7).

The tool execution terminal 1 outputs the logon result total log (see reference numeral C9).

The user receives the output of the aggregated log of the logon results from the tool execution terminal 1 (see reference numeral C10).

FIG. 7 is a table illustrating user ID list information in the tool execution terminal 1 shown in FIG.

The user ID list information is a list of user IDs used for the test, and the number of user IDs of the number of VM202s to be tested is prepared. In the example shown in FIG. 7, a case where five VM202s are tested is shown.

The user ID list information is, for example, a file name of "TestUserIDList" .log and is saved in the local disk of the tool execution terminal 1 (in other words, the storage device 14).

FIG. 8 is a table illustrating log file information in the tool execution terminal 1 shown in FIG.

The log file information includes the connection time, success / failure, virtual PC host, hypervisor host name, affiliated security group name, affiliated Organization Unit (OU) name, and connection broker name.

The connection time is the time when the connection is started from the VDI client software. For success / failure, "success" is registered when the logon script 221 is executed. The virtual PC host name is the host name of VM202. The hypervisor host name is the host name of the hypervisor 201 on which the VM202 operates. The affiliation security group name is the name of the security group to which the user ID belongs. The affiliation OU name is the OU name to which the user ID belongs. The connection broker name is the name of the server 2 that connects first.

For example, the log file information is set with a file name of "[implementation date] + [user ID] .log" and is saved in the local disk of the tool execution terminal 1 (in other words, the storage device 14). File sharing is set so that the log file information can be accessed from the virtual desktop 220.

FIG. 9 is a table showing a first example of the join log file information in the tool execution terminal 1 shown in FIG.

The combined log file information is a combination of a plurality of log file information shown in FIG. Like the log file information, the combined log file information includes the connection time, success / failure, virtual PC host, hypervisor host name, affiliated security group name, affiliated OU name, and connection broker name.

In the example shown in FIG. 9, logon has failed with the user ID names "test03" and "test09". In addition, the hypervisor host names "Server1" and "Server2" have been successfully logged on, and the connection broker names "Broker1" and "Broker2" have been successfully logged on.

That is, the logon failure is not due to the hypervisor 201 or the connection broker, but to the virtual PC hosts "PC03" and "PC09" that the user ID names "test01" and "test02" attempted to log on, respectively. Is presumed to be.

FIG. 10 is a table showing a second example of the join log file information in the tool execution terminal 1 shown in FIG.

In the example shown in FIG. 10, logon has failed with the user ID names "test03" and "test09". In addition, only the hypervisor host name "Server1" has been successfully logged on, and the connection broker names "Broker1" and "Broker2" have been successfully logged on.

That is, it is presumed that the logon failure is caused by the hypervisor 201 of "Server2" in which the logon has never been successful.

FIG. 11 is a table showing a third example of the join log file information in the tool execution terminal 1 shown in FIG.

In the example shown in FIG. 11, logon has failed with the user ID names "test03" and "test09". In addition, the hypervisor host names "Server1" and "Server2" have been successfully logged on, and only the connection broker name "Broker1" has been successfully logged on.

In other words, it is presumed that the logon failure is due to the connection broker of "Broker2" whose logon has never been successful.

FIG. 12 is a table showing a fourth example of the join log file information in the tool execution terminal 1 shown in FIG.

In the example shown in FIG. 12, logon has failed with the user ID names "test03" and "test09". In addition, only the hypervisor host name "Server1" has been successfully logged on, and only the connection broker name "Broker1" has been successfully logged on.

In other words, the login failure is caused by one or more of the hypervisor 201 of "Server1", the connection broker of "Broker1", and the virtual PC hosts "PC03" and "PC09", which have never been successfully logged on. It is presumed to be the cause.

Therefore, if you try to connect to PC03 on Server2 with test03 and succeed, it turns out that Server2 and test03 are normal, and the cause of the failure can be estimated according to the result of the connection test of Broker2.

Also, if you try to connect to PC03 on Server2 with test03 and fail, it turns out that Server2, test03 or Broker2 is abnormal, and by trying the connection test with Broker2 and the connection test with test04, the cause of the failure Can be estimated.

[A-2] Operation Example The script execution process in the tool execution terminal 1 shown in FIG. 3 will be described with reference to the flowcharts (steps S1 to S11) shown in FIG.

The script execution unit 111 repeats the script execution shown in steps S2 to S11 by the number of user IDs (step S1).

The script execution unit 111 extracts one user ID from the user ID list information (step S2).

The script execution unit 111 inputs the start time of the script into the log file information of the user ID name (step S3).

The script execution unit 111 executes the VDI client software by specifying the user ID (step S4).

The script execution unit 111 executes the logon script 221 on the virtual desktop 220 (step S5). The details of the execution process of the logon script 221 in step S5 will be described later with reference to FIG.

The script execution unit 111 extracts the virtual PC host name from the log file information of the user ID name (step S6).

The script execution unit 111 confirms which hypervisor 201 the virtual PC is operating on (step S7).

The script execution unit 111 inputs the confirmed hypervisor host name in the log file information of the user ID name (step S8).

The script execution unit 111 inputs the group name to which the user ID name belongs in the log file information (step S9).

The script execution unit 111 inputs the belonging OU name into the log file information of the user ID name (step S10).

The script execution unit 111 confirms the broker from the log of the VDI client software (step S11). Then, the script execution process ends.

Next, the logon script processing in the tool execution terminal 1 shown in FIG. 3 will be described with reference to the flowcharts (steps S51 to S54) shown in FIG.

The script execution unit 111 inputs "success" in the log file information of the user ID name (step S51).

The script execution unit 111 inputs the virtual PC host name into the log file information of the user ID name (step S52).

The script execution unit 111 logs off from the virtual desktop 220 after waiting for a certain period of time (step S53).

The script execution unit 111 inputs the confirmed hypervisor host name in the log file information of the user ID name (step S54). Then, the logon script processing ends.

Next, the log combination process in the tool execution terminal 1 shown in FIG. 3 will be described according to the flowchart (step S21) shown in FIG.

The log aggregation execution unit 114 combines the log file information of all user ID names and outputs the combined log file information (step S21). Then, the log combination process ends.

[A-3] Effect The log aggregation execution unit 114 compares the ID of the user who succeeded in connecting to the VM202 with the IDs of a plurality of users who connect to the VM202, so that the user who fails to connect to the VM202 Identify the ID. Further, the log aggregation execution unit 114 outputs a tool execution result 142 for identifying the reason why the user who has failed to connect to the VM202 cannot connect to the VM202 based on the result log 141 relating to the user who has succeeded in connecting to the VM202. To do.

This makes it easy to identify the cause of the failure in the connection to the server 2. Specifically, by checking the connection before and after the system change, it is possible to check the effect of the system change (in other words, setting change, patch application, etc.). Further, the connection operation can be confirmed by the same procedure even when the information processing system 100 is newly introduced or the setting is changed. Furthermore, since the connection confirmation mechanism is simple, the cost for operation confirmation can be reduced, and operation confirmation can be performed by the same procedure regardless of the type of virtualization product. In addition, no specialized skill is required to operate the tool, and the tool execution result 142 can be easily confirmed.

The log aggregation execution unit 114 has a result log 141 relating to a user who has successfully connected to the VM202 and a result log 141 relating to a user who has failed to connect to the VM202, and a result log relating to a user who has successfully connected to the VM202. Only 141 is received from VM202.

Thereby, the user who failed in the connection can be estimated from the result log 141 relating to the user who succeeded in connecting to the VM202.

The result log 141 includes the host name of VM202. The result log 141 also includes the host name of the hypervisor 201 that deploys the VM202. In addition, the result log 141 contains the name of the server that first connects to connect to the VM202.

From these, it is possible to efficiently estimate in which part of the information processing system 100 the cause of the failure occurs. Specifically, the tendency of problematic users (for example, using the same group policy, using terminals with the same manufacturer / model name, participating in the same security group, using the same server 2) Etc.) can be confirmed.

The script execution unit 111 causes each of the plurality of VM 202s to execute multiple connections by the identifiers of the plurality of users.

As a result, even if there is only one operator 4 and one tool execution terminal 1, the operation can be confirmed in a relatively short time.

[B] Other disclosed techniques are not limited to the above-described embodiments, and can be variously modified and implemented without departing from the spirit of the present embodiment. Each configuration and each process of the present embodiment can be selected as necessary, or may be combined as appropriate.

[C] Additional Notes The following additional notes will be further disclosed with respect to the above embodiments.

(Appendix 1)
On the computer
By comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifier of a plurality of users who connect to the virtual machine, the identifier of the user who failed to connect to the virtual machine can be identified.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine is output.
A tool execution program that executes processing.

(Appendix 2)
Of the connection information related to the user who succeeded in connecting to the virtual machine and the connection information related to the user who failed to connect to the virtual machine, only the connection information related to the user who succeeded in connecting to the virtual machine. , Received from the virtual machine,
The tool execution program according to Appendix 1, which causes the computer to execute the process.

(Appendix 3)
The connection information includes the host name of the virtual machine.
The tool execution program according to Appendix 1 or 2.

(Appendix 4)
The connection information includes the host name of the hypervisor that deploys the virtual machine.
The tool execution program according to any one of Items 1 to 3.

(Appendix 5)
The connection information includes the name of the server that first connects to connect to the virtual machine.
The tool execution program according to any one of Items 1 to 4.

(Appendix 6)
Multiple connections are executed for each of the plurality of virtual machines by the identifiers of the plurality of users.
The tool execution program according to any one of Items 1 to 5, which causes the computer to execute the process.

(Appendix 7)
A specific unit that identifies the identifier of the user who failed to connect to the virtual machine by comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifiers of a plurality of users who connect to the virtual machine.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, an output unit that outputs a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine, and an output unit.
Information processing device.

(Appendix 8)
Of the connection information related to the user who succeeded in connecting to the virtual machine and the connection information related to the user who failed to connect to the virtual machine, only the connection information related to the user who succeeded in connecting to the virtual machine. The information processing apparatus according to Appendix 7, further comprising a receiving unit that receives from the virtual machine.

(Appendix 9)
The connection information includes the host name of the virtual machine.
The information processing device according to Appendix 7 or 8.

(Appendix 10)
The connection information includes the host name of the hypervisor that deploys the virtual machine.
The information processing device according to any one of Supplementary note 7 to 9.

(Appendix 11)
The connection information includes the name of the server that first connects to connect to the virtual machine.
The information processing device according to any one of Appendix 7 to 10.

(Appendix 12)
The information processing apparatus according to any one of Supplementary note 7 to 11, further comprising an execution unit that executes multiple connections to each of the plurality of virtual machines by the identifiers of the plurality of users.

(Appendix 13)
By comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifier of a plurality of users who connect to the virtual machine, the identifier of the user who failed to connect to the virtual machine can be identified.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine is output.
How to run the tool.

(Appendix 14)
Of the connection information related to the user who succeeded in connecting to the virtual machine and the connection information related to the user who failed to connect to the virtual machine, only the connection information related to the user who succeeded in connecting to the virtual machine. , Received from the virtual machine,
The tool execution method according to Appendix 13.

(Appendix 15)
The connection information includes the host name of the virtual machine.
The tool execution method according to Appendix 13 or 14.

(Appendix 16)
The connection information includes the host name of the hypervisor that deploys the virtual machine.
The tool execution method according to any one of Appendix 13 to 15.

(Appendix 17)
The connection information includes the name of the server that first connects to connect to the virtual machine.
The tool execution method according to any one of Appendix 13 to 16.

(Appendix 18)
Multiple connections are executed for each of the plurality of virtual machines by the identifiers of the plurality of users.
The tool execution method according to any one of Appendix 13 to 17.

100, 600a, 600b: Information processing system 1: Tool execution terminal 11: CPU
111: Script execution unit 112: User ID list creation unit 113: Agent installation unit 114: Log aggregation execution unit 12: Memory 13: Display control unit 130: Display device 14: Storage device 141: Result log 142: Tool execution result 15: Input I / F
151: Mouse 152: Keyboard 16: Read / write processing unit 160: Recording medium 17: Communication I / F
2,7: Server 201,701: Hypervisor 202,702: VM
211: User ID registration unit 212: Group policy setting unit 213: Group policy allocation unit 220: Virtual desktop 221: Logon script 3, 8: Operation terminal 4: Operator 6: Management terminal 9: User

Claims (8)

On the computer
By comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifier of a plurality of users who connect to the virtual machine, the identifier of the user who failed to connect to the virtual machine can be identified.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine is output.
A tool execution program that executes processing. Of the connection information related to the user who succeeded in connecting to the virtual machine and the connection information related to the user who failed to connect to the virtual machine, only the connection information related to the user who succeeded in connecting to the virtual machine. , Received from the virtual machine,
The tool execution program according to claim 1, wherein the computer executes the process. The connection information includes the host name of the virtual machine.
The tool execution program according to claim 1 or 2. The connection information includes the host name of the hypervisor that deploys the virtual machine.
The tool execution program according to any one of claims 1 to 3. The connection information includes the name of the server that first connects to connect to the virtual machine.
The tool execution program according to any one of claims 1 to 4. Multiple connections are executed for each of the plurality of virtual machines by the identifiers of the plurality of users.
The tool execution program according to any one of claims 1 to 5. A specific unit that identifies the identifier of the user who failed to connect to the virtual machine by comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifiers of a plurality of users who connect to the virtual machine.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, an output unit that outputs a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine, and an output unit.
Information processing device. By comparing the identifier of the user who succeeded in connecting to the virtual machine with the identifier of a plurality of users who connect to the virtual machine, the identifier of the user who failed to connect to the virtual machine can be identified.
Based on the connection information related to the user who succeeded in connecting to the virtual machine, a list for identifying the reason why the user who failed to connect to the virtual machine cannot connect to the virtual machine is output.
How to run the tool.

Images