JP2012198651A - Cluster system, virtual machine server, failover method for virtual machine, and failover program for the virtual machine - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform automated failover of a virtual machine by utilizing failure detection of a physical NIC.SOLUTION: A cluster system 100 comprises a virtual machine server 1 capable of operating a virtual machine. The virtual machine server 1 comprises; one or more physical NICs; one or more virtual switches connected to physical NICs; monitoring means 111 for detecting failure in physical NICs; control means 112 for invalidating one or more ports of a virtual switch which is connected to a physical NIC in which failure has been detected; and clusterware 5 which is connected to each of virtual switches and performs failover of a virtual machine and monitoring of a status of a virtual switch. The clusterware 5 detects failure of a virtual switch caused by invalidation of a port by the control means 112 and performs failover of a virtual machine.

Description

  The present invention relates to clusterware, and more particularly, to a technology for performing automatic failover of a virtual machine by using failure detection of a physical NIC.

  In recent years, there are an increasing number of systems in which a virtual machine is failed over to another virtual machine server when a failure occurs in the virtual machine server by combining virtualization technology and clusterware.

  Here, failover refers to a function in which an alternative server takes over processing and data when a failure occurs in the server.

  Although the specifications and operations are various even though it is a clusterware, a cluster that can monitor the status by giving IP addresses to various resources such as NIC (Network Interface Card) and applications. Wear exists.

  By using the clusterware, when any failure occurs in the monitoring target resource, it is possible to promptly execute a countermeasure such as restart of an application or a virtual machine or failover.

  The network in the virtual machine server has the following structure.

  A physical NIC is mounted on the virtual machine server, and the physical NIC is connected to a virtual switch provided by a hypervisor (software that provides a virtual environment).

  The virtual switch is connected to a virtual NIC prepared by the hypervisor for each virtual machine. The OS on the virtual machine performs communication using a virtual NIC prepared for each.

  That is, by using a virtual switch, one physical NIC can be shared and used by a plurality of virtual machines. Normally, an IP address is required for a virtual NIC, but communication with a virtual switch can be performed without assigning an IP address to a physical NIC.

  FIG. 5 shows an example of a cluster system in a virtual environment based on background technology using clusterware that employs an IP address monitoring method.

  As shown in FIG. 5, the cluster system in the virtualized environment according to the background art is composed of a virtual machine server 19 and a virtual machine server 20.

  The virtual machine server 19 includes a management OS (operating system) 21, virtual machines 32 to 33, virtual NICs V8 to V11, virtual switches 25 to 26, and physical NICs P5 to P6. The management OS 21 has clusterware 23.

  Similarly, the virtual machine server 20 includes a management OS (operating system) 22, virtual NICs V12 to V14, virtual switches 27 to 28, and physical NICs P7 to P8. The management OS 22 has clusterware 24.

  The physical NICs P5 and P7 are connected to the L2 switch 29. Using this communication path, the clusterware 23 and 24 check whether each other is operating normally.

  Further, the physical NICs P6 and P8 are connected to the L2 switch 30, and this network can communicate with an external network through an external connection 31. Specifically, this network is used when a virtual machine user connects to the virtual machine 32, 33, or 34 on the virtual machine server 19 or 20 from the outside through the external connection 31.

  In the cluster system in the virtual environment according to this background art, the ports that can be monitored by the clusterware 23 and 24 are virtual NICs V8 to V14 as shown in FIG. 6, and the physical NICs P5 to P8 cannot be monitored.

  The cluster system in the virtual environment according to the background art having such a configuration operates as follows.

  That is, when a failure occurs in the physical NIC P6, the virtual machine server 19 cannot communicate with the L2 switch 29, so that the virtual machine user connects to the virtual machines 32-33 using the external connection 31. Is impossible.

  However, since the communication between the virtual NIC V9 and the virtual switch 26 can operate normally, the clusterware 23 cannot detect that the virtual machine server 19 cannot communicate with the L2 switch 29.

  Therefore, in order to deal with the virtual machines 32 to 33 in which the virtual machine user becomes unable to connect, work by maintenance personnel is indispensable.

  Here, as a related technique, Patent Document 1 describes that a physical port number and a virtual port number are associated and managed.

  Further, as a related technique, Patent Document 2 describes a virtual machine failer.

  Further, as a related technique, it is described that a channel failure is determined by notifying a pseudo channel error.

JP 2008-219531 A JP 2009-163736 A JP-A-01-021542

  In a cluster system in a virtual environment, when a failure occurs in a physical NIC installed in a virtual machine server, the virtual NIC monitored by the clusterware is operating normally with connection to the virtual switch. The clusterware cannot detect a failure of the physical NIC.

  Also, depending on the clusterware, it is not possible to monitor a physical NIC to which no IP address is assigned.

  Note that Patent Document 1 has a description of managing physical port numbers and virtual port numbers in association with each other, Patent Document 2 has a description of failing over a virtual machine, and Patent Document 3 has There is a description that a channel failure is determined by notifying a pseudo channel error.

  However, in any of Patent Documents 1-3, there is no description of a specific method for detecting a failure of a physical NIC and a failover of a virtual machine triggered by the failure.

  For this reason, there is a problem that it is not possible to quickly respond to a physical NIC failure.

(Object of invention)
An object of the present invention is to provide a cluster system, a virtual machine server, a virtual machine failover method, and a virtual machine failover program that solves the above-described problems and performs automatic failover of a virtual machine using failure detection of a physical NIC. That is.

  A first cluster system according to the present invention is a cluster system including a virtual machine server capable of operating a virtual machine, wherein the virtual machine server includes one or more physical NICs and one or more physical NICs connected to the physical NICs. A virtual switch, a monitoring unit that detects a failure of the physical NIC, a control unit that disables one or more ports of the virtual switch connected to the physical NIC that has detected the failure, and a virtual machine connected to each virtual switch The clusterware detects a failure of the virtual switch due to port invalidation by the control means and performs failover of the virtual machine.

  The first virtual machine server of the present invention is a virtual machine server capable of operating a virtual machine of a cluster system, and includes one or more physical NICs, one or more virtual switches connected to the physical NIC, Monitoring means for detecting a NIC failure, control means for invalidating one or more ports of a virtual switch connected to a physical NIC that has detected a failure, failover of a virtual machine and virtual switch connected to each virtual switch The clusterware detects a failure of the virtual switch due to port invalidation by the control means, and performs failover of the virtual machine.

  A first virtual machine failover method according to the present invention is a virtual machine failover method in a cluster system including a virtual machine server capable of operating a virtual machine, wherein the virtual machine server detects a failure of a physical NIC. By disabling one or more ports of the virtual switch connected to the physical NIC that has detected the failure, and by clusterware connected to each virtual switch and performing failover of the virtual machine and monitoring of the status of the virtual switch, Detecting a failure of the virtual switch due to port invalidation and performing failover of the virtual machine.

  A first virtual machine failover program according to the present invention is a virtual machine failover program in a cluster system including a virtual machine server capable of operating a virtual machine, the virtual machine server detecting a failure of a physical NIC. The clusterware that disables one or more ports of the virtual switch connected to the physical NIC that detected the failure, and that is connected to each virtual switch and that performs failover of the virtual machine and monitoring the status of the virtual switch, A process of detecting a virtual switch failure caused by port invalidation and performing a failover of the virtual machine is executed.

  According to the present invention, automatic failover of a virtual machine can be performed using failure detection of a physical NIC.

It is a block diagram which shows the structure of the cluster system by the 1st Embodiment of this invention. It is a figure which shows the structural example of the data management table by 1st Embodiment. It is a block diagram which shows the detail of the virtual switch control part by 1st Embodiment. It is a flowchart which shows operation | movement of the cluster system by 1st Embodiment. It is a block diagram which shows the structure of the cluster system by background art. It is a figure which shows the port which clusterware can monitor in the cluster system by background art. It is a block diagram which shows the hardware structural example of the virtual machine server of this invention.

  The present invention uses the virtual switch control function to link down a port of a virtual switch associated with a failed physical NIC when an abnormality occurs in communication between the virtual switch and the failed physical NIC. .

  Clusterware cannot detect the occurrence of an error in the communication path because the virtual NIC registered in the clusterware cannot normally communicate with the virtual switch. It is possible to automatically deal with failover and the like.

  In order to clarify the above and other objects, features and advantages of the present invention, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. In addition to the above-described object of the present invention, other technical problems, means for solving the technical problems, and operational effects thereof will become apparent from the disclosure of the following embodiments.

  In all the drawings, the same reference numerals are given to the same components, and the description will be omitted as appropriate.

(First embodiment)
FIG. 1 is a block diagram showing the configuration of the first cluster system 100 of the present invention. The cluster system 100 is a cluster system in a virtual environment.

  Referring to FIG. 1, a cluster system 100 has a virtual environment cluster configuration with two virtual machine servers 1 and 2.

  The virtual machine server 1 includes a management OS 3, virtual machines 16 to 17, virtual NICs V1 to V4, virtual switches 7 to 8, ports C1 to C4 on the virtual switch, virtual switch control means 11, and physical NICs P1 to P2. Including. The management OS 3 includes clusterware 5.

  Similarly, the virtual machine server 2 includes a management OS 4, virtual NICs V5 to V7, virtual switches 9 to 10, ports C5 to C7 on the virtual switch, virtual switch control means 12, and physical NICs P3 to P4. The management OS 4 has clusterware 6.

  Note that each unit of the virtual machine server 1 and each unit of the virtual machine server 2 have the same functions, and thus description thereof will be omitted as appropriate.

  The virtual NIC V1 on the management OS 3 can perform communication using the physical NIC P1 via the port C1 on the virtual switch 7.

  Similarly, the virtual NIC V5 on the management OS 4 can perform communication using the physical NIC P3 via the port C5 on the virtual switch 9.

  The physical NICs P1 and P3 are connected to the L2 switch 14, and the clusterware 5 and 6 check whether each other is operating normally through this network.

  In addition, the virtual NIC V2 on the management OS 3, the virtual NIC V3 on the virtual machine 16, and the virtual NIC V4 on the virtual machine 17 communicate with each other using the physical NIC P2 via the ports C2 to C4 on the virtual switch 8. Can be done.

  Similarly, the virtual NIC V6 on the management OS 4 and the virtual NIC V7 on the virtual machine 18 can perform communication using the physical NIC P4 via the ports C6 to C7 on the virtual switch 10.

  The physical NICs P2 and P4 are connected to the L2 switch 13, and this network can communicate with an external network through the external connection 15. Specifically, this network is used when a virtual machine user connects to the virtual machine 16 or 17 or 18 on the virtual machine server 1 or 2 through the external connection 15 from the outside.

  As shown in FIG. 3, the virtual switch control unit 11 includes a monitoring unit 111, a control unit 112, and a data management unit 113. The monitoring unit 111 is connected to the virtual switch 8 through the communication path Lb, and the control unit 112 is A connection with the virtual switch 8 is established by the communication path Le.

  The data management unit 113 has a data management table to be described later.

(Description of the operation of the first embodiment)
Next, the operation of the cluster system 100 according to the present embodiment will be described in detail with reference to the drawings.

  First, referring to FIG. 2, FIG. 2 is a diagram showing a configuration example of a data management table according to the present embodiment.

  As shown in FIG. 2, the ports C1 to C3 on the virtual switch connected to the virtual NIC between the physical NIC P2 and the virtual NIC connected via the virtual switch are the children of P2. It is set to do.

  This is data for determining which port is a child port associated with a failure in a parent port. Based on the data, the control unit 112 invalidates a predetermined port on the virtual switch.

  Note that when a failure occurs in a child port, the clusterware can detect it at that time, so there is no need to determine which port is its parent port.

  FIG. 4 is a flowchart showing the operation of the cluster system 100 according to this embodiment. The operation will be described below with reference to FIG.

  As shown in FIG. 3, the monitoring unit 111 is connected to the virtual switch via the communication path Lb and periodically monitors whether the communication on the communication path La is operating normally (step S401).

  The monitoring unit 11 monitors whether the communication on the communication path La is operating normally by performing a connection test between the physical NIC P2 and the virtual switch 8.

  When an abnormality occurs in the communication path La (step S402 “NO”), the monitoring unit 111 notifies the control unit 112 that an abnormality has occurred in the physical NIC P2 via the communication path Lc (step S403).

  The control unit 112 that has received the notification extracts information on the ports C2 to C4 on the virtual switch 14 that is a child of the physical NIC P2 from the data management table stored in the data management unit 113 via the communication path Ld. (Step S404).

  Next, the control unit 112 invalidates the ports C2 to C4 of the virtual switch 14 via the communication path Le (step S405).

Since the virtual NIC V2 cannot communicate with the port C2 because the port C2 becomes invalid, the clusterware 5 detects that an abnormality has occurred in the communication path Lf (step S1). S406).

  In response to this, the clusterware 5 causes the virtual machines 16 to 17 to fail over to the virtual machine server 2 (step S407).

(Effects of the first embodiment)

  In the present embodiment, since the ports C2 to C4 on the virtual switch are invalidated when an abnormality occurs in the communication path La, the clusterware 5 is notified that an abnormality has occurred in the communication path La. It becomes possible to detect in a pseudo manner. That is, the clusterware 5 can detect a failure of the physical NIC in a pseudo manner.

  In the present embodiment, all the ports C2 to C4 on the virtual switch are invalidated, but only the port C2 connected to the clusterware 5 may be invalidated.

  In response to this detection, the virtual machines 16 to 17 can be automatically failed over, and the continuity of work is increased without requiring intervention by maintenance personnel.

  Note that the above-described problem of the present invention can be solved even with the minimum configuration including the monitoring unit 111 and the control unit 112 in the background art.

  Next, a hardware configuration example of the virtual machine server 1 of the present invention will be described with reference to FIG. FIG. 7 is a block diagram illustrating a hardware configuration example of the virtual machine server 1.

  Referring to FIG. 7, the virtual machine server 1 has a hardware configuration similar to that of a general computer device, and includes a data work area including a memory such as a CPU (Central Processing Unit) 801 and a RAM (Random Access Memory). And a main storage unit 802 used for a temporary data saving area, a communication unit 803 that transmits and receives data via a network, an input / output interface that transmits and receives data by connecting to the input device 805, the output device 806, and the storage device 807 A unit 804 and a system bus 808 for interconnecting the above components. The storage device 807 is realized by, for example, a hard disk device including a non-volatile memory such as a ROM (Read Only Memory), a magnetic disk, and a semiconductor memory.

  The monitoring unit 111, the control unit 112, and the data management unit 113 of the virtual machine server 1 according to the present invention operate by mounting a circuit component that is a hardware component such as an LSI (Large Scale Integration) incorporating a program. As a matter of course, it is realized in software by storing a program providing the function in the storage device 807, loading the program into the main storage unit 802, and executing it by the CPU 801. It is also possible.

  The virtual machine server 2 also has the hardware configuration as described above, and implements each function of the virtual machine server 2 in terms of hardware or software.

  Although the present invention has been described with reference to the preferred embodiments, the present invention is not necessarily limited to the above embodiments, and various modifications can be made within the scope of the technical idea. .

  It should be noted that any combination of the above-described constituent elements and a conversion of the expression of the present invention between a method, an apparatus, a system, a recording medium, a computer program, etc. are also effective as an aspect of the present invention.

  The various components of the present invention do not necessarily have to be independent of each other. A plurality of components are formed as a single member, and a single component is formed of a plurality of members. It may be that a certain component is a part of another component, a part of a certain component overlaps with a part of another component, or the like.

  Moreover, although the several procedure is described in order in the method and computer program of this invention, the order of the description does not limit the order which performs a several procedure. For this reason, when implementing the method and computer program of this invention, the order of the several procedure can be changed in the range which does not interfere in content.

  The plurality of procedures of the method and the computer program of the present invention are not limited to being executed at different timings. For this reason, another procedure may occur during the execution of a certain procedure, or some or all of the execution timing of a certain procedure and the execution timing of another procedure may overlap.

  Further, a part or all of the above-described embodiment can be described as in the following supplementary notes, but is not limited thereto.

(Appendix 1)
A cluster system including a virtual machine server capable of operating a virtual machine,
The virtual machine server is
One or more physical NICs;
One or more virtual switches connected to the physical NIC;
Monitoring means for detecting a failure of the physical NIC;
Control means for invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Clusterware connected to each of the virtual switches and performing failover of virtual machines and monitoring the status of the virtual switches,
The clusterware is
A cluster system, wherein a failure of the virtual switch due to port invalidation by the control means is detected and a virtual machine is failed over.

(Appendix 2)
One or more virtual NICs connected to the port of the virtual switch and assigned to the clusterware or the virtual machine;
The clusterware is
The cluster system according to appendix 1, wherein a status of a communication path between the virtual NIC assigned to itself and the virtual switch is monitored.

(Appendix 3)
The control means includes
The cluster system according to appendix 2, wherein a port connected to the virtual NIC allocated to the clusterware is invalidated among the ports of the virtual switch connected to the physical NIC that detects the failure.

(Appendix 4)
The control means includes
The cluster system according to appendix 1 or appendix 2, wherein all ports of the virtual switch connected to the physical NIC that detects the failure are invalidated.

(Appendix 5)
The virtual machine server is
A data management table for managing the physical NIC in association with the port of the virtual switch connected to the physical NIC;
The control means includes
The cluster system according to any one of appendix 1 to appendix 4, wherein the port to be invalidated is determined with reference to the data management table.

(Appendix 6)
A virtual machine server that can operate the virtual machines of the cluster system,
One or more physical NICs;
One or more virtual switches connected to the physical NIC;
Monitoring means for detecting a failure of the physical NIC;
Control means for invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Clusterware connected to each of the virtual switches and performing failover of virtual machines and monitoring the status of the virtual switches,
The clusterware is
A virtual machine server that detects a failure of the virtual switch due to port invalidation by the control means and performs failover of the virtual machine.

(Appendix 7)
One or more virtual NICs connected to the port of the virtual switch and assigned to the clusterware or the virtual machine;
The clusterware is
The virtual machine server according to appendix 6, wherein the status of a communication path between the virtual NIC allocated to itself and the virtual switch is monitored.

(Appendix 8)
The control means includes
The virtual machine server according to appendix 7, wherein a port connected to the virtual NIC allocated to the clusterware is invalidated among the ports of the virtual switch connected to the physical NIC that detects the failure. .

(Appendix 9)
The control means includes
The virtual machine server according to appendix 6 or appendix 7, wherein all ports of the virtual switch connected to the physical NIC that detects the failure are invalidated.

(Appendix 10)
A data management table for managing the physical NIC in association with the port of the virtual switch connected to the physical NIC;
The control means includes
The virtual machine server according to any one of appendix 6 to appendix 9, wherein the port to be invalidated is determined with reference to the data management table.

(Appendix 11)
A virtual machine failover method in a cluster system including a virtual machine server capable of operating a virtual machine,
The virtual machine server
Detecting a failure of the physical NIC;
Invalidating one or more ports of a virtual switch connected to the physical NIC that detected the failure;
A step of detecting a failure of the virtual switch caused by port invalidation and performing failover of the virtual machine by clusterware connected to each of the virtual switches and performing failover of the virtual machine and monitoring of the state of the virtual switch. And a virtual machine failover method.

(Appendix 12)
The clusterware is
The virtual machine connected to the port of the virtual switch and monitoring a state of a communication path between the virtual NIC assigned to the clusterware or the virtual machine and the virtual switch. Failover method.

(Appendix 13)
In the port invalidation step,
13. The virtual machine according to appendix 12, wherein a port connected to the virtual NIC assigned to the clusterware is invalidated among the ports of the virtual switch connected to the physical NIC that detects the failure. Failover method.

(Appendix 14)
In the port invalidation step,
13. The virtual machine failover method according to appendix 11 or appendix 12, wherein all ports of the virtual switch connected to the physical NIC that detects the failure are invalidated.

(Appendix 15)
In the port invalidation step,
Any one of appendix 11 to appendix 14, wherein a port to be invalidated is determined by referring to a data management table that manages the physical NIC and the port of the virtual switch connected to the physical NIC in association with each other 2. The virtual machine failover method according to item 1.

(Appendix 16)
A virtual machine failover program in a cluster system including a virtual machine server capable of operating a virtual machine,
On the virtual machine server
A process of detecting a failure of the physical NIC;
A process of invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Processing for detecting a failure of the virtual switch due to port invalidation and performing failover of the virtual machine by clusterware connected to each of the virtual switches and performing failover of the virtual machine and monitoring of the state of the virtual switch And a virtual machine failover program.

(Appendix 17)
The clusterware is
The virtual machine connected to the port of the virtual switch, and monitors a state of a communication path between the virtual NIC assigned to the clusterware or the virtual machine and the virtual switch. Failover program.

(Appendix 18)
In the port invalidation process,
18. The virtual machine according to appendix 17, wherein a port connected to the virtual NIC assigned to the clusterware is invalidated among the ports of the virtual switch connected to the physical NIC that has detected a failure. Failover program.

(Appendix 19)
In the port invalidation process,
18. The virtual machine failover program according to appendix 16 or appendix 17, wherein all ports of the virtual switch connected to the physical NIC that detects the failure are invalidated.
(Appendix 20)
In the port invalidation process,
Any one of appendix 16 to appendix 19, wherein a port to be invalidated is determined by referring to a data management table for managing the physical NIC in association with the port of the virtual switch connected to the physical NIC The virtual machine failover program according to item 1.

  INDUSTRIAL APPLICABILITY According to the present invention, it can be applied to uses such as detection of a physical NIC failure in a cluster environment configured with a plurality of virtual machine servers. Further, the present invention can be applied to a usage such as operation by virtual machine when a physical NIC failure occurs in a cluster environment configured by a plurality of virtual machine servers.

100: Cluster system 1, 2: Virtual machine server 3, 4: OS for management
5, 6: Clusterware 7, 8, 9, 10: Virtual switch 11, 12: Virtual switch control unit 13, 14: L2 switch 15: External connection P1-P4: Physical NIC
V1 to V6: Virtual NIC
C1 to C7: Ports on the virtual switch 801: CPU
802: Main storage unit 803: Communication unit 804: Input / output interface unit 805: Input device 806: Output device 807: Storage device 808: System bus

Claims (10)

A cluster system including a virtual machine server capable of operating a virtual machine,
The virtual machine server is
One or more physical NICs;
One or more virtual switches connected to the physical NIC;
Monitoring means for detecting a failure of the physical NIC;
Control means for invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Clusterware connected to each of the virtual switches and performing failover of virtual machines and monitoring the status of the virtual switches,
The clusterware is
A cluster system, wherein a failure of the virtual switch due to port invalidation by the control means is detected and a virtual machine is failed over. One or more virtual NICs connected to the port of the virtual switch and assigned to the clusterware or the virtual machine;
The clusterware is
The cluster system according to claim 1, wherein a status of a communication path between the virtual NIC and the virtual switch allocated to itself is monitored. The control means includes
3. The cluster system according to claim 2, wherein a port connected to the virtual NIC allocated to the clusterware is invalidated among the ports of the virtual switch connected to the physical NIC that has detected a failure. . The control means includes
3. The cluster system according to claim 1, wherein all the ports of the virtual switch connected to the physical NIC that detects the failure are invalidated. The virtual machine server is
A data management table for managing the physical NIC in association with the port of the virtual switch connected to the physical NIC;
The control means includes
The cluster system according to any one of claims 1 to 4, wherein a port to be invalidated is determined by referring to the data management table. A virtual machine server that can operate the virtual machines of the cluster system,
One or more physical NICs;
One or more virtual switches connected to the physical NIC;
Monitoring means for detecting a failure of the physical NIC;
Control means for invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Clusterware connected to each of the virtual switches and performing failover of virtual machines and monitoring the status of the virtual switches,
The clusterware is
A virtual machine server that detects a failure of the virtual switch due to port invalidation by the control means and performs failover of the virtual machine. One or more virtual NICs connected to the port of the virtual switch and assigned to the clusterware or the virtual machine;
The clusterware is
The virtual machine server according to claim 6, wherein a status of a communication path between the virtual NIC assigned to itself and the virtual switch is monitored. A virtual machine failover method in a cluster system including a virtual machine server capable of operating a virtual machine,
The virtual machine server
Detecting a failure of the physical NIC;
Invalidating one or more ports of a virtual switch connected to the physical NIC that detected the failure;
A step of detecting a failure of the virtual switch caused by port invalidation and performing failover of the virtual machine by clusterware connected to each of the virtual switches and performing failover of the virtual machine and monitoring of the state of the virtual switch. And a virtual machine failover method. The clusterware is
9. The virtual machine according to claim 8, wherein the virtual machine is connected to the port of the virtual switch and monitors a state of a communication path between the virtual NIC assigned to the clusterware or the virtual machine and the virtual switch. Failover method. A virtual machine failover program in a cluster system including a virtual machine server capable of operating a virtual machine,
On the virtual machine server
A process of detecting a failure of the physical NIC;
A process of invalidating one or more ports of the virtual switch connected to the physical NIC that has detected a failure;
Processing for detecting a failure of the virtual switch due to port invalidation and performing failover of the virtual machine by clusterware connected to each of the virtual switches and performing failover of the virtual machine and monitoring of the state of the virtual switch And a virtual machine failover program.

Images