Network management for automatic recovery in the event of a failure

Patent metadata

Field	Value
Publication number	US-12147298-B2
Application number	US-202217910458-A
Country	US
Kind code	B2
Filing date	May 23, 2022
Priority date	May 23, 2022
Publication date	Nov 19, 2024
Grant date	Nov 19, 2024

Abstract

A network management device executes acquisition processing, determination processing, and implementation processing. The acquisition processing is for acquiring notification information that is issued in response to a failure occurring in a physical server or a virtual machine constructed in the physical server in a network virtual environment. The determination processing is for determining, in a case where the notification information is acquired, whether or not healing processing for recreating the virtual machine in which the failure has occurred needs to be implemented, based on information related to the failure. The implementation processing is for automatically implementing the healing processing in a case where it is determined that the healing processing needs to be implemented.

First claim

The invention claimed is:

1. A network management device comprising:
one or more processors,
at least one of the one or more processors executing:
acquisition processing of acquiring notification information that is issued in response to a failure occurring in a physical server or a virtual machine constructed in the physical server in a network virtual environment;
determination processing of determining, in a case where the notification information is acquired, whether or not healing processing of recreating the virtual machine in which the failure has occurred needs to be implemented, based on information related to the failure, wherein in the determination processing,
a running state of t e virtual machine in which the failure has occurred is monitored in a case where it is determined that the healing processing does not need to be implemented, and
it will be re-determined that the healing processing needs to be implemented in a case where the virtual machine does not run normally even after a predetermined period of time has passed since the failure occurred; and

implementation processing of automatically implementing the healing processing in a case where it is determined that the healing processing needs to be implemented.

2. The network management device according to claim 1 ,
wherein in the determination processing, state information regarding the physical server on which the virtual machine in which the failure has occurred is constructed is acquired as the information related to the failure, and whether or not the healing processing needs to be implemented is determined based on the state information.

3. The network management device according to claim 2 ,
wherein the state information is system event log information.

4. The network management device according to claim 2 ,
wherein in the determination processing, it is determined that the healing processing does not need to be implemented in a case where it is determined based on the state information that the physical server has rebooted after the failure occurred.

5. The network management device according to claim 1 ,
wherein in the determination processing, it is determined that the healing processing needs to be implemented in a case where the failure is a physical failure, and it is determined that the healing processing does not need to be implemented in a case where the failure is a logical failure that is resolvable by a reboot.

6. The network management device according to claim 1 ,
wherein in the determination processing, it is determined that the healing processing does not need to be implemented in a case where the failure is a failure that has occurred due to communication timing.

7. The network management device according to claim 1 ,
wherein in the determination processing, it is determined that the healing processing does not need to be implemented in a case where the failure is a kernel panic.

8. The network management device according to claim 1 ,
wherein in the determination processing, it is determined that the healing processing does not need to be implemented in a case where the failure is a bus error between a field programmable gate array (FPGA) and a host.

9. A network management method comprising:
acquiring notification information that is issued in response to a failure occurring in a physical server or a virtual machine constructed in the physical server in a network virtual environment;
determining, in a case where the notification information is acquired, whether or not healing processing of recreating the virtual machine in which the failure has occurred needs to be implemented, based on information related to the failure, wherein in the determining,
a running state of the virtual machine in which the failure has occurred is monitored in a case where it is determined that the healing processing does not need to be implemented, and
it will be re-determined that the healing processing needs to be implemented in a case where the virtual ma chine does not run normal even after a predetermined period of time has assed since the failure occurred; and

automatically implementing the healing processing in a case where it is determined that the healing processing needs to be implemented.

10. A network management system comprising:
one or more memories configured to store computer program codes; and
one or more processors configured to operate as instructed by the computer program code the computer program code including:
acquisition code configured to cause the one or more processors to perform acquisition processing of acquiring notification information that is issued in response to a failure occurring in a physical server or a virtual machine constructed in the physical server in a network virtual environment;
determination code configured to cause the one or more processors to perform determination processing of determining, in a case where the notification information is acquired, whether or not healing processing of recreating the virtual machine in which the failure has occurred needs to be implemented, based on information related to the failure, wherein in the determination processing,
a running state of the virtual machine in which the failure has occurred is monitored in a case where it is determined that the healing processing does not need to be implemented, and
it will be re-determined that the healing processing needs to be implemented in a case where the virtual machine does not run normally even after a predetermined period of time has passed since the failure occurred; and
implementation code configured to cause the one or more processors to perform implementation processing of automatically implementing the healing processing in a case where it is determined that the healing processing needs to be implemented.

Assignees

• Rakuten Mobile Inc

Inventors

• Kosugi Masaaki
• Okada Jun
• URASAWA Go

Classifications

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F11/1415

  at system level · CPC title

• G06F11/0712

  in a virtual computing platform, e.g. logically partitioned systems · CPC title

• G06F9/45558 Primary

  Hypervisor-specific management and integration aspects · CPC title

• G06F11/0709

  in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title