JPH0993265A - Distributed type network management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To distribute the processing load imposed onto a manager by providing plural distribution managers in a communication network so as to distribute the traffic of a communication packet when node information is collected in a system where the communication network is managed based on an SNMP protocol. SOLUTION: Distribution managers 10-1, 10-2,... acquire node information from agents 20-1, 20-2,... which belong respectively to partial networks 30-1, 30-2 in the management range to generate topology information of the network. The distribution manager 10-1 acquires the topology information generated by other distribution manager to grasp the entire topology information of a communication network 40.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management method, and more particularly to a network management method for distributing a plurality of managers in a communication network and performing communication between the distributed managers based on SNMP.

[0002]

2. Description of the Related Art In the IAB (IAB) management standard, a protocol for network management is named as SMP (SNMP). This standard is based on RFC 1157, Simple Network Management Protocol (RFC 11
57, "A Simple Network Mana
A standard management method based on SNMP collects information about nodes to which agents belong, and manages network topology information of the entire communication network managed by the manager (hereinafter referred to as "network protocol"). The network configuration diagram is easily created by the graphical user interface (GUI) using this topology information, and is displayed on the display device.

As a method for a manager to detect a node belonging to a communication network, there is known Japanese Unexamined Patent Publication No. 4-229742, "Node discovery method for computer network". In this method, a manager detects a node by collecting an address conversion table for converting an internet protocol (IP) address of an agent into a physical address. Further nodes can be detected by querying the nodes contained in the address translation table collected by the manager. A list of all the nodes belonging to the communication network is created based on the address translation table collected in this way.

[0004]

According to the above-mentioned conventional technique, the manager can collect the information about all the nodes belonging to the communication network, but the node has the address translation information about the plurality of nodes as communication partners, In addition, since address translation information is usually duplicated among multiple agents, it is generally necessary to refer to a larger number of address translation information than the number of nodes that belong to the communication network. There is a problem that the number of communication packets transferred to the network increases, and the traffic of the communication packets concentrates on the communication path around the manager.

Further, the conventional manager must generate the topology information from the information about all the nodes belonging to the communication network, and the load on the manager becomes large in the case of a large-scale communication network having a large number of nodes. There is a problem.

In the prior art, a plurality of managers can be provided in the communication network, but each manager manages all the nodes belonging to the communication network, and there is no communication between the managers, so the above problem is solved. You cannot do it.

The present invention relates to a manager for distributing the traffic of communication packets transferred to collect node information and providing topology information by providing a plurality of distributed managers in a communication network. The purpose is to balance the load.

[0008]

According to the present invention, a plurality of distributed managers are provided in a communication network, each distributed manager receives node information from an agent belonging to the management range of the distributed manager, and based on this node information. Topology information about each object to be network-managed and topology information representing a relationship between different objects are generated and stored in a storage device, and at least one distributed manager has topology information within the management range of another distributed manager. Is characterized by a distributed network management method for receiving and storing in a storage device.

Here, the objects to be subjected to network management refer to constituent elements such as "network", "segment", "node", "gateway" and "interface" that hierarchically configure the communication network. In the IAB management standard, topology information is defined by a virtual database having a unique logical structure called a management information base. Therefore, hereinafter, this management information base will be referred to as Topology M.B. (Topology MIB). The topology MIB expresses, for each object, the address, name, operation state, etc. of the object in a table format, and provides an index for accessing each entry on the table. The actual data that is each entry on the table is also called an instance. Further, a table showing the correspondence relationship between different objects is provided, and an index for accessing each entry on this table is provided. Information representing the relationship between different components is treated as a management object. Topology MIB
The syntax for describing and the method of identifying each instance are described in RFC 1155, Structure and Identification of Management Information for TCS.
PIP Based Internets (RFC
1155, "Structure and Ide
ntificatoin of Management
Information for TCP / IP-b
ased internets ") and R.F.
Sea 1212, Concise M.B.D.Definitions (RFC 1212, "Conscious M"
IB Definitions)).

Since each distributed manager collects node information only from the agents of the nodes belonging to the management range, the number of communication packets for collecting the node information can be reduced and the traffic of the communication packets is distributed. Further, the processing load of the distribution manager that generates the topology information from the collected node information can be distributed. At least one distribution manager can acquire the topology information of the entire communication network by a process of receiving the topology information generated by another distribution manager and storing it in the storage device. Also, since the distributed manager that manages the entire communication network communicates with other distributed managers based on SNMP, the communication protocol handled by the distributed managers is unified to SNMP, and the configuration of the distributed managers can be simplified.

[0011]

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

FIG. 1 is a diagram showing the configuration of a communication network from the viewpoint of network management. The communication network 40 includes partial networks 30-1, 30-2, ...
・ ・ Composed of Here, the partial network is a division of the communication network 40 for the purpose of network management, and does not necessarily match the logical division unit of the communication network based on the communication control protocol. A multi-layered communication network in which the partial network 30 is further divided into several partial networks is also possible.

Distribution managers 10-1, 10-2, ...
· Indicates the partial networks 30-1, 30-2,
Information about each node is collected from the agents 20-1, 20-2, ... Within the ... And topology information about its own partial network is generated. Here, the agent 20 is an agent referred to as SNMP, and is located in each node and holds information about the node. The distribution manager 10-1 acquires the topology information from the other distribution managers 10-2, 10-3, ... And acquires the topology information of the entire communication network 40. The network management system shown in FIG. 1 is an example of a vertically distributed network management system.

FIG. 2 is a diagram showing the configuration of another communication network from the viewpoint of network management. The communication network 40 includes partial networks 30-11 and 30.
-12. Partial network 30-11
Is composed of partial networks 30-5, 30-6 ,. The partial network 30-12 is composed of partial networks 30-8, 30-9, .... The distributed managers 10-5, 10-6, ... Collect information about each node from the agents 20-5, 20-6, ... Within the partial networks 30-5, 30-6 ,. Collect and generate topology information about its own sub-network. Distribution manager 10
-5 is another distribution manager 10-6, 10-
Topology information is obtained from 7, ..., And the topology information of the entire partial network 30-11 is obtained. Further, the distribution manager 10-8 is the other distribution manager 10-.
Topology information is acquired from 9, 10-10, ... And the topology information of the entire partial network 30-12 is obtained.
Further, the distribution manager 10-5 is the distribution manager 10-5.
-8 obtains the topology information of the entire communication network 40 by referring to the topology information of the partial network 30-12. The distribution manager 10-8 is the partial network 30-1 of the distribution manager 10-5.
The topology information of the entire communication network 40 is obtained by referring to the topology information of No. 1. That is, the distribution managers 10-5 and 10-8 are based on the vertical distribution model, and the partial networks 30-11 and 30-, respectively.
Manage 12 The distribution managers 10-5 and 10
-8 is a communication network 4 based on the horizontal distribution model.
Manage 0.

FIG. 3 is a diagram showing the configuration of the distribution manager 10, in which the agent 20 and another distribution manager 1
It is a figure which shows the relationship with 0. Management range definition file 11
Is a file that defines the address range of the nodes belonging to the partial network 30. The node attribute table 12 is a table that stores node information. The node information collection unit 3 refers to the management range definition file 11,
It is a processing unit that collects node information from the agent 20 of the corresponding node and stores it in the node attribute table 12. The topology MIB 13 is a table that stores topology information. The topology MIB generation unit 4 is a processing unit that inputs the node attribute table 12 to generate topology information and stores it in the topology MIB 13. The other distribution manager definition file 14 is a file that defines addresses of other distribution managers. The topology MIB collection unit 6
This is a processing unit that refers to the other distribution manager definition file 14, collects topology information from the corresponding other distribution manager 10 and stores it in the topology MIB 13. Topology M
The IB distribution unit 8 refers to the other distribution manager definition file 14 and sends the topology M to the corresponding other distribution manager 10.
It is a processing unit that sends the requested topology MIB in the IB 13. Graphical user interface 9
Is notified from the topology MIB generation unit 4 and the topology MIB collection unit 6 when the contents of the topology MIB 13 are updated, added, or deleted, and the display unit 15 visually displays the topology MIB by referring to the topology MIB 13. Is a processing unit to be displayed. According to the communication network having the configuration shown in FIG. 1, the distribution manager 10-1 has the topology MI.
It has the B collection unit 6, but does not have the topology MIB distribution unit 8. Further, other distributed managers 10-2, 10-3, ...
Has a topology MIB distribution unit 8
The B collection unit 6 is not provided. Further, according to the communication network configured as shown in FIG. 2, the distributed managers 10-5 and 10-
Reference numeral 8 includes a topology MIB collection unit 6 and a topology MIB distribution unit 8. Other distributed managers 10-6, 10-
7, 10-9, 10-10 are topology MIB distribution units 8
However, the topology MIB collection unit 6 is not provided. The distribution manager 10 communicates with the agent 20 and other distribution managers 10 based on SNMP. The distribution manager 10 can be realized by an information processing device including a personal computer and a workstation. The node information collection unit 3, the topology MIB generation unit 4, the topology MIB collection unit 6, the topology MIB distribution unit 8, and the graphical user interface 9 are realized by executing a program stored in the storage device of this information processing device. To be done. Further, the management range definition file 11, the node attribute table 12,
The topology MIB 13 and the other distribution manager definition file 14 are files or tables stored in the storage device of this information processing device.

The management range definition file 11 sets the address range of the nodes belonging to the partial network 30. For example, 200.10.20.1-70 200.10.20.100 indicates that the distribution manager 10 has the node address 200.10.
It shows that the address range from 20.1 to 200.10.20.70 and the node address 200.10.20.100 are directly managed.

FIG. 4 is a diagram showing a data format of the node attribute table 12 and its case. The name and specification of the MIB-II object are specified in RFC1213.
If the node has multiple interfaces, there will be as many columns as there are interfaces. FIG. 4 shows an example in which the node has two interfaces.

The node information collection unit 3 refers to the management range definition file 11 and acquires the range of addresses of the nodes belonging to the partial network 30 designated to be directly managed by the distribution manager. Next, the node information collection unit 3
Discovers a node only within the designated partial network 30, and the agents 20 to M of the discovered node
The node information shown in FIG. 4 among the management objects defined by IB-II is acquired and stored in the corresponding storage location of the node attribute table 12. When the collection of node information is completed, the node information collection unit 3 causes the topology MIB generation unit 4 to
To notify. The node information collection unit 3 periodically acquires node information from the agent 20.

5a and 5b show the topology MIB13.
It is a figure which shows the data format and its example. The topology information about each object has an address, a name, an instance having an operating state of this object, and an index for accessing each instance. The topology information indicating the relationship between different objects has an instance indicating the correspondence relationship between the addresses of different objects and an index for accessing each instance. The case shows the topology MIB generated from the case of the node attribute table 12 shown in FIG. topoN
etTable is the MIB for the network. Here, the network is a network defined by a communication control protocol, and is a range in which managed objects are managed by unique network addresses. topoSegTable is the MIB for the segment. Here, the segment is a unit that physically and electrically divides the network. to
poNodeTable is the MIB for a node. The node is a terminal device or an information processing device connected to the network. topoGWTable is the MIB for the gateway. A gateway is a type of node, which is a device that connects networks. topoIFTable is a MIB about an interface. The interface belongs to a node including a gateway and is a connection part between the node and a physical communication line. In addition, to of the topoNetTable
poNetStatus and topoSegTable
TopoSegStatus is a case where only the node shown in FIG. 4 is considered, and does not necessarily become the illustrated state when another node is included in the network or segment.

The topoSeg2NodeTab of FIG. 5b
le is a table showing the relationship between the segment and the nodes belonging to the segment. topoSeg2GWT
A table is a table showing the relationship between the segment and the gateway connected to the segment. topoG
W2SegTable is a table showing the relationship between the gateway and the segment connecting the gateway. topoNode2IFTable is a table showing the relationship between a node and the interface of the node. For example, topoSeg2NodeTable
'2' represents a segment-to-node toe.

FIG. 6 is a flow chart showing the flow of processing of the topology MIB generator 4. The topology MIB generation unit 4 inputs the node attribute table 12 for one node (step 42), determines the node address (step 43), and determines the address and segment of the network to which the node belongs (step 44). Next topo
The process from the generation / update process of the NodeTable entry (step 45) to the generation / update process of the topoNode2IFTable entry (step 50) is performed. As a result of the segment determination processing, if the node belongs to a plurality of different segments (YES in step 51), to
The process from generation / update processing of the poGWTable entry (step 52) to generation / update processing of the topoGW2SegTable entry (step 54) is performed. Next, when the content (instance) of the topology MIB is updated, added, or deleted (YES in step 55), the topology MIB distribution unit 8 and the graphical user interface 9 are notified (step 56). Finally, depending on the current state of the node, topoNetStatus and topoSe
gStatus is determined and stored in the table (step 57). For the first node, the to of that node
poNodeStatus is topoNetStatus
s and topoSegStatus. For the subsequent nodes, for example, topoNetStatus or topoSegStatus is Normal, and if the node is Normal, then Normal and the node is Cri.
Marginal if it is tial, Margi if the node
If it is nal, it is Marginal. topoNetS
status or topoSegStatus is Crit
ical and the node is Normal, Margi
nal, if the node is Critical, it is Critical
l, if the node is Marginal, it is Marginal. In this example, if all the nodes belonging to the network or segment are Normal, they are Normal, if all the nodes are Critical, they are Critical; otherwise, they are Marginal.

FIG. 7 is a flow chart showing details of the node address determination process (step 43). By referring to the interface column of the node information, the node name corresponding to the interface address is acquired using the service of the communication control mechanism (step 432), and the acquired node name and the node name in the node attribute table 12 are If they match (YES in step 433), the interface address is determined as a node address (step 4).
34). If not, the process returns to step 432 for the next interface column and repeats the above processing (step 431). If the interface column is exhausted but the node address cannot be determined (step 435), the address with the smallest number among the interface addresses is set as the node address (step 436).

FIG. 8 is a flow chart showing details of the process (step 44) for determining the address and segment of the network to which the node belongs. The address of the network to which the node belongs is calculated from the logical product of the interface address and the subnet mask (step 44).
2), if topoSegType matches the interface type for the entry having the index starting with the network address obtained in the index of topoSegTable (step 444YE)
S), and determines the value of topoSegIndex of the entry as the identifier of the segment to which the node belongs (step 445). If the segment identifier cannot be determined (YES in step 446), a new segment identifier is assigned to the segment to which the node belongs (step 447). Step 4 if there is a next interface field
Returning to step 42, the above process is repeated (step 441).
If the entry corresponding to topoSegTable has not been created, the segment identifier cannot be determined, so a new segment identifier is assigned. If the networks to which the two interfaces belong are different, the segments are different, and the segment identifier initially assigned is 1.

FIG. 9 is a flowchart showing the flow of generation / update processing of the topoNodeTable entry. By this processing, the topoNodeTable of FIG. 5a (iii) is generated from the case of the node attribute table 12 of FIG.

FIG. 10 is a flowchart showing the flow of generation / update processing of the topoNetTable entry. By this processing, the topoNetTable of FIG. 5a (i) is generated from the case of the node attribute table 12 of FIG.

FIG. 11 is a flowchart showing the flow of generation / update processing of the topoSegTable entry. By this processing, the topoSegTable of FIG. 5a (ii) is generated from the case of the node attribute table 12 of FIG.

FIG. 12 is a flow chart showing the flow of generation / update processing of the topoIFTable entry.
By this processing, the topoIFTable of FIG. 5a (v) is generated from the case of the node attribute table 12 of FIG.

FIG. 13 shows topoSeg2NodeTa.
It is a flow chart which shows the flow of generation update processing of a ble entry. By this processing, from the example of the node attribute table 12 of FIG. 4 totopeg2Nod of FIG. 5b (vi)
An eTable is created.

FIG. 14 shows topoNode2IFTab.
It is a flow chart which shows a flow of generation update processing of an le entry. By this processing, the node attribute table 1 of FIG.
2 case, topoNode2IFT of FIG. 5b (ix)
The ABLE is generated.

FIG. 15 is a flow chart showing the flow of generation / update processing of the topoGWTable entry.
By this processing, the topoGWTable of FIG. 5a (iv) is generated from the case of the node attribute table 12 of FIG.

FIG. 16 shows topoSeg2GWTabl.
It is a flow chart which shows the flow of generation update processing of e entry. By this processing, the node attribute table 12 of FIG.
5b (vii) topoSeg2GWTa from the example
ble is generated. When a node is a gateway, the network or segment to which the node belongs is the network or segment itself to which the gateway connects.

FIG. 17 shows the topoGW2SegTabl.
It is a flow chart which shows the flow of generation update processing of e entry. By this processing, the node attribute table 12 of FIG.
5b (viii) topoGW2SegTa from the example
ble is generated.

The other distribution manager definition file 14 includes a distribution manager located at a higher position in the vertical distribution relationship from the distribution manager, a distribution manager located at a lower position in the vertical distribution relationship, and a horizontal distribution distribution manager. Defines the node address of the relevant distributed manager. The following definition is an example of the other distributed manager definition file 14. Vertical upper distribution manager = 201.20.10.10 Vertical upper distribution manager = 201.18.20.20 Vertical lower distribution manager = 201.10.21.30 Vertical lower distribution manager = 201.10.22.40 Horizontal distribution Manager = 201.20.1.100 Horizontal distribution manager = 201.30.2.50 In the network management system shown in FIG. 1, for example, the distribution manager 10-1 defines only a vertical subordinate distribution manager. Further, in the network management system shown in FIG. 2, for example, the distribution manager 10-5 defines a vertical subordinate distribution manager and a horizontal distribution manager.

The topology MIB collection unit 6 refers to the other distribution manager definition file 14 and refers to the distribution manager 1 concerned.
A node address of a distribution manager located in a lower position in a vertical distribution relationship with 0 and a distribution manager 10 in a horizontal distribution relationship with the distribution manager 10 is acquired. Topology MI of distribution manager 10 of the acquired address
The entire B13 is collected using the SNMP request and the SNMP response, and the collected result is stored in the topology MIB 13 of the distribution manager 10. Further, the change of the topology MIB notified from the other distribution manager 10 via the SNMP trap is reflected in the topology MIB 13 of the distribution manager 10. When an instance of the topology MIB 13 is updated, added, or deleted, the fact is notified to the topology MIB distribution unit 8 and the graphical user interface 9. The topology MIB distribution unit 8 is also notified of the distinction between the information obtained from the vertically lower distribution manager and the information obtained from the horizontal distribution manager. The topology MIB collection unit 6 periodically acquires the topology MIB from another distribution manager.

The topology MIB distributor 8 receives the topology M from another distribution manager 10 in response to an SNMP request.
When the IB reference request is received, the topology MIB 13 is referenced and the instance of the requested topology MIB is S
It responds as an NMP response. Further, referring to the other distribution manager definition file 14, the distribution manager 10 concerned
And the node addresses of the distribution manager 10 which is in the upper position in the vertical distribution relationship and the distribution manager 10 which is in the horizontal distribution relationship with the distribution manager 10. When the topology MIB generation unit 4 notifies the change of the topology MIB, the topology MIB 13 is referred to and the topology MI is changed.
The changed contents of B are notified to the vertically upper distribution manager and horizontal distribution manager defined via the SNMP trap. From the topology MIB collection unit 6 to the topology M
When the change in the IB is notified, the changed content of the topology MIB is notified to another distributed manager by referring to the topology MIB 13 via the SNMP trap. If the changed topology MIB is the information obtained from the vertically lower distribution manager, the vertically upper distribution manager and the horizontal distribution manager are notified, and if the changed topology MIB is the information obtained from the horizontal distribution manager, only the vertically upper distribution manager is notified.

Graphical user interface 9
Displays a network configuration diagram visually representing the topology MIB on the display unit 15 with reference to the topology MIB 13. When a topology MIB change is notified from the topology MIB generation unit 4 or the topology MIB collection unit 6, the changed contents are displayed with reference to the topology MIB 13.
It will be reflected in the above network configuration diagram.

FIG. 18 is a diagram showing a display example, which is an example of displaying a map of the entire communication network. The network net1, the network net3, and the gateway (GW) are represented by symbols, and the network net1
And gateway, gateway and network net3
Are connected by wiring symbols, respectively, and show the configuration of the entire communication network. The name and address are displayed below the symbol indicating the network or gateway, respectively. The state can be displayed by the display color of the symbol. All networks existing in the communication network are topoNetT of topology MIB13.
You can find out by looking at all the entries in the table. All gateways present in the communication network can be known by referring to all the entries in topoGWTable. The connection between the network and the gateway is topoSe
g2GWTable or topoGW2SegTable
It can be known by referring to e.

FIG. 19 is a diagram showing another display example, which is a display example of a network map for expanding the network net1 into segments. The figure shows that the network net1 is composed of one segment net1: Seg1. The state can be displayed by the display color of the symbol. The segment belonging to the network net1 can be known by referring to the entry having the index starting with the address of the network net1 among the entries of the topoSegTable. The gateway connecting to this segment is t
The entry in the opoSeg2GWTable that has an index that starts with the index of this segment is referenced, and the topoSeg2GW GW of that entry is referenced.
TopoG that has the value of Address as an index
This can be known by referring to the entry of WTable.

FIG. 20 is a diagram showing another display example, which is a display example of a node map for expanding the node node002 into an interface. The figure shows that node node002 is 2
Two interfaces node002: he1 and nod
e002: he8. The interface name and address are displayed below the symbol that represents the interface. The state can be displayed by the display color of the symbol. The interface of a certain node refers to the entry having the index starting with the address of the node among the entries of topoNode2IFTable, and further, t of that entry is referenced.
This can be known by referring to the entry of topoIFTable having the value of opoNode2IF IFAddress as an index.

FIGS. 21a and 21b are diagrams showing another example of the topology MIB 13 for explaining the following display examples. The meaning of each table is as described above.

FIG. 22 is a diagram showing another display example, and is a display example of a segment map for expanding the segments net1: Seg1 of FIG. 19 when the topology MIB 13 is as shown in FIGS. 21a and 21b. The segment map displays symbols representing nodes belonging to the designated segment and connection symbols representing connections between the nodes. The figure shows that three nodes belong to the segment net1: Seg1, of which the node node002 is a gateway and the three nodes are connected to each other by a bus-type communication path. The state can be displayed by the display color of the symbol. The node belonging to the segment is topoSeg2NodeTa
In the ble, an entry having an index that starts with the index of the segment is referred to, and further, topoSeg2Node NodeAddress of the entry is referenced.
TopoNodeTable with the value of as an index
It can be known by referring to the entry of e. The gateway belonging to the segment is topo
In the Seg2GWTable, the entry having the index that starts with the index of the segment is referred to, and further the topoSeg2GW GWAdd of the entry is referenced.
topoGWTa that has the value of “ress” as an index
This can be known by referring to the entry of ble. The connection shape between the nodes belonging to the segment is
Determined by referring to the segment's topoSegType.

The network configuration diagram described above is used not only for the purpose of displaying the configuration and status of the communication network, but, for example, a specific node in the segment map is selected to execute a specific network management operation. Play an important role.

Below is a part of the design specifications used when developing the topology MIB generator 4,
An example of the definition description that defines the logical structure of each managed object of B will be given.

IMPORTS indicates the name of the standard to which it conforms. Next 4 OBJECT IDENTIFIER
Shows the method of constructing the ID to be inserted in the request. t
opoNet OBJECT IDENTIFIER
Indicates to group objects starting with topoNet. Next, the attributes of topoNetTable are shown, and topoNetTable has a plurality of topoNs.
It is indicated that it is composed of etEntry. Next top
oNetEntry attributes and topoNetEntry
y is topoNetAddress, topoNetS
It consists of each data item of status and topoNetName, and the index is topoNetAddre.
It indicates that ss is used as it is. Next, the attributes of each data item and their possible values are defined. Below is topoSeg
Table, topoNodeTable, topoG
The same applies to WTable and topoIFTable. TopoSeg that indicates the correspondence between the components
2NodeTable, topoSeg2GWTabl
e, topoGW2SegTable and topoNo
The same applies to de2IFTable.

TOPOLOGY-MIB-EXAMPLE DEFINITIONS :: = BEGIN IMPORTS enterprises, NetworkAddress, IpAddress, Counter, Gauge, Timeticks FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212 DisplayString FROM RFC1213-MIB; tokyo OBJECT IDENTIFIER :: = (enterprises 116} systemExMib OBJECT IDENTIFIER :: = {tokyo 5} cometMibs OBJECT IDENTIFIER :: = {systemExMib 1} topology OBJECT IDENTIFIER :: = {cometMibs 5} --Topology MIB --Logical element of management network and --configuration MIB topoNet OBJECT IDENTIFIER :: = {topology 1}-Topology Network Group-(The Topology Network group)-MIB topoNetTable OBJECT-TYPE SYNTAX SEQUENCE OF topoNetEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table that represents networks that exist in the management network" :: = {topoNet 1} topoNetEntry OBJECT-TYPE SYNTAX topoNetEntry ACCESS not-acces sible STATUS mandatory INDEX {topoNetAddess} :: = {topoNetTable 1} topoNetEntry :: = SEQUENCE {topoNetAddress IpAddress, topoNetStatus INTEGER, topoNetName Display String} topoNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Network address" :: = {topoNetEntry 1} topoNetStatus OBJECT-TYPE SYNTAX INTEGER {unknown (1), normal (2), marginal (3), critical (4)} ACCESS read-only STATUS mandatory DESCRIPTION "Network status unknown (1) unrecognizable normal (2) Normal area marginal (3) Warning area critical (4) Critical area :: = {topoNetEntry 2} topoNetName OBJECT-TYPE SYNTAX Display String ACCESS read-only STATUS mandatory DESCRIPTION "Network name :: = {topoNetEntry 3}.

TopoSeg OBJECT IDENTIFIER :: = {topology 2} --Topology Segment Group-(The Topology Segment group)-MIB topoSegTable OBJECT-TYPE SYNTAX SEQUENCE OF topoSegEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table that represents the segments existing in the management network" :: = {topoSeg 1} topoSegEntry OBJECT-TYPE SYNTAX topoSegEntry ACCESS not-accessible STATUS mandatory INDEX {topoSegNetAddess, topoSegIndex} :: = {topoSegTable 1} topoSegEntry :: = SEQUENCE {topoSegNetAddress IpAddress, topoSegIndex INTEGER, topoSegStatus INTEGER, topoSegName Display String, topoSegType INTEGER} topoSegNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Address of the network to which the segment belongs" :: = {topoSegEntry 1} -topoSeg SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Segment identification ":: = {topoSegEntry 2} topoSegStatus OBJECT-TYPE SYNTAX INTEGER {unknown (1), normal (2), marginal (3), critical (4)} ACCESS read-only STATUS mandatory DESCRIPTION" Segment status unknown (1) Unrecognizable normal (2) Normal area marginal (3) Warning area critical (4) Critical area :: = {topoSegEntry 3} topoSegName OBJECT-TYPE SYNTAX Display String ACCESS read-only STATUS mandatory DESCRIPTION "Segment name :: = {topoSegEntry 4} topoSegType OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The segment type. Use the same value as ifType of MIB-II. ":: = {topoSegEntry 5}."

TopoNode OBJECT IDENTIFIER :: = {topology 3}-Topology Node group-(The Topology Node group)-MIB topoNodeTable OBJECT-TYPE SYNTAX SEQUENCE OF topoNodeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table representing nodes existing in the management network" :: = {topoNode 1} topoNodeEntry OBJECT-TYPE SYNTAX topoNodeEntry ACCESS not-accessible STATUS mandatory INDEX {topoNodeAddess} :: = {topoNodeTable 1} topoNodeEntry :: = SEQUENCE { topoNodeAddress IpAddress, topoNodeNetAddress IpAddress, topoNodeSegIndex INTEGER, topoNodeStatus INTEGER, topoNodeName Display String} topoNodeAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Node address" :: = {topoNodeEntry 1} topoNodeNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only only STATUS mandatory DESCRIPTION "Address of the network to which the node belongs" :: = {topoNode Entry 2} topoNodeSegIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifier of the segment to which the node belongs" :: = {topoNodeEntry 3} topoNodeStatus OBJECT-TYPE SYNTAX INTEGER {unknown (1), normal (2), marginal ( 3), critical (4)} ACCESS read-only STATUS mandatory DESCRIPTION "Node status unknown (1) unrecognizable normal (2) normal marginal (3) warning area critical (4) critical area" :: = {topoNodeEntry 4 } topoNodeName OBJECT-TYPE SYNTAX Display String ACCESS read-only STATUS mandatory DESCRIPTION "Node name :: = {topoNodeEntry 5}.

TopoGW OBJECT IDENTIFIER :: = {topology 4} --Topology Gateway Group-(The Topology Gateway group)-MIB representing a component gateway topoGWTable OBJECT-TYPE SYNTAX SEQUENCE OF topoGWEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table representing gateways existing in the management network" :: = {topoGW 1} topoGWEntry OBJECT-TYPE SYNTAX topoGWEntry ACCESS not-accessible STATUS mandatory INDEX {topoGWAddess} :: = {topoGWTable 1} topoGWEntry :: = SEQUENCE { topoGWAddress IpAddress, topoGWStatus INTEGER, topoGWName Display String} topoGWAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Gateway address" :: = {topoGWEntry 1} topoGWStatus OBJECT-TYPE SYNTAX INTEGER {unknown (1), normal (2 ), marginal (3), critical (4)} ACCESS read-only STATUS mandatory DESCRIPTION "Gateway status unknown (1) unrecognizable normal (2) normal range m arginal (3) Critical area critical (4) Critical area ":: = {topoGWEntry 2} topoGWName OBJECT-TYPE SYNTAX Display String ACCESS read-only STATUS mandatory DESCRIPTION" Gateway name :: = {topoGWEntry 3}.

TopoIF OBJECT IDENTIFIER :: = {topology 5} --Topology Interface Group-(The Topology Interface group)-MIB topoIFTable OBJECT-TYPE SYNTAX SEQUENCE OF topoIFEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table representing interfaces existing in the management network" :: = {topoIF 1} topoIFEntry OBJECT-TYPE SYNTAX topoIFEntry ACCESS not-accessible STATUS mandatory INDEX {topoIFAddess} :: = {topoIFTable 1} topoIFEntry :: = SEQUENCE { topoIFAddress IpAddress, topoIFNodeAddress IpAddress, topoIFStatus INTEGER, topoIFName Display String} topoIFAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "interface address" :: = {topoIFEntry1} topoIFNodeAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Address of the node to which the interface belongs" :: = {topoIFE ntry 2} topoIFStatus OBJECT-TYPE SYNTAX INTEGER {unknown (1), normal (2), marginal (3), critical (4)} ACCESS read-only STATUS mandatory DESCRIPTION "Interface status unknown (1) unrecognizable normal (2 ) Normal area marginal (3) Warning area critical (4) Critical area ":: = {topoIFEntry 3} topoIFName OBJECT-TYPE SYNTAX Display String ACCESS read-only STATUS mandatory DESCRIPTION" Interface name :: = {topoIFEntry 4}.

TopoSeg2Node OBJECT IDENTIFIER :: = {topology 6}-(The Topology Segment to Node group)-From a network identifier or from a segment identifier --To that network or segment Belonging to-can get nodes topoSeg2NodeTable OBJECT-TYPE SYNTAX SEQUENCE OF topoSeg2NodeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table representing the relationship between a network or segment and the nodes that belong to that network or segment" :: = { topoSeg2Node 1} topoSeg2NodeEntry OBJECT-TYPE SYNTAX topoSeg2NodeEntry ACCESS not-accessible STATUS mandatory INDEX {topoSeg2NodeNetAddess, topoSeg2NodeSegIndex, topoSeg2NodeNodeAddess} Address NodeNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Network Address" :: = {topoSeg2NodeEntry 1} topoSeg2NodeSegIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Segment Identifier" :: = {topoSeg2NodeEntry 2} topoSeg2NodeNodeAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Node address" :: = {topoSeg2NodeEntry 3}.

TopoSeg2GW OBJECT IDENTIFIER :: = {topology 7}-Topology Network to Gateway Group-(The Topology Segment to Gateway group)-From a network identifier or from a segment identifier --To that network or segment Connected-You can get the gateway topoSeg2GWTable OBJECT-TYPE SYNTAX SEQUENCE OF topoSeg2GWEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table representing the relationship between a network or segment and the gateway connected to that network or segment": : = {topoSeg2GW 1} topoSeg2GWEntry OBJECT-TYPE SYNTAX topoSeg2GWEntry ACCESS not-accessible STATUS mandatory INDEX {topoSeg2GWNetAddess, topoSeg2GWSegIndex, topoSeg2GWGWAddesseg 2GWTable 1} topoSeg2GWtoAddress, = Spo2egPoseg2GW } topoSeg2GWNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Network Address" :: = {topoSeg2GWEntry 1} topoSeg2GWSegIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Segment Identifier" :: = {topoSeg2GWEntry 2 } topoSeg2GWGWAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Gateway address" :: = {topoSeg2GWEntry 3}.

TopoGW2Seg OBJECT IDENTIFIER :: = {topology 8}-(The Topology Gateway to Segment group)-Connecting to the gateway from the gateway address--Network or segment TopoGW2SegTable OBJECT-TYPE SYNTAX SEQUENCE OF topoGW2SegEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table representing the relationship between a gateway and the network or segment connected to that gateway" :: = {topoGW2Seg 1} topoGW2SegEntry OBJECT- TYPE SYNTAX topoGW2SegEntry ACCESS not-accessible STATUS mandatory INDEX {topoGW2SegGWAddess, topoGW2SegNetAddess, topoGW2SegSegIndex} :: = topoGW2SegTable 1} topoGW2SegEntry INTO_topoGW2SegGWAddress IpAddress, topoGW2SegGWAddress IpAddress, topoGW2SegGWAddress IpAddress, topoGW, S TATUS mandatory DESCRIPTION "Gateway address" :: = {topoGW2SegEntry 1} topoGW2SegNetAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Network address" :: = {topoGW2SegEntry 2} topoGW2SegSegIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Segment identifier" :: = {topoGW2SegEntry 3}.

TopoNode2IF OBJECT IDENTIFIER :: = {topology 9}-(Topology Node to Interface group) Yes topoNode2IFTable OBJECT-TYPE SYNTAX SEQUENCE OF topoNode2IFEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table that represents the relationship between the node and the interface that the node has" :: = {topoNode2IF 1} topoNode2IFEntry OBJECT-TYPE SYNTAX topoNode2IFEntry ACCESS not-accessible STATUS mandatory INDEX {topoNode2IFNodeAddess, topoNode2IFIFAddess} :: = {topoNode2IFTable 1} topoNode2IFEntry :: = SEQUENCE {topoNode2IFNodeAddress IpAddress, topoNode2IFIFAddress IpAddress} topoNode2IFNodeAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only Node2) => Address to 1 of the nodes :: IF_ACCESS_NOTIFY topoNode2IFIFAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Interface address" :: = {topoNode2IFEntry 2}.

[0054]

According to the present invention, since the process of collecting node information and the process of generating topology information are distributed to a plurality of distribution managers, the number of communication packets to be transferred can be reduced and the traffic concentration of communication packets can be avoided. The load on the manager can be distributed, and at least one distribution manager can acquire the topology information of the other communication manager by collecting the topology information of the other distribution managers.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a vertically distributed communication network.

FIG. 2 is a diagram showing a configuration of a horizontally distributed communication network.

FIG. 3 is a diagram showing a configuration of a distribution manager 10 according to an embodiment.

FIG. 4 is a diagram showing a data format of a node attribute table 12 of an embodiment and its example.

FIG. 5a is a diagram showing a data format of a topology MIB 13 and an example thereof according to the embodiment.

FIG. 5b is a diagram showing a data format of the topology MIB 13 of the embodiment and its example (continuation of FIG. 5a).

FIG. 6 is a flowchart showing a processing flow of a topology MIB generation unit 4 of the embodiment.

FIG. 7 is a flowchart showing details of a node address determination process (step 43).

FIG. 8 is a flowchart showing details of a process (step 44) for determining an address and a segment of a network to which a node belongs.

FIG. 9 is a flowchart showing a flow of generation / update processing of a topoNodeTable entry.

FIG. 10 is a flowchart showing a flow of generation / update processing of a topoNetTable entry.

FIG. 11 is a flowchart showing a flow of generation / update processing of a topoSegTable entry.

FIG. 12 is a flowchart showing a flow of generation / update processing of a topoIFTable entry.

FIG. 13 is a flowchart showing a flow of generation / update processing of a topoSeg2NodeTable entry.

FIG. 14 is a flowchart showing a flow of generation / update processing of a topoNode2IFTable entry.

FIG. 15 is a flowchart showing a flow of generation / update processing of a topoGWTable entry.

FIG. 16 is a flowchart showing a flow of generation / update processing of a topoSeg2GWTable entry.

FIG. 17 is a flowchart showing a flow of generation / update processing of a topoGW2SegTable entry.

FIG. 18 is a diagram showing a display example of an entire communication network map.

FIG. 19 is a diagram showing a display example of a network map for expanding the network net1 into segments.

FIG. 20 is a diagram showing a display example of a node map in which a node node002 is expanded to an interface.

FIG. 21a is a diagram showing another example of the topology MIB13.

FIG. 21b is another example of topology MIB13 (FIG. 21a).
FIG.

FIG. 22 is a diagram showing a display example of a segment map for expanding the segments net1: Seg1.

[Explanation of symbols]

3 ... Node information collection unit, 4 ... Topology MIB generation unit, 6 ... Topology MIB collection unit, 8 ... Topology MIB distribution unit, 9 ... Graphical user interface, 10 ... Distributed manager, 13 ... Topology MIB, 20 ... Agent, 30 ... Partial network

Claims (2)

[Claims] 1. A distributed network management method for performing communication between an agent belonging to a communication network and a distributed manager and between a distributed manager and another distributed manager based on SNMP, the distributed manager comprising: Node information is received from an agent belonging to the management range, and based on the node information, network topology information about each object to be network-managed and topology information indicating a relationship between different objects are generated and stored in a storage device. A distributed network management method, wherein at least one distributed manager further receives topology information within a management range of another distributed manager and stores it in a storage device. 2. The network topology information on each object has an address, a name, an instance having an operation state of the object, and an index for accessing each instance, and the topology information indicating the relationship between different objects is different. 2. The distributed network management method according to claim 1, further comprising an instance indicating a correspondence relationship of object addresses and an index for accessing each instance.