JP7708461B1 - SERVER, PROCESSING SYSTEM, PROCESSING METHOD, AND PROGRAM - Google Patents

Abstract

To provide a server capable of shortening the time until alive-or-dead monitoring begins even if some alive-or-dead monitoring frames are lost.
[Solution] In health monitoring, the server is provided with a control mechanism that transmits a second health monitoring frame, which is a health monitoring frame, to a server other than the server itself before receiving the first of a plurality of first health monitoring frames, which are health monitoring frames transmitted from the server other than the server itself, and determines whether the network is down or not based on the plurality of first health monitoring frames.
[Selection] Figure 13

Description

The present disclosure relates to a server, a processing system, a processing method, and a program.

Systems in which servers communicate with each other are used in a variety of fields. Patent Document 1 discloses a related technology for determining whether an abnormality in the operation of a virtualization system is due to an abnormality in an application or virtual machine, or due to an abnormality on the network side.

JP 2014-007609 A

In the system related to Patent Document 1, alive monitoring does not start until a User Datagram Protocol (UDP) packet for alive monitoring is received, and if the UDP packet is lost, it takes time for alive monitoring to start. Therefore, there is a demand for technology that can shorten the time until alive monitoring starts even if some of the alive monitoring frames are lost.

Each aspect of the present disclosure has the objective of providing a server, processing system, processing method, and program that can solve the above problems.

In order to achieve the above-mentioned object, according to one aspect of the present disclosure, in a health/death monitoring, a server is provided with a control mechanism that transmits a second health/death monitoring frame to another server before receiving the first of a plurality of first health/death monitoring frames, which are health/death monitoring frames transmitted from a server other than the server itself, and determines whether or not the network is down based on the plurality of first health/death monitoring frames, and the other server transmits a connection frame to the server itself before receiving the second health/death monitoring frame from the server itself, and the control mechanism determines whether or not the network is down based on the second health/death monitoring frame and the response frame transmitted from the other server .

To achieve the above object, according to another aspect of the present disclosure, a processing system includes the above server and the other server .

In order to achieve the above object, according to another aspect of the present disclosure, a processing method includes, in health monitoring, sending a second health monitoring frame, which is a health monitoring frame, to a server other than the own server before receiving a first of a plurality of first health monitoring frames, which are health monitoring frames transmitted from the other server, determining whether or not the network is down based on the plurality of first health monitoring frames, and, if the other server sends a connection frame to the own server before receiving the second health monitoring frame from the own server, determining whether or not the network is down based on the second health monitoring frame and the response frame sent from the other server .

In order to achieve the above object, according to another aspect of the present disclosure, a program causes a computer to perform the following operations in health/death monitoring: before receiving a first of a plurality of first health/death monitoring frames, which are health/death monitoring frames transmitted from a server other than the own server, send a second health/death monitoring frame to the other server; determine whether or not the network is down based on the plurality of first health/death monitoring frames; and, if the other server sends a connection frame to the own server before receiving the second health/death monitoring frame from the own server, determine whether or not the network is down based on the second health/death monitoring frame and the response frame sent from the other server .

According to each aspect of the present disclosure, even if some of the alive monitoring frames are lost, the time until alive monitoring begins can be shortened.

FIG. 1 illustrates an example of a configuration of a processing system according to some embodiments of the present disclosure. FIG. 13 is a diagram showing an example of functions of a control mechanism according to some embodiments of the present disclosure. FIG. 2 is a diagram illustrating an example of a processing flow of a processing system according to some embodiments of the present disclosure. FIG. 2 is a diagram for explaining a first process performed by a processing system according to some embodiments of the present disclosure. 11A to 11C are diagrams for explaining second and third processes performed by a processing system according to some embodiments of the present disclosure. FIG. 1 is a first diagram for explaining transmission of a health check frame according to some embodiments of the present disclosure. FIG. 2 is a second diagram for explaining transmission of health check frames according to some embodiments of the present disclosure. FIG. 11 is a diagram for explaining a fourth process performed by a processing system according to some embodiments of the present disclosure. FIG. 11 is a diagram for explaining a fifth process performed by a processing system according to some embodiments of the present disclosure. FIG. 13 is a diagram for explaining a sixth process performed by a processing system according to some embodiments of the present disclosure. FIG. 13 is a diagram illustrating an example of a state of a determination made by a processing system according to some embodiments of the present disclosure. FIG. 13 is a diagram illustrating an example of a function suspension performed by a server in accordance with some embodiments of the present disclosure. FIG. 4 is a diagram illustrating an example of a processing flow of a server according to some embodiments of the present disclosure. FIG. 4 is a diagram illustrating an example of a processing flow of a server according to some embodiments of the present disclosure. FIG. 1 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment.

Hereinafter, the embodiments will be described in detail with reference to the drawings.
<Embodiment>
A processing system 1 according to an embodiment of the present disclosure will be described with reference to the drawings. The processing system 1 is a system that monitors whether a network between server devices 10a and 10b, which will be described later, is down and quickly detects when it is down. This makes it possible to suppress the impact on communication by users using the server devices 10a and 10b. In addition, the processing system 1 makes it possible for a user to not use or stop monitoring whether the network is down at their discretion.

(Configuration of the processing system of the present disclosure)
Fig. 1 is a diagram illustrating an example of a configuration of a processing system 1 according to some embodiments of the present disclosure. As shown in Fig. 1, the processing system 1 according to one embodiment of the present disclosure includes servers 10a and 10b, a communication device 20, and cables 30a and 30b. As shown in Fig. 1, the server 10a is connected to the communication device 20 via the cable 30a. As shown in Fig. 1, the server 10b is connected to the communication device 20 via the cable 30b. The servers 10a and 10b may be collectively referred to as servers 10. The cables 30a and 30b may be collectively referred to as cables 30. The cable 30 is, for example, a LAN (Local Area Network) cable.

Each of the servers 10 includes a network device 101. As shown in FIG. 1, the network device 101 includes a NIC (Network Interface Card) 1011, a NIC driver 1012, and a control mechanism 1013.

The NIC 1011 is a card-type expansion device for connecting the server 10 including the NIC 1011 to a communication network (e.g., a local area network).

The NIC driver 1012 is a program that mediates communication between the NIC 1011 and the OS (Operating System) in the network device 101 that includes the NIC driver 1012 itself. The NIC driver 1012 runs within the network device 101 that includes the NIC driver 1012 itself.

The control mechanism 1013 is firmware for the network device 101 provided in each server 10. The control mechanism 1013 runs a health monitoring program in each network device 101. FIG. 2 is a diagram showing an example of functions possessed by the control mechanism 1013 according to some embodiments of the present disclosure. As shown in FIG. 2, the control mechanism 1013 has a frame transmission/reception function 1013a, a counter function 1013b, a timer function 1013c, and a health monitoring flag setting function 1013d.

The frame transmission/reception function 1013a is a function for transmitting and receiving alive monitoring frames, which are frames for alive monitoring. The alive monitoring frames include UDP (User Datagram Protocol) packets for alive monitoring. The counter function 1013b is a function for counting the reception of alive monitoring frames, and for incrementing and checking the count value. The timer function 1013c is a function for measuring the passage of time. The alive monitoring flag setting function 1013d is a function for setting the enable/disable of alive monitoring. Alive monitoring refers to continuously checking the operating status of devices such as servers and the software running on those devices.

The control mechanism 1013 uses the frame transmission/reception function 1013a to send and receive alive monitoring frames using a socket API (Application Programming Interface) 1013a5. The socket API 1013a5 is a set of socket calls that enable various communication functions to be executed between application programs. For example, the socket API 1013a5 includes socket calls for setting up and establishing connections with other users (processes) on the network, and socket calls for sending and receiving data between other users (processes).

The control mechanism 1013 also uses a counter function 1013b to count up and check the count value at regular intervals T. The control mechanism 1013 uses a timer function 1013c to repeatedly measure, for example, the passage of a certain period of time T. The control mechanism 1013 uses a health check flag setting function 1013d to perform settings for controlling whether health checks are enabled or disabled, as set by the OS or a higher-level application.

The communication device 20 is, for example, a router connected to a communication network, or a hub connected to a router.

Cable 30a connects server 10a and communication device 20. Through this connection, server 10a is connected to the communication network. Cable 30b connects server 10b and communication device 20. Through this connection, server 10b is connected to the communication network. In this way, by connecting server 10a and communication device 20 and server 10b and communication device 20, server 10a and server 10b are able to communicate via the communication network.

Note that the above-described processing performed by the processing system 1 according to an embodiment of the present disclosure is merely an example, and is not limited to the above-described processing. For example, the processing system 1 may perform the processing described below.

(Processing performed by the processing system of the present disclosure)
Fig. 3 is a diagram showing an example of a processing flow of the processing system 1 according to some embodiments of the present disclosure. Here, a process performed by the processing system 1 shown in Fig. 3 will be described. Note that here, a process of alive monitoring when communication is performed between the control mechanism 1013 of the server 10a and the control mechanism 1013 of the server 10b will be described.

In the network device 101 of the server 10, the control mechanism 1013 runs a health monitoring program. FIG. 4 is a diagram for explaining a first process performed by the processing system 1 according to some embodiments of the present disclosure. The first process is, for example, the process of step S1 performed by the processing system 1. The control mechanism 1013 of the server 10 enables the health monitoring flag setting function 1013d, and establishes a connection with the control mechanism 1013 of the other server 10 by a handshake with the network device 101 enabling the health monitoring flag using the health monitoring flag setting function 1013d (step S1).

Specifically, for example, in the processing system 1, the control mechanism 1013 of the server 10a activates the alive monitoring flag. Then, the control mechanism 1013 of the server 10a transmits a connection frame to the server 10b. The connection frame is a frame including a UDP packet for establishing a connection. The data portion of the UDP packet is in a data format that allows the control mechanism to recognize it as a connection request. This transmission is performed before the control mechanism 1013 of the server 10b receives the alive monitoring frame from the server 10a. The control mechanism 1013 of the server 10b receives the connection frame from the server 10a. When the control mechanism 1013 of the server 10b receives the connection frame, it transmits a response frame to the server 10a in response to the reception. The control mechanism 1013 of the server 10a receives the response frame from the server 10b. When the control mechanism 1013 of the server 10a receives the response frame from the server 10b, it transitions to a state in which a connection is established in response to the reception. Furthermore, in the processing system 1, the control mechanism 1013 of the server 10b enables the alive/dead monitoring flag. Then, the control mechanism 1013 of the server 10b transmits an alive/dead monitoring frame to the server 10a. This transmission is performed before the control mechanism 1013 of the server 10a receives the alive/dead monitoring frame from the server 10b. The control mechanism 1013 of the server 10a receives the alive/dead monitoring frame from the server 10b. When the control mechanism 1013 of the server 10a receives the received alive/dead monitoring frame, it transmits a response frame to the server 10b in response to the reception. The control mechanism 1013 of the server 10b receives the response frame from the server 10a. When the control mechanism 1013 of the server 10b receives the response frame from the server 10a, it transitions to a state in which a connection is established in response to the reception.

FIG. 5 is a diagram for explaining the second process and the third process performed by the processing system 1 according to some embodiments of the present disclosure. The second process is, for example, the process of step S2 performed by the processing system 1. The third process is, for example, the process of step S3 performed by the processing system 1. The control mechanism 1013 of the server 10 enables the counter function 1013b and the timer function 1013c (step S2). Then, the control mechanism 1013 of the server 10 starts a transmission check and a reception check of the UDP alive/dead monitoring frame in the transmission and reception of the alive/dead monitoring frame by the frame transmission/reception function 1013a (step S3). For example, the transmission check is performed by checking whether the transmission process of the frame is completed normally. Also, for example, the reception check is performed by reading the data portion of the received frame and checking whether the alive/dead monitoring frame has been received. The transmission of the alive/dead monitoring frame is performed periodically at a constant interval T using the timer function 1013c.

Note that the transmission of the alive/dead monitoring frame does not have to be performed periodically at a fixed interval T. FIG. 6 is a first diagram for explaining the transmission of the alive/dead monitoring frame according to some embodiments of the present disclosure. FIG. 7 is a second diagram for explaining the transmission of the alive/dead monitoring frame according to some embodiments of the present disclosure. For example, the fixed interval T may be calculated from the arrival time t of the alive/dead monitoring frame when establishing a connection (i.e., at the time of handshake) as shown in FIG. 6. The fixed interval T is set to, for example, t×1.2 times the arrival time t, assuming a value with a margin. For example, the transmission interval of the alive/dead monitoring frame from the second time onwards may be changed based on statistical information on the transmission interval of the alive/dead monitoring frame and the line usage rate as shown in FIG. 7. Specifically, as shown in (a) and (b) of FIG. 7, statistical information on the transmission interval of the alive/dead monitoring frame and the line usage rate are obtained using a well-known technology. As shown in FIG. 7B, when the line usage rate exceeds a certain value, the transmission interval of the alive/dead monitoring frame may be lengthened to reduce the impact on traffic, and when the line usage rate is below a certain value, the transmission interval of the alive/dead monitoring frame may be shortened to shorten the time to detect a network down. In the specific example shown in FIG. 7B, when the line usage rate is 80% or more, the transmission interval of the alive/dead monitoring frame is set to twice the transmission interval of the previous alive/dead monitoring frame. When the line usage rate is 40% or more and less than 80%, the transmission interval of the alive/dead monitoring frame is set to the transmission interval of the previous alive/dead monitoring frame. When the line usage rate is 0% or more and less than 40%, the transmission interval of the alive/dead monitoring frame is set to half the transmission interval of the previous alive/dead monitoring frame.

It is also possible to set an upper limit on the interval for sending alive check frames. Setting an upper limit on the interval for sending alive check frames has the effect of preventing the time it takes to discover a network downtime from becoming excessively long.

Figure 8 is a diagram for explaining the fourth process performed by the processing system 1 according to some embodiments of the present disclosure. The fourth process is, for example, the process of step S4 performed by the processing system 1. The control mechanism 1013 of the server 10 uses the counter function 1013b to count up and check the count value at regular intervals T (step S4).

Figure 9 is a diagram for explaining the fifth process performed by the processing system 1 according to some embodiments of the present disclosure. The fifth process is, for example, the process of step S5 performed by the processing system 1. When the control mechanism 1013 of the server 10 receives the alive monitoring frame, it resets the counter function 1013b (step S5).

Figure 10 is a diagram for explaining the sixth process performed by the processing system 1 according to some embodiments of the present disclosure. The sixth process is, for example, the process of step S6 performed by the processing system 1. If the count value exceeds a certain value, the control mechanism 1013 of the server 10 determines that the network is down (step S6).

Note that even if some of the alive/dead monitoring frames are lost, the control mechanism 1013 of the server 10 determines that the network is not down if the next alive/dead monitoring frame is received before the count value exceeds a certain value. FIG. 11 is a diagram showing an example of a state of determination made by the processing system 1 according to some embodiments of the present disclosure. Specifically, it is a diagram showing a state in which the processing system 1 determines that the network is not down even if some of the alive/dead monitoring frames are lost. As shown in FIG. 11, in the processing system 1, the control mechanism 1013 of the server 10 receives the next alive/dead monitoring frame before the count value exceeds a certain value. In this case, the control mechanism 1013 of the server 10 determines that the network is not down even if some of the alive/dead monitoring frames are lost.

In addition, when an enabled alive monitoring flag is cleared or the network device 101 transitions to a disconnected state by a handshake, the server 10 stops the frame transmission/reception function 1013a, counter function 1013b, and timer function 1013c that perform transmission and reception checks of alive monitoring frames. FIG. 12 is a diagram showing an example of the suspension of functions performed by the server 10 according to some embodiments of the present disclosure. In the example shown in FIG. 12, when the network device 101 transitions to a disconnected state by a handshake, the server 10 stops the frame transmission/reception function 1013a, counter function 1013b, and timer function 1013c.

(advantage)
The processing system 1 according to an embodiment of the present disclosure has been described above. In the processing system 1, the server 10 includes a control mechanism 1013 that, in alive/dead monitoring, transmits a second alive/dead monitoring frame, which is an alive/dead monitoring frame, to another server 10 before receiving a first first alive/dead monitoring frame among a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from the other server 10, and determines whether the network is down or not based on the plurality of first alive/dead monitoring frames.

The invention described in Patent Document 1 transmits a live/death monitoring UDP packet in response to a received live/death monitoring UDP packet. In other words, with the invention described in Patent Document 1, live/death monitoring does not start until the live/death monitoring UDP packet is received, and in particular, if the live/death monitoring UDP packet is lost, it takes time before live/death monitoring starts. In contrast to the invention described in Patent Document 1, the server 10 can shorten the time until live/death monitoring starts even if some of the live/death monitoring frames are lost.

In addition, even if some of the multiple first alive/dead monitoring frames are lost, the control mechanism 1013 determines that the network is not down if the next first alive/dead monitoring frame is received before the count value of the received first alive/dead monitoring frame among the multiple first alive/dead monitoring frames exceeds a certain value.

The invention described in Patent Document 1 compares the number of sent UDP packets with the number of returned UDP packets, and if the two numbers are the same, it is determined that there is no network failure. In the invention described in Patent Document 1, UDP is a connectionless protocol, and the invention described in Patent Document 1 may erroneously diagnose a network failure if a return UDP packet cannot be received due to a momentary network interruption or the like. In contrast to the invention described in Patent Document 1, the control mechanism 1013 in the server 10 can determine that the network is not down and receive new alive/dead monitoring frames even if some of the alive/dead monitoring frames are lost. As a result, the server 10 can reduce the possibility of diagnosing that the network is down even if some of the alive/dead monitoring frames are lost due to a momentary network interruption or the like.

The control mechanism 1013 may limit the number of packets in the alive/dead monitoring frame to a predetermined number based on the load during alive/dead monitoring. For example, by controlling the transmission (start/stop/transmission interval) of the alive/dead monitoring frame according to the state (i.e., load) of the network device 101 included in the server 10, appropriate traffic can be achieved and an increase in traffic can be suppressed. On the other hand, the invention described in Patent Document 1 limits the number of transmitted UDP packets to a predetermined number, but does not set the predetermined number to appropriate traffic according to the load. The alive/dead monitoring frame includes UDP packets. Therefore, when the number of alive/dead monitoring frames is considered to be synonymous with the number of UDP packets, the limit on the number of alive/dead monitoring frames is considered to be the limit on the number of packets.

Also, by providing the server 10 with the control mechanism 1013, the servers 10 can monitor each other's status. In contrast, the invention in question (for example, the invention described in the patent document JP 2007-312091 A) uses a protocol in which packets are sent and received between routers, and it is not possible to monitor the status between servers.

In another embodiment of the present disclosure, the processing system 1 may include three or more servers 10. In the processing system 1, each server 10 may communicate with two or more servers 10 other than the server 10 itself in the same manner as the server 10 in one embodiment of the present disclosure.

In another embodiment of the present disclosure, the processing system 1 may notify a higher-level application or an OS (operating system) via the control mechanism 1013 when the network goes down.

In another embodiment of the present disclosure, the network device 101 is not limited to being provided in the server 10, but may be a network device that operates independently, such as a router. And, the network device may have a control mechanism 1013.

FIG. 13 is a diagram illustrating an example of a processing flow of the server 300 according to some embodiments of the present disclosure. Next, the processing of the server 300 according to some embodiments of the present disclosure will be described with reference to FIG. 13.

The server 300 includes a control mechanism 301. In the alive/dead monitoring, the control mechanism 301 transmits a second alive/dead monitoring frame, which is an alive/dead monitoring frame, to a server other than the server itself before receiving the first of a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from the server itself, and determines whether the network is down or not based on the plurality of first alive/dead monitoring frames.

The control mechanism 301 can be realized, for example, by using the functions of the control mechanism 1013 illustrated in FIG. 1 and FIG. 2. The server 300 can be realized, for example, by using the functions of the servers 10a and 10b illustrated in FIG. 1.

Next, the processing performed by the server 300 according to some embodiments of the present disclosure will be described. FIG. 14 is a diagram showing an example of a processing flow of the server 300 according to some embodiments of the present disclosure. Here, the processing of the server 300 will be described with reference to FIG. 14.

In server 300, before receiving the first of a plurality of first alive/dead monitoring frames transmitted from a server other than the server itself, the control mechanism 301 transmits a second alive/dead monitoring frame to the other server in alive/dead monitoring, and determines whether the network is down or not based on the plurality of first alive/dead monitoring frames (step S101).

The above describes the server 300 according to some embodiments of the present disclosure. This server 300 can shorten the time until health monitoring begins even if some of the health monitoring frames are lost.

The order of the processes in each embodiment of the present disclosure may be changed as long as appropriate processing is performed.

Although each embodiment of the present disclosure has been described, the above-mentioned processing system 1, server 10, and other control devices may have a computer system inside. The above-mentioned process steps are stored in the form of a program on a computer-readable recording medium, and the above-mentioned processes are performed by the computer reading and executing this program. Specific examples of computers are shown below.

FIG. 15 is a schematic block diagram showing the configuration of a computer according to at least one embodiment. As shown in FIG. 15, the computer 5 includes a CPU (Central Processing Unit) 6, a main memory 7, a storage 8, and an interface 9.

For example, each of the above-mentioned processing system 1, server 10, and other control devices is implemented in a computer 5. The operation of each of the above-mentioned processing units is stored in the storage 8 in the form of a program. The CPU 6 reads the program from the storage 8, expands it in the main memory 7, and executes the above-mentioned processing in accordance with the program. The CPU 6 also secures storage areas in the main memory 7 corresponding to each of the above-mentioned storage units in accordance with the program.

Examples of storage 8 include HDD (Hard Disk Drive), SSD (Solid State Drive), magnetic disk, magneto-optical disk, CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disc Read Only Memory), and semiconductor memory. Storage 8 may be an internal medium directly connected to the bus of computer 5, or an external medium connected to computer 5 via interface 9 or a communication line. In addition, when this program is distributed to computer 5 via a communication line, computer 5 that receives the program may expand the program in main memory 7 and execute the above-mentioned process. In at least one embodiment, storage 8 is a non-transitory tangible storage medium.

The program may also realize some of the functions described above. Furthermore, the program may be a file that can realize the functions described above in combination with a program already recorded in the computer system, a so-called differential file (differential program).

Although several embodiments of the present disclosure have been described, these embodiments are merely examples and do not limit the scope of the disclosure. Various additions, omissions, substitutions, and modifications may be made to these embodiments without departing from the spirit and scope of the disclosure.

In addition, some or all of the above embodiments can be described as follows, but are not limited to the following:

(Appendix 1)
a control mechanism for, in alive/dead monitoring, transmitting a second alive/dead monitoring frame to a server other than the server itself before receiving a first one of a plurality of first alive/dead monitoring frames transmitted from the server itself, and determining whether or not the network is down based on the plurality of first alive/dead monitoring frames;
A server comprising:

(Appendix 2)
The control mechanism includes:
Even if some of the plurality of first alive/dead monitoring frames are lost, if a next first alive/dead monitoring frame is received before a count value of a received first alive/dead monitoring frame among the plurality of first alive/dead monitoring frames exceeds a certain value, the network is determined not to be down.
2. The server according to claim 1.

(Appendix 3)
The control mechanism includes:
limiting the number of packets in the alive-or-dead monitoring frame to a predetermined number based on a load during the alive-or-dead monitoring;
2. The server according to claim 1 or 2.

(Appendix 4)
The other server,
a control mechanism for transmitting the initial first health check frame to the other server before receiving the second health check frame from the server itself, and determining whether or not the network is down based on the second health check frame;
Equipped with
5. The server according to claim 1,

(Appendix 5)
A server according to any one of claims 1 to 4;
A server separate from the server;
A processing system comprising:

(Appendix 6)
In the alive/dead monitoring, before receiving a first alive/dead monitoring frame among a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from a server other than the server itself, a second alive/dead monitoring frame, which is an alive/dead monitoring frame, is transmitted to the other server;
determining whether or not a network is down based on the plurality of first alive-check frames;
A processing method comprising:

(Appendix 7)
On the computer,
In the alive/dead monitoring, before receiving a first alive/dead monitoring frame among a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from a server other than the server itself, a second alive/dead monitoring frame, which is an alive/dead monitoring frame, is transmitted to the other server;
determining whether or not a network is down based on the plurality of first alive-check frames;
A program that executes the following.

1... Processing system 5... Computer 6, 205... CPU
7: Main memory 8: Storage 9: Interface 10, 10a, 10b, 300: Server 20: Communication device 101: Network device 301, 1013: Control mechanism 1011: NIC (Network Interface Card)
1012: NIC driver 1013a: Frame transmission/reception function 1013a5: Socket API
1013b: Counter function 1013c: Timer function 1013d: Alive/dead monitoring flag setting function

Claims (5)

a control mechanism for, in alive/dead monitoring, transmitting a second alive/dead monitoring frame to a server other than the server itself before receiving a first one of a plurality of first alive/dead monitoring frames transmitted from the server itself, and determining whether or not the network is down based on the plurality of first alive/dead monitoring frames;
Equipped with
The other server,
transmitting a connection frame to the server before receiving the second alive-check frame from the server;
The control mechanism includes:
determining whether the network is down or not based on the second alive check frame and a response frame transmitted from the other server;
server. The control mechanism includes:
limiting the number of packets in the second alive check frame to a predetermined number based on a load during the alive check;
The server of claim 1 . A server according to claim 1 or 2 ;
said other server;
A processing system comprising: In the alive/dead monitoring, before receiving a first alive/dead monitoring frame among a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from a server other than the server itself, a second alive/dead monitoring frame, which is an alive/dead monitoring frame, is transmitted to the other server;
determining whether or not a network is down based on the plurality of first alive-check frames;
When the other server transmits a connection frame to the server before receiving the second alive-check frame from the server, determining whether or not the network is down based on the second alive-check frame and a response frame transmitted from the other server;
A processing method comprising: On the computer,
In the alive/dead monitoring, before receiving a first alive/dead monitoring frame among a plurality of first alive/dead monitoring frames, which are alive/dead monitoring frames transmitted from a server other than the server itself, a second alive/dead monitoring frame, which is an alive/dead monitoring frame, is transmitted to the other server;
determining whether or not a network is down based on the plurality of first alive-check frames;
When the other server transmits a connection frame to the server before receiving the second alive-check frame from the server, determining whether or not the network is down based on the second alive-check frame and a response frame transmitted from the other server;
A program that executes the following.