JP2017011567A - Failure notification system, relay device, and relay method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To detect failure information generated on the server side, on the network side.SOLUTION: A relay device that is connected, via a first network, to a monitoring device for monitoring a server and is connected, via a second network, to a terminal device includes: an input processing unit for receiving input of first data including failure information on the server and first network information showing that a transfer destination is in the first network, from the monitoring device via the first network; a conversion unit that, when the first data has been input using the input processing unit, replaces the first network information with second network information showing that a transfer destination is in the second network to convert the first data to second data; and an output processing unit that, according to the second network information included in the second data obtained by the conversion of the conversion unit, outputs the second data to the terminal device via the second network.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a failure notification system, a relay device, and a relay method for notifying a failure.

  There is Patent Document 1 as a background art of this technical field. Patent Document 1 describes that “when a failure occurs in a physical network, a virtual server that constitutes a slice can detect a network failure” (see summary). Attention is also focused on solutions that virtualize network functions. For example, there is a vCPE (Virtualized Customer Premises Equipment) that provides a function provided by a Customer Premises Equipment (CPE) that has been placed in a home in the network of a communication carrier. In this virtualization solution, the network and the service providing server perform independent fault monitoring.

JP 2013-207341 A

  However, the technique described in Patent Document 1 is a technique for notifying a failure on the network side to the virtual server side, and as a failure notification means to the virtual server, forcibly in a virtual switch that connects the network and the virtual server. A link down occurs or a virtual switch is deleted. Therefore, there is a problem that a failure on the virtual server side cannot be notified to the network side. An object of the present invention is to detect failure information generated on the server side on the network side.

  A failure notification system according to one aspect of the invention disclosed in the present application is a monitoring device that monitors a first server, is connected to the monitoring device via a first network, and is connected to a terminal device via a second network A failure notification system, wherein the monitoring device detects failure information of the first server and a transfer destination within the first network when detecting a failure of the first server. A first output processing unit that generates first data including first network information indicating that the first network information is output and outputs the first data to the first network. An input processing unit that receives an input of the first data via a first network, and when the first data is input by the input processing unit, the first network information is transferred. A conversion unit that converts the first data into second data by replacing the second network information indicating that the destination is in the second network, and the second converted by the conversion unit And a second output processing unit that outputs the second data to the terminal device via the second network in accordance with the second network information included in the data.

  According to a typical embodiment of the present invention, failure information generated on the server side can be detected on the network side. Problems, configurations, and effects other than those described above will become apparent from the description of the following embodiments.

1 is an explanatory diagram illustrating a system configuration example of a failure notification system according to Embodiment 1. FIG. It is a block diagram which shows the functional structural example of a function monitoring terminal. It is explanatory drawing which shows the example 1 of memory content of a line table. It is explanatory drawing which shows the example 2 of memory content of a line table. It is explanatory drawing which shows the example of a sequence which a function monitoring terminal notifies the alarm of a server failure to the network side. It is explanatory drawing which shows the example of replacement of a VLAN tag. It is explanatory drawing which shows the 1st setting sequence example. It is explanatory drawing which shows the example of a setting place selection screen which selects the setting place of the monitoring mode shown by step S60 of FIG. It is explanatory drawing which shows the example of the monitoring mode selection screen which selects the monitoring mode shown by step S61 of FIG. It is explanatory drawing which shows the example of an input screen of the value of the setting item shown by step S62 of FIG. It is explanatory drawing which shows the 2nd example of a setting sequence. It is explanatory drawing which shows the example of a login screen displayed on a user apparatus. FIG. 11 is a flowchart illustrating a detailed processing procedure example of monitoring processing based on statistical information, which is an example of the monitoring processing (steps S67 and S109) in FIGS. 6 and 10. FIG. 11 is a flowchart illustrating a detailed processing procedure example of a monitoring process by frame insertion, which is an example of the monitoring process (steps S67 and S109) of FIGS. 6 and 10; FIG. 11 is a flowchart illustrating a detailed processing procedure example of a monitoring process based on communication confirmation, which is an example of the monitoring process (steps S67 and S109) in FIGS. 11 is a flowchart illustrating a detailed processing procedure example of polling monitoring processing by a server manager, which is an example of the monitoring processing (steps S67 and S109) in FIGS. 6 and 10; 11 is a flowchart illustrating a detailed processing procedure example of monitoring processing by notification from a server manager, which is an example of the monitoring processing (steps S67 and S109) in FIGS. 6 and 10; FIG. 10 is an explanatory diagram of a system configuration example of a failure notification system according to a second embodiment.

  Embodiments of the present invention will be specifically described below with reference to the drawings. In addition, when there are a plurality of components of the same type in the reference numerals attached to the components, for example, “terminal devices 12-1 and 12-2” are distinguished using branch numbers. When not distinguished, the branch number is omitted, for example, “terminal device 12”.

<System configuration example>
FIG. 1 is an explanatory diagram of a system configuration example of the failure notification system according to the first embodiment. The failure notification system 1 includes a terminal device 12, a NE (Network Element) device 13, a server base 17, and a controller 19. The terminal device 12 is installed at the edge portion of the network 10 and is connected to the user device 11. The NE device 13 is a relay device that constitutes the network 10.

  Note that the function monitoring terminal 14-1, the NE devices 13-2 and 13-3, the function monitoring terminal 14-2, and the line L1 connecting them are referred to as a network NW1. The terminal device 12-1, the NE devices 13-1, 13-2, the function monitoring terminal 14-1, and the line L2 connecting them are referred to as a network NW2. The terminal device 12-2, the NE devices 13-3 and 13-4, the function monitoring terminal 14-2, and the line L3 connecting them are referred to as a network NW3. Also, the terminal device 12-1, the NE devices 13-1, 13-2, the function monitoring terminal 14-1, the NE devices 13-2, 13-3, the function monitoring terminal 14-2, the NE devices 13-3, 13- 4. A line connecting the terminal device 12-2 is a user line L.

  The server base 17 is a base where the server 16 provides a service. The server base 17 includes a function monitoring terminal 14, a switch 15, and a server 16. The switch 15 connects the function monitoring terminal 14 and the server 16 via a network. That is, the server base 17 is connected by a network via the switch 15. The function monitoring terminal 14 monitors the server 16 and notifies failure information generated in the server 16 to the network 10 side. The server 16 is a computer that implements a specific function such as a Web service or a database. The server 16 may be a physical server or a virtual server.

  The server 16 is managed by a server manager (not shown). The server manager may manage the server 16 from the outside of the server 16 or may manage the server 16 inside the server 16. The server manager monitors the server 16 and acquires failure information indicating at least one of hardware failure of the server 16, temperature abnormality, database failure in the server 16, no response, and processing delay of the server 16.

  The controller 19 performs management control of the terminal device 12, the NE device 13, and the function monitoring terminal 14 constituting the network network 10 and setting of a line in the network network 10. The controller 19 is connected between the terminal device 12-1 and the function monitoring terminal 14-1, between the terminal device 12-2 and the function monitoring terminal 14-2, between the function monitoring terminal 14-1 and the function monitoring terminal 14-. By setting a line connecting the two to the user apparatus 2, communication via the server base 17-1 and the server base 17-2 can be performed between the user apparatus 11-1 and the user apparatus 11-2. .

  Here, the function monitoring terminal 14 will be described more specifically. The function monitoring terminal 14 has a plurality of types of server monitoring modes in order to correspond to the server type of the server 16 installed at the server base 17, the function provided by the server 16, or the required time until failure detection. Prepare.

  Specifically, for example, the server monitoring mode includes a monitoring mode based on statistical information, a monitoring mode based on frame insertion, a monitoring mode based on communication confirmation, a monitoring mode based on server manager polling monitoring, and a monitoring mode based on notification reception from the server manager. There is.

  The monitoring mode based on statistical information is a monitoring mode in which the server 16 is monitored by comparing the number of frames sent to the server base 17 and the number of frames passed through the server base 17.

  In the monitoring mode by frame insertion, the function monitoring terminal 14 transmits a function monitoring frame represented by OAM (Operations Administration Maintenance) or BFD (Bidirectional Forwarding Detection) to the server base 17 to the server base 17. This is a monitoring mode in which the server 16 is monitored by receiving again after passing through.

  The monitoring mode based on the communication confirmation is a monitoring mode in which the function monitoring terminal 14 transmits a function monitoring frame such as Ping to each server 16 and checks the response from the server 16 to monitor the server 16.

  The monitoring mode based on the polling monitoring of the server manager is a monitoring mode in which the server 16 is monitored by periodically acquiring a function monitoring frame including failure information for the server manager that collectively manages the server 16 at the server base 17. It is.

  In the monitoring mode by receiving notification from the server manager, a function monitoring frame including failure information of each server 16 is transmitted from the server manager to the function monitoring terminal 14, and the function monitoring terminal 14 receives the failure information to receive the server. 16 is a monitoring mode for monitoring 16.

<Example of Functional Configuration of Function Monitoring Terminal 14>
FIG. 2 is a block diagram illustrating a functional configuration example of the function monitoring terminal 14. The function monitoring terminal 14 is a relay device having a monitoring function and a relay function. The monitoring function is a function for monitoring the server 16 in the server base 17 to which the server belongs. The relay function is a function for relaying the connectivity monitoring frame from another server base 17 to a network different from the network to which the connectivity monitoring frame is transmitted.

  The function monitoring terminal 14 includes a device management unit 20, an input processing unit 21, a specifying unit 22, a conversion unit 23, a monitoring execution unit 24, a server monitoring management unit 25, an output processing unit 26, and a port 27. Have. Specifically, the device management unit 20 to the output processing unit 26 are realized, for example, by causing a processor (not shown) to execute a program stored in a storage device (not shown). Further, the function of the device management unit 20 to the output processing unit 26 may be realized by hardware by designing with an integrated circuit such as an FPGA (field-programmable gate array).

  The device management unit 20 is a functional block that determines the content set by the controller 19 and controls the function monitoring terminal 14. The device management unit 20 includes a device control unit 200, a routing table 201, and a line table 28. The device control unit 200 receives the setting content from the controller 19 through a control IF (interface). When the setting content from the controller 19 is content related to the line setting, the device control unit 200 updates the line table 28. When the setting content from the controller 19 is content related to the server function monitoring setting, the device control unit 200 updates the communication policy 251 in the server monitoring management unit 25.

  When the setting content from the controller 19 is the setting content related to the routing of the adjacent device, the device control unit 200 stores the routing table 201 indicating the setting content related to the routing of the adjacent device. The setting content related to the routing of the neighboring device is, for example, correspondence information in which the port number of the function monitoring terminal 14 is associated with the MAC (Media Access Control) address of the neighboring device connected to the port having the port number. The routing table 201 is referred to by the output processing unit 26.

  The line table 28 is a table for managing lines in the network 10. The line table 28 is set in advance from the controller 19. Specifically, the line table 28 is stored in a storage device (not shown), for example.

  The input processing unit 21 inputs a frame received at the port 27 and sends the frame to the specifying unit 22.

  The identifying unit 22 identifies the line through which the received frame has been input. Specifically, for example, the specifying unit 22 refers to the line table 28, the port number of the port 27 to which the received frame is input, the MEL (Maintenance Entity Group Level) included in the received frame, the internal An entry that matches a VLAN (Virtual Local Area Network) tag and an external VLAN tag is specified, and the line identifier of the specified entry is acquired. The acquired line identifier is sent to the conversion unit 23.

  For example, in the function monitoring terminal 14-1, the port number of the port 27 to which the received frame from the network NW2 is input is “1”, the MEL level included in the received frame is “3”, and included in the received frame. When the internal VLAN tag is “3” and the external VLAN tag included in the frame is “2”, the specifying unit 22 of the function monitoring terminal 14-1 performs the line table 28-1 of FIG. 3A described later. The entry of the first line is identified, and “1” that is the line identifier of the identified entry is acquired.

  In the function monitoring terminal 14-1, the port number of the port 27 to which the received frame from the network NW1 is input is “3”, the MEL level included in the received frame is “6”, and is included in the received frame. When the internal VLAN tag is “1” and the external VLAN tag included in the frame is “1”, the specifying unit 22 of the function monitoring terminal 14-1 enters the first line entry from the line table 28-2. And “1” which is the line identifier of the specified entry is acquired.

  The conversion unit 23 performs conversion (replacement) of the VLAN tag and MEL included in the frame with reference to the line table 28 using the line identifier specified by the specifying unit 22. The line table 28 is correspondence information that associates network information of two networks that are connected via the function monitoring terminal 14. The network information is, for example, an internal VLAN tag and an external VLAN tag, which will be described later, and is information that defines frame transfer within the network. Details of the conversion of the VLAN tag and MEL will be described later. By converting the VLAN tag and MEL, a frame from one VLAN can be transferred to the other VLAN.

  The monitoring execution unit 24 performs monitoring in the above-described multiple types of server monitoring modes. Specifically, for example, in the monitoring mode based on statistical information, the monitoring execution unit 24 receives from the server 16 the number of user frames (the number of transmission frames) transmitted to the server 16 in the server base 17 to which the user belongs. The number of user frames (the number of received frames) is counted, and the number of frame losses is calculated. The number of frame losses is a value obtained by subtracting the number of received frames from the number of transmitted frames. The monitoring execution unit 24 sends the number of frame losses to the failure determination unit 250 and receives a determination result from the failure determination unit 250.

  In the monitoring mode based on frame insertion, the monitoring execution unit 24 generates a function monitoring frame addressed to the server 16 in the server base 17 to which it belongs and transfers it to the output processing unit 26. The monitoring execution unit 24 sends the function monitoring frame generation time to the failure determination unit 250. Then, the monitoring execution unit 24 waits for the function monitoring frame to be transferred from the server 16. When the function monitoring frame is received from the server 16, the monitoring execution unit 24 sends the reception time to the failure determination unit 250. The monitoring execution unit 24 receives the determination result from the failure determination unit 250.

  Further, in the monitoring mode based on communication confirmation, the monitoring execution unit 24 generates a communication confirmation frame addressed to the server 16 in the server base 17 to which it belongs and transfers it to the output processing unit 26. The monitoring execution unit 24 sends the communication confirmation frame generation time to the failure determination unit 250. Then, the monitoring execution unit 24 waits for a response frame for the communication confirmation frame to be transferred from the server 16. When the response frame is received from the server 16, the monitoring execution unit 24 sends the reception time to the failure determination unit 250. The monitoring execution unit 24 receives the determination result from the failure determination unit 250.

  In the monitoring mode based on the polling monitoring of the server manager, the monitoring execution unit 24 transmits a failure information acquisition request to the server manager as a function monitoring frame. As described above, the failure information is information indicating at least one of hardware failure of the server 16, temperature abnormality, database failure in the server 16, no response, and processing delay of the server 16. The monitoring execution unit 24 sends the function monitoring frame acquisition request time to the failure determination unit 250. Then, the monitoring execution unit 24 waits for a function monitoring frame including failure information to be transferred from the server manager. When the function monitoring frame including the failure information is received from the server 16, the monitoring execution unit 24 sends the reception time to the failure determination unit 250. The monitoring execution unit 24 receives the determination result from the failure determination unit 250.

  In the monitoring mode based on the notification received from the server manager, the monitoring execution unit 24 waits for a function monitoring frame including failure information to be autonomously transferred from the server manager. When a function monitoring frame including failure information is received from the server 16, the monitoring execution unit 24 sends the failure information to the failure determination unit 250. The monitoring execution unit 24 receives the determination result from the failure determination unit 250.

  In any monitoring mode, if the previous state of the server 16 is “normal” and the failure determination unit 250 determines that a failure has occurred in the server 16, the monitoring execution unit 24 uses an internal table (not shown). , The state of the server 16 to be determined is updated from “normal” to “failure”. When the previous state of the server 16 is “failure” and the failure determination unit 250 determines that no failure has occurred in the server 16, the monitoring execution unit 24 determines the server to be determined in the internal table. The status of 16 is updated from “failure” to “normal”. When updated to “failure”, the notification content to the output processing unit 26 is “failure detection”. On the other hand, when updated to “normal”, the notification content to the output processing unit 26 is “failure recovery”. The monitoring execution unit 24 sends a message including the notification content to the output processing unit 26.

  The server monitoring management unit 25 includes a failure determination unit 250 and a communication policy 251. The communication policy 251 is a table that stores various setting values used in the monitoring mode. The communication policy 251 is set in advance from the user device 11 or the controller 19. Specifically, the communication policy 251 is stored in a storage device (not shown), for example.

  The failure determination unit 250 determines whether there is a failure in the server 16 in the server base 17 to which the failure belongs. The failure determination unit 250 manages the status of whether or not the server 16 has a failure. The default state is “normal”. The failure determination unit 250 returns the determination result to the monitoring execution unit 24.

  For example, in the case of the monitoring mode based on statistical information, the failure determination unit 250 compares the number of frame losses with the failure determination reference value in the communication policy 251, and if the number of frame losses is equal to or greater than the failure determination reference value, the server 16 It is determined that a failure has occurred. On the other hand, when the number of frame losses is less than the failure determination reference value, the failure determination unit 250 determines that no failure has occurred in the server 16.

  In the monitoring mode based on frame insertion, the failure determination unit 250 determines whether or not a monitoring frame has been received within a set time after transmitting the monitoring frame, that is, from the generation time of the monitoring frame. Further, the failure determination unit 250 determines whether failure information is added to the monitoring frame when the monitoring frame is received. The failure determination unit 250 refers to the set time stored in the communication policy 251.

  When the monitoring frame is not received within the set time, or when failure information is added to the monitoring frame received within the set time, the failure determination unit 250 determines that a failure has occurred in the server 16. judge. On the other hand, when the monitoring frame is received within the set time and no failure information is given to the received monitoring frame, the failure determination unit 250 determines that no failure has occurred in the server 16.

  In the monitoring mode based on communication confirmation, the failure determination unit 250 determines whether a function monitoring frame has been received from the server 16 within a set time. The failure determination unit 250 refers to the set time stored in the communication policy 251. The starting time of the set time is the generation time of the function monitoring frame in the monitoring execution unit 24. When the reception time sent from the monitoring execution unit 24 exceeds the set time, the failure determination unit 250 determines that a failure has occurred in the server 16. On the other hand, when it is within the set time, the failure determination unit 250 determines that no failure has occurred in the server 16.

  In the monitoring mode based on the polling monitoring of the server manager, the failure determination unit 250 determines whether failure information has been acquired within the set time. Further, the failure determination unit 250 refers to the communication policy 251 and determines whether failure information to be applied to failure determination is included in the acquired failure information. The failure determination unit 250 refers to the set time stored in the communication policy 251. The start time of the set time is a function monitoring frame acquisition request time in the monitoring execution unit 24.

  The failure determination unit 250 refers to the communication policy 251 and determines whether failure information to be applied to failure determination is included in the acquired failure information. For example, when the acquired failure information includes “temperature abnormality” and the failure information applied to the failure determination specified in the communication policy 251 is also “temperature abnormality”, the failure determination unit 250 acquires the failure information. It is determined that On the other hand, when the acquired failure information includes “temperature abnormality” and the failure information applied to the failure determination defined in the communication policy 251 does not include “temperature abnormality”, the failure determination unit 250 acquires the failure information. Judge that it is not.

  When the function monitoring frame is received within the set time and the failure information is acquired, the failure determination unit 250 determines that a failure has occurred in the server 16. Further, even when the function monitoring frame is not received within the set time, the failure determination unit 250 determines that a failure has occurred in the server 16. On the other hand, when the function monitoring frame is received within the set time and failure information is not acquired from the function monitoring frame, the failure determination unit 250 determines that no failure has occurred in the server 16.

  In the case of the monitoring mode based on notification received from the server manager, the failure determination unit 250 determines whether failure information has been acquired. Further, the failure determination unit 250 refers to the communication policy 251 and determines whether failure information to be applied to failure determination is included in the acquired failure information. For example, when the acquired failure information includes “temperature abnormality” and the failure information applied to the failure determination specified in the communication policy 251 is also “temperature abnormality”, the failure determination unit 250 acquires the failure information. Thus, the failure determination unit 250 determines that a failure has occurred in the server 16. On the other hand, when the acquired failure information includes “temperature abnormality” and the failure information applied to the failure determination defined in the communication policy 251 does not include “temperature abnormality”, the failure determination unit 250 acquires the failure information. The failure determination unit 250 determines that no failure has occurred in the server 16.

  The output processing unit 26 executes output processing for outputting a frame. The output processing unit 26 refers to the routing table 201 of the device management unit 20 to identify a port that outputs a frame, and transmits the frame from the identified port. The output processing unit 26 generates a connectivity monitoring frame when the failure determination unit 250 determines that a failure has occurred. A generation example of the connectivity monitoring frame will be described later with reference to FIG.

  The NW side ports 27-1 and 27-2 are ports connected to the network 10. Server side ports 27-3 and 27-4 are ports connected to the server base 17. The NW side ports 27-1 and 27-2 are, for example, Port1 and Port3 in FIG. 1, and the server side ports 27-3 and 27-4 are, for example, Port5 and Port6 in FIG.

<Line table 28>
3A and 3B are explanatory diagrams showing examples of stored contents of the line table 28. FIG. The line tables 28-1 and 28-2 in FIG. 3A are tables held by the function monitoring terminal 14-1, and the line tables 28-3 and 28-4 in FIG. 3B are held by the function monitoring terminal 14-2. It is a table. In FIG. 3A, the left line table 28-1 is a table for managing the line L2 in the network NW2 connected to the server base 17-1, and the right line table 28-2 is connected to the server base 17-1. This is a table for managing the line L1 in the network NW1. In FIG. 3B, the left line table 28-3 is a table for managing the line L1 in the network NW1 connected to the server base 17-2, and the right line table 28-4 is connected to the server base 17-2. This is a table for managing the line L3 in the network NW3.

  The line table 28 has, as fields, a line identifier 31, line identification information 32 of the affiliated network, and line identification information 33 of the affiliated server base. The line identifier 31 is a field for storing a line identifier for specifying a user line as a value. The line identification information 32 of the affiliation destination network is a field for storing various line identification information of the affiliation network as a value. The line identification information 33 of the affiliated server base is a field for storing various line identification information of the server base to which the affiliate belongs as a value.

  In the case of the line table 28-1, line identification information of the line L2 in the affiliation network (network NW2 connected to the server base 17-1) is stored. In the case of the line table 28-2, the affiliation network (server The line identification information of the line L1 in the network NW1) connected to the base 17-1 is stored.

  In the case of the line table 28-3, the line identification information of the line L1 in the affiliated network (network NW1 connected to the server base 17-2) is stored. In the case of the line table 28-4, the affiliated network (server The line identification information of the line L3 in the network NW3) connected to the base 17-2 is stored.

  The line identification information 32 of the affiliation network includes a port number 34, an MEL 35, an internal VLAN tag 36, and an external VLAN tag 37 as fields. The port number 34 is a field for storing, as a value, a port number for specifying the port 27 of the function monitoring terminal 14 that inputs a frame to the belonging network. The MEL 35 is a field that stores a management level (MEL) of MEG (Maintenance Entity Group) as a value. The MEG is a set of ME (Maintenance Entity) which is a management unit (also referred to as a monitoring section). In this example, the management unit is a section in which the line of the affiliation network is routed. For example, when the affiliation network is the network NW1, the line L1 is the monitoring section.

  The internal VLAN tag 36 is a field for storing, as a value, identification information (internal VLAN tag) that identifies the VLAN in the affiliation network. The external VLAN tag 37 is a field that stores, as a value, identification information (external VLAN tag) that identifies a VLAN outside the affiliation network. The combination of the internal VLAN tag 36 and the external VLAN tag 37 uniquely identifies the VLAN. The combination of the internal VLAN tag 36 and the external VLAN tag 37 is network information indicating that the frame transfer destination is in the VLAN specified by the combination of the internal VLAN tag 36 and the external VLAN tag 37.

  The affiliated server base line identification information 33 is a field for storing various kinds of line identification information for specifying the server base 17 to which the function monitoring terminal 14 belongs. Specifically, the line identification information 33 of the affiliated server base has a port number 38 and a VLAN tag 39 as fields. The port number 38 is a field for storing a port number for identifying the port 27 of the function monitoring terminal 14 that outputs a frame from the affiliated server base 17 as a value. The VLAN tag 39 is a field that stores, as a value, identification information that identifies a VLAN in the affiliated server base 17.

  In the line tables 28-1 and 28-2, entries having the same line identifier 31 are associated. For example, an entry whose line identifier 31 is “1” in the line table 28-1 is defined as a line L2, and an entry whose line identifier 31 is “1” in the line table 28-2 is a line L1. Yes. Since both entries are associated by the line identifier 31: 1, the connection between the line L2 and the line L1 is defined. The same applies to the line tables 28-3 and 28-4.

<Failure notification sequence>
Next, a sequence from when the failure of the server 16 is detected by the function monitoring terminal 14 until the failure alarm is notified to the terminal device and the controller 19 will be described.

  FIG. 4 is an explanatory diagram showing an example of a sequence in which the function monitoring terminal 14 notifies a server failure alarm to the network side. Here, a case where the failure determination unit 250 of the function monitoring terminal 14-2 determines that a failure has occurred will be described as an example. If the failure determination unit 250 determines that a failure has occurred, the function monitoring terminal 14-2 detects the failure (step S40). Then, the function monitoring terminal 14-2 transmits a connectivity monitoring frame including a failure alarm of the server 16 to the NE device 13 (Steps S41-1, S41-2). Generation of a frame to be transmitted to the NE devices 13-3 and 13-4 will be described later. The connectivity monitoring frame transferred to the NE device 13-3 is transferred to the function monitoring terminal 14-1 via the NE device 13-2 and also to the terminal device 12-2 via the NE device 13-4. Forwarded to

  When receiving the connectivity monitoring frame, the terminal device 12-2 terminates the connectivity monitoring frame, and detects that a failure has occurred in the server 16 at the server base 17-2 by receiving the connectivity monitoring frame (step S42). ). Then, the terminal device 12-2 extracts failure information from the connectivity monitoring frame, generates a message including the failure information, and transmits the message to the adjacent NE device 13-4 (step S43). When the NE device 13-4 receives the message including the failure information, the NE device 13-4 notifies the controller 19 of the message (step S44).

  When the function monitoring terminal 14-1 receives the monitoring frame from the function monitoring terminal 14-2, the conversion unit 23 replaces the VLAN tag in the connectivity monitoring frame (step S45). Specifically, the replacement of the VLAN tag is performed by the connectivity monitoring frame from the network NW1 including the line L1 between the function monitoring terminal 14-2 that detects the server failure and the function monitoring terminal 14-1 that receives the connectivity monitoring frame. Shows a change to the network NW2 including the line L2 between the function monitoring terminal 14-1 and the terminal device 12-1. The replacement of the VLAN tag will be described later with reference to FIG.

  The function monitoring terminal 14-1 transmits the connectivity monitoring frame after the replacement of the VLAN tag to the terminal device 12-1 via the NE devices 13-2 and 13-1 (step S46). Since the VLAN tag is replaced, the NE device 13-2 connects not to the network NW1 before the VLAN tag replacement but to the adjacent NE device 13-1 belonging to the network NW2 after the VLAN tag replacement after the VLAN tag replacement. Forward the security monitoring frame. Similarly, the NE device 13-1 also transfers the connectivity monitoring frame after the VLAN tag change to the terminal device 12-1 belonging to the network NW2 after the VLAN tag change. As a result, failure information indicating a failure that has occurred in the server 16 of the server base 17-2 that does not belong to the network NW2 is detected on the network NW2 side.

  The terminal device 12-1 terminates the connectivity monitoring frame after the VLAN tag replacement, and detects that a failure has occurred in the server 16 at the server base 17-2 by receiving the connectivity monitoring frame after the VLAN tag replacement. (Step S47). Then, the terminal device 12-1 extracts the failure information from the connectivity monitoring frame after the VLAN tag change, generates a message including the failure information, and transmits the message to the adjacent NE device 13-1 (step S48). When the NE device 13-1 receives the message including the failure information, the NE device 13-1 notifies the controller 19 of the message (step S49).

<Example of VLAN tag replacement>
FIG. 5 is an explanatory diagram showing an example of replacing a VLAN tag. In FIG. 5, (A) shows an example of the frame format of the connectivity monitoring frame generated by the function monitoring terminal 14-2 that has detected the failure, and (B) has received the connectivity monitoring frame of (A). An example of a frame format of the connectivity monitoring frame in the function monitoring terminal 14-1 is shown. For transferring the connectivity monitoring frame, for example, ITU-T G. 8013 / Y. ETH-VSP (Ethernet Vendor-Specific OAM function (Ethernet is a registered trademark)) defined in 1731 is used.

  In each field of FIG. 5, a MAC DA (Destination Address) 501 stores a destination MAC address as a value. In a MAC SA (Source Address) 502, a transmission source MAC address is stored as a value. The external VLAN tag 503 stores the external VLAN tag as a value. The internal VLAN tag 504 stores the internal VLAN tag as a value. When relaying a frame, the function monitoring terminal 14 or the NE device 13 refers to the internal VLAN tag 36 and the external VLAN tag 37, and transmits the frame in the VLAN specified by the combination of the internal VLAN tag 36 and the external VLAN tag 37. However, it is not transmitted to other networks. When relaying to another network, the function monitoring terminal 14 replaces the values of the internal VLAN tag 36 and the external VLAN tag 37 with values specifying the relay destination network, as will be described later. The MEL 505 stores the MEG management level as a value. Version 506 stores a protocol version number as a value.

  In OpCode 507, a value indicating ETH-VSP is stored as a value in order to distinguish it from the network connectivity monitoring frame. Flags 508 stores a flag as a value. The TLV (Type, Length, and Value) Offset 509 stores a TLV offset value as a value. An OUI (Organizationally Unique Identifier) 510 stores the first half part (product code) of the source MAC address as a value.

  In SubOpCode 511, a value indicating a server failure alarm is stored as a value. The MEP (MEG End Point) ID 512 stores the MEP ID of the function monitoring terminal 14 that detected the server failure as a value. The MEG ID 513 stores the MEG ID of the function monitoring terminal 14 that detected the server failure as a value. By assigning the MEP ID and MEG ID to the failure alarm that is the SubOpCode, it becomes possible to identify the function monitoring terminal 14 that has issued the failure alarm from the controller 19.

  In addition, the function identifier 514 is an optional item, assuming that the server 16 itself in which a failure has occurred can be identified, such as a monitoring mode using a server manager, or that alarms are forwarded including information indicating the function that has failed in the virtual server. May also be provided. The connectivity monitoring frame is transmitted to the adjacent function monitoring terminal 14 or terminal device 12 by ETH-VSP. When the received device is the terminal device 12, the terminal device 12 terminates the connectivity monitoring frame, refers to the MEP ID 512, MEG ID 513, and the function identifier 514 in the connectivity monitoring frame, and the server base 17 has a fault. The controller 19 is notified of the occurrence. When the received device is the function monitoring terminal 14, since it is necessary to relay to the terminal device 12, the function monitoring terminal 14 that has received the connectivity monitoring frame performs a relay process.

  Here, as shown in FIG. 4, an example of generating a connectivity monitoring frame when a failure occurs in the function monitoring terminal 14-2 will be described. Here, the case where the function monitoring terminal 14-2 receives a function monitoring frame including failure information of the server 16 from the Port 5 in the server base 17-2 will be described as an example.

  Since the port 27 that has received the function monitoring frame including the failure information is Port 5, the function monitoring terminal 14-2 stores the port in the line identification information 32 of the destination server base in the line tables 28-3 and 28-4. Reference is made to the line table 28-3 in FIG. 3B where the value of the number 38 is “5”. For example, in the line table 28-3 in FIG. 3B, when the line identifier 31-3 is “1”, the function monitoring terminal 14-2 sets the value of the external VLAN tag 503 to “1” in the connectivity monitoring frame. ", The value of the internal VLAN tag 504 is set to" 1 ", and the value of the MEL 505 is set to" 6 ".

  The function monitoring terminal 14-2 sets the value of the MAC SA 502 to the MAC address of the function monitoring terminal 14-2. In addition, since the port number 34-3 of the network NW1 of the entry is “1”, the function monitoring terminal 14-2 refers to the routing table 201 and refers to the MAC address (NE device 13) corresponding to the port number “1”. -3 MAC address) and the value of the MAC DA 501 is set to the specified MAC address. As a result, a connectivity monitoring frame indicating that a failure has been detected is generated, transmitted from Port 1 to the network NW 1 via the NE device 13-3, and input to Port 3 of the function monitoring terminal 14-1 (Step S 41-1). ).

  Further, when the connectivity monitoring frame is generated and transmitted in step S41-1, the function monitoring terminal 14- is referred to because the entry whose line identifier 31-3 is "1" in the line table 28-3 in FIG. 3B is referred to. 2 specifies an entry whose line identifier 31-4 has the same value, that is, "1" from the line table 28-4. In this case, the function monitoring terminal 14-2 sets the value of the external VLAN tag 503 to “1”, the value of the internal VLAN tag 504 to “2”, and the value of the MEL 505 to “6” in the connectivity monitoring frame. The function monitoring terminal 14-2 sets the value of the MAC SA 502 to the MAC address of the function monitoring terminal 14-2.

  Further, since the port number 34-4 of the network NW3 of the entry is “3”, the function monitoring terminal 14-2 refers to the routing table 201 and refers to the MAC address (NE device 13) corresponding to the port number “3”. -3 MAC address) and the value of the MAC DA 501 is set to the specified MAC address. As a result, a connectivity monitoring frame indicating that a failure has been detected is generated, transmitted from the Port 3 to the network NW 3 via the NE device 13-3, and input to the terminal device 12-2 (step S41-2).

  In (B), when receiving the connectivity monitoring frame from the function monitoring terminal 14-2, the function monitoring terminal 14-1 that performs the relay process rewrites the MAC DA 501 to the transfer destination MAC DA 501 and changes the MAC SA 502 to its own. The MAC address of the function monitoring terminal 14-1 is rewritten. The function monitoring terminal 14-1 transmits the external VLAN tag 503 and the internal VLAN tag 504 of the received connectivity monitoring frame to the line between the function monitoring terminal 14-1 that performs relay processing and the transfer destination terminal apparatus 12-1. The internal VLAN tag 36 and the external VLAN tag 37 corresponding to the identifier are replaced.

  Further, the function monitoring terminal 14-1 monitors the connectivity of the network NW2 between the function monitoring terminal 14-1 that relays the MEL 505 and the terminal device in order to prevent the server failure alarm from being discarded during the intra-network transfer. To the value “3” of the MEL35-1 of the ETH-OAM used for

  For the Version 506, OpCode 507, Flags 508, TLV Offset 509, OUI 510, SubOp Code 511, MEP ID 512, MEG ID 513, function identifier 514, and the end TLV 515, the function monitoring terminal 14-1 copies the contents of the received connectivity monitoring frame.

  The terminal device 12-1 terminates the received connectivity monitoring frame and notifies the controller 19 of the MEP ID 512, the MEG ID 513, and the function identifier 514. As a result, the controller 19 can identify the function monitoring terminal 14-2 that has issued a server failure alarm, and can know at which server site 17 the failure has occurred.

  Here, as shown in FIG. 4, in the function monitoring terminal 14-1, the connectivity monitoring frame in the case where the connectivity monitoring frame from the function monitoring terminal 14-2 is transferred to the terminal device 12-1. A conversion example will be described. Here, the case where the function monitoring terminal 14-1 receives the function monitoring frame from the function monitoring terminal 14-2 including the failure information of the server 16 at Port 3 will be described as an example.

  Since the port 27 that has received the function monitoring frame is Port 3, the function monitoring terminal 14-1 sets the value of the port number 34 in the line identification information 32 of the network to which it belongs in the line tables 28-1 and 28-2. Reference is made to the line table 28-2 of FIG. The function monitoring terminal 14-1 receives the connectivity received from the function monitoring terminal 14-2 in the entry group in which the value of the port number 34-2 of the line identification information 32-2 of the affiliation network is “3”. The entry whose value matches the external VLAN tag 503, the internal VLAN tag 504, and the MEL 505 of the monitoring frame is specified, and the value of the line identifier 31-2 of the specified entry is specified. In this example, since the internal VLAN tag of the connectivity monitoring frame received from the function monitoring terminal 14-2 is “1”, the external VLAN tag is “1”, and the MEL is “6”, the line in the line table 28-2 An entry whose value of the identifier 31-2 is “1” is specified.

  Then, the function monitoring terminal 14-1 identifies the entry having the line identifier 31-1 having the same value as the value “1” of the line identifier 31-2 of the identified entry from the line table 28-1. In the case of this example, an entry whose value of the line identifier 31-1 of the line table 28-1 is “1” is specified. Then, the function monitoring terminal 14-1 rewrites the value “1” of the external VLAN tag 503 of the received connectivity monitoring frame to the value “2” of the external VLAN tag 37-1 of the identified entry, and receives the received connectivity. The value “1” of the internal VLAN tag 504 of the monitoring frame is rewritten to the value “3” of the internal VLAN tag 36-1 of the specified entry, and the value “6” of the MEL 505 of the received connectivity monitoring frame is specified. To MEL35-1 value “3” (step S45).

  In addition, the function monitoring terminal 14-1 sets the MAC DA 501 of the received connectivity monitoring frame, that is, the MAC address of the function monitoring terminal 14-1, in the MAC SA 502 of the received connectivity monitoring frame. Further, the function monitoring terminal 14-1 determines the MAC address corresponding to the value “1” of the port number 34-1 of the line identification information 32-1 of the network to which the identified entry belongs, that is, the MAC of the NE device 13-2. An address is specified from the routing table 201 and set in the MAC DA 501. Thereafter, the function monitoring terminal 14-1 transmits the renewed connectivity monitoring frame from Port 1 (step S46). The transmitted connectivity monitoring frame reaches the terminal device 12-1 via the NE devices 13-2 and 13-1.

<Monitoring mode setting sequence>
There are two methods for setting the monitoring mode. The first setting sequence is a sequence for setting the monitoring mode by the operation of the administrator of the controller 19 (FIGS. 6 to 9), and the second setting sequence is for setting the monitoring mode by the operation from the user device 11. This is a sequence (FIGS. 10 and 11). First, the sequence for setting the monitoring mode by the operation of the administrator of the controller 19 will be described.

  FIG. 6 is an explanatory diagram showing a first setting sequence example. The controller 19 selects the function monitoring terminal 14 that is the setting destination of the monitoring mode by the operation of the administrator (step S60). Next, the controller 19 selects the monitoring mode to be set in the selected function monitoring terminal 14 by the operation of the administrator (step S61). And the controller 19 inputs a value into the setting item of the selected monitoring mode by operation of an administrator (step S62). An example of selecting a monitoring mode and an example of inputting values for setting items of the monitoring mode will be described later. Then, the controller 19 transmits the selected monitoring mode and the value of the setting item to the selected function monitoring terminal 14 (step S63).

  The function monitoring terminal 14 specifies the monitoring mode from the received content (step S64), and reflects the setting content of the monitoring mode according to the value of the setting item (step S65). Specifically, for example, the function monitoring terminal 14 sets the specified monitoring mode in the monitoring execution unit 24 and the failure determination unit 250, and stores the value of the setting item in the communication policy 251. When the storage of the setting item value is completed, the function monitoring terminal 14 notifies the controller 19 that the reflection of the selected monitoring mode and the setting item value has been completed (step S66). And the function monitoring terminal 14 performs the monitoring process by the specified monitoring mode (step S67). Thereby, the first setting sequence ends. Details of the monitoring process will be described with reference to FIGS.

  FIG. 7 is an explanatory diagram showing an example of a setting destination selection screen for selecting the setting destination of the monitoring mode shown in step S60 of FIG. The setting destination selection screen 70 displays a terminal setting 71 to be set. The setting target terminal setting 71 displays list information for selecting the function monitoring terminal 14 that is the setting target of the monitoring mode that is the setting target terminal. The setting destination of the monitoring mode can be selected by using a radio button 72, for example. FIG. 7 is an example in which “function monitoring terminal CCCC” of “base C” is selected. When the “next” button 73 is pressed, the process proceeds to step S61.

  FIG. 8 is an explanatory diagram showing an example of a monitoring mode selection screen for selecting the monitoring mode shown in step S61 of FIG. A monitoring mode selection 81 is displayed on the monitoring mode selection screen 80. Monitoring mode selection 81 displays monitoring mode list information. For example, one or more monitoring modes can be selected by the check box 82. FIG. 8 is an example in which a monitoring mode based on statistical information and a monitoring mode based on a server manager are selected. When the “next” button 83 is pressed, the process proceeds to step S62.

  FIG. 9 is an explanatory diagram showing an example of an input screen for setting item values shown in step S62 of FIG. The input screen 90 includes a first input area 91 for the monitoring mode based on statistical information, a second input area 92 for the monitoring mode based on frame insertion, and a third input area 93 for the monitoring mode based on communication confirmation. The fourth input area 94 for the monitoring mode by the server manager polling monitoring is displayed.

  In the first input area 91, for example, the frame number confirmation interval and the difference between transmission and reception frames are displayed as items that can be input, and as an option, “notify even when the received frame is 0 for a certain period of time” or “ “Notify when transmission frame is 0 for a certain time or longer” is displayed as a selectable item.

  In the fourth input area 94, for example, a polling monitoring method and an information receiving method are displayed as selectable items. As a setting item of the polling monitoring method, for example, a polling interval is displayed as an inputable item. Also, server failure, temperature rise, DB (Data Base) failure, no response, and server processing delay are displayed as selectable items. The server processing delay is displayed as an item in which the delay time can be input.

  In the example of FIG. 8, since the monitoring mode based on the statistical information and the monitoring mode based on the server manager are selected, the second input area 92 regarding the monitoring mode based on the frame insertion that was not selected and the monitoring mode based on the communication confirmation The third input area 93 may not be input or may not be displayed. When the transmission button 95 is lowered, transmission in step S63 is executed.

  FIG. 10 is an explanatory diagram illustrating a second setting sequence example. First, the user device 11 to the controller 19 execute an authentication process related to the user of the user device 11 (step S100). Specifically, the user device 11 performs user authentication input using a login screen by a user operation (step S01). As an example of the authentication method, there is a method of inputting a password, a method of confirming whether the serial number of the user device 11 used by the requested user and the identifier of the user line match the information on the controller 19 side, or the like. is there.

  FIG. 11 is an explanatory diagram illustrating an example of a login screen displayed on the user device 11. FIG. 11 shows an example of a login screen 110 using a password. The login screen 110 displays a login 111 based on line information and a login 112 based on a password as selectable items. For the login 112 using a password, there are a user name input area 113 and a password input area 114, and a user name and a password can be input. The login 111 by line information or the login 112 by password can be selected by radio buttons 115 and 116, respectively. When the transmission button 117 is pressed, the contents of the logins 111 and 112 selected by the radio buttons 115 and 116 on the login screen 110 are transmitted to the terminal device 12 (step S02).

  Returning to FIG. 10, the terminal device 12 converts the received data including the input contents into a control frame, and conceals the setting source user address by encapsulation (step S03). Then, the terminal device 12 transmits a control frame to the controller 19 (step S04). The controller 19 decapsulates the received control frame, takes out the input contents (for example, the user name and password) of the login screen 110, and compares them with the combination of the user name and password stored in the controller 19 for authentication processing. Is executed (step S05).

  The controller 19 transmits a control frame including an authentication result indicating successful authentication to the terminal device 12 (step S06). The terminal device 12 decapsulates the control frame, acquires the authentication result (step S07), and returns the authentication result to the user device 11 (step S08). If the authentication result is an authentication failure, the process ends. On the other hand, if the authentication result is authentication success, the user apparatus 11 executes monitoring mode selection and setting item input processing (step S101).

  In the monitoring mode selection and setting item input processing (step S101), the user device 11 selects the function monitoring terminal 14 as the monitoring mode setting destination by the user's operation (step S10). In selecting the function monitoring terminal 14, the setting destination selection screen of FIG. 7 is used as in the first setting sequence.

  Next, the user device 11 selects a monitoring mode to be set in the selected function monitoring terminal 14 by a user operation (step S11). In the selection of the monitoring mode, the monitoring mode selection screen 80 of FIG. 8 is used as in the first setting sequence.

  Next, the user device 11 sends data including the selected monitoring mode to the terminal device 12 (step S12). The terminal device 12 converts the data including the monitoring mode into a control frame, and conceals the setting source user address by encapsulation (step S13). Then, the terminal device 12 transmits a control frame to the controller 19 (step S14). The controller 19 decapsulates the received control frame, and extracts and confirms the monitoring mode (step S15). Then, the controller 19 converts the data of the input screen 90 as shown in FIG. 9 into a control frame, encapsulates it, and transmits it to the terminal device 12 (step S16).

  The terminal device 12 decapsulates the control frame to acquire the data on the input screen 90 (step S17), and returns the data on the input screen 90 to the user device 11 (step S18). And the user apparatus 11 displays the input screen 90, and inputs a value into a setting item by a user's operation (step S19). Thus, the monitoring mode selection and setting item input processing (step S101) ends.

  Next, the user apparatus 11 transmits the setting content in S19 to the terminal apparatus 12 (step S102). The terminal device 12 converts the received data including the setting contents into a control frame, and conceals the setting source user address by encapsulation (step S103). Then, the terminal device 12 transmits a control frame to the controller 19 (step S104).

  The controller 19 extracts the monitoring mode selected for the function monitoring terminal 14 and the value of the setting item in the monitoring mode from the received control frame, and transmits them to the function monitoring terminal 14 via the NE device 13 (step S105).

  The function monitoring terminal 14 specifies the monitoring mode from the received content (step S106), and reflects the setting content of the monitoring mode according to the value of the setting item (step S107). Specifically, for example, the function monitoring terminal 14 sets the specified monitoring mode in the monitoring execution unit 24 and the failure determination unit 250, and stores the value of the setting item in the communication policy 251. The function monitoring terminal 14 returns a control frame including a setting completion notification to the controller 19 via the NE device 13 (step S108). Thereafter, the function monitoring terminal 14 performs monitoring processing in the specified monitoring mode (step S109). Details of the monitoring process will be described with reference to FIGS.

  The controller 19 receives the control frame from the function monitoring terminal 14 and transfers it to the terminal device 12 (step S110). The terminal device 12 decapsulates the control frame, acquires a completion notification (step S111), and transmits it to the user device 11 (step S112). Thereby, the second setting sequence ends.

<Monitoring process>
FIG. 12 is a flowchart illustrating a detailed processing procedure example of the monitoring process based on statistical information, which is an example of the monitoring process (steps S67 and S109) of FIGS. 6 and 10. The function monitoring terminal 14 uses the monitoring execution unit 24 to count the number of frames transmitted to the server 16 and the number of frames received from the server 16 within a predetermined time (step S120). The predetermined time is, for example, 10 seconds of [frame / 10 seconds] in the “transmission / reception frame difference” in the first input area 91 on the input screen 90 of FIG. 10 seconds is an example.

  Next, the function monitoring terminal 14 calculates the number of frame losses by the monitoring execution unit 24 (step S121). The number of frame losses is a value obtained by subtracting the number of received frames from the number of transmitted frames. Then, the function monitoring terminal 14 determines whether or not the number of frame losses is greater than or equal to the failure determination reference value by using the failure determination unit 250 (step S122). The failure determination reference value is a value input to “transmission / reception frame difference” in the first input area 91 on the input screen 90 in FIG. 9, and is read from the communication policy 251.

  When the number of frame losses is less than the failure determination reference value (step S122: No), it means that no failure has occurred, and the function monitoring terminal 14 determines by the failure determination unit 250 in the monitoring process based on the previous statistical information. It is determined whether or not the state of the server that has been made (hereinafter, the previous state) is a failure state (step S123). When the previous state is not a failure state (step S123: No), that is, when the internal table is “normal”, the process proceeds to step S129.

  On the other hand, when the previous state is a failure state (step S123: Yes), that is, when the internal table is “failure”, the state is recovered from the failure state. Therefore, the function monitoring terminal 14 outputs a message indicating failure recovery by the output processing unit 26 (step S124). Then, the function monitoring terminal 14 updates the state of the server in the internal table from “failure” to “normal” by the monitoring execution unit 24 (step S125), and proceeds to step S129.

  In step S122, if the number of frame losses is equal to or greater than the failure determination reference value (step S122: Yes), a failure has occurred, and the function monitoring terminal 14 uses the failure determination unit 250 to determine that the previous state is a failure state. It is determined whether or not (step S126). When the previous state is a failure state (step S126: Yes), that is, when the internal table is “failure”, the process proceeds to step S129. On the other hand, if the previous state is not a failure state (step S123: No), that is, if the internal table is “normal”, the failure has occurred from the normal state. Therefore, the function monitoring terminal 14 outputs a message indicating failure detection by the output processing unit 26 (step S127). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “normal” to “failure” by the monitoring execution unit 24 (step S128), and proceeds to step S129.

  In step S129, the function monitoring terminal 14 puts the monitoring execution unit 24 in the sleep state for a certain time (step S129). The fixed time is, for example, a value input in the “frame number confirmation interval” in the first input area 91 on the input screen 90 of FIG. In addition, the sleep state is a state in which a process is continued without waiting for completion in a series of processes. Step S120 is re-executed after a certain period of time.

  FIG. 13 is a flowchart illustrating a detailed processing procedure example of the monitoring process by frame insertion, which is an example of the monitoring process (steps S67 and S109) of FIGS. 6 and 10. First, the function monitoring terminal 14 transmits a function monitoring frame to the server 16 side by the failure determination unit 250 (step S130), and determines whether or not the transmitted function monitoring frame is received within a predetermined time (step S131). ). The predetermined time is, for example, a value input in the “frame insertion interval” of the second input area 92 on the input screen 90 of FIG. If it is not received within the predetermined time (step S131: No), it means that a failure has occurred, and the process proceeds to step S136. On the other hand, when it is received within the set time (step S131: Yes), the function monitoring terminal 14 determines whether or not the received function monitoring frame has failure information by the failure determination unit 250 (step S132). The failure information is given by the server manager.

  If there is failure information (step S132: Yes), a failure has occurred, and the process proceeds to step S136. On the other hand, when there is no failure information (step S132: No), it means that no failure has occurred, and the function monitoring terminal 14 determines whether or not the previous state is a failure state by the failure determination unit 250 ( Step S133). When the previous state is not a failure state (step S133: No), that is, when the internal table is “normal”, the process proceeds to step S139. On the other hand, when the previous state is a failure state (step S133: Yes), that is, when the internal table is “failure”, the state is recovered from the failure state. Therefore, the function monitoring terminal 14 outputs a message indicating failure recovery by the output processing unit 26 (step S134). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “failure” to “normal” by the monitoring execution unit 24 (step S135), and proceeds to step S139.

  In step S136, the function monitoring terminal 14 uses the failure determination unit 250 to determine whether the previous state is a failure state (step S136). When the previous state is a failure state (step S136: Yes), that is, when the internal table is “failure”, the process proceeds to step S139. On the other hand, if the previous state is not a failure state (step S136: No), that is, if the internal table is “normal”, the failure has occurred from the normal state. Therefore, the function monitoring terminal 14 outputs a message indicating failure detection by the output processing unit 26 (step S137). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “normal” to “failure” by the monitoring execution unit 24 (step S138), and proceeds to step S129.

  In step S139, the function monitoring terminal 14 puts the monitoring execution unit 24 in the sleep state for a certain time (step S129). The fixed time is, for example, a value input in the “set time” of the first input area 91 on the input screen 90 of FIG. Step S130 is re-executed after a certain period of time.

  FIG. 14 is a flowchart showing a detailed processing procedure example of the monitoring process by the communication confirmation which is an example of the monitoring process (steps S67 and S109) of FIGS. First, the function monitoring terminal 14 transmits a communication confirmation frame to the server 16 side by the failure determination unit 250 (step S140), and determines whether a response frame is returned within a predetermined time (step S131). The predetermined time is, for example, a value input in the “confirmation interval” of the third input area 93 on the input screen 90 of FIG.

  When the response frame is returned (step S141: Yes), it means that no failure has occurred, and the function monitoring terminal 14 determines whether or not the previous state is a failure state by the failure determination unit 250 ( Step S142). When the previous state is not a failure state (step S142: No), that is, when the internal table is “normal”, the process proceeds to step S148. On the other hand, when the previous state is a failure state (step S142: Yes), that is, when the internal table is “failure”, the state is recovered from the failure state. Therefore, the function monitoring terminal 14 outputs a message indicating failure recovery by the output processing unit 26 (step S143). Then, the function monitoring terminal 14 updates the state of the server in the internal table from “failure” to “normal” by the monitoring execution unit 24 (step S144), and proceeds to step S148.

  If a response frame is not returned in step S141 (step S122: No), a failure has occurred, and the function monitoring terminal 14 uses the failure determination unit 250 to check whether the previous state is a failure state. Is determined (step S145). When the previous state is a failure state (step S145: Yes), that is, when the internal table is “failure”, the process proceeds to step S148. On the other hand, if the previous state is not a failure state (step S145: No), that is, if the internal table is “normal”, the failure has occurred from the normal state. Therefore, the function monitoring terminal 14 outputs a message indicating failure detection by the output processing unit 26 (step S146). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “normal” to “failure” by the monitoring execution unit 24 (step S147), and proceeds to step S148.

  In step S148, the function monitoring terminal 14 puts the monitoring execution unit 24 in the sleep state for a certain time (step S129). The fixed time is, for example, a value input in the “set time” of the third input area 93 on the input screen 90 of FIG. Step S140 is re-executed after a certain period of time.

  FIG. 15 is a flowchart showing a detailed processing procedure example of monitoring processing by polling of the server manager, which is an example of the monitoring processing (steps S67 and S109) of FIGS. First, the function monitoring terminal 14 inquires of the server 16 for failure information by the monitoring execution unit 24 (step S150), and determines whether or not the failure information is acquired from the server manager by the failure determination unit 250 (step S150). S151). If failure information has not been acquired (step S151: No), a failure has occurred, and the process proceeds to step S157. On the other hand, when failure information is acquired (step S151: Yes), the function monitoring terminal 14 uses the failure determination unit 250 to narrow down the received failure information with the communication policy 251 (step S152). It is determined whether or not there is (step S153).

  If there is a failure (step S152: Yes), the process proceeds to step S157. On the other hand, when there is no failure (step S152: No), the function monitoring terminal 14 determines whether or not the previous state is a failure state by the failure determination unit 250 (step S154). When the previous state is not a failure state (step S154: No), that is, when the internal table is “normal”, the process proceeds to step S15A. On the other hand, when the previous state is a failure state (step S154: Yes), that is, when the internal table is “failure”, the state is recovered from the failure state. Therefore, the function monitoring terminal 14 outputs a message indicating failure recovery by the output processing unit 26 (step S155). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “failure” to “normal” by the monitoring execution unit 24 (step S156), and proceeds to step S15A.

  In step S157, the function monitoring terminal 14 uses the failure determination unit 250 to determine whether the previous state is a failure state (step S157). When the previous state is a failure state (step S157: Yes), that is, when the internal table is “failure”, the process proceeds to step S15A. On the other hand, if the previous state is not a failure state (step S157: No), that is, if the internal table is “normal”, the failure has occurred from the normal state. Therefore, the function monitoring terminal 14 outputs a message indicating failure detection by the output processing unit 26 (step S158). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “normal” to “failure” by the monitoring execution unit 24 (step S159), and proceeds to step S15A.

  In step S15A, the function monitoring terminal 14 puts the monitoring execution unit 24 in the sleep state for a certain time (step S15A). The fixed time is, for example, a value input in the “polling interval” of the fourth input area 94 on the input screen 90 of FIG. Step S150 is re-executed after a certain period of time.

  FIG. 16 is a flowchart illustrating a detailed processing procedure example of the monitoring process based on the notification from the server manager, which is an example of the monitoring process (steps S67 and S109) of FIGS. First, the function monitoring terminal 14 receives failure information from the server manager by the monitoring execution unit 24 (step S160). Next, the function monitoring terminal 14 uses the failure determination unit 250 to narrow down the received failure information using the communication policy 251 (step S161), and determines whether or not there is a failure based on the failure information after narrowing down (step S162).

  When there is no failure (step S162: No), the function monitoring terminal 14 determines whether the previous state is a failure state by the failure determination unit 250 (step S163). When the previous state is not a failure state (step S163: No), that is, when the internal table is “normal”, the process proceeds to step S169. On the other hand, when the previous state is a failure state (step S163: Yes), that is, when the internal table is “failure”, the state is recovered from the failure state. Therefore, the function monitoring terminal 14 outputs a message indicating failure recovery by the output processing unit 26 (step S164). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “failure” to “normal” by the monitoring execution unit 24 (step S165), and proceeds to step S169.

  If there is a failure in step S162 (step S162: Yes), the function monitoring terminal 14 determines whether or not the previous state is a failure state by the failure determination unit 250 (step S166). When the previous state is a failure state (step S166: Yes), that is, when the internal table is “failure”, the process proceeds to step S169. On the other hand, if the previous state is not a failure state (step S163: No), that is, if the internal table is “normal”, the failure has occurred from the normal state. Therefore, the function monitoring terminal 14 outputs a message indicating failure detection by the output processing unit 26 (step S167). Then, the function monitoring terminal 14 updates the state of the server 16 in the internal table from “normal” to “failure” by the monitoring execution unit 24 (step S168), and proceeds to step S129.

  In step S169, the function monitoring terminal 14 puts the monitoring execution unit 24 in the sleep state for a certain time (step S169). Step S160 is re-executed after a certain period of time.

  As described above, according to the first embodiment, a failure occurring on the server 16 side can be detected on the network side. Moreover, this can reduce the burden of the network maintenance person's work for identifying the fault location. In addition, the failure notification method to the network side is not a link down, but a notification method using OAM or the like, so that the failure notification on the server side can be performed without affecting the control signal outside the failure occurrence section. Become.

  The second embodiment is an example in which the server 16 and the server base 17 are monitored without installing the function monitoring terminal 14 for monitoring the server 16 and the server base 17. The same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof is omitted.

  FIG. 17 is an explanatory diagram of a system configuration example of the failure notification system 1 according to the second embodiment. The failure notification system 1 according to the second embodiment has a system configuration for notifying a failure of the server 16 to the network side. FIG. 17 shows an example in which function monitoring units 140-1 and 140-2 for monitoring a failure of the server 16 are implemented as functions of the NE devices 13-2 and 13-3. The function monitoring units 140-1 and 140-2 are equivalent to the function monitoring terminal 14 already described.

  Further, since the NE devices 13-2 and 13-3 have a larger number of lines that can be accommodated than the function monitoring terminal 14, it is possible to monitor a section with a high network density. For example, when the server base 17-2 to be monitored is a large-scale server base or the like, by installing the NE device 13-3 including the function monitoring unit 140-2, a plurality of function monitoring terminals 14 are not installed. The server base 17 can be monitored. Further, since the NE device 13-2 has the function monitoring unit 140-1, it is not necessary to install a device for monitoring a server failure in the server base 17-1.

  The connectivity monitoring frame including the failure alarm is transferred from the function monitoring unit 140 to the adjacent terminal device 12 or the function monitoring unit 140. For example, when the function monitoring unit 140-1 detects a server failure, the NE device 13-2 having the function monitoring unit 140-1 includes a failure alarm addressed to the terminal device 12-1 and the function monitoring unit 140-2. Issue a security monitoring frame. Since the terminal device 12-1 is an edge device, the terminal device 12-1 terminates the connectivity monitoring frame including a failure alarm and notifies the controller 19 that a failure has occurred in the server 16.

  On the other hand, the function monitoring unit 140-2 that has received the connectivity monitoring frame including the failure alarm issued by the function monitoring unit 140-1 relays the connectivity monitoring frame including the failure alarm to the terminal device 12-2. The failure information is stored in the connectivity monitoring frame and transmitted to the terminal device 12-2. The terminal device 12-2 terminates the received failure alarm and notifies the controller 19 that a failure has occurred in the server 16.

  As described above, also in the second embodiment, a failure occurring on the server 16 side can be detected on the network side. Moreover, this can reduce the burden of the network maintenance person's work for identifying the fault location. In addition, the failure notification method to the network side is not a link down, but a notification method using OAM or the like, so that the failure notification on the server side can be performed without affecting the control signal outside the failure occurrence section. Become.

  Further, since the NE device 13 has a larger number of lines than the function monitoring terminal 14, it is possible to improve the monitoring accuracy in a section with a high network density by mounting the function monitoring unit 140 on the NE device 13. it can. Further, since the NE device 13 has the function monitoring unit 140, it is not necessary to install a device for monitoring a server failure at the server base 17-1, and the cost at the server base 17 can be reduced.

  The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described. A part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Moreover, you may add the structure of another Example to the structure of a certain Example. Moreover, you may add, delete, or replace another structure about a part of structure of each Example.

  In addition, each of the above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, with an integrated circuit, and the processor realizes each function. It may be realized by software by interpreting and executing the program to be executed.

  Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, and an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, and a DVD.

  Further, the control lines and the information lines are those that are considered necessary for the explanation, and not all the control lines and the information lines that are necessary for the mounting are shown. In practice, it can be considered that almost all the components are connected to each other.

DESCRIPTION OF SYMBOLS 1 Failure notification system 10 Network network 11 User apparatus 12 Terminal apparatus 13 NE apparatus 14 Function monitoring terminal 16 Server 17 Server base 19 Controller 20 Apparatus management part 21 Input processing part 22 Identification part 23 Conversion part 24 Monitoring execution part 26 Output processing part 27 Port 28 Line table 140 Function monitoring unit 200 Device control unit 201 Routing table 250 Failure determination unit 251 Communication policy

Claims (11)

A failure notification system comprising: a monitoring device that monitors a first server; and a relay device that is connected to the monitoring device via a first network and that is connected to a terminal device and a second network,
The monitoring device
When a failure of the first server is detected, first data including failure information of the first server and first network information indicating that a transfer destination is in the first network is generated. A first output processing unit for outputting to the first network,
The relay device is
An input processing unit that receives input of the first data from the monitoring device via the first network;
When the first data is input by the input processing unit, the first network information is replaced with second network information indicating that a transfer destination is in the second network, thereby the first data. A conversion unit for converting the data of the second to the second data;
A second output processing unit that outputs the second data to the terminal device via the second network in accordance with the second network information included in the second data converted by the conversion unit. When,
A failure notification system comprising: The relay device is
A storage unit that stores correspondence information that associates the first network information with the second network information;
A specifying unit that refers to the correspondence information and specifies the second network information associated with the first network information included in the first data;
The converting unit replaces the first network information included in the first data with the second network information specified by the specifying unit, thereby converting the first data into the second data. The failure notification system according to claim 1, wherein the failure notification system is converted into data.   The first network information includes identification information that uniquely identifies the first network, and the second network information includes identification information that uniquely identifies the second network. The failure notification system according to claim 1.   The first network information includes information indicating a monitoring section of the first network, and the second network information includes information indicating a monitoring section of the second network. 3. The fault notification system according to 3. The relay device is
A monitoring execution unit for monitoring the second server in the third network;
A failure determination unit that determines whether or not a failure has occurred in the second server during monitoring of the second server by the monitoring execution unit;
The output processing unit, when it is determined by the failure determination unit that a failure has occurred, includes the failure information of the second server and the first network information that defines transfer within the first network. The failure notification system according to claim 1, wherein the third data is output to the first network. A relay device connected to the monitoring device for monitoring the first server via the first network and connected to the terminal device via the second network;
Input of first data including failure information of the first server and first network information indicating that a transfer destination is in the first network from the monitoring device via the first network An input processing unit for receiving,
When the first data is input by the input processing unit, the first network information is replaced with second network information indicating that a transfer destination is in the second network, thereby the first data. A conversion unit for converting the data of the second data into the second data;
An output processing unit that outputs the second data to the terminal device via the second network according to the second network information included in the second data converted by the conversion unit;
A relay apparatus comprising: A storage unit that stores correspondence information that associates the first network information with the second network information;
A specifying unit that specifies the second network information associated with the first network information included in the first data with reference to the line information;
The converting unit replaces the first network information included in the first data with the second network information specified by the specifying unit, thereby converting the first data into the second data. The relay apparatus according to claim 6, wherein the relay apparatus converts the data into data.   The first network information includes identification information that uniquely identifies the first network, and the second network information includes identification information that uniquely identifies the second network. The relay device according to claim 6.   The first network information includes information indicating a monitoring section of the first network, and the second network information includes information indicating a monitoring section of the second network. 8. The relay device according to 8. A monitoring execution unit for monitoring the second server in the third network;
A failure determination unit that determines whether or not a failure has occurred in the second server during monitoring of the second server by the monitoring execution unit;
The output processing unit, when it is determined by the failure determination unit that a failure has occurred, includes the failure information of the second server and the first network information that defines transfer within the first network. The relay apparatus according to claim 6, wherein the third data including the data is output to the first network. A failure notification method by a failure notification system comprising: a monitoring device that monitors a server; and a relay device that is connected to the monitoring device through a first network and that is connected to a terminal device through a second network,
The monitoring device
When detecting a failure of the server, the server generates first data including failure information of the server and first network information indicating that a transfer destination is in the first network, and Execute the first output process to output to the network,
The relay device is
An input process for receiving an input of the first data from the monitoring device via the first network;
When the first data is input by the input process, the first network information is replaced with second network information indicating that the transfer destination is in the second network, thereby A conversion process for converting data into second data;
Second output processing for outputting the second data to the terminal device via the second network in accordance with the second network information included in the second data converted by the conversion processing; ,
A failure notification method characterized by executing: