JP2007006291A - Gateway device, relay method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a load from being concentrated on a GW (gateway) node in constitution wherein a TCP/IP network and a non-TCP/IP network are connected by the GW node when a node on a non-TCP/IP network is managed from a managing device placed on a TCP/IP network through the GW node by using SNMP. <P>SOLUTION: The GW node 2 holds OIDs of SNMP and processing systems for management requests in the form of a node address table by a plurality of nodes 3 included in ring type network as the non-TCP/IP network, compares an OID included in a management request with the node address table when the management device transmits the management request to specify a node as the object of the management request and the processing system of the node, and transmits the management request according to the processing system specified to the specified node. Then the node receives an answer to the management request from the node and transmits the received answer to the management device 1. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to network management technology in a configuration in which a plurality of networks having different network protocols, for example, a TCP / IP network and a non-TCP / IP network are connected.

  When a non-TCP / IP network is managed by a network management device placed on a TCP / IP network, this network management device uses SNMP (Simple Network Management Protocol), which is a standard network management protocol based on TCP / IP. . A gateway is provided for connection between the TCP / IP network and the non-TCP / IP network.

  Conventionally, in such a configuration, as in Patent Document 1, this gateway has a table for associating a node address and a node identifier of a node in a non-TCP / IP network, and has means for automatically generating the table. A community name defined by SNMP is used as the node identifier. Further, the management device on the TCP / IP network collects and stores this table from the gateway, and searches for the identifier of the node in the target non-TCP / IP network based on the operator's instruction. It has a means to send a request with an identifier to the gateway.

  As a result, node configuration information for a non-TCP / IP network using the SNMP community name is automatically created at the gateway, so even if the configuration is changed due to the addition of a node or a new network connection, the operator can configure it. There is no need to change the information. Also, it was not necessary to be aware of community names.

Further, in network management using SNMP, a method for dividing an agent that realizes a management function of a management target into a plurality of parts has been proposed (for example, Non-Patent Document 1).
JP 7-79246 A IETF RFC2741, January 2000

  In the conventional method, (1) SNMP protocol processing, (2) conversion from a management request given by the management device using the SNMP protocol to a management request using a management protocol used by a non-TCP / IP network, (3) non-TCP All processes are concentrated on the gateway, such as determining the forwarding destination of management requests based on the association between the community name, which is the node identifier of the / IP network, and the node address. Therefore, the gateway needs to have higher performance compared to other nodes of the non-TCP / IP network.

  In addition, when connecting a TCP / IP network and a non-TCP / IP network, a node disposed in the non-TCP / IP network does not have a dedicated gateway that mediates both networks, but a TCP / IP function and a gateway function. By having, there is a configuration that plays the role of a gateway. In particular, when the non-TCP / IP network is a ring network having a punctual communication function, a configuration in which the load is concentrated as described above may adversely affect the punctual communication. Even if a node arranged in a non-TCP / IP network is inferior in processing performance as compared to a node in a TCP / IP network, the load concentration on a node having a gateway function is a response to a management request. Adversely affects performance.

  In addition, there is a ring network in which a node dynamically determined by a network protocol holds information about the network. Such a node having a role representing the ring network is referred to as a representative node herein. In a network having a representative node, a community device that is a simple character string is used as a node identifier, and a node that plays the role of the representative node cannot be represented simply by associating it with a node address. Can't get information about.

  The main object of the present invention is to solve the above-described problems. A TCP / IP network and a ring network that is a non-TCP / IP network are connected to each other and placed in the TCP / IP network. Network information that prevents concentration of load on the gateway node and is dynamically determined when managing the ring network using SNMP from one management device via one node of the ring network having a gateway function The main purpose is to enable network information acquisition from the holding node.

The gateway device according to the present invention is:
Between a management device that is arranged in the first network and performs network management using the SNMP (Simple Network Management Protocol) protocol, and a plurality of nodes that are arranged in the second network and are targets of network management by the management device A gateway device for relaying communication,
For each node, an OID processing method table management unit that manages an OID processing method table indicating an OID corresponding to each node in an SNMP protocol OID (Object Identifier) and a processing method of each node;
A first network communication unit that receives a management request including an OID corresponding to one of the nodes from the management device;
A node processing method specifying unit for comparing the OID included in the management request with the OID shown in the OID processing method table to identify the node targeted by the management request, and for specifying the processing method of the node;
A second network communication unit that transmits a management request for the specific node specified by the node processing method specifying unit to the specific node according to the processing method specified by the node processing method specifying unit. And

  According to the present invention, in order to manage the node OID and the processing method of each node in the gateway device, the identification of the node to be managed and the processing of the node based on the OID included in the management request from the management device It is possible to simplify the method specifying process, to prevent the load from being concentrated on the gateway device, and to simplify the configuration of the gateway device.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing an example of a network system to which the present invention is applied.

  In FIG. 1, a management device 1 is connected to a TCP / IP network 4 that is a first network, and is a device that manages a ring network using the SNMP protocol. A ring network 5 as a second network is a non-TCP / IP network, and includes nodes 3 a to 3 c and a gateway (hereinafter referred to as GW) node (gateway device) 2. The GW node 2 includes two protocol stacks, a ring network protocol and a TCP / IP network protocol.

  FIG. 2 is a diagram illustrating an example of the configuration of the GW node 2 and the configuration of the node 3 illustrated in FIG.

  2, the GW node 2 includes an SNMP protocol processing unit 21, a MIB (Management Information Base) management unit 22, a management request processing unit 23a, a node information collection unit 24a, a node address table management unit 25, a ring network management protocol processing unit. 26a, a communication unit 27a, a TCP / IP protocol stack 270a, and a ring network protocol stack 271a.

  The MIB management unit 22 manages an MIB that includes an OID associated with network information as a part thereof.

  The node address table management unit 25 manages the node address table. As will be described in detail later, the node address table indicates each node, an OID (Object Identifier) in the MIB corresponding to each node, and the processing method of each node. The node address table corresponds to an OID processing method table, and the node address table management unit 25 corresponds to an OID processing method table management unit. Here, the processing method means a way of passing a management request to each node.

  When there is a management request from the management apparatus 1, the management request processing unit 23a specifies a node targeted by the management request and specifies a processing method of the specified node. The management request processing unit 23a corresponds to a node processing method specifying unit.

The communication unit 27a includes a TCP / IP protocol stack 270a for communicating with the TCP / IP network 4 that is the first network, and a ring network protocol stack for communicating with the ring network 5 that is the second network. 271a. The communication unit 27a corresponds to a first network communication unit and a second network communication unit.
The node 3a includes a management request processing unit 23b, a node information collection unit 24b, a ring network management protocol processing unit 26b, a communication unit 27b, and a ring network protocol stack 271b.

  FIG. 3 is a diagram showing an example of a node address table managed by the node address table management unit 25 shown in FIG.

  In FIG. 3, the node address table includes an arrangement 31, a node address 32, an OID 33, and a processing method 34 as items. The arrangement 31 represents the position where each node is arranged from the GW node 2. The node address 32 is an address of a node used in the data link of the ring network 5. The OID 33 is a list of OIDs in which nodes are involved among the OIDs of the MIB. When using a MIB that describes a plurality of OIDs, it may take the form of describing a link to a separately created OID table instead of describing the OID directly. The processing method 34 is a way of passing a management request to each node. In FIG. 3, one processing method is described for one node.

  FIG. 4 shows an example of another node address table. In the example of FIG. 4, when there are a plurality of OIDs, it is possible to specify a processing method for each OID. Therefore, in the example of FIG. 4, a plurality of processing methods can be specified for one node by specifying a processing method for each OID.

  Next, the operation of the GW node 2 according to the present embodiment will be outlined using FIG. 5 and FIG.

  The operation of the GW node 2 according to the present embodiment can be roughly divided into a preparation operation and a management request processing operation. FIG. 5 is a flowchart showing the preparation operation, and FIG. 6 is a flowchart showing the management request processing operation. is there.

  First, the preparation operation will be outlined with reference to FIG.

  First, in the GW node 2, when the data link with each node is established by the ring network protocol stack 271a of the communication unit 27a (S101), the node information collection unit 24a moves from the ring network protocol stack 271a to the ring network 5. The node addresses of all connected nodes are acquired (S102), and the arrangement 31 and the node address 32 are entered in the node address table (S103).

  Next, the management request processing unit 23a queries the MIB management unit 22 for the MIB, associates the node address with the OID for each node (S104), and enters the OID of each node in the OID 33 of the node address table (S105). ).

  Next, the node information collection unit 24a inquires each node about the processing method via the communication unit 27a (S106), and writes the processing method 34 in the node address table based on the response to the inquiry (S107).

  Also, as shown in FIG. 4, when different processing methods are set for each OID for a plurality of OIDs, processing method information for each OID is collected from the node in step S106, and processing for each OID is performed in step S107. Enter the method in the node address table.

  Next, the management request processing operation will be outlined with reference to FIG.

  First, the communication unit 27a receives a management request from the management apparatus 1 through the TCP / IP protocol stack 270a (S201, first network communication step). This management request includes an OID, and the node that is the target of the management request is specified by the OID.

  Next, the management request processing unit 23a compares the OID included in the management request with the OID of the node address table, and extracts the node address and processing method of the node with the matching OID (S202, node processing method specifying step). ).

  Next, the SNMP protocol processing unit 21 converts the management request into a protocol corresponding to the ring network 5 (S203).

  Next, the communication unit 27a transmits a management request after the protocol conversion to the node specified in step S202 in accordance with the specified processing method (S204, second network communication step).

  Next, the communication unit 27a receives a response from the node (S205), and the SNMP protocol processing unit 21 converts the response from the node into an SNMP message (S206).

  Finally, the response converted into the SNMP message by the communication unit 27a is transmitted to the management apparatus (S207).

  Next, the flow of the preparation operation up to the manageable state will be described with reference to FIG.

  When the data link of the ring network 5 is established by the ring network protocol stacks 271a and 271b (41), the node information collection unit 24a of the GW node 2 is connected to the ring network 5 from the ring network protocol stack 271a. The node addresses of all the nodes are received (42), and the arrangement 31 and the node address 32 are entered in the node address table.

  The node information collection unit 24a receives the node address of the representative node of the ring network that grasps the network information from the ring network protocol stack 271a (43), and manages the node addresses of all nodes together with other node addresses. It passes to processing part 23a (44). The management request processing unit 23a queries the MIB management unit 22 for the MIB, associates the node address with the OID, and enters the OID corresponding to each node in the OID 33 of the node address table (45).

  The node information collection unit 24a of the GW node 2 inquires about how to send the management request to the node information collection unit 24b of each node (46) and enters the processing method 34 of the node address table according to the response from the node. .

  Next, the flow of the management request processing operation will be described with reference to FIG.

  A management request is sent from the management apparatus 1 to the GW node 2 by SNMP (501a). In the GW node 2, the SNMP protocol processing unit 21 processes the SNMP message and extracts the OID and operation to be managed. The extracted OID and operation are sent to the management request processing unit 23a (502a). The management request processing unit 23a extracts the node address and processing method corresponding to the OID from the node address table.

  Here, it is assumed that the use of the ring network management protocol is specified as the processing method. The management request processing unit 23a gives the management request corresponding to the operation received from the SNMP protocol processing unit 21 and the node address as the request destination to the ring network management protocol processing unit 26a of the GW node 2 (503). The ring network management protocol processing unit 26a of the GW node 2 gives a management request to the designated node using the ring network management protocol, and receives the result (504). The ring network management protocol processing unit 26a of the GW node 2 gives the received result to the management request processing unit (505). The management request processing unit 23a passes the result to the SNMP protocol processing unit 21 (506a), and the result is transmitted to the management device 1 (507a).

  On the other hand, it is assumed that end-to-end communication is specified in the node address table as a node processing method to be a management request target. In this case, the processes 501b and 502b are the same as the above-described 501a and 502b (501b) (502b). The management request processing unit 23a creates a management request message based on the management request corresponding to the operation received from the SNMP protocol processing unit 21, and transmits it to the management request processing unit 23b of the request destination node (508). ). The management request processing unit 23b of the request destination node 3a receives the management request message, executes a management operation based on the message, and returns the result to the management request processing unit 23a of the GW node 2 (509). The management request processing unit 23a of the GW node 2 passes the received result to the SNMP protocol processing unit 21 (506b), and the result is transmitted to the management apparatus 1 (507b).

Thus, in this embodiment, there is a management apparatus placed on the network and a ring network different from the network, and one of the nodes constituting the ring network is a gateway to the network on which the management apparatus is placed. In a configuration that plays a role, when the management device manages the ring network with SNMP, the node acting as a gateway
(A) Means for storing node arrangement, node address, OID, and processing method (b) Means for processing the SNMP protocol (c) Means for obtaining node addresses of all nodes constituting the ring network (d) Ring network (E) Means for knowing the processing method in the nodes constituting the ring network (f) Means for communicating with the nodes of the ring network according to the processing method (g) OID and nodes of the ring network It is characterized in that a means for associating is provided, and a node other than the gateway is provided with means for informing the node processing method to the gateway node.

  In the above, an example in which the non-TCP / IP network as the second network is a ring network has been described. However, the non-TCP / IP network may be a network other than the ring network.

  As described above, according to the present embodiment, in order to manage the node OID and the processing method of each node in the GW node, the node to be managed based on the OID included in the management request from the management apparatus Identification processing and identification processing of the processing method of the node can be simplified, load concentration on the GW node can be prevented, and the configuration of the GW node can be simplified.

  Further, by configuring and operating a GW node and a node other than the GW node, network information accumulated in a node representing the network can be acquired.

  Also, by changing the processing method between the GW node and the node according to the characteristics of the node of the ring network (performing individual processing method for each node), the processing performed by the GW node is performed in the node, and the GW node The load can be reduced.

  Further, when a processing method is set for each OID, an optimum processing method can be selected according to each processing content corresponding to the OID.

  In addition, it is possible to execute a management function that is not realized by the management protocol of the ring network.

Embodiment 2. FIG.
In the first embodiment described above, SNMP message processing is performed by the GW node 2, but the nodes 3a, 3b, and 3c other than the GW node 2 of the ring network 5 then execute the SNMP protocol processing unit. An embodiment in the case of having it will be described.

  FIG. 9 is a diagram showing an example of the configuration of the GW node 2 and the configuration of the node in such a case.

  In FIG. 9, the GW node 2 has an OID analysis unit, and the node 3a has an SNMP protocol processing unit 21b. Other configurations are the same as those in the first embodiment.

  Next, the management request processing operation will be described with reference to FIG.

  An SNMP message is sent from the management apparatus 1 to the GW node 2 (701). The OID analysis unit 28 of the GW node 2 extracts the OID to be managed from the received SNMP message, and gives it to the management request processing unit 23a together with the SNMP message (702). The management request processing unit 23a extracts the node address and processing method corresponding to the received OID from the node address table.

  When the extracted processing method specifies the use of the SNMP message, the management request processing unit 23a instructs the communication unit 27a to transmit the SNMP message as it is, and the communication unit 27a transmits the communication unit of the target node 3a. An SNMP message is transmitted to the management request processing unit 23b via the terminal 27b (703). The management request processing unit 23b that has received the SNMP message passes the SNMP message to the SNMP protocol processing unit 21b and receives the OID and the management request (704). A management operation is executed in accordance with the received OID and management request, and the result is passed to the SNMP protocol processing unit 21b. The SNMP protocol processing unit 21b converts the result into an SNMP message and returns it to the management request processing unit 23b (705). The management request processing unit 23b returns an SNMP message to the management request processing unit 23a of the GW node 2 (706). The management request processing unit 23a of the GW node 2 returns the received SNMP message to the management apparatus 1 (707).

  When the extracted processing method is designated other than the use of the SNMP message such as the use of the ring network management protocol as in the case of the first embodiment, the management request processing unit 23a sends the SNMP message to the SNMP protocol processing unit 21. Pass and receive OID and management request. The operation after receiving is the same as in the first embodiment.

  As described above, the present embodiment is characterized in that the gateway node is provided with means for obtaining an OID from the SNMP message, and the nodes other than the gateway node are provided with means for performing SNMP protocol processing.

  As described above, according to the present embodiment, the SNMP message processing is executed by a node other than the GW node. Therefore, the processing capability of the node other than the GW node is effectively utilized, and the processing of the GW node is performed. Can be further reduced.

Embodiment 3 FIG.
In the first and second embodiments, the node information collection unit of the GW node inquires the ring network protocol stack in the GW node about the node address when creating the node address table. An embodiment in which the node information collection unit inquires of the node information collection unit of another node is shown.

  The configuration is the same as in the first and second embodiments.

  A preparatory operation according to the present embodiment will be described with reference to FIG.

  When the data link of the ring network 5 is established, the node information collection unit 24a of the GW node 2 broadcasts a node address request to the other nodes 3a, 3b, and 3c in the ring network 5 (801). Upon receiving the node address request, the node information collection units 24b, 24c, and 24d of the nodes 3a, 3b, and 3c simultaneously indicate that the node is a representative node if the node is a representative node of the ring network (802). ). The node information collection unit 24a of the GW node 2 that has received the response writes the arrangement 31 and the node address 32 in the node address table.

  The node information collection unit 24a passes the node address information to the management request processing unit 23a (803). The management request processing unit 23a inquires the MIB to the MIB management unit 22, associates the node address with the OID, and enters the OID corresponding to each node in the OID 33 of the node address table (804).

  The node information collection unit 24a of the GW node 2 queries the node information collection units 24b, 24c, and 24d of each node about how to pass the management request (805), and processes the node address table according to the response from the node. Enter 34.

  As described above, this embodiment is characterized in that the gateway node includes means for inquiring the node address of other nodes.

  By operating as described above, according to the present embodiment, even when the ring network protocol stack of the GW node uses a ring network protocol that does not collect the arrangement and node addresses of other nodes, the implementation is performed. The same effect as in the first embodiment can be obtained.

Embodiment 4 FIG.
In the method shown in the first embodiment, an embodiment in which a processing method between a GW node and a node can be changed by a failure or a load change detected by each node will be described.

  The configuration is the same as in the first embodiment.

  The operation will be described with reference to FIG.

  Here, a node in which a processing method needs to be changed due to occurrence of a failure or a change in load is assumed to be a node 3a. The node information collection unit 24b of the node 3a sends an OID corresponding to a newly used processing method to the node information collection unit 24a of the GW node 2. The node information collection unit 24a of the GW node 2 updates the node address table based on the received processing method and OID.

  When a management request arrives from the management apparatus 1, the GW node 2 determines a processing method based on the updated node address table, and communicates with the node 3a using the determined processing method.

  As described above, this embodiment is characterized in that a node other than the gateway is provided with means for notifying the gateway node of the processing method and OID to be newly used according to the state of the node.

  By operating as described above, according to the present embodiment, the processing method can be appropriately selected according to the state of the active node, so that the processing load can be shared between the GW node and the node.

Embodiment 5. FIG.
In the second embodiment, an embodiment in which a processing method between a GW node and a node can be changed by a failure or a load change detected by each node will be described.

  The configuration is the same as in the second embodiment.

  Since the operation is the same as that of the fourth embodiment, description thereof is omitted.

  As described above, the present embodiment is characterized in that a node other than the gateway is provided with means for notifying the gateway node of the processing method and OID that are newly used according to the state of the node.

  By operating as described above, in this embodiment, the processing method can be appropriately selected according to the state of the active node, so that the processing load can be shared between the GW node and the node.

Embodiment 6 FIG.
In the method shown in the first embodiment, an embodiment in which a processing method between a GW node and a node can be changed by a change in a network state detected by the GW node will be described.

  FIG. 12 is an example of a node address table in the present embodiment. The processing method 92 can be determined according to the condition 91. For example, when the condition 91 is “the network operates normally”, the processing method 92 is “end-to-end communication”, and the condition 91 is “the network loopback operation”, the processing method 92 is “ring network management protocol”. Use of ".

  Further, as in the node address table shown in FIG. 13, when a plurality of OIDs exist and a processing method is designated for each OID, the condition 91 may be defined for each OID.

  The configuration of the GW node itself is the same as in the first embodiment.

  The operation will be described with reference to FIGS.

  In the preparatory operation up to the manageable state, the operation is the same as in the first embodiment until the node information collection unit 24a of the GW node 2 makes an inquiry about the processing method (46). In the processing method inquiry, a processing method and a condition that is a criterion for selecting the processing method are inquired (46). Based on the inquiry result, the node address table condition 91 and processing method 92 are entered.

  In the management request processing operation, when the management request processing unit 23a of the GW node 2 receives the OID and the operation (502a), the node address corresponding to the OID and the contents corresponding to the network state at that time are described in the condition 91. The processing method is extracted from the node address table. Other operations are the same as those in the first embodiment.

  As described above, according to the present embodiment, the gateway node determines the processing method in the nodes constituting the ring network and the conditions for applying the processing method, and determines the processing method according to the conditions. And means for communicating.

  By operating as described above, in the present embodiment, the processing method can be appropriately selected according to the state detected by the GW node, so that the processing load can be shared between the GW node and the node.

Embodiment 7 FIG.
In the method shown in the second embodiment, an embodiment in which a processing method between a GW node and a node can be changed by a change in a network state detected by the GW node will be described.

  The configuration is the same as that of the second embodiment except that the node address table of FIG. 12 or FIG. 13 is used.

  The operation will be described with reference to FIG.

  The preparation operation up to the manageable state is the same as in the sixth embodiment.

  In the management request processing operation, when the management request processing unit 23a of the GW node 2 receives the OID and the SNMP message (702), the node address corresponding to the OID and the contents matching the network state at that time are described in the condition 91. From the node address table. Other operations are the same as those in the second embodiment.

  As described above, according to the present embodiment, the gateway node determines the processing method in the nodes constituting the ring network and the conditions for applying the processing method, and determines the processing method according to the conditions. And means for communicating.

  By operating as described above, the processing method can be appropriately selected according to the state detected by the GW node, so that the processing load can be shared between the GW node and the node.

Embodiment 8 FIG.
In the method shown in the first embodiment, an embodiment in which the node information collection unit collects network information when the representative node that grasps the network information does not exist in the ring network will be described.

  The configurations of the GW node 2 and the node 3 are the same as those in the first embodiment.

  Next, referring to FIG. 14, a preparation operation until reaching the manageable state will be described.

  When the data link of the ring network 5 is established, the node information collection unit 24a of the GW node 2 receives the node addresses of all the nodes connected to the ring network 5 from the ring network protocol stack 27a (1001). The arrangement 31 and the node address 32 are entered in the node address table.

  The node information collecting unit 24a inquires the ring network protocol stack 27a about the node address of the representative node of the ring network (1002). A response from the possible node is obtained (1003). If no response is obtained, the node information collection unit of the GW node 2 collects network information. In addition, the address of the node having the node information collection unit in charge of network information collection is entered in the node address of the node address table. Together with the node addresses of all nodes, the address of the node having the node information collection unit in charge of network information collection is passed to the management request processing unit 23a (1004). The management request processing unit 23a inquires the MIB to the MIB management unit 22, associates the node address with the OID, and enters the OID corresponding to each node in the OID 33 of the node address table (1005).

  The node information collection unit 24a of the GW node 2 inquires about how to send the management request to the node information collection unit 24b of each node (1006), and enters the processing method 34 of the node address table according to the response from the node. .

  The management request processing operation is the same as in the first embodiment.

  As described above, the present embodiment is characterized in that the gateway node has means for inquiring another node for a node that manages network information of the ring network.

  By operating as described above, the network information can be collected even when the representative node that knows the network information does not exist in the ring network.

Embodiment 9 FIG.
In the method shown in the second embodiment, an embodiment in which a node information collection unit collects network information when a representative node that grasps network information does not exist in the ring network will be described.

  The configurations of the GW node 2 and the node 3 are the same as those in the second embodiment.

  Since the preparatory operation up to the manageable state is the same as that in the eighth embodiment, description thereof is omitted.

  Further, the management request processing operation is the same as that of the second embodiment, and thus the description thereof is omitted.

  As described above, the present embodiment is characterized in that the gateway node has means for inquiring another node for a node that manages network information of the ring network.

  By operating as described above, the network information can be collected even when the representative node that knows the network information does not exist in the ring network.

  In each embodiment described above, the GW node 2 and the node 3 can be realized by a computer.

  Although not shown, the GW node 2 and the node 3 include a CPU (Central Processing Unit) that executes a program.

  For example, the CPU is connected via a bus to a ROM (Read Only Memory), a RAM (Random Access Memory), a flash memory, a communication board, a display device, a K / B (keyboard), a mouse, an FDD (Flexible Disk Drive), and a CDD. (Compact disk drive), magnetic disk device, optical disk device, printer device, scanner device, etc. can be connected.

  The RAM is an example of a volatile memory. ROM, flash memory, FDD, CDD, magnetic disk device, and optical disk device are examples of nonvolatile memory. These are examples of a storage device or a storage unit.

  The data and information handled by the GW node 2 and the node 3 of each embodiment described above are stored in a storage device or a storage unit, and are recorded and read out by each unit of the GW node 2 and the node 3.

  The magnetic disk device stores an operating system (OS), a window system, a program group, and a file group (database).

  The program group is executed by a CPU, OS, window system, and the like.

  Each part of the GW node 2 and the node 3 may be configured by a program that can be operated by a computer partially or entirely. Alternatively, it may be realized by firmware stored in the ROM. Alternatively, it may be implemented by software, hardware, or a combination of software, hardware, and firmware.

  The program group stores a program that causes the CPU to execute the processing described as “˜unit” in the description of the embodiment. These programs are created in a computer language such as C language, for example.

  The program is stored in another recording medium such as a magnetic disk device, FD (Flexible Disk), optical disk, CD (compact disk), MD (mini disk), DVD (Digital Versatile Disk), and read by the CPU. And executed.

The figure which shows the network structural example which concerns on Embodiment 1-9. FIG. 3 is a diagram illustrating a configuration example of a GW node and nodes according to the first embodiment. FIG. 3 is a diagram showing an example of a node address table according to the first embodiment. FIG. 3 is a diagram showing an example of a node address table according to the first embodiment. FIG. 3 is a flowchart showing an example of a preparation operation according to the first embodiment. FIG. 3 is a flowchart showing an example of a management request processing operation according to the first embodiment. FIG. 4 shows an example of a preparation operation according to the first embodiment. FIG. 6 is a diagram showing an example of a management request processing operation according to the first embodiment. The figure which shows the structural example of the GW node which concerns on Embodiment 2, and a node. FIG. 9 is a flowchart showing an example of a management request processing operation according to the second embodiment. FIG. 11 shows an example of a preparation operation according to the third embodiment. FIG. 18 shows an example of a node address table according to the sixth embodiment. FIG. 18 shows an example of a node address table according to the sixth embodiment. FIG. 20 shows an example of a preparation operation according to the eighth embodiment.

Explanation of symbols

  1 management device, 2 gateway node, 3 node, 4 network, 5 ring network, 21 SNMP protocol processing unit, 22 MIB management unit, 23 management request processing unit, 24 node information collection unit, 25 node address table management unit, 26 Ring network management protocol processing unit, 27 communication unit, 28 OID analysis unit, 270 TCP / IP protocol stack, 271 ring network protocol stack.

Claims (13)

Between a management device that is arranged in the first network and performs network management using the SNMP (Simple Network Management Protocol) protocol, and a plurality of nodes that are arranged in the second network and are targets of network management by the management device A gateway device for relaying communication,
For each node, an OID processing method table management unit that manages an OID processing method table indicating an OID corresponding to each node in an SNMP protocol OID (Object Identifier) and a processing method of each node;
A first network communication unit that receives a management request including an OID corresponding to one of the nodes from the management device;
A node processing method specifying unit for comparing the OID included in the management request with the OID shown in the OID processing method table to identify the node targeted by the management request, and for specifying the processing method of the node;
A second network communication unit that transmits a management request for the specific node specified by the node processing method specifying unit to the specific node according to the processing method specified by the node processing method specifying unit. A gateway device. The OID processing method table management unit
When there is a node having a plurality of corresponding OIDs, an OID processing method table indicating a processing method for each OID is managed for the node,
The node processing method identification unit is
The OID included in the management request is compared with the OID shown in the OID processing method table to identify the node targeted by the management request, and the processing method for each OID is indicated in the OID processing method table for the specified node. 2. The gateway device according to claim 1, wherein a processing method corresponding to the OID included in the management request is specified. The gateway device further includes:
It has a node information collection unit that collects processing method information for each node,
The OID processing method table management unit
2. The gateway device according to claim 1, wherein a processing method of each node is managed in an OID processing method table based on information collected by the node information collecting unit. The node information collection unit
When there is a node with multiple corresponding OIDs, collect processing method information for each OID for the node,
The OID processing method table management unit
4. The gateway device according to claim 3, wherein a processing method for each OID is managed in an OID processing method table for a node for which processing method information is collected for each OID by the node information collection unit. The plurality of nodes correspond to protocols other than the SNMP protocol,
The first network communication unit is
Receiving a management request by the SNMP protocol from the management device;
The node processing method identification unit is
Protocol conversion is performed on the management request received by the first network communication unit, and a management request according to a protocol to which the node targeted by the management request corresponds is generated,
The second network communication unit is
The gateway apparatus according to claim 1, wherein the management request after the protocol conversion by the node processing method specifying unit is transmitted to the specific node. The plurality of nodes correspond to the SNMP protocol,
The first network communication unit is
Receiving a management request by the SNMP protocol from the management device;
The node processing method identification unit is
2. The gateway device according to claim 1, wherein the second network communication unit is instructed to transmit a management request by the SNMP protocol received by the first network communication unit to a node targeted by the management request. . The gateway device further includes:
A node information collection unit that collects node address information of each node from each node,
The OID processing method table management unit
The gateway device according to claim 1, wherein the node address of each node is managed in the OID processing method table based on the node address information collected by the node information collection unit. The OID processing method table management unit
2. The gateway apparatus according to claim 1, wherein in a predetermined case, the processing method of any node indicated in the OID processing method table is changed. Any one of the plurality of nodes corresponds to a plurality of processing methods,
The OID processing method table management unit
Managing an OID processing method table in which selection conditions serving as a reference for selecting a processing method are managed for nodes corresponding to a plurality of processing methods;
The node processing method identification unit is
When the OID included in the management request is compared with the OID shown in the OID processing method table to identify the node targeted by the management request, and when the identified node corresponds to a plurality of processing methods, 2. The gateway device according to claim 1, wherein a specific processing method is selected from a plurality of processing methods in accordance with a processing method selection condition for the node indicated in the OID processing method table. Any one of the plurality of nodes has a plurality of corresponding OIDs, and a plurality of processing methods exist for any one of the OIDs.
The OID processing method table management unit
For a node having a plurality of corresponding OIDs and a plurality of processing methods for any one of the OIDs, a selection condition serving as a criterion for selecting a processing method is indicated for each OID having a plurality of processing methods. Manage the OID processing method table,
The node processing method identification unit is
The OID included in the management request is compared with the OID shown in the OID processing method table to identify the node targeted by the management request, and there are multiple processing methods for the OID included in the management request. 2. The gateway device according to claim 1, wherein a specific processing method is selected from a plurality of processing methods according to the processing method selection condition for the OID indicated in the OID processing method table. The gateway device further includes:
When a node that can collect network information is queried with respect to the plurality of nodes and a response is received from any node that network information can be collected, the node is designated as an information collection node. The gateway apparatus according to claim 1, further comprising a node information collection unit configured to collect network information when a response is not obtained from any of the nodes. Between a management device that is arranged in the first network and performs network management using the SNMP (Simple Network Management Protocol) protocol, and a plurality of nodes that are arranged in the second network and are targets of network management by the management device A relay method for relaying communication,
A first network communication step of receiving a management request including an SNMP protocol OID (Object Identifier) corresponding to one of the nodes from the management device;
The OID processing method table indicating the OID corresponding to each node and the processing method of each node is compared with the OID included in the management request to identify the node targeted by the management request, and A node processing method specifying step for specifying a processing method;
A second network communication step of transmitting a management request for the specific node specified by the node processing method specifying step to the specific node according to the processing method specified by the node processing method specifying step. Relay method. Between a management device that is arranged in the first network and performs network management using the SNMP (Simple Network Management Protocol) protocol, and a plurality of nodes that are arranged in the second network and are targets of network management by the management device A program that causes a computer to relay communication,
A first network communication process for receiving a management request including an SNMP protocol OID (Object Identifier) corresponding to one of the nodes from the management device;
The OID processing method table indicating the OID corresponding to each node and the processing method of each node is compared with the OID included in the management request to identify the node targeted by the management request, and A node processing method specifying process for specifying a processing method;
Causing the computer to execute a second network communication process for transmitting the management request for the specific node specified by the node processing method specifying process to the specific node according to the processing method specified by the node processing method specifying process. A program characterized by that.

Images