Network management system, server, and program

Abstract

It is beneficial to use only the SNMP to aggregate the MIB / Trap of the terminal.SOLUTION: The SNMP manager function of the server requests the MIB from the terminal, the SNMP agent function of the terminal transmits the MIB of the terminal to the server, the SNMP manager function of the server gives a dedicated OID to the received MIB of the terminal and registers the MIB in the MIB of the server, and the SNMP agent function of the server transmits the MIB of the server to the overall management server when the server receives a request for the MIB from the overall management server.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a network management system, a server, and a program. [Background technology]

[0002] SNMP (Simple Network Management Protocol) is a protocol for monitoring and controlling communication devices connected to a network via the network. SNMP is composed of two parts: an SNMP manager on the managing side and an SNMP agent on the managed side. The SNMP manager requests information from the SNMP agent and monitors it, while the SNMP agent responds to requests from the SNMP manager and notifies it of status changes. The SNMP manager and SNMP agent understand the status of communication devices by exchanging a collection of device information held by the SNMP agent called the MIB (Management Information Base). SNMP also defines a message called a Trap that the SNMP agent will automatically send to the SNMP manager if there is a change in the device's status.

[0003] Patent Document 1 discloses an example of a management technique for communication devices connected to a network using SNMP. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-086183 Summary of the Invention [Problem to be solved by the invention]

[0005] The disclosures of the above-mentioned prior art documents are incorporated herein by reference. The following analysis has been carried out by the present inventors.

[0006] When using SNMP to manage each terminal on an entire network, it is necessary to know the IP addresses of all terminals. This is not a problem if there are only a few terminals, but the more terminals there are, the more difficult it becomes to keep track of all terminals. While it is possible to prepare a server for each network and aggregate the information, this would require the implementation of dedicated processing to exchange the aggregated MIBs and traps.

[0007] In view of the above-mentioned problems, an object of the present invention is to provide a network management system, a server, and a program that contribute to aggregating MIB / Trap of terminals using only SNMP. [Means for solving the problem]

[0008] In a first aspect of the present invention, there is provided a network management system in which a server having an SNMP manager function and an SNMP agent function, and a terminal having an SNMP agent function are installed on a network, wherein the SNMP manager function of the server requests an MIB from the terminal, the SNMP agent function of the terminal transmits the MIB of the terminal to the server, the SNMP manager function of the server assigns a dedicated OID (Object IDentifier) ​​to the MIB of the terminal that it has received, and registers it in the MIB of the server, and when the server receives a request for an MIB from an overall management server, the SNMP agent function of the server transmits the MIB of the server to the overall management server.

[0009] In a second aspect of the present invention, there is provided a network management system in which a server having an SNMP manager function and an SNMP agent function, and a terminal having an SNMP agent function are installed on a network, wherein the SNMP agent function of the terminal sends a trap from the terminal to the server, the SNMP manager function of the server assigns a dedicated OID to the received trap from the terminal, and the SNMP agent function of the server sends the trap to an overall management server.

[0010] In a third aspect of the present invention, there is provided a server having an SNMP manager function that requests an MIB from an SNMP agent function possessed by a terminal installed on a network, assigns a dedicated OID to the received MIB of the terminal, and registers it in its own MIB, and an SNMP agent function that, when a MIB request is received from an overall management server, transmits its own MIB to the overall management server.

[0011] In a fourth aspect of the present invention, there is provided a server having an SNMP manager function that receives a trap from a terminal installed on a network from an SNMP agent function possessed by the terminal and assigns a dedicated OID to the received trap from the terminal, and an SNMP agent function that transmits the trap to an overall management server.

[0012] In a fifth aspect of the present invention, there is provided a program that causes an information providing device to execute the following processes: requesting an MIB from an SNMP agent function possessed by a terminal installed on a network, assigning a dedicated OID to the received MIB of the terminal, and registering it in its own MIB; and, when a request for an MIB is received from an overall management server, transmitting its own MIB to the overall management server.

[0013] In a sixth aspect of the present invention, there is provided a program that causes an information providing device to execute the following processes: receive a trap from a terminal installed on a network from the SNMP agent function of the terminal; assign a dedicated OID to the received trap from the terminal; and send the trap to an overall management server. The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present invention can also be embodied as a computer program product. [Effects of the Invention]

[0014] According to each aspect of the present invention, it is possible to provide a network management system, a server, and a program that contribute to aggregating MIB / Trap of terminals using only SNMP. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a network to which a network management system according to an embodiment is applied. [Figure 2] FIG. 2 is a block diagram showing the functions of the server. [Figure 3] FIG. 3 is a block diagram showing the functions of the terminal. [Figure 4] FIG. 4 is a diagram showing an example of a dedicated OID of the MIB of the terminal registered in the MIB-DB of the server. [Figure 5] FIG. 5 is a sequence diagram illustrating the processing of the network management system according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of an MIB registered in the MIB-DB of the server. [Figure 7] FIG. 7 illustrates an example of a hardware configuration of a server. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not limited to the embodiments described below. In addition, the same or corresponding elements in each drawing are appropriately designated by the same reference numerals. Furthermore, it should be noted that the drawings are schematic, and the dimensional relationships and ratios of each element may differ from those in reality. There may also be parts in which the dimensional relationships and ratios differ between the drawings.

[0017] Fig. 1 is a diagram showing an example of the configuration of a network to which a network management system according to an embodiment is applied. As shown in Fig. 1, the network is made up of a LAN 101, a LAN 111, and a LAN 121. A server 102, a router 112, and a router 122 are connected to the LAN 101. The server 102 is an overall management server.

[0018] A router 112, a server 113, a terminal 114, and a terminal 115 are connected to the LAN 111, and the LAN 101 and the LAN 111 are connected via the router 112. The server 113 is an aggregation server within the LAN 111. The IP address of the terminal 114 is 192.168.10.1, and the IP address of the terminal 115 is 192.168.10.2.

[0019] A router 122, a server 123, a terminal 124, and a terminal 125 are connected to the LAN 121, and the LAN 101 and the LAN 121 are connected via the router 122. The server 123 serves as an aggregation server within the LAN 121.

[0020] Figure 2 is a block diagram showing the functions of the server. As shown in Figure 2, the server has an SNMP manager 201, an SNMP agent 202, and an MIB-DB 203. The SNMP manager 201 requests an MIB from the SNMP agent function of a terminal installed on the network, assigns a dedicated OID to the MIB of the received terminal, and registers it in its own MIB-DB 203. When the SNMP agent 202 receives a request for an MIB from the overall management server, it obtains the MIB from the MIB-DB 203 and sends this MIB to the overall management server.

[0021] Fig. 3 is a block diagram showing the functions of a terminal. As shown in Fig. 3, the terminal has an SNMP agent 301 and an MIB-DB 302. In response to a request from a server, the SNMP agent 301 retrieves an MIB from the MIB-DB 302 and responds.

[0022] Fig. 4 is a diagram showing an example of a dedicated OID for a terminal MIB registered in the server's MIB-DB. As shown in Fig. 4, the dedicated OID for a terminal MIB registered in the server's MIB-DB is first set to the OID (401) of the table that stores the terminal MIB. This OID (401) can be any OID that does not overlap with the OIDs of already defined MIBs. Then, the IP address (402) of the terminal and the OID (403) of the terminal's MIB are assigned as the index of that table. This makes it possible to store multiple MIBs for multiple terminals in a single table.

[0023] For example, when the OID (401) of the table storing the terminal MIB is defined as 1.3.6.1.4.1.X, the OID corresponding to the sysDescr of the terminal 114 is 1.3.6.1.4.1.X.192.168.10.1.1.3.6.1.2.1.1.1.0 shown in FIG.

[0024] [Network Management System Processing] 5 is a sequence diagram illustrating the processing of the network management system according to the embodiment. As shown in FIG. 5, the processing of the network management system according to the embodiment includes a process of aggregating terminal MIBs and a process of acquiring the aggregated terminal MIBs. Below, the processing of the network management system according to the embodiment will be explained using an example in which the MIBs of terminals 114 in LAN 111 are aggregated in server 113 and the MIBs are acquired from server 102 in LAN 101.

[0025] (Terminal MIB aggregation processing) The process of aggregating terminal MIBs (501) will now be described. First, SNMP manager 201 of server 113 requests the MIB of terminal 114 from SNMP agent 301 of terminal 114 (502). Next, SNMP agent 301 of terminal 114 acquires the requested MIB from MIB-DB 302 (503) and transmits the MIB to SNMP manager 201 of server 113 (504). Then, SNMP manager 201 of server 113 registers the acquired MIB of terminal 114 in its own MIB-DB 203 (505). Note that the method described above is used when registering the MIB of terminal 114 in its own MIB-DB 203.

[0026] By repeating this process for the number of MIBs to be consolidated, the MIBs of terminal 114 are consolidated into server 113. Terminal 115 in the same LAN 111 is also consolidated into server 113 using the same procedure. Terminals 124 and 125 in LAN 121 are also consolidated into server 123 using the same procedure.

[0027] 6 is a diagram showing an example of a MIB registered in the MIB-DB 203 of the server 113. Here, the OID of the table storing the terminal MIB is defined as 1.3.6.1.4.1.X. As shown in FIG. 4, the OID of the aggregated MIB includes the IP address of the terminal and the OID of the terminal MIB, so that OIDs can be registered in the server's MIB without overlapping between multiple terminals or MIBs.

[0028] (Acquisition process of aggregated terminal MIB) Next, the acquisition of the aggregated terminal MIB (511) will be described. First, the SNMP manager 201 of server 102, which is the overall management server, requests the terminal MIB from the SNMP agent 202 of server 113 (512). Then, the SNMP agent 202 of server 113 acquires the requested MIB from the MIB-DB 203 (513) and sends the MIB to the SNMP manager 201 of server 102. At this time, if the IP address of the terminal is unknown on the server 102 side, the MIB of each terminal in the table can be acquired by using an SNMP GetNext or GetBulk request. The terminal MIBs aggregated in server 123 within LAN 121 are also acquired using the same procedure.

[0029] [Hardware configuration example] Fig. 7 is a diagram showing an example of the hardware configuration of a server. That is, server 102, server 113, and server 123 can realize the respective functions of server 102, server 113, and server 123 by executing the processing of the network management system described above as a program on information processing device (computer) 10 employing the hardware configuration shown in Fig. 7. However, the hardware configuration example shown in Fig. 7 is an example of a hardware configuration that realizes the respective functions of server 102, server 113, and server 123, and is not intended to limit the hardware configuration of server 102, server 113, and server 123. Server 102, server 113, and server 123 may include hardware not shown in Fig. 7.

[0030] As shown in FIG. 7, the hardware configuration that can be adopted by server 102, server 113, and server 123 includes a CPU (Central Processing Unit) 11, a main memory device 12, an auxiliary memory device 13, and an IF (Interface) unit 14, which are interconnected by, for example, an internal bus.

[0031] The CPU 11 executes each command included in a program executed by the information processing device (computer) 10. The main storage device 12 is, for example, a RAM (Random Access Memory), and temporarily stores various programs executed by the information processing device (computer) 10 for processing by the CPU 11.

[0032] The auxiliary storage device 13 is, for example, a hard disk drive (HDD), and is capable of storing various programs executed by the information processing device (computer) 10 for a medium to long term. The various programs can be provided as program products recorded on a non-transitory computer-readable storage medium.

[0033] The IF unit 14 provides an interface for input and output of the servers 102, 113, and 123, for example.

[0034] The information processing device (computer) 10 employing the above hardware configuration implements the functions of the servers 102, 113, and 123 by executing the processes of the network management system described above as a program.

[0035] [Explanation of effects] As described above, in the network management system according to the embodiment, by aggregating the MIBs of terminals in the aggregation server, even if the overall management server does not know the IP addresses of the terminals, the overall management server can obtain the MIBs of the terminals as long as it knows the IP address of the aggregation server. The aggregation server only needs to know the IP addresses of the terminals that are the targets of MIB aggregation.

[0036] In the network management system according to the embodiment, the MIB acquired from the terminal is registered as the MIB of the aggregation server, so that the aggregated terminal MIB can be acquired by the overall management server using SNMP. In other words, there is no need to implement a dedicated process for acquiring the aggregated terminal MIB.

[0037] Example 1 In the above-mentioned embodiment, MIBs within a LAN were aggregated, but aggregation can also be performed on a different scale. Terminal MIBs can be aggregated in units that are easy to manage, such as organizations or bases. In addition, the number of terminals and networks shown in the examples can be expanded.

[0038] Example 2 Although IPv4 addresses are used in the above embodiment, IPv6 addresses can also be used. IPv6 addresses are converted into decimal numbers, one byte at a time, to create an OID. To distinguish between IPv4 and IPv6, the length of the IP address OID is added before the IP address. The OID length of an IPv4 address is 4, and the OID length of an IPv6 address is 16. For example, the OID for the IPv4 address 192.168.10.1 is 4.192.168.10.1. The OID for the IPv6 address 2001:db8::1 is 16.32.1.13.184.0.0.0.0.0.0.0.0.0.0.0.0.1.

[0039] Example 3 In the above-mentioned embodiment, the overall management server and the aggregation server were separated, but it is also possible to use all servers as aggregation servers and obtain terminal MIBs from each other. In this case, it is possible to set restrictions in advance on the IP addresses and MIBs of the aggregation targets so that terminal MIBs obtained from other aggregation servers are not registered in the server's own MIB.

[0040] Example 4 In the above-mentioned embodiment, MIBs were aggregated, but traps can also be aggregated in a similar manner. First, the OID of the trap to be issued when a terminal trap is received is defined. Then, when the aggregation server receives a trap from a terminal, the previously defined trap is sent to the overall management server, with the terminal's IP address, the terminal's trap OID, and other parameters included. This allows the terminal to exchange MIBs and traps only with the aggregation server, while still notifying the overall management server of the trap.

[0041] The disclosures of the above-cited patent documents and other documents are incorporated herein by reference. Modifications and adjustments of the embodiments and examples are possible within the scope of the entire disclosure of the present invention (including the claims), and further based on the basic technical concepts thereof. Furthermore, various combinations and selections (including partial deletions) of various disclosed elements (including elements of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible within the scope of the entire disclosure of the present invention. In other words, the present invention naturally embraces various modifications and alterations that would be possible by a person skilled in the art in accordance with the entire disclosure and technical concepts, including the claims. In particular, with regard to the numerical ranges set forth herein, any numerical value or subrange within that range should be construed as specifically set forth, even if not otherwise specified. Furthermore, the disclosures of the above-cited documents, when used in part or in whole in combination with the disclosures herein as part of the disclosure of the present invention, in accordance with the spirit of the present invention, are also deemed to be included in the disclosures of this application. [Explanation of symbols]

[0042] 101,111,121 LAN 102,113,123 servers 112,122 routers 114,115,124,125 terminals 201 SNMP Manager 202,301 SNMP agents 203,302 MIB-DB 10. Information processing equipment 11 CPU 12 Main storage 13 Auxiliary storage device 14 IF Section

Claims

1. A server with SNMP manager and agent functions, A network management system in which a terminal having an SNMP agent function is installed on a network, The SNMP manager function of the server requests an MIB from the terminal; The SNMP agent function of the terminal transmits the MIB of the terminal to the server; The SNMP manager function of the server assigns a dedicated OID to the received MIB of the terminal and registers it in the MIB of the server, In the network management system, when the server receives a request for an MIB from a total management server, an SNMP agent function of the server transmits the MIB of the server to the total management server.

2. A server with SNMP manager and agent functions, A network management system in which a terminal having an SNMP agent function is installed on a network, The SNMP agent function of the terminal sends a trap of the terminal to the server, The SNMP manager function of the server assigns a dedicated OID to the received trap from the terminal, A network management system in which the SNMP agent function of the server transmits the trap to a central management server.

3. 3. The network management system according to claim 1, wherein the SNMP manager function of said server is set to manage the SNMP agent function of a terminal installed in the subnetwork.

4. 3. The network management system according to claim 1, wherein the SNMP manager function of said server is set to manage the SNMP agent function of a terminal installed in a predetermined organization.

5. 3. A network management system according to claim 1, wherein said overall management server has an SNMP manager function and an SNMP agent function for said servers.

6. 3. The network management system according to claim 1, wherein the dedicated OID includes an IP address.

7. An SNMP manager function that requests an MIB from an SNMP agent function of a terminal installed on the network, assigns a dedicated OID to the MIB of the terminal received, and registers it in its own MIB; a server having an SNMP agent function for transmitting its own MIB to the overall management server when receiving a request for the MIB from the overall management server.

8. an SNMP manager function that receives a trap from a terminal installed on the network from the SNMP agent function of the terminal and assigns a dedicated OID to the received trap from the terminal; A server having an SNMP agent function for transmitting the trap to the overall management server.

9. A process of requesting an MIB from the SNMP agent function of a terminal installed on the network, assigning a dedicated OID to the MIB of the terminal received, and registering it in its own MIB; and a program for causing the information providing device to execute a process of transmitting the MIB of the device to the overall management server when a request for the MIB is received from the overall management server.

10. A process of receiving a trap from a terminal installed on a network from the SNMP agent function of the terminal and assigning a dedicated OID to the received trap from the terminal; and a program for causing the information providing device to execute a process of transmitting the trap to the overall management server.

Images