JPH04199933A - Network management system and its operation method - Google Patents

Abstract

PURPOSE:To economically realize a management system by defining a management object instance becoming a management object through the use of the management system of totally same constitution and the same function at the time of managing an information network by means of dividing it into plural sub-networks different in the functions. CONSTITUTION:A management information definition template 11 is set to be a management information base 10 for managing the network and the attribute of the object existing in respective units is defined by object identifier information 12 and the management object instance 13 of tree structure, which is the real management object, is stored. The management object instance tree is composed of totally same hardware and software excluding a case when it is composed only of the management object instance 13 within a self management range. At the time of managing the management object instance 13, the class is obtained and the management function corresponding to class information is executed. Thus, the economical management system can be obtained.

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field 1] The present invention relates to a network management system that has the same management functions and can centrally manage networks regardless of the scale, and a method of operating the same.

[Conventional technology]

Traditional network management systems are modeled by manager roles, agent roles, and managed objects (ISO/I EC7498-4:
I Nis O/I E C and IS○/I
ECJTC/5C21IS○/DP10040:I・
Niss O/I.E.C.T.C./
'Nis See, I Nis O/Da Be).

In other words, standard 11! of network protocols established by the International Organization for Standardization (I5O) to facilitate connections between different types of computers and different types of networks. ! A network management system is operated based on (an open system).

Generally, the manager role and agent role are information processing processes that reside in different oven systems. In other words, a process that plays an agent role is a process that performs direct management functions for managed objects (devices to be managed) within its own system, whereas a process that plays a manager role performs direct management functions for agents. It is a process that requires functions of management. Hereinafter, the information processing process that performs the functions of the manager role will be referred to as a management manager (also referred to as a manager or a network management system), and the information processing process that performs the functions of the agent role will be referred to as a management agent (also referred to as an agent).

On the other hand, a managed object is a name that abstractly represents resources in various networks that are actually managed, and there are various classes of managed objects depending on the content of the information to be managed (for example, packet switching equipment, LAN, host (terminals such as computers, workstations, etc.)

The types of managed objects viewed in terms of their management information are particularly called managed object classes. In actual management, each managed object (this is called a managed object instance, for example, PBX, LAN, workstation (W)
This is done by mutually exchanging management information corresponding to managed object classes of host computers (HOS, etc.).

The contents exchanged between the manager and the agent are broadly divided into two parts, one of which is management operation requests for each managed object instance.
request information sent from the manager to the agent;
Conversely, it is an event report (notification) sent from the agent to the manager to report events that occur in each managed object instance.

The specific contents of management operation requests and event reports are defined in detail as attributes corresponding to each management object class.

In SI (open systems), management operations, event reporting formats, types of management information set therein, their values, and methods of defining these management information are being considered.

[Problems to be Solved by the Invention] As mentioned above, in the conventional method, a protocol for exchanging management information between the manager role and the agent role and a method for defining management information have been studied; Little consideration has been given to specific operational methods, ie, how to manage networks with various actual sizes and configurations, or how to operate managers and agents.

The first object of the present invention is to solve these conventional problems and provide an economical network management system that can be managed using the same management system even when managing multiple networks separately. It's about doing.

A second object of the present invention is to provide a method of operating a network management system that can cope with the development and expansion of new subnetworks and new devices.

A third object of the present invention is to create a network management system in which, when one network is managed by multiple management systems, information defined in one management system is automatically defined in all other management systems. The purpose is to provide operational methods.

[Means to solve the problem]

In order to achieve the above object, the network management system according to the present invention (a) uses a management information definition template and object identifier information that defines attributes of objects existing in each device as a management information base for managing the network. , stores the tree-structured managed object instances that are actually managed, and multiple management systems do not have exactly the same managed object instance tree structure, except when the managed object instance tree is composed only of managed object instances within the self-management scope. When each management system manages a managed object instance, it is characterized by determining the class of the managed object instance and executing a management function corresponding to the class information. Also,
(b) When the number of managed object instances to be managed in the network is small, the network is managed by one management system, and when the number of managed object instances increases, the increased number of managed object instances is managed. Add a management system with exactly the same configuration to , and create a management system that manages all managed object instances that are connected to the management system and managed by the management system, using the already existing management system and the added management system as managed objects. There is also a feature in providing . Furthermore, in the method of operating a network management system according to the present invention, (c) if there is a management system below the self-management system that manages managed object instances in a tree configuration,
The self-management system operates as a higher-level management manager for lower-level management systems, and if a higher-level management system than the self-management system is connected and the higher-level management system operates as a management manager, the self-management system It is characterized by automatically performing management functions as a management agent.

(d) The self-management system determines whether a lower-order management system exists based on the managed object instance information provided by the self-management system, and when receiving a management association from another management system, The existence of a lower management system is detected when an event report of a managed object instance is received from a management system, and the existence of an upper management system is detected when an operation request for a managed object instance is received from a higher management system. There are also characteristics. In addition, (e) if the management system has a hierarchical structure, the management functions of referring to and adding information corresponding to object identifiers are performed with the same function in each management system, and in the management system at a certain hierarchical level, the management system is When management information is added, a request is made to the lower management system to add information corresponding to the managed object identifier, and the lower management system that receives the addition request adds the information corresponding to the object identifier to its own management information base. In addition, a report to the effect that the addition has been made is sent to the upper management system, and upon receiving the report, the upper management system adds information corresponding to the object identifier to its own management information. Therefore, even if management information corresponding to an object identifier is added or changed in any management system, the same management information is added or changed in all other management systems. Furthermore, (to) the self-management system operates as a higher-level management manager for the management system when there is a lower-level management system that manages each management object instance in the tree configuration, and when a new management system is connected. Another feature is that when a management system operates as a management agent, the management function as a management manager is automatically executed for the management system as well.

[Function] In the present invention, when the network management system executes management, it depends only on the managed object instance (managed device) and its object class information (identifier of the managed device), and even when operating as a manager, , and even when acting as an agent, no different processing is performed on this information. That is,
Whether a system operates as a manager or an agent is determined depending on whether there is a management system above the management system that operates as a manager.

For a managed object instance (managed device) managed by a management system, if a management agent exists, the management system operates as a management manager. However, if another management system connected to this management system acts as a management manager,
The management system operates as a management twenty-one client.

Therefore, the management system according to the invention operates both as a management client and as a management manager, and as a management system that simultaneously executes a management client and a management manager. The management system itself automatically determines in which of these modes it will function, depending on the environment and conditions.

〔Example〕

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a basic configuration diagram of a network management system showing an embodiment of the present invention.

In FIG. 1, l is a management system and 10 is a management information base. The management information base 10 includes a management information definition template 11 that defines various management information using templates, object identifier information 12 that is defined corresponding to an object identifier as a glass or attribute of a managed device, and information that is actually notified. The information 13 includes information 13 about managed object instances, which are objects to be managed and instructions are given.

The network management system l uses these management information 11
, 12.13 to perform its respective functions.

Each execution program of the information processing device includes an advanced management function 70, a specific management function 50, an environment control function 40, a local object management function 60, a common management information service execution module 20, and the like. A module 20 running a common management information service (CMIS) is connected to upper management managers and lower management agents and communicates with each other by sending reports and instructions. The operator interface 30 is a module that executes an interface with an operator, and includes a display 100.
In addition to displaying guidance and processing results, the input information is transmitted to each module. The environment control function 40 is a module that controls the operation of the management system according to the environment, and determines whether there is a management manager at the upper level or a management agent at the lower level.

The specific management function 50 is a module that controls a specific management function for instructing contents and content. The local object management function 60 is a module for directly controlling managed object instances (managed devices) within the self-management system. The advanced management function 70 is
This is a group of modules that execute functions to improve performance, issue alarms in the event of a failure, and detect where the failure is. The management information control module 80 stores the object identifier information 12
It is composed of a module 81 that manages and controls the managed object instance, and a module 82 that controls the managed object instance.

Whether this management system 1 operates as a management manager or a management agent is determined by the module 20 that executes the common management information service receiving a request from the upper management system, or by the definition information of the environment control function 40. If an upper management system is defined, it is determined that the management system operates as a management agent, and the module 20 that executes the common management information service provided at the lower level receives reports from the lower management system. The management system is automatically determined to operate as a management manager when the management information base 10 receives an instance of the management object or an instance other than the one managed by the own management system is stored in the management object instance in the management information base 10. These decisions are made by the environmental control function 4o.

FIG. 2 is a diagram showing an operational example of network management by the management system of the present invention.

In this example, one management system l manages the multiplexer ~ jUX, switch PBX, packet switch PS, local area network LAN, host computer HO3T,
Network 100 consisting of workstations WS, etc.
0 is managed.

Here, the management information base 10 of the management system 1 stores all managed object instances (managed devices) of the managed network 1000 and information corresponding to object identifiers such as object classes (attributes, identifiers) and attributes. ing.

Here, since one management system 1 manages the network, this management system 1 functions as a management agent.

FIG. 3 is a diagram showing an application example of the operating method of the present invention, and shows an example in which one network is managed by one or two devices.

In FIG. 3(a), the entire network 1000 is managed by one management system l, and in FIG. 3(b), the network 1000 is managed by two subnetworks 10.
00-2.1000-3, each with a management system 1-2.1-3, and the network management system 1-1 connected to each of these management systems 1-2.1-3. It manages the whole thing.

In this case, in FIG. 3(a), the management system 1 functions as a management agent, and in FIG. 3(b), the management system 1-1 functions as a management manager, 1-2 . l-3 performs the functions of a management agent.

Each management system has different managed object instance information. That is, management system 1
-2 and 1-3 have instance information only for managed objects within their own management range, and management system 1-1 has managed object instance information for the entire network. Here, as the managed object instance of the management system 1-1, especially the management systems 1-2 and 1-3
There are some things that exist at the boundary of the management scope of

FIG. 4 is a diagram showing the relationship between the management systems in FIG. 3.

As shown in FIG. 4, each connection between the management systems 1-1 and 1-2 and the management systems 1-1 and 1-3 is made through the C to 1ISE (common management information service execution module 20) of each management system. will be carried out.

In the management system based on the present invention, there is no limit to the number of connections, that is, the number of layers. Therefore, even if management systems are connected in n layers, all networks can be managed in exactly the same way by a management system with the same configuration.

When a management system employs a hierarchical configuration, a management system at a certain level in the hierarchical configuration only recognizes whether a management system exists above or below it. If you want to recognize the existence of a higher-level management system, use CMISE20.
This is performed either by receiving a management association setting request from the higher-level management system, or by having the higher-level management system defined in the definition information of the environment control function 40 within the self-management system.

In addition, when recognizing the existence of a lower-level management system, check whether there is a management system that manages managed object instances that are not directly managed in the managed object instance information 13 in the self-management information base 1o. It is m1ft depending on the situation. That is, in the managed object instance information 13 of the upper management system,
In addition to object instances (managed devices) managed by lower-level management systems, object instances (managed devices) managed by the self-management system are stored, so there are instances other than those managed by the self-management system. All you have to do is decide whether or not.

FIG. 5 is a diagram showing managed object instances managed by the management system in FIG. 4 in correspondence with an instance tree.

Each management system 1-1 in Figure 4. FIG. 5 shows the managed object instances managed by l-2 and l-3 in correspondence with the managed object instance tree of the network 1000. The managed object instance managed by the management system 1-2 corresponds to the network 100o-1 part of the instance tree of the network 100o, and
The managed object instance managed by 3 is network 1 in the instance tree of network 1000.
This corresponds to the part 000-2.

Also, if management system 1 is subordinate to management system 1-2,
-4 exists, the managed object instance managed by that management system 1-4 is assigned to network 1000 in the instance tree of network 1000.
-It corresponds to part 3. In this manner, the management information page of the upper management system stores managed object instances managed by the lower management system and managed object instances managed by the own management system.

In FIG. 5, management system 1-1 operates as a management manager, while management system 1-2.1-3 operates as a management agent. Note that if the management system 1-4 exists in a lower level, the management system 1-2 also operates as a management manager.

FIG. 6 is a diagram showing an example of operation of the management system according to the present invention depending on the scale of the managed network. In FIG. 6(a), since the scale of the network is small, one management system l-1 of the present invention This example shows an example where the entire system is managed by . Further, FIG. 6(b) shows a case where a management system has been added because the scale of the network has increased due to expansion etc. In this case, three management systems are used for management.

The transition from FIG. 6(a) to FIG. 6(b) is performed in response to an increase in the number of devices to be managed. That is, in the state shown in FIG. 6(a), the management system 1-1 only manages the network 1000-10, and the number of devices to be managed is also small, so one network is sufficient for management. If the number of components of the network 1000-20 to be managed increases from the state shown in FIG. If the number exceeds 20, the management system 1-1 will no longer be able to handle it, and the management system 1-3 will be added to manage the increasing number of network devices, and the management system 1-2 will be added to manage the entire network. Double pipe ring system l-1,1-
3 to manage the entire network.

In this case, the network size to be managed is 1000-20
If there are few components that exceed the number of components and there is room for management system 1-3, management system l-3 will replace management system 1.
-2 may be substituted. However, in this case, the management system 1-3 is connected to the managed network 1000-20.
The management information held regarding the managed object instance of the management system 1-1 does not need to be the same as the management information held by the management system 1-1, and may be part of it. For example, only borderline instances and frequently used instances within network 1000-20 are sufficient.

Note that when the management system 1-2 exists, the management information of the management system 1-2 does not need to be the same as the management information of the management systems 1-1 and 1-3.

FIG. 7 is a processing flowchart when starting up the management system of the present invention, in which FIG. 7(a) shows the case where the system is started up by itself, and FIG. 7(b) shows a setting request from another management system. This is the case when the device is activated by receiving the .

In FIG. 7(a), first the advanced management function 70 is activated (step 301), and then the specific management function 50 is activated (step 302). Note that the startup order may be any order. Next, under the control of the management information control module 80 under the instruction of the specific management function 50, the lower management system is determined by referring to the content of the managed object instance information 13 of the self-management information base 10 (step 303). A management association is set for the management system that requires association setting (steps 304, 305). Here, setting up a management association means setting up a communication path connection with another management system connected to the C to 1IsE 20 in order to combine the management systems. Furthermore, if there is a local managed object (resource in the managed network) that is directly managed by the self-managed system (step 307), the local managed object management function 60 is activated (step 308) and the state is changed to the managed state. , executes management (step 309).

In FIG. 7(b), when the CMISE 20 receives a management association setting request from another management system (step 320), the management information control module 80 controls the CMISE 20 to set the self-management information base lO in response to an instruction from the environment control function 40. By referring to it, it is determined whether the request is from a lower management system (step 321). If the request is from a lower management system, establish an association with that management system (step 3).
23), if it is a request to set up a management association from an upper management system (step 321), a management association is set up with that management system, and a flag indicating the existence of an upper management system (upper management The system existence display flag) is turned on (step 322). Note that the higher-level management system existence display flag is used when determining the necessity of processing for a higher-level system when executing a management function. Furthermore, when a newly connected management system operates as a lower-level agent, it is necessary to expand the managed object instance of the higher-level management system. This expanded operation is automatically performed by sending a report from the lower management system to the higher management system.

FIG. 8 is a processing flowchart when the management system of the present invention receives an event report from a lower management system.

When the CMISE 20 receives an event report from a lower-level management system (step 401), it first determines whether or not a higher-level management system exists by turning on/off the upper-level management system existence display flag (step 402).
. This upper management system existence display flag is set when a management association is received from the upper management system.
○ due to the process in FIG. 7(b) (step 322)
It has been N. If a higher management system exists (
Step 402) Next, determine whether it is necessary to report to the upper management system (Step 403), and if necessary, report the received event to the upper management system (step 405). Next, it is determined whether the content of the event report needs to be reflected in the corresponding managed object instance information in the self-management information base 10, that is, whether it is necessary to update the self-management base 10 (step 406).
). If necessary, the class of the managed object instance is determined and the corresponding processing is performed on the corresponding class (step 407). That is, when the attributes of the instance are changed, the class also needs to be changed.

Next, it is determined whether this event needs to be displayed to the operator (step 408), and if necessary, this received event is displayed on the operator interface 3.
0 and display it on the display (step 409
).

FIG. 9 is a processing flowchart when the management system of the present invention receives an operation request from a higher-level management system.

When the CMISE 20 receives an operation request from the upper management system (step 421), first, the specific management function 50 queries the information management control module 80 to determine the necessity of the operation to the self-management information base 10 (step 422). Here, operation is managed object instance information 1
This is an operation to change the contents of item 3. If it is determined that the self-management information needs to be changed, the class of the managed object instance is determined, and the operation corresponding to the class is executed (step 423). Next, the specific target function 50 determines whether or not the target managed object is directly managed (step 424), and determines whether or not the target managed object is directly managed by the own management system and an operation on the managed object is required. For example, the local object management function 60 performs the operation (steps 432-433). If the managed object instance that is the target of the operation is an object managed by a lower-level management system and an operation on the lower-level management system is required (step 425), the operation is sent to the lower-level management system and the response is received. (step 426). In other words, the CM I S E 2 issues operation requests that instruct operations such as changing attributes such as type, changing managed object instances, etc.
0 to the lower management system. When a response to the operation is received from the lower management system (step 427), it is determined whether there is a need to transmit the operation response to the upper management system (step 428). In other words, each managed object instance managed by a hierarchical management system stores the lower managed object instances plus the managed object instances directly managed by the own management system, with some exceptions. When a managed object instance of
This is because it is necessary to update the contents of . If it is determined that transmission to the upper management system is necessary, the operation result is transmitted to the upper management system (step 429). Furthermore, it is determined whether it is necessary or unnecessary to reflect the operation result in the self-management information (step 430),
If necessary, the corresponding attribute value of the corresponding managed object instance in the self-management information is updated (step 431).

FIG. 1O is a processing flowchart in response to an operation request from an operator in the present invention.

Requests from the operator are sent to the operator interface 30
When a request is received via the operator (step 501), it is determined whether the operation request from the operator is a request corresponding to an object identifier or a request for a managed object instance (step 502). If the operation target is a request for a managed object instance, the same processing as shown in FIG. 9 when an operation request is received from the upper management system is executed (step 510).

In addition, in the case of an operation request for an object identifier, the contents of the operation (request type)
is determined (step 503). If the operation request is to add information corresponding to a new object identifier, a definition template (template) corresponding to the additional information is obtained from the management information definition template 11 (step 50
4). The definition template is then displayed on the display 100 via the operator interface 30 (step 505). The operator uses the displayed definition template to define information corresponding to the object identifier (step 506), and after completing the definition, stores the information corresponding to the object identifier in the object identifier information 12 (step 507).

In the case of an operation request for an object identifier and a reference request for object identifier information that has already been defined, the object identifier information 1 of the reference request
2 from the managed object base 10 and displayed on the display 100 via the operator interface 30 (step 508).

The processing procedures of the management system for management operations and event reporting for normal managed object instances have been described above.

Note that in the present invention, not only such basic management operations but also the advanced management function 70 are common to each management system, that is, perform the same functions.

Next, as an example of the advanced management function 70, a method for managing object identifier correspondence information will be described.

FIG. 11 is an explanatory diagram of the two management systems, upper and lower, in the present invention.

The difference between these two management systems is that the management information base 1
As mentioned above, there is only managed object instance information 13 in o.

The upper management system 1-1 uses managed object instance information 13-1 possessed by a plurality of lower management systems.
have. Each of the management systems l-1 and 1-2 includes a class information management function 700 as the advanced management function 70. Each of these class information management functions 700-
1,700-2 are defined as management object instances of each management system. That is, the class information management function 700-1 of the management system l-1
is defined in the managed object instance information 13-1 of the management system 1-1. That is, in the upper managed object instance information 13-1, instance 1. l is the class information management function 700-1, and instance 1゜2.1 is the class information management function 700-1.
2 are shown respectively.

On the other hand, the class information □ information management function 700-2 of the management system l-2 is defined in the managed object instance information 13-2 of the management system l-2. In addition, managed object instance information 1 of the management system 1-1
1.1 in 3-1 indicates the class information management function 700-1, 1 indicates the entire management system 1-1, and 1 and 2 indicate the entire lower management system 1-2. There is.

FIG. 12 is a processing flowchart of the class information management function in FIG. 11.

The class information management function 700 performs processing when an object identifier is updated in the self-management system, processing when an update request is received from a higher-level management system, and processing when there is an update report from a lower-level management system. There is.

First, if there is an update in the self-management system, the 12th
As shown in Figure (C), the class information management function 700 changes object identifier information (step 601).

That is, object identifier information 1 in FIG.
．． Change l. Next, in order to make this change to the lower management system, an object instance corresponding to the glass information management function of each lower management system is searched from the managed object instance information of the own management system (step 602). That is, in FIG. 11, from the managed object instance information 13-1 to the object instance corresponding to the class information management function of the lower management system! , 2.1.

A change request is sent to the managed object instance 1.2.1 (step 603). This change request uses, for example, M-ACTTON (change instruction only), which is a common management protocol in Sl (open system) management. Next, it is determined whether an upper management system exists (Step 604), and if it exists,
The object instance corresponding to the class information management function 700 in the own management system is used to report to the upper management system (step 605).

Next, processing when an update request is received from a higher level will be explained.

As shown in FIG. 12(b), when a glass information change request is received from the upper management system by specifying an instance of the class information management function (step 611), the class information management function (700-2 in FIG. 11) is The change request message is passed to the client (step 612). The class information management function (700-2) uses the self-management information base 10-
The class information of No. 2 is changed (step 613).

Next, when a change report of the management information corresponding to the object identifier is received from the lower management system, as shown in Fig. 12 (
As shown in a), the received message is passed to the class information management function (700-1 in FIG. 11) (step 6
22). The class information management function (700-1) changes the class information (12-1) of the self-management information base (10-1) based on the received message (step 623).
.

Note that processing step 621 in FIG. 12(a) (that is, receiving a change report from a lower-level management system) corresponds to processing step 6o5 in FIG. 12(C) (that is, notifying a change to a higher-level management system). It is processing.

In this way, in the present invention, (a) if the network is small, management is performed by one management system A;
When the network becomes large, you can divide the network into multiple subnetworks, manage each subnetwork with a management system that has exactly the same management functions, and then connect each of these management systems to manage the entire network. The management system C to be managed can also be managed by a management system having exactly the same management functions as each of the management systems A and B. Therefore, economical and highly reliable management is possible.

(b) Furthermore, object-oriented management functions are applied to the management system, and the functions of a management manager and an agent are realized as one system. Whether a certain management system functions as a manager or an agent is automatically determined based on its relationship with other management systems and the managed objects it manages. That is, the management system has managed object instances and managed object class information to be managed by the own management system, so that the management function does not depend on the scope of the instance tree of the managed object. In this case, it is determined whether a change report is received from a lower-level management system or whether there is a lower-level management system based on managed object instance information, and whether or not the own management system operates as a management manager is determined. Furthermore, depending on whether a management association is established or an operation request is received from a higher-level management system, it is determined whether or not the self-management system operates as a management agent.

Furthermore, if there is no lower-level management system, it is determined whether or not there is a local object, and if there is, the local object management function is activated.

[Effects of the Invention] As explained above, according to the present invention, (a) even when managing an information network by dividing it into a plurality of subnetworks with different functions, a management system with a different configuration for each subnetwork can be developed; There is no need to do this, and the network can be managed by defining managed object instances to be managed using management systems with exactly the same configuration and the same functions, so the management system can be realized economically.

(b) In addition, by defining management information corresponding to object identifiers and defining managed object instances to be managed, it is possible to execute management functions, so new subnetworks and new devices can be developed. Even when the management object instance information is updated, this can be handled by updating the management object instance information.

(C) Also, if one network is managed by multiple management systems, just by defining new managed object identifier correspondence information in one management system,
Since notification is reported to the upper management system and the lower management system, the new managed object can be automatically defined in other management systems as well.

[Brief explanation of the drawing]

Figure 1 is a configuration diagram of a network management system showing an embodiment of the present invention, Figure 2 is a conceptual diagram of the management system of the present invention applied to network management, and Figure 3 is a diagram of the management system of the present invention. An explanatory diagram showing an example of using one system and three systems, Figure 4 is a detailed diagram of the connection relationship between the management systems in Figure 3, and Figure 5 shows the management objects of each management system in Figure 4. A relationship diagram of instances defined in the instance information, FIG. 6 is a diagram showing an example of an operation method as the network scale increases by the management system of the present invention, and FIG. 7 is a processing flowchart at startup of the management system of the present invention. , FIG. 8 is a processing flowchart when the management system of the present invention receives an event report from a lower-level management system, and FIG. 9 is a processing flowchart when the management system of the present invention receives a management operation from a higher-level management system. , FIG. 10 is a processing flowchart when the management system of the present invention receives a request from an operator, and FIG. 11 is an example of the advanced management function of the present invention, showing the class information management function and the positioning of instances in its managed object instance information. Diagram showing the relationship between
FIG. 2 is a processing flowchart of the class information management function shown in FIG. 11. ■ Management system, 10 Management information pace, 11. Management information definition template, 12. Object identifier information, 13. Managed object instance information, 20.
Common information service control function (C, MISE), 30 operator interface, 40 environment control function, 50:
Specific management functions, 60 local object management functions, 7
0. Advanced management function, 80 management information control module,
81: Object identifier information control, 82. Managed object instance information control, +00: Display,
700 Class information management function! 000: Network. Representative Patent Attorney Masatoshi Isomura, I□v-1 t+,・～-j″- Figure 3 Figure 6 (Part 1) Figure 6 (Part 2) Figure 7 (Part 1) (a) Figure 7 (Part 2) (b) Figure 8 Figure 11 Figure 7' (Correspondence) Figure 12 (Part 1) (a) <Receiving update report from lower level> Figure 12 (Part 2) (b) Update from higher level Request reception> Figure 12 (Part 3) cl <When there is an update in self-management/system> In the old inquiry system

Claims (1)

[Claims] 1. For a network configured by interconnecting a plurality of communication devices and information processing devices, a management agent existing in each device and a management manager interconnected to the management agent. In a network management system that centrally manages a network by exchanging management information regarding managed objects existing in each device, a management information definition template and each of the above devices are used as a management information base for managing the network. Object identifier information that defines the attributes of objects existing in Unless it is composed only of object instances, when each management system manages the above managed object instances with the same hardware and software, the class of the managed object instance is determined and corresponds to the class information. A network management system characterized in that it performs management functions. 2. In the network management system according to claim 1, when the number of managed object instances to be managed in the network is small, one management system manages the network and the number of managed object instances increases. In some cases, a management system with exactly the same configuration is added to manage the increased number of managed object instances, and the existing management system and the added management system are connected to the management system as management agents. A network management system comprising: a management system that manages all managed object instances managed by the management system. 3. In a network configured by interconnecting multiple communication devices and information processing devices, the management agent existing in each device and the management manager interconnected to the management agent exist in each device. In the operation method of a network management system that performs centralized management by exchanging information on managed objects that are managed, if there is a management system below the self-management system that manages managed object instances in a tree configuration, the self-management system If the self-management system operates as a higher-level management manager for the lower-level management system, and a higher-level management system is connected to the self-management system, and the higher-level management system operates as the management manager, the self-management system automatically A method for operating a network management system, characterized in that the system also performs management functions as a management agent. 4. In the method of operating a network management system according to claim 3, when the management system has a hierarchical structure, the management function of referring to and adding information corresponding to an object identifier is performed by the same function in each management system. In a management system at a certain hierarchical level, when management information is added through a man-machine interface, a request is made to a lower management system to add information corresponding to a managed object identifier, and the lower management system that receives the addition request The system adds information corresponding to the object identifier to the self-management information base, and also sends a report to the higher-level management system that the addition has been made, and when the higher-level management system receives the report, By adding information corresponding to object identifiers to self-management information, even if management information corresponding to object identifiers is added or changed in any management system, the same management information will be added or changed in all other management systems. A method of operating a management system characterized by: 5. In the method of operating a network management system according to claim 1, when there is a lower-level management system that manages each managed object instance in a tree configuration, the self-management system provides a higher-level management system to the management system. It operates as a manager, and when a new management system is connected and the management system operates as a management agent, it automatically executes the management function as a management manager for the management system as well. How to operate a network management system.