JP6612151B2 - Network equipment monitoring device - Google Patents

Description

  The present invention relates to a monitoring device for a device connected to a network, and particularly to a device having an automatic power supply restart function.

  The number of network communication devices (hereinafter referred to as network devices) connected to the network and the Internet is increasing day by day. Security is added to DHCP for providing flexible connectivity to devices connected to the network, HTTP for providing information to unspecified large numbers connected to the network, SNMP for monitoring network devices, and TCP The number of applications provided for providing services such as SSL is increasing day by day.

  These services are provided by being connected to a physical port (physical layer) of a network device. These physical ports are assigned a MAC address (data link layer) and an IP address (network layer). Each service (application) is assigned a port number (transport layer), and a service is provided by sending a request to the MAC address, IP address, and port number. The most famous port number would be “80” assigned to the HTTP server.

  In the past, one server was often assigned to each of these services. In such a state, there is one port number for each physical port, and an ICMP (Internet Control Message Protocol) PING command corresponding to the network layer is used to check whether the service is provided without any delay. I should have seen if a response was returned using. Even now, the PING command is often used for monitoring network devices.

  Regarding the PING command, the IPv4 ICMP protocol is defined by RFC 792 (Non-Patent Document 1), and the IPv6 ICMP protocol is defined by RFC 4443 (Non-Patent Document 2).

RFC 792 RFC4443

  However, it is now common for multiple services to be implemented on a single server due to the increased processing capacity of the server. In such a case, even if the physical port is open, if the program corresponding to the specific port number has dropped, it may be necessary to determine whether to perform the reactivation process.

  In other words, even if the program corresponding to a specific port number is running, if the service used in the previous stage of providing that service is down, the restart process is performed to restart the down service. It may be necessary to do

The purpose of the present invention is not only to confirm the existence of a physical port, but also to confirm that the service of a specific port number is operating normally, and to restart the server on which that service operates in the processing when an abnormality is detected It is to provide means for enabling processing.
Another object of the present invention is to provide means for deciding whether or not to perform re-operation processing based on a port number.

  Still other objects and advantages of the present invention will become apparent from the following description.

  A network device monitoring apparatus according to the present invention monitors a network device according to a protocol of a network layer and a transport layer, and performs processing when an abnormality is detected in the network layer and processing when an abnormality is detected in the transport layer. It is characterized by being different.

  In this network device monitoring device, the network device monitoring device includes a CPU, a relay controller, and a relay controlled by the relay controller. The relay controller controls the relay so that the CPU controls the relay as a process when an abnormality is detected in the transport layer. It may be characterized by instructing.

  In this network device monitoring apparatus, a relay may control power supply.

  In this network device monitoring apparatus, the relay may control power supply to the network device.

  These network device monitoring devices may have a means by which a user can change the process when the abnormality is detected.

Another network device monitoring apparatus according to the present invention is a network device monitoring apparatus that monitors a network device according to a protocol of a network layer and a transport layer,
The network device monitoring apparatus is characterized in that it can separately and independently monitor anomalies of two or more applications using one network layer and using different transport layers.

With the network device monitoring apparatus according to the present invention, it is possible to change processing at the time of abnormality detection for each network layer and transport layer. More specifically, when an abnormality is detected in the network layer, the network device to be detected is restarted by turning on / off an appropriate relay of the network device monitoring apparatus, and the abnormality is detected in the transport layer. If it is detected, it may be possible to make corrections in service units.
In addition, the network device monitoring apparatus according to the present invention allows the user to arbitrarily change the process when an abnormality is detected in the network layer and the transport layer.

It is a conceptual diagram showing the physical electrical structure of the network equipment monitoring apparatus in connection with this invention. It is a connection diagram showing an example of the operating environment of the network device monitoring apparatus according to the first embodiment. It is a flowchart explaining the outline of operation | movement of the monitoring module which CPU processes on a network equipment monitoring apparatus. It is a flowchart showing the flow of a process for a network equipment monitoring apparatus to disclose a user's setting information and the condition of the present monitoring object to a user. This is a result of displaying output data sent to the transmission source of the disclosure request (Request) on the browser of the terminal after performing the processing of FIG. 4 in the first embodiment. It is a flowchart showing the flow of a process for a network device monitoring apparatus to reflect the change of own setting information. It is a figure showing the screen for monitoring in a 1st embodiment. It is a connection diagram showing an example of the operating environment of the network device monitoring apparatus according to the second embodiment. This is the result of displaying the output data sent to the transmission source of the disclosure request (Request) in the second embodiment on the browser of the terminal.

  Embodiments of the present invention will be described below with reference to the drawings.

(First embodiment)
(Hardware description)
FIG. 1 is a conceptual diagram showing a physical and electrical configuration of a network device monitoring apparatus according to the first embodiment of the present invention.

  A network device monitoring apparatus 100 according to the present invention includes a CPU 101, a bus controller 102, a memory 201, a peripheral bus controller 202, a LAN I / F 301, an LED controller 302, a relay controller 303, relays 311, 312, 313, outlets 321, 322, 323.

  The CPU 101 is a central control device that performs processing according to a program recorded in the memory 201. In this specification, the CPU is used, but there is no problem with the MPU. Although the number of CPU cores in the so-called CPU 101 is not limited, it is preferable to support pseudo multitasking by time division.

The bus controller 102 is a chip set through which the CPU 101 accesses the memory 201 and the like.

  Due to its nature, the bus controller 102 is connected to the internal bus a and the external bus b, and controls communication from the CPU 101 with a controller or the like existing in the external bus b and the peripheral bus c.

  In the market, a product (dedicated product) is prepared for the bus controller 102 corresponding to the type of the CPU 101. However, it is only necessary that the CPU 101 can communicate with the controller or the like existing in the external bus b and the peripheral bus c.

  The memory 201 is a memory for recording a program executed by the CPU 101 and data to be processed (such as setting of a network device monitoring apparatus). Normally, it can be divided into a volatile memory element such as DRAM and a nonvolatile memory element such as NVRAM that is retained even when the power is turned off, and ROM (Read Only Memory), but this specification includes all Thus, the memory 201 is obtained.

The peripheral bus controller 202 is a chip set that is used when the CPU 101 or the like controls a controller on the peripheral bus c from the external bus b.
Like the bus controller 102, the peripheral bus controller 202 is connected to the external bus b and the peripheral bus c. The peripheral bus controller 202 controls communication from the CPU 101 with a controller or the like existing in the external bus b and the peripheral bus b.
In the market, a product (dedicated product) is also prepared for the peripheral bus controller 202 corresponding to the type of the CPU 101. However, in this embodiment, it is only necessary to be able to communicate with the CPU 101 and the controller existing on the peripheral bus.

  The LAN I / F 301 is an interface group including a connector (physical layer) and a chip (data link layer, network layer) for connecting to the HUB 500. Communication with other network devices is performed via the LAN I / F 301. Needless to say, the LAN I / F 301 must be connectable to the HUB 500.

  When there are a plurality of LAN I / Fs 301, an IP address is assigned to each LAN I / F. Therefore, it should be noted that when the network device monitoring apparatus 100 has two ports, a wireless LAN and a wired LAN, an IP address is assigned to each.

  The LED controller 302 is a controller for controlling the LED for transmitting the status of the network device monitoring apparatus 100 to the user. Although not shown in the figure, the LED controller 302 is connected to an LED (not shown) and lights up and blinks to inform the user of the state of the network device monitoring apparatus 100.

  The relay controller 303 is a controller for controlling the relays 311, 312, and 313. The minimum required number of relays to be controlled is determined according to the product specifications of the network device monitoring apparatus 100. The relay controller 303 has a register according to the number of relays. The CPU 101 has a structure in which 1/0 is written to a corresponding register in the relay controller 303 to turn on / off the corresponding relay and control power supply to the corresponding outlet. However, the present invention is not limited to this, and if a means capable of controlling the relay by any method can be provided, the role of the relay controller 303 can be achieved.

  Relays 311, 312, and 313 are relays for controlling power supply from the power source to the outlet. The relays 311, 312, and 313 are configured such that power supply to the corresponding outlets can be controlled independently by a control signal from the relay controller 303.

  The outlets 321, 322, and 323 are outlets for supplying power from the network device monitoring apparatus 100 to the network device to be monitored. Each outlet can be controlled by the CPU 101 by being connected to a corresponding relay.

  Note that if the network device to be monitored is not properly connected to the outlet, an error will occur in the network device, and the network device will be turned off when the power is turned off. Connection and network device monitoring apparatus 100 should be set.

Next, a connection method of the network device monitoring apparatus 100 will be described with reference to FIG.
FIG. 2 is a connection diagram showing an example of the operating environment of the network device monitoring apparatus 100 according to the first embodiment of the present invention.

  In this figure, a network device monitoring apparatus 100, a router 501, an HTTP server 502, a settlement server 503, and a monitor PC 504 are connected to the HUB 500, and each is configured to be able to communicate at the network layer level.

  The power cables of the router 501, the HTTP server 502, and the settlement server 503 are connected to the outlets 321, 322, and 323 of the network device monitoring apparatus 100, respectively, from which power for operating the devices is supplied.

  The router 501 is a network device that relays transmission of information to the Internet or reception of information from the Internet. Normally, the router 501 manages the connection to the network layer of the OSI seven-layer model, but in the present embodiment, it may provide a higher-layer service.

  The HTTP server 502 transmits homepage information (mainly written in HTML format) to unspecified terminals on the Internet. Normally, the user is guided to the settlement server 503 by being guided from the homepage information transmitted by the HTTP server 502.

  The settlement server 503 is a server for performing payment settlement for communicating and managing credit card information when providing products from the Internet.

  The monitor PC 504 is a PC for monitoring the status of the network device monitoring apparatus 100. It is assumed that the browser can operate on this PC. In addition, the network device monitoring apparatus 100 must generate and output data (FIGS. 5 and 7 to be described later) that can be displayed by a browser operating on the monitor PC 504.

  Usually, the user is guided from a home page described in the HTML format and receives the service of the settlement server 503. For this reason, when the HTTP server 502 is down, the user cannot use the settlement server 503 in most cases. Therefore, when only the payment server 503 is active and the other routers 501 and the HTTP server 502 are down, the significance of the operation of the payment server 503 decreases.

(Software description)
(Monitoring network devices)
In the following, the operation of software operating on the network device monitoring apparatus 100 will be described with the configurations of FIGS. 1 and 2 in mind.

  FIG. 3 is a flowchart for explaining an outline of the operation of the monitoring module configured by software processed by the CPU 101 on the network device monitoring apparatus 100. This monitoring module operates on the CPU 101. The network device monitoring by the network device monitoring apparatus 100 in the present embodiment is realized by so-called polling.

  When the network device monitoring device 100 is activated or reset, the OS on the network device monitoring device performs various pre-processing and then activates the monitoring module (step S10).

  When the monitoring module is activated, initialization processing (step S11) is performed. In the initialization process, a necessary memory amount is secured, an IP address and a port number to be monitored are specified, and a waiting time (polling cycle) in step S14 to be described later is performed. However, the initialization process is not necessarily limited thereto.

  When the start process of the monitoring module is performed, monitoring of the monitoring target by the monitoring module is started. The monitoring module sends a command (hereinafter referred to as a TELNET command) by designating a specific port using an ICMP PING command (step S12) and TELNET (step S13). In this case, if the PING command is abnormally terminated, the TELNET command may not be transmitted, or the TELNET command may be transmitted regardless of the termination state of the PING command. These are design matters.

  If the process ends abnormally in steps S12 and S13, an interrupt process corresponding to each is called. Since it is an interrupt, when the interrupt process ends, the process returns to the place where the interrupt process occurred and the process of the monitoring module is resumed.

  Here, as an interrupt process, the CPU 101 writes 1/0 to an appropriate register of the relay controller 303 that controls the power supply to be monitored. Thereby, the supply of power to the corresponding outlet can be resumed (connected) / disconnected. As a result, it is possible to turn on / off the power supply of the network device to be monitored.

  It is also conceivable that the CPU 101 records a log indicating that the relay relay has turned on / off a specific relay. This is because the log is essential information for the user for trouble analysis.

  Here, the processing contents of the interrupt processing in step S12 and the interrupt processing in step S13 may be changed. For example, if the process ends abnormally in step S12, it is highly necessary to restart each server. However, in the case of abnormal termination in step S13, the hardware function (physical layer or data link layer) to be monitored is not necessarily lost. Therefore, in such a case, the processing may be such that only the service related to the port corresponding to the server is restarted.

  When the transmission of the PING command and the TELNET command is completed, the system waits for the standby time set in the initialization process (step S11) (step S14).

  It is assumed that this waiting time uses the “waiting seconds” in FIG. 5 described later as it is, but the processing time in steps S12 to S14 is subtracted from the processing times in steps S12 and S13. May be handled.

Thereafter, the processing returns to step S12, and the processing from step S12 to step S14 is repeated until the power of the network device monitoring apparatus 100 is turned off or reset.
(Change network device settings)

  Next, the setting change read out in the initialization process (step S11) will be described.

  First, the network device monitoring apparatus needs to disclose to the user what the current settings are. This is because it is impossible to determine whether or not to change the setting unless the current state is known. The information disclosure process will be described with reference to FIG.

  FIG. 4 is a flowchart showing a flow of processing for the network device monitoring apparatus 100 to disclose its setting information and the current monitoring target status to the user. FIG. 5 shows a result of displaying the output data sent to the transmission source of the disclosure request (Request) on the browser of the terminal after performing the processing of FIG. 4 in the first embodiment.

  In this embodiment, it is assumed that the browser on the monitor PC 504 outputs HTML format data. Therefore, it is assumed that the network device monitoring apparatus 100 generates HTML format data unless otherwise specified.

  First, a setting information disclosure request (Request) is transmitted from the monitoring PC 504 to the network device monitoring apparatus 100 (step S20). For this disclosure request, a method is considered in which an HTTP request is made by adding a necessary parameter (for example, which setting to be monitored is changed) to the IP address assigned to the network device monitoring apparatus 100. It does n’t matter.

  In the output data of this figure, it is assumed that the disclosure request of the monitor PC 504 is transmitted from the HUB 500 of FIG. 2 through the LAN I / F 301 of FIG.

  Receiving the disclosure request in step S20, the CPU 101 of the network device monitoring apparatus 100 reads its own settings (monitoring target IP address, port number, waiting number of seconds, etc.) from the non-volatile area on the memory 201 (step S21). .

  Further, the CPU 101 collects information on the current state of the network device to be monitored, if necessary, based on the setting read in step S21 to display the current state of the monitoring target (step S22). At this time, not only the PING command and the TELNET command as performed in step S12 and step S13 in FIG. 3, but also data collection using SNMP may be performed.

  The CPU 101 generates output data that summarizes the setting information obtained in step S21 and the current state of the monitoring target obtained in step S22 (step S23). If a dedicated application is prepared on the terminal side and displayed on the application, what is generated in step S23 is data dedicated to the application.

  In FIG. 5, since there is no item for displaying the status of the monitoring target, the result of step S22 is not reflected in the data.

  The generated output data is returned to the sender of the disclosure request (Request) (= monitoring PC 504) (step S24). Based on the output data, the monitor PC 504 that is the transmission source of the disclosure request (Request) displays the output data with a browser or the like.

1 and 2, the output data generated by the CPU 101 is returned from the LAN I / F 301 in FIG. 1 to the monitor PC 504 via the HUB 500 in FIG.

Next, the format of the output data that is actually displayed will be described.
As described above, FIG. 5 displays the output data sent to the sender of the disclosure request (Request) on the browser of the monitor PC 504 after performing the processing of FIG. 4 in the first embodiment. It is a result. In other words, the items displayed in this drawing are the items whose settings of the network device monitoring apparatus 100 can be changed.

The display screen of FIG. 5 includes a monitoring target designation column 410, a monitoring valid setting column 420, a detailed setting column 430, and a setting save button 440.

  The monitoring target designation column 410 is a column for designating which of the monitoring targets of the network device monitoring apparatus 100 is set. There is an upper limit to the number of monitoring targets depending on the product specifications of the network device monitoring apparatus 100. These monitoring targets are managed by being numbered uniquely. In other words, there are “monitoring object 2”, “monitoring object 3”, and “monitoring object n” (n = the upper limit value of the number of monitoring objects) other than “monitoring object 1” displayed on the screen of FIG.

  A monitoring target designation column 410 is a pull-down menu for designating the monitoring target.

The monitoring effective setting column 420 is a column that defines whether or not to enable the monitoring. The higher the processing capacity of the CPU 101, the higher the product price of the network device monitoring apparatus 100. Further, as the number of monitoring targets increases, the number of data (= number of packets) flowing on the network increases. However, if unnecessary processing is cut, it is not necessary to purchase expensive products, and the number of packets flowing for monitoring on the network can be reduced.
Also, it is assumed that the responses in step S12 and step S13 are clearly abnormal, such as when the HTTP server 502 or the settlement server 503 is restarted. In such a case, restarting is repeated by repeatedly turning the power ON / OFF, and these servers do not operate normally.

  In such cases, checking the dialog box in the monitoring valid setting column 420 temporarily disables monitoring, and enables smooth use of the system.

  The detailed setting column 430 is a column for setting details of the actual monitoring target device such as the IP address and port number of the monitoring target.

  The monitoring condition setting field 431 is provided with a plurality of text areas and check boxes in which essential items for determining the monitoring target and operating conditions can be input.

  An “IP address” text box in the monitoring condition setting column 431 is a column for defining an IP address to be monitored. The “port number” text box is a column for defining the port number to be monitored. If at least these two cannot be specified, the transport layer cannot be monitored, so this is an indispensable item.

  The “waiting seconds” text box in the monitoring condition setting column 431 is a column for determining the waiting time in step S14 of FIG. If this waiting time is short, more real-time monitoring can be performed, but if the monitoring frequency is high, many related packets are output on the network. This field is necessary to let the user define this balance. In other words, this column is not necessary when the user is not allowed to define the number of waiting seconds.

  The “port check only” check box in the monitoring condition setting column 431 is a column for determining whether or not step S12 in FIG. 3 is omitted. When the PING command is output for another monitoring target, step S12 is an overlapping process. Therefore, when step S12 is omitted for the monitoring target, this column is checked.

  The name column 432 is a text box for displaying the monitoring target so as to be easily understood by the user. The memo column 433 is a text box for the user to leave a comment regarding the monitoring target. These are not indispensable items, but they are also adopted in this embodiment because they are convenient for daily operation.

  The setting save button 440 is a button for transmitting the items described in each column when this button is pressed to the network device monitoring apparatus 100 that is the output data transmission source.

  In the present embodiment, it is assumed that the output result is described in HTML (Hyper Text Markup Language) so as to be displayed on a browser. Therefore, the data is generated so that the main part of the data is surrounded by <FORM> </ FORM> tags. Between these tags, an input field is provided using tags such as <INPUT> <SELECT> <TEXTAREA>.

  In the monitoring target designation column 410 of FIG. 5, pull-down tags (<SELECT> <OPTION> tags) are used, but these must be programmed to be generated by the CPU 101 in step S23.

  Similarly, an “IP address” text box, a “port number” text box, and a “waiting second” text box in the monitoring condition setting field 431 are text boxes and their initial values (for example, FIG. 5). As for the “port number”, it is necessary to prepare <INPUT type = “text” value = “5901” name = “port”> tag) at the generation time of the CPU 101 (step S23). These initial values are obtained from the own settings read in step S21.

  Further, by activating the “PORT check only” check box in FIG. 5, step S12 (PING command) in FIG. 3 can be omitted. Such display needs to be performed so that the CPU 101 can display in step S23 (for example, <INPUT type = “Checkbox” name = “check”> tag). This data is also defined from the settings of the network device monitoring apparatus 100 itself read out in step S21.

In addition, display data should be configured with a <FORM> tag so that data that can be input by the user on this display screen can be sent back to the network device monitoring apparatus 100 by pressing the setting save button 440.

  At this time, it is necessary for the CPU 101 to define an address to be accessed when the setting save button 440 is pressed. In this way, the setting of the network device monitoring apparatus 100 can be changed by simply pressing the setting save button 440 without the user inputting an incorrect address.

  In this way, the network device monitoring apparatus 100 prepares a method for transmitting the display format and the corrected data, and sends back to the transmission source of the disclosure request (Request) in that state, thereby restricting the input value to a certain limit. It can be multiplied.

  Of course, the CPU 101 of the network device monitoring apparatus 100 needs to change the setting based on the returned information.

FIG. 6 is a flowchart showing the flow of processing for the network device monitoring apparatus 100 to reflect the change of its own setting information.

  As can be seen from the comparison between FIG. 4 and FIG. 6, there is no significant difference between the case of reading and the processing even when the setting is changed. The difference is that not only address information but also data is sent to the network device monitoring apparatus 100 (step S30), and the CPU 101 is stored in a non-volatile area on the memory 201 reflecting this data. Only the process of changing the set value (step S31) is entered.

  After this setting is changed, its own setting (monitoring target IP address, port number, polling cycle, etc.) is read from the non-volatile area on the memory 201 after the setting change (step S21). Information on the current state of the network device is collected (step S22), the CPU 101 generates output data (step S23), and returns a response (step S24).

That is, if the setting is changed, the status of the network device monitoring apparatus 100 for the designated monitoring target is displayed again on the terminal unless the browser is closed.
(List display)

  Finally, the operation of the software that transmits the list of monitoring targets to the monitoring PC will be described.

The display of the list of monitoring targets is basically the same as the processing in FIG. However, it is “monitoring”, there is no need to change the setting, the entire list needs to be updated periodically, and the monitor PC 504 periodically performs communication in a request-response format such as HTTP. Display data created by the CPU 101 needs to be changed.

  FIG. 7 is a diagram illustrating a monitoring screen according to the first embodiment.

  In the output data of the setting screen of FIG. 5, only the setting object was displayed due to its nature. However, when performing normal monitoring, it is preferable that all monitoring targets can be seen. Therefore, the monitoring screen excludes the setting change function and focuses on all the monitoring targets.

  In FIG. 7, columns 710, 720, and 730 are allocated for each monitoring target. Each column includes items of a “name” column, an “IP: Port” column, and a “status” column. Among these, “name” and “IP: Port” represent settings, and “state” represents the state of the monitoring target.

  It should be noted that even if the IP addresses are the same, the network device monitoring apparatus 100 is handled as a separate independent monitoring target when the port numbers are different. As a result, even if the IP address is the same, different handling is possible when the port number is different. This is convenient for the user, and will be described in the second embodiment.

  The “name” column is a column for displaying a name given to the monitoring target by the user defined in the name column 432 of FIG. Of course, if the user cannot define the name, this field will be omitted.

  The “IP: Port” column is a column for displaying the IP address and port number defined in the monitoring condition setting column 431 of FIG.

  The “status” column is a column that indicates the status of the monitoring target. The “status” column is roughly divided into two, and items that are periodically grasped by the network device monitoring apparatus 100 are described in the upper section as indicators. In the lower part, the state estimated by the network device monitoring apparatus 100 is displayed.

  “ON” in the upper part of the “Status” column indicates whether the corresponding relay of the network device monitoring apparatus 100 is in a connected state, that is, whether the power source is connected to the server. This is determined by looking at the corresponding register of the relay controller 303.

  “ON” is displayed as an indicator. That is, the background is displayed in green if the relay is in a conductive state, and the background is displayed in gray if the relay is not conductive.

  “PI” in the upper part of the “status” column indicates whether the processing of the PING command in step S12 in FIG. 3 has been normally performed. This reflects the processing result of step S12 in FIG. When step S12 is omitted in the monitoring (= when only “port check” in the monitoring condition setting field 431 in FIG. 5 is checked), the description is different from the normal one as in column 730. However, the background color when “PI” is not implemented may be displayed in the same manner as the failure.

  “PO” in the upper part of the “Status” column indicates whether the processing of the TELNET command in Step S13 in FIG. 3 has been normally performed.

  “PI” and “PO” are displayed as indicators. In other words, the background is green if it is operating normally, the background is gray if it ends abnormally, and if the process itself is omitted, it is painted black. preferable. In FIG. 7, “PI” in the column 730 is represented by being painted.

  The lower part of the “Status” column indicates how the current network device monitoring apparatus 100 is responding. The matter displayed here may be anything, but it should have a certain rule and disclose it to the user.

  The processing on the CPU 101 side when outputting the display screen in FIG. 7 is the same as the flowchart in FIG. Whether to transmit the data for displaying the screen of FIG. 5 or the data for displaying the screen of FIG. 7 may be determined by the parameter added to the disclosure request sent in step S20 of FIG.

  In addition, if the self-address is automatically read again after a predetermined number of seconds from the output data to be transmitted, the state can be updated repeatedly. In the HTML format, such a function can be realized by using a <META> tag.

  In this way, it is possible to improve user convenience by repeating the display of the setting state of the network device monitoring apparatus 100.

As described above, it is possible to detect the failure in the transport layer in parallel with the detection of the failure in the network layer, and to make the interrupt processing after detecting the abnormality different at that time, thereby making the situation more It is possible to recover from abnormal conditions.
(Second Embodiment)

  Next, a second embodiment of the present invention will be described with reference to the drawings.

  In the first embodiment, interrupt processing is not defined by the user's intention. However, depending on the IP address and port number, it is often convenient for the user to operate the interrupt process in a programmable manner. In particular, when a plurality of services are provided by the same server, such an advantage is remarkable.

  That is, the IP address is used in common for all services on the same server. Therefore, it is preferable to restart the entire server as soon as a failure occurs in the network layer. However, even if a problem occurs with a certain port number, it is also possible that an application that provides a service with a different port number is active. In such a case, it is not always appropriate to suddenly turn off the power.

  Therefore, an object of the present embodiment is to provide means for enabling a user to set an interrupt processing operation by an IP address or a port number.

  FIG. 8 is a connection diagram illustrating an example of an operating environment of the network device monitoring apparatus 100 according to the second embodiment. Note that description of portions that are not changed from FIG. 2 is omitted.

  Unlike the first embodiment, this embodiment has a configuration in which an HTTP application and a payment application are installed in a single server 600. Accordingly, the HTTP server 502 and the settlement server 503 are deleted. In recent years, the processing capability of servers has been dramatically improved, and thus it is often the case that an application including processing of a plurality of transport layers to application layers is always executed on a single server.

  By adopting such a configuration, it is conceivable that either the HTTP application or the payment application is dropped even if the network layer of the server 600 is alive. In this case, it may not be appropriate to perform the power supply restart process in all situations.

  The present embodiment is characterized in that the processing contents of the interrupt processing (see FIG. 3) of the network device monitoring apparatus 100 are defined by the user.

FIG. 9 shows the result of displaying the output data sent to the transmission source of the disclosure request (Request) in the second embodiment on the browser of the monitor PC 504.

  In FIG. 9, in addition to the display of FIG. 5, the items of action 810 and action setting 820 are increased.

  By selecting an item in the pull-down menu displayed in action 810, the user can freely select up to four rough processes. Although the number is four according to the specification, the maximum number of user-defined operation definitions depends on the intention of the designer of the network device monitoring apparatus 100.

  In FIG. 9, only the options of power ON (action 2), power OFF (action 1), and “logging” (action 3) are described. For example, “confirm operation of another module” or “the server It can also be thought of as adding an action type such as “instructing restart of the port corresponding to“ ”.

  In accordance with the item selected in the action 810, the user can select a detailed operation in the action setting 820.

  If no action is selected, even if the application related to the monitored port is abnormally terminated, it is possible to stop interrupt processing at all. It is a feature of the present embodiment that the judgment can be left to the user.

  In the action setting 820 of FIG. 9, the sub setting item corresponding to the power OFF currently selected in the action 1 is displayed. Here, it is possible to input the number of standby seconds until the power is turned off and the number of standby seconds until the next action is executed after the power is turned off.

  As described above, the priority of services can be increased by combining and monitoring up to the port number (transport layer) in the first embodiment and allowing the user of the second embodiment to freely define interrupt processing. The corresponding interrupt processing can be set.

  This will be described with reference to the example of FIG. On the server 600, the payment application and the HTTP application are running simultaneously. Although it is difficult to compare the superiority and inferiority of the HTTP application and the payment application in the actual environment, here, the HTTP application that needs to be sent out immediately if there is a request is preferential.

  In this case, if the HTTP application goes down and the TELNET command for the corresponding port (80 in Wellnon) ends abnormally, the relay 311 corresponding to any one of the outlets 321, 322, and 323 connected to the power cable corresponding to the server 600. , 312, and 313 are set to be turned on again after being turned off and restarted.

  On the other hand, even if the TELNET command for the payment application port ends abnormally, if the HTTP application port is alive, priority is given to the transmission of information by the HTTP application, so only log accumulation is performed. In the example of this is considered.

  Regarding the processing on the network device monitoring apparatus 100 side, the CPU 101 defines action-related variables and default values in step S23 (see FIG. 4), and the CPU 101 corrects these variables in step S30 (see FIG. 6). If it can be received (= adding a processing module), it can be handled, so it will not be described in detail here.

  As described above, by providing means for changing the processing method according to the user's intention according to the IP address and port number, it becomes possible to perform a restart process more effective for the user.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiments. However, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the invention. Needless to say.

  The present invention is applicable to a monitoring apparatus for network equipment. Needless to say, not only routers, accounting servers, and HTTP servers, but also other network devices may be monitored.

100 network equipment monitoring device,
101 CPU,
102 bus controller,
201 memory,
202 peripheral bus controller,
301 LAN I / F,
302 LED controller,
303 relay controller,
311, 312, 313 relay,
321, 322, 323 outlets,
500 HUB,
501 router,
502 HTTP server,
503 payment server,
504 PC for monitor,
600 servers.

Claims (3)

The transport layer of the connected monitor network layer logical port and the identity related to the network layer of the network devices of interest monitored network device via the LAN to the according to the network layer and the transport layer protocol OSI7 layer model A network device monitoring device that monitors the transport layer logical ports involved,
The network device monitoring device includes a CPU, a relay controller, and a relay controlled by the relay controller,
The processing in the network device monitoring device when an abnormality is detected in the network layer logical port is to disconnect the relay;
A network device monitoring apparatus, characterized in that the processing in the network device monitoring apparatus when an abnormality is detected in the transport layer logical port does not disconnect the relay . The transport layer of the connected monitor network layer logical port and the identity related to the network layer of the network devices of interest monitored network device via the LAN to the according to the network layer and the transport layer protocol OSI7 layer model A network device monitoring apparatus for monitoring a first transport layer logical port involved and a second transport layer logical port involved in the transport layer ,
The network device monitoring device includes a CPU, a relay controller, and a relay controlled by the relay controller,
Processing at the network device monitoring device upon detection of an abnormality in the first transport layer logical port disconnects the relay;
The network equipment monitoring apparatus, wherein the processing in the network equipment monitoring apparatus when an abnormality is detected in the second transport layer logical port does not disconnect the relay . In the network equipment monitoring device according to claim 1 or 2,
A network device monitoring apparatus, wherein power is supplied to the network device to be monitored via the relay.

Images