JP6015056B2 - Network management system, network management method, network monitoring system, and network management program - Google Patents

Description

  The present invention relates to a technical field of a network management system, a network management method, a network monitoring system, and a network management program.

  An example of a network monitoring system is disclosed in Patent Document 1, for example. The network monitoring system of Patent Document 1 includes one network management system, a plurality of management agents placed at each base, and a plurality of communication devices (routers, switches, etc.) to be monitored at each base. ), And a network management system and a wide area communication network connecting each base, and operates as follows.

  The management agent collects the status of communication devices in a specific site and manages them as the status of the management agent. The management agent notifies them to the network management system as the status of the management agent.

  The network management system manages all communication devices by monitoring one management agent at each site. Further, the network management system issues an instruction with a predetermined signal to a management agent placed at each site. Upon receiving the instruction, the management agent controls all communication devices existing in the specific base.

JP 2008-117096 A

  However, the technique disclosed in Patent Document 1 has a problem that a dedicated device for the management agent is required.

  In addition, the technique disclosed in Patent Document 1 has a problem that the processing load of the management agent cannot be dynamically adjusted when the number of communication devices increases. The reason is that one management agent is placed at each site.

  The object of the present invention is to solve the above-described problems that the device dedicated to the management agent is necessary and the problem that the processing load of the management agent cannot be adjusted dynamically when the number of communication devices increases. A management system, a network management method, a network monitoring system, and a network management program are provided.

  The network management system of the present invention can provide a route acquisition means for acquiring a route from a network management system to a managed network node and a service other than network management, and can operate as a network management manager proxy for the network management system. A management agent selection means for selecting a network management manager proxy and a server to be actually operated as a network management agent proxy from a plurality of servers capable of operating as a network management agent proxy of a managed network node; and the management agent And a network management manager that operates as a network management manager for the server selected by the selecting means.

  The network monitoring system of the present invention can provide a route acquisition means for acquiring a route from a network management system to a managed network node and a service other than network management, and can operate as a network management manager proxy for the network management system. A management agent selection means for selecting a network management manager proxy and a server to be actually operated as a network management agent proxy from a plurality of servers capable of operating as a network management agent proxy of a managed network node; and the management agent One or more network management systems comprising: a network management manager that operates as a network management manager for the server selected by the selection means; A plurality of servers that provide services other than network management, can operate as a network management manager proxy for a network management system, and can operate as a network management agent proxy for a managed network node; And a plurality of routers including a network management agent that can operate as a network management agent.

  The network management method of the present invention provides a route acquisition step for acquiring a route from a network management system to a managed network node and a service other than network management in a network management agent management method by a network management manager. A server that can operate as a network management manager proxy of the system, and can operate as a network management agent proxy of a managed network node, and can actually operate as the network management manager proxy and the network management agent proxy from a plurality of servers. And a management agent selection step of selecting.

  A network management program according to the present invention provides a route acquisition procedure for acquiring a route from a network management system to a managed network node in a network management program of a network management agent by a network management manager, and services other than network management. A plurality of servers that can operate as a network management manager proxy of a management system and can operate as a network management agent proxy of a managed network node, and actually operate as the network management manager proxy and the network management agent proxy. And a management agent selection procedure for selecting a server.

  According to the present invention, there is no need for a dedicated device for the management agent, and it becomes possible to dynamically adjust the processing load of the management agent even when the number of communication devices increases.

It is a block diagram which shows the structure of the network monitoring system in embodiment of this invention. It is a flowchart explaining operation | movement of the network management system in embodiment of this invention. It is a figure which shows an example of the network connection state in embodiment of this invention. It is a figure which shows an example of the path | route table in embodiment of this invention. It is a flowchart explaining operation | movement of the management agent selection means of the network management system in embodiment of this invention. It is a figure which shows an example of the path | route table in embodiment of this invention. It is a figure which shows an example of the network connection state in embodiment of this invention. It is a figure which shows an example of the network connection state in embodiment of this invention. It is a figure which shows an example of the path | route table in embodiment of this invention. It is a figure which shows an example of the network connection state in embodiment of this invention. It is a figure which shows an example of the path | route table in embodiment of this invention. It is a figure which shows an example of the network connection state in embodiment of this invention. It is a figure which shows an example of the path | route table in embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In all the drawings, the same reference numerals are given to the same components, and the description will be omitted as appropriate.

  FIG. 1 is a block diagram showing a configuration of a network monitoring system according to an embodiment of the present invention.

The network monitoring system in this embodiment includes a network management system 100 and a monitoring target network 200.
The network management system 100 includes an SNMP manager 120, a route acquisition unit 130, and a management agent selection unit 140.

  The monitoring target network 200 includes one or more routers 300 (300, 301, 302, 303), one or more servers 500 (500, 501, 502, 503), and other network nodes (not shown). Yes. Here, as an example, four routers and four servers are illustrated.

  Each of the routers 300 and the like includes SNMP (Simple Network Management Protocol) agents 310 and the like (310, 311, 312 and 313). In addition, other network nodes not shown include SNMP agents.

  Each of the servers 500 and the like includes an SNMP agent 510 and the like (510, 511, 512, and 513) and an SNMP manager 520 and the like (520, 521, 522, and 523).

  The SNMP managers 120 and 520 and the like are means for transmitting a management operation request to the SNMP agent, receiving a trap from the SNMP agent, and the like.

  The SNMP agents 310, 510, etc. are means for transmitting a management operation response to the SNMP manager, transmitting a trap to the SNMP manager, and the like.

  The server 500 or the like is a server computer that operates as an SNMP agent or an SNMP manager and provides other services at the same time. The server 500 or the like can operate as a management agent. The management agent is a network node that operates as an SNMP manager for a lower SNMP agent and also operates as an SNMP agent that acts as a proxy for the lower SNMP agent for a higher SNMP manager. Since the server 500 and the like can operate as a management agent, they are management agent candidates.

  Here, as an example, a case where the server 500 and the server 502 are selected as management agents is illustrated. In the following, in the figure, servers surrounded by a wavy line indicate servers selected as management agents.

  The upper SNMP manager of the server 500 is the SNMP manager 120 of the network management system 100. The lower level SNMP agents of the server 500 are the SNMP agent 511 of the server 501, the SNMP agent 310 of the router 300, and the SNMP agent 311 of the router 301. The upper SNMP manager of the server 502 is the SNMP manager 120 of the network management system 100. The SNMP agents below the server 502 are the SNMP agent 513 of the server 503, the SNMP agent 312 of the router 302, and the SNMP agent 313 of the router 303.

  The management agent selection means 140 is a means for selecting a management agent from management agent candidates.

  The route acquisition unit 130 includes an identifier (for example, IP address, host name, FQDN (Fully Qualified Domain Name), etc.) of a transit node (router) on a network path from one network node to another network node. A list of addresses). The route acquisition unit 130 includes, for example, traceroute, which is a route information acquisition tool.

  The router 300 is a communication device that interconnects two or more different network segments.

  Next, the operation of this embodiment will be described.

  FIG. 2 is a flowchart for explaining the operation of the route acquisition unit 130 of the network management system according to the embodiment of the present invention.

  First, the route acquisition unit 130 creates an empty route table (step S110). The route table has one record for each route from a network node as a starting point to a network node as a destination point. Each record in the routing table has an identifier (IP address, etc.) of the network node that is the arrival point in the first column, and a value (0: unselected state, 0) indicating whether the record is selected in the second column. Other than: selected state) has the identifiers (IP addresses, etc.) of each network node on the route in the third and subsequent columns.

  The route acquisition unit 130 executes the following processing for all management agent candidates (step S120 to step S170).

  The route acquisition unit 130 searches for a route from the network management system 100 to the management agent candidate for a certain management agent candidate (step S130).

  If there is a route (Yes in step S140), the route acquisition unit 130 adds a row to the route table, and sets the management agent candidate identifier in the first column and 0 (unselected state) in the second column. (Step S150). When there is a route, the route acquisition unit 130 subsequently sets the identifier of each network node (router) in the order of passage in the search result in each column after the third column in the row of the route table (step S160). When there is no route (No in step S140), the route acquisition unit 130 does nothing for the management agent candidate.

  FIG. 3 is a diagram illustrating an example of a network connection state according to the embodiment of the present invention. FIG. 4 is a diagram showing an example of a route table in the embodiment of the present invention.

  For example, when the procedure shown in the flowchart of FIG. 2 is performed in the network connection state shown in FIG. 3, the route table shown in FIG. 4 is obtained.

  FIG. 5 is a flowchart for explaining the operation of the management agent selection means of the network management system according to the embodiment of the present invention.

  First, in consideration of the configuration of the network monitoring system, communication traffic, and the like, it is assumed that a suitable number of management agents to be monitored (hereinafter referred to as “specified number”) is designated in advance (step S205). .

  Next, the management agent selection unit 140 performs the following processing from the third column to the last column on the route table created by the route acquisition unit 130 (step S210 to step S250). In the following, the column currently being processed is referred to as a J column.

  First, the management agent selection unit 140 groups the rows of the routing table with the same value in the J column (step S215).

  Next, the management agent selection unit 140 selects an unselected row (row in which the second column is 0) of the route table including the most columns (routers) in the group for all the groups (the second column is 0). Set the value to J) (steps S220 to S230).

  If the number of all selected rows in the routing table (the second column is a row other than 0) is larger than the specified number (Yes in step S235), the management agent selecting unit 140 selects the row newly selected in the processing of the J column ( The number obtained by subtracting the number of selected rows from the specified number to the previous column in order from the row including the most columns (routers) among the values in the second column is J) (3 ≦ value in the second column <J. The number of rows) is selected again (the second column of the rows not selected again is set to 0) (step S240). On the other hand, if the total number of selected rows in the route table is equal to or less than the specified number (No in step S235), the management agent selecting unit 140 does nothing for that column.

  When the total number of selected rows is equal to the specified number (Yes in step S245), the management agent selecting unit 140 ends the process.

  FIG. 6 is a diagram showing an example of a route table in the embodiment of the present invention.

  For example, when the procedure shown in the flowchart of FIG. 5 is performed on the route table shown in FIG. 4, the route table shown in FIG. 6 is obtained. Here, the designated number is four. As a result, the server surrounded by the broken line in the diagram showing the network connection state in FIG. 3 is selected as the management agent.

  In the block diagram shown in FIG. 1, the network management system 100 has a network node for each network node (router 300, 301, 302, 303, server 500, 501, 502, 503, or other network node). Management agents 500 and 502 (hereinafter referred to as “representative agents”).

  First, the network management system 100 divides all network nodes to be managed into a specified number of groups (here, a case where the specified number is two is shown as an example). Here, a network node surrounded by an alternate long and short dash line represents one group. The group is divided so that the total processing load on the network nodes belonging to each group falls within the available processing capacity of one management agent.

  Next, the network management system 100 selects the management agents 500 and 502 corresponding to each group on a one-to-one basis as representative agents. Here, the network management system 100 may associate the representative agents in consideration of the processing capacity of the management agent and the total processing load of the network nodes belonging to each group, or may associate them at random.

  The SNMP manager 120 performs a management operation using the management agent as an SNMP agent when performing a management operation of a certain network node.

  First, the network management system 100 collects management information (performance information, etc.) other than failure information only for the representative agent of the network node to be managed.

  However, if the network management system 100 cannot communicate with the representative agent, the management agent is selected again according to the operations described with reference to FIGS. 2 and 5, and the representative agent is determined again. When the network management system 100 becomes unable to communicate with a certain management agent, after the communication is restored, the network management system 100 manages management information (performance information) other than the fault information collected and accumulated by the management agent. Etc.) can be complemented. However, when a certain representative agent becomes unable to communicate with the network node that is the management target, after the communication is restored, the network management system 100 manages the management information (performance information) other than the fault information from the occurrence of the communication fault to the recovery. Etc.) cannot be complemented.

  On the other hand, the network management system 100 collects all the network nodes for all the management agents 500 and 502 with respect to the failure information (operation status information and the like).

  In the network management system 100, the SNMP manager 120 sets a list of network nodes managed by the representative agent and a list of all network nodes to be managed for the representative agents 500 and 502.

  Each of the representative agents 500 and 502 collects and accumulates management information of the network node that is the management target. However, each of the representative agents 500 and 502 collects and accumulates management information (performance information, etc.) other than failure information only for the network node that is the management target. On the other hand, each of the representative agents 500 and 502 collects and accumulates fault information (operation status information and the like) for all network nodes of the management target network 200. Each network node to be managed operates as the SNMP manager using the SNMP manager 120 of the network management system 100 without going through the management agents 500 and 502 when transmitting SNMP Trap.

  FIG. 7 is a diagram illustrating an example of a network connection state according to the embodiment of the present invention.

  The number of network nodes that cannot be monitored by the management agent when a failure occurs in one router will be described.

  The monitoring of a certain network node cannot be continued when the network node is located in a network segment that is not connected to the management agent due to a failure of a certain router. Because, if a network node has a network connection with at least one management agent after a failure occurs in a router, the network node collects failure information (operation status information, etc.) by the management agent.・ Monitoring is continued by accumulation.

  For example, consider a case where four servers 1, 2, 6, and 7 are selected as management agents in the network connection state diagram of FIG. In this case, when a failure occurs in a certain router, there are seven routers 3, 7, 8, 9, 10, 13, 14 that cannot continue to monitor network nodes other than the failed router itself.

  On the other hand, for example, let us consider a case where four servers 1, 3, 4, and 7 are selected as management agents in the network connection state of FIG. In this case, when a failure occurs in a certain router, there are only four routers 5, 6, 10, and 11 that cannot continue monitoring network nodes other than the failed router itself, and a more suitable management agent is selected. Has been.

  This is because the network management system 100 preferentially selects the management agent from the management agent candidates at each branch destination of the network (step S215 in FIG. 5), and prioritizes the management agent from the management agent candidates farther away from the network. This is because the selection (step S225 in FIG. 5) increases the possibility that a management agent exists in each network segment separated at the failure location when a failure occurs in a certain router.

  FIG. 8 is a diagram showing an example of a network connection state in the embodiment of the present invention. FIG. 9 is a diagram showing an example of a route table in the embodiment of the present invention.

  The network management system 100 can detect a network failure or configuration change. For example, the network node to be monitored transmits an SNMP Trap to the network management system 100 when a failure or a configuration change occurs in itself. In addition, the management agent collects failure information (operation status information, etc.) of the network node to be monitored, and transmits a SNMP Trap to the network management system 100 when a failure or configuration change is detected. good. Further, the network management system 100 may monitor failure information (operation status information, etc.) of the network node to be monitored via a management agent. When the network management system 100 detects a network failure or configuration change, it again selects a management agent according to the operations described with reference to FIGS.

  A case where the router 9 fails in the network connection state shown in FIG. 8 will be described. When the procedure shown in the flowcharts of FIGS. 2 and 5 is performed in the network connection state shown in FIG. 8, the route table shown in FIG. 9 is obtained. Here, it is assumed that the designated number is four. As a result, the server surrounded by a broken line in the diagram showing the network connection state in FIG. 8 is selected as the management agent.

  FIG. 10 is a diagram illustrating an example of a network connection state according to the embodiment of the present invention. FIG. 11 is a diagram illustrating an example of a route table according to the embodiment of this invention.

  In the network connection state shown in FIG. 10, the case where the router 9 is out of order and the alternative route between the router 8 and the router 14 becomes effective will be described. When the procedure shown in the flowcharts of FIGS. 2 and 5 is performed in the network connection state shown in FIG. 10, the route table shown in FIG. 11 is obtained. Here, it is assumed that the designated number is four. As a result, the server surrounded by the broken line in the diagram showing the network connection state in FIG. 10 is selected as the management agent.

  FIG. 12 is a diagram showing an example of a network connection state in the embodiment of the present invention. FIG. 13 is a diagram showing an example of a route table in the embodiment of the present invention.

  In the network connection state shown in FIG. 12, a case where the router 15 is added to the network connection state shown in FIG. 3 and the route to the server 6 is changed to pass through the router 15 will be described.

  When the procedure shown in the flowcharts of FIGS. 2 and 5 is performed in the network connection state shown in FIG. 12, the route table shown in FIG. 11 is obtained. Here, since the processing load increases because the router 15 is added, the designated number is assumed to be 5. As a result, the server surrounded by the broken line in the diagram showing the network connection state in FIG. 10 is selected as the management agent. Here, assuming that the processing load of each node is constant and the processing capacity of each server is also constant, the processing load before the change is 21 nodes per four servers, whereas the processing load after the change is The number is reduced to 22 nodes per 5 servers.

  As described above, the network management system according to the embodiment of the present invention does not require a dedicated device for the management agent, and can dynamically adjust the processing load of the management agent even when the number of communication devices increases.

  In this example, SNMP is used as the network management protocol. However, the present embodiment is not limited to this, and network management such as CMIP (Common Management Information Protocol), WS-Management (Web Service for Management), etc. A network management system using a protocol may be used.

  In addition, this invention is not limited to the above-mentioned embodiment, It can implement in various changes and deformation | transformation in the range which does not deviate from the summary of this invention.

DESCRIPTION OF SYMBOLS 100 Network management system 120 SNMP manager 130 Path | route acquisition means 140 Management agent selection means 200 Monitoring object network 300,301,302,303 Router 310,311,312,313 313 SNMP agent 510,511,512,513 SNMP agent 520,521, 522, 523 SNMP manager 500, 501, 502, 503 Server

Claims (8)

Route acquisition means for acquiring a route from the network management system to the managed network node;
The network management manager proxy from a plurality of servers that provide services other than network management, can operate as a network management manager proxy for a network management system, and can operate as a network management agent proxy for a managed network node. And a management agent selection means for preferentially selecting a server that is actually operated as a proxy for the network management agent , giving priority to the server at a different branch destination of the network, and giving priority to the server at a farther hop of the network ;
A network management manager that operates as a network management manager for the server selected by the management agent selection means;
A network management system comprising:   The network management system according to claim 1, wherein the network management protocol is SNMP. One or more network management systems according to claim 1;
A plurality of servers that provide services other than network management, can act as a network management manager proxy for a network management system, and can act as a network management agent proxy for a managed network node;
A plurality of routers comprising a network management agent capable of operating as a network management agent for the server;
A network monitoring system comprising:   The network monitoring system according to claim 3, wherein the network management protocol is SNMP. In the management method of the network management agent by the network management manager,
A route acquisition step for acquiring a route from the network management system to the managed network node;
The network management manager proxy from a plurality of servers that provide services other than network management, can operate as a network management manager proxy for a network management system, and can operate as a network management agent proxy for a managed network node. And a management agent selection step of selecting a server that is actually operated as a proxy for the network management agent in preference to the server in a different branch destination of the network and in preference to the server in a farther hop of the network ;
A network management method comprising:   The network management method according to claim 5, wherein the network management protocol is SNMP. In the network management program of the network management agent by the network management manager,
A route acquisition procedure for acquiring a route from the network management system to the managed network node;
The network management manager proxy from a plurality of servers that provide services other than network management, can operate as a network management manager proxy for a network management system, and can operate as a network management agent proxy for a managed network node. And a management agent selection procedure for selecting a server that is actually operated as a proxy for the network management agent by giving priority to the server at a different branch destination of the network and giving priority to the server at a farther hop of the network ;
A network management program for causing a computer to execute the above.   The network management program according to claim 7, wherein the network management protocol is SNMP.

Images