JP3018468B2 - Network management system - Google Patents

Description

Description: BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management system suitable for managing an information network configured by interconnecting a plurality of communication devices and information processing devices, and in particular, A database of management information to be shared by the integrated network management device and the sub-network management device of the information network,
The present invention relates to a flexible network management system realized by a management information control unit including an interface function provided by accessing this database.

[Conventional technology]

In recent years, in an information network configured by connecting a plurality of communication devices and information processing devices to each other, a sub-network management device that manages the devices, and an integrated network management device that is connected to the sub-network management device A network management system for centrally managing a network by exchanging management information on a management object existing in each device has been constructed.

These network management systems comply with ISO / IEC 7498
-4, Modeled by manager role, agent role, and managed objects, as shown in ISO / IEC JTC / SC 21 ISO / DP 10040, etc. Generally, the manager role and the agent role are information processing processes that exist in different open systems, respectively, and the process that becomes the agent role is a process that directly performs a management function on a management object in the own system. On the other hand, the process serving as the manager role is a process for requesting the agent to perform a management function.

Also, as shown in ISO / IEC / DP 10165-1, 10165-4, the management object is an abstract representation of various network resources that are actually managed by object-oriented design. There are various classes of management objects depending on the contents of the information to be performed.
If you look at a managed object in terms of its management information,
In particular, it is called a management object class. The relationship between the management object classes is represented by a tree structure (inheritance tree) reflecting the inheritance of the management information.

On the other hand, the actual individual managed objects are called managed object instances, and the relationship between the managed object instances is expressed by a tree structure (containment tree) that reflects the actual inclusion relationship of the managed objects. The integrated network management device and the sub-network management device of the information network have management information corresponding to the management object class of each managed object instance in a management information database, and the network management is performed by the integrated network management device of the information network and the sub-network management. This is realized by exchanging the management information between the devices.

The above exchanged contents are roughly divided into two.
That is, as a management operation request for each managed object instance, the management object request transmitted from the integrated network management device to the sub network management device and the management object request transmitted from the sub network management device to the integrated network management device on the contrary are Event reporting for reporting an event that occurs (this is called "notification"). Details of the specific contents of these management operation requests and event reports are defined as attributes corresponding to the classes of the management objects.

In OSI, the format of these management operations and event reports, the type and value of management information set therein, and the definition method using a template as a method of defining these management information, etc. Is being considered.

[Problems to be solved by the invention]

However, although the above-mentioned prior art discusses the types and contents of the management information of the management objects constituting the network and the method of defining the management information, the database configuration and the provision of the management information are provided on an actual network management system. No specific method of realizing the interface function has been studied.

The present invention has been made in view of the above circumstances, and an object of the present invention is to use a flexible management information database configuration and this database in an integrated network management device and a sub-network management device of a network management system. An object of the present invention is to provide a network management system having a management information control function including an effective and efficient interface function.

[Means for solving the problem]

An object of the present invention is to provide a sub-network management device for managing each device of an information network configured by interconnecting a plurality of communication devices and information processing devices, and the sub-network management device being interconnected with the sub-network management device. In a network management system that centrally manages a network by exchanging management information on a management object existing in each device with an integrated network management device, a database storing the management information and the database are used. A management information control unit having an interface function group provided by the same specification in the integrated network management device and the sub-network management device in common, and collectively manages management information by the management information control unit; The database is used to store class information, Characterized in that it comprises a table group defining and storing object information and operation information, and a table group defining and storing managed object instance information and attribute value information which are individual information for each actual managed object instance. Achieved by a management system.

[Action]

In the network management system according to the present invention,
A management information control unit having a database for storing the management information and an interface function group provided by using the database is shared by the same specifications in the integrated network management device and the sub-network management device of the network management system. By providing the management information collectively by the management information control unit, it is possible to prevent the influence of the update of the management information on other modules in the integrated network management device and the sub network management device. By making the management information control unit a common specification between the integrated network management device and the sub-network management device, the module can be provided as a highly versatile module. Other features will be described in detail in the description of the embodiments.

〔Example〕

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

First, the configuration of the first embodiment of the present invention will be described with reference to FIGS.
This will be described with reference to the drawings.

FIG. 1 shows a network management system according to the present embodiment. FIG. 3 is a configuration diagram of a network management device common to the sub-network management devices of the integrated network management device and the information processing network management device. A network management device 101 shown in FIG. 1 includes a management information communication protocol control unit 102 for exchanging management information with the sub-network management device or the integrated network management device, and a management function execution control for executing various management functions described below. Interface 103, a CRT display 104, a keyboard 105, a man-machine interface control unit 107 for realizing input as an interface with an operator via a mouse 106, and management information control for realizing management and control of management information on network management objects. It comprises a part 108.

FIG. 2 is a diagram illustrating a configuration example of the entire network management system. As shown in the figure, a transmission network management device 202 for managing a transmission network composed of a multiplexing device 201 and the like, a switching network management device 204 for managing a switching network such as a PBX 203, and a computer 205, a workstation 206 and the like are managed. Each sub-network management device (hereinafter, also referred to as “management agent”) of the information processing network management device 207 is connected to an integrated network management device (hereinafter, also referred to as “management manager”),
The integrated network management device 208 realizes management of the entire information network by exchanging management information with these sub-network management devices 202, 204, and 207.

FIG. 3 is a diagram showing a configuration of a management information control unit in the integrated network management device and the sub-network management device. The management information control unit 108 includes a management information database 301 for storing management information on management objects, and a group of interface functions provided by accessing the database. This interface function group includes a display name conversion processing function 302 having an interface with the man-machine interface control unit 107, an object registration / deletion function 303 having an interface with the management function execution control unit 103, an event information addition function 304, an object inquiry There are a function 305, an object update function 306, an object creation version number management function 307 having an interface with the management information communication protocol control unit 102, an operation check function 308, and a PDU format check / conversion function 309. These are each realized as one functional module.

FIG. 4 is a diagram showing a configuration of a management information related table in the management information database. First, the table access control table 401 stores addresses of various table groups, and is used when specifying a table to be accessed. The table group to be accessed includes an agent information table 402, an instance information table 403, and an attribute value information table 404, which are unique information for each sub-network management device, and a class information table, which is one common information in the network to be managed. 405, an attribute information table 406, an object identifier conversion table 407, a display name conversion table 408, and a protocol format reference table 409.

In the agent information table 402 described above, the management agent name 410, the address 411 to the top instance table managed by the management agent, the instance expression identifier 412 that specifies the instance expression used by the management agent for communication, and the object identifier are specified. Information such as a profile identifier 413 and an object creation version number 414 is stored.

In the instance information table 403, one table is configured for each management instance, and a relative HOS 415, a relative identifier 416, and a relative identifier 416, which are part of two types of instance expressions of an identifier and a hierarchical octet string (HOS), Upper and lower instance address pointers 419 and 420 indicating the upper and lower instance table addresses of the inclusive relationship between instances, forward address pointer 421 for sequentially specifying the next instance address when all base instances are to be searched by base instance specification, instance has Information such as a table address pointer 422 pointing to the attribute value information table and an object identifier 423 of the instance is stored. Note that a concatenation of the relative HOS and the relative identifier from the top instance is an instance expression using the HOS and the identifier.

The attribute value information table 404 stores an attribute value 425 corresponding to each attribute identifier 424. The class information table 405 and the attribute information table 406 store information reflecting the contents of the OSI class and attribute template definitions. The class information table 405 stores attribute list information 426 and operation list information 427 of the class. However, the attribute information table 406 stores information such as an allowable value and a data type of each attribute. In order to express the inheritance relationship between the classes between the class information tables, as in the case of the instance information table, the upper and lower levels are used. They are connected by lower pointers 428 and 429.

Next, the display name conversion table 408 stores the correspondence information between the display name 430, the agent name 431, and the instance expression HOS432 assigned to the management object used by the operator, and the object identifier conversion table 407 stores Object identifier 433 with different representation
(For example, iso (1) -memberbody (2) -Japan (392)
-Company (90)-Company A (1000000)-Network management (0
0) -Object class (0) -Network (0)
Identifier with a long data length) and internal unified code
434 (for example, a short integer type identifier such as a network class (1) of company A specification) is stored for each class identifier, attribute identifier, action identifier, and event type identifier.

Finally, the protocol format reference table 409 stores the communication protocol format used for exchanging management information for each information protocol service type. Here, the communication protocol format is
The ASN.1 transfer syntax, which is a protocol data unit (PDU) representation, expresses one parameter of each protocol service by a TLC structure consisting of a data type T, a data length L, and a data value C. , L. This format information indicates the data type (integer type, string type) of each parameter, T of the parameter structured type (SEQUENCE, SET), and essential / optional identification information of each parameter.

Next, an example of the operation of the network management system according to the present invention will be described with reference to FIGS. In addition,
FIG. 5 is an explanatory diagram showing a method of setting an instance address pointer on an instance tree, FIG. 6 is a flowchart of a start-up operation of the integrated network management device (management manager), and FIG. FIG. 8 is a flowchart of a status inquiry request receiving operation of the PBX network management device, and FIG. 9 is a flowchart of a status inquiry result receiving operation of the management manager.

First, the operation of the network management system when starting up will be described with reference to FIG. Administration Manager 208
Is used by each management agent 202, 204, 207
(Association Control Service) protocol,
An association setting request is made (step 601). At this time, the object creation version number 414 for each managed management agent is stored in the agent information table 402 of the management information control unit 108 of the management manager 208.
Is requested to the object creation version number management function 307 (step 602), and the management agents 202 and 2
Compare with the version number 414 notified from 04,207 (step 603). As a result of the comparison, if the two match, the association is established (step 604), and if not, the connection is disconnected (step 605). The version number 414 is a creation version number of the instance information table 403, which is an integer type or a time type data. If any part of the table content is updated, the version number is also updated. Thereby, the management manager 20
8 and the management information of the management agents 202, 204, and 207 are guaranteed, and security is ensured.

Next, as an example of an operation operation from the management manager 208 to the management agents 202, 204, and 207 at the time of operation, a case will be described in which a PBX status management performed by the PBX network management device 204 is performed. The operator of the management manager 208 inputs the display name (for example, Tokyo.
A status inquiry command is issued to PBX.No.1) (step 701). The man-machine interface control unit 107 issues a display name conversion request to the management information control unit 108 (step 702), and acquires a class instance (internal unified code) expression corresponding to the display name (step 70).
3). At this time, the management information control unit 108 has a display name conversion function.
The display name conversion table 408 is searched by 302 to obtain the corresponding agent name 431 and the instance expression HOS432 (for example, 1.1), and further, the object class identifier 423 of the corresponding instance is obtained from the instance information table 403 of the corresponding agent name. .

The internal unified code of the instance representation is HOS,
The specification of the corresponding instance table is realized as follows. As shown in FIG. 5, based on the HOS expression (1.1) of PBX.No. 1 described above, the top instance address 411 on the agent information table 402 is pointed to the top instance (1) on the instance information table 403,
The lower instance address 418 of the top instance table points to the HOS (1.2) instance table. This HOS (1.2) is the HOS I want
Since it is larger in lexical enumeration order than (1.1), it jumps to the instance table indicated by the left pointer 419 and returns to the HOS (1.
Get the instance table of 1).

As described above, the lower pointer 418 is set in advance so that the HOS value of the lower-level instance of the instance tree structure points to the instance having the intermediate value of the lexical enumeration order. The pointers 419 and 420 are set so that the HOS value indicates the instance having the lower intermediate value and the higher intermediate value of the lexical enumeration order with respect to the instance at the same level in the instance tree structure. Is searched and specified at high speed by a binary tree (binary tree) search.

The man-machine interface control unit 107 transmits a class identifier, instance information HOS, and a state attribute identifier to be queried (for example, Operational State ID = 21, Adm).
inistrative State ID = 1) Information is stored in steps 704 and 705
Then, the information is passed to the management information communication protocol control unit 102 via the management function execution control unit 103. The management information communication protocol control unit 102 requests the management information control unit 108 to check the operation of the corresponding attribute identifier with respect to the class identifier of the corresponding PBX.No.1 (step 706). The operation check function 308 of the management information control unit 108 searches the class information table 405 of the management information database 301 based on the class identifier, and sends a status inquiry (M_G) to the operation list information field 427 on the corresponding class table.
et operation) is permitted (whether or not described in the table), and the corresponding attribute identifier (Operational State ID = 21, Administrative State ID) is stored in the attribute list information field 426.
= 1) is checked, and the result is returned to the management information communication protocol control unit 102 (step 707).

If the result of the above check is NG, the management information communication protocol control unit 102, via the management function execution control unit 103,
Notify NG to man-machine interface 107 (step 8
01, 802), the fact that the operation is not possible is displayed on the CRT 104 (step 803). Also, if the check result is O
If it is K, the management information communication protocol control unit 102 requests the management information control unit 108 to create a protocol data unit of the protocol service (M_Get_req, service type ID = 1) in step 804. On the basis of this, the management information control unit PDU conversion function 309 recognizes the M_Get_req service from the service type ID = 1 and recognizes the M_Get_req service.
The PDU of the M_Get_req service is assembled according to the protocol format reference table 409 on 01, and the result is returned to the management information communication protocol control unit 102 (step 805).

Here, the PDU is assembled by associating the structured type, the data type T, and the data length L of each service stored in the protocol format reference table 409 with ASN.
A transfer syntax (PDU) according to the management information communication protocol format is created by adding a TLC structure to each parameter according to one grammar. At this time, the class and attribute identifiers are obtained from the profile identifier 413 on the agent table 402 based on the internal unified code 434 expression from the service issuing destination management agent PBX.
The network management device determines which object identifier expression is used for communication, and converts the object identifier into an object identifier 433 of the designated expression by using the object identifier conversion table 407.

In addition, the instance expression
(2) Determine whether the HOS or the identifier is used from the instance expression identifier in the HOS or the identifier, search the instance information table 403 for the HOS as it is, or search the instance information table 403 for the identifier, The corresponding relative identifier 416 is obtained, and the identifier is obtained by concatenating the relative identifiers 416.

The management information communication protocol control unit 102 is a CMIS (Common
Management Information Service) protocol
In step 806, an M_Get_req service is issued to the PBX network management device 204. M_Get_r from admin manager 208
PBX network management device 20 that received the eq service (step 901)
4 is a step 902 in which the management information communication protocol control unit 10
M_Get_req for the management information control unit PDU conversion function 309 from 2
Request PDU disassembly. The management information control unit 108 recognizes the M_Get_req service from the service ID = 1, and converts the PDU from the transfer syntax into a parameter list using the corresponding protocol format reference table 409.

At this time, the class and the attribute identifier are the internal unified code, and the instances are also the internal unified code.
Converted to HOS. Management information communication protocol control unit 1
02 is notified of the parameter list as the conversion result from the management information control unit 108 (step 903) and passes it to the management function execution control unit 103 (step 904). Management function execution control unit 103
Is the instance (P
BX.No.1) HOS value and query-designated attribute identifier (Operational State ID = 21, Administrative St
ate ID = 1) is extracted from the parameter list, and in step 905, an attribute value inquiry request is made to the object inquiry function 305 of the management information control unit 108 using this as a search key.

Upon receiving the request, the object query function 305 specifies the corresponding instance table 403 in the management information database 301 from the specified instance, points to the corresponding attribute value table 404, and is further stored on the attribute value table 404. Specified attribute identifier 402 (Operational State ID = 21, Administrative
Take out the attribute value 425 of State ID = 1),
It notifies the management function execution control unit 103 (step 1001).
The management function execution control unit 103 notifies the obtained attribute value information to the management information communication protocol control unit 102 (step 1002), and the management information communication protocol control unit 102
In step 1003, M_Get_c
Requests creation of an onf service PDU (service ID = 2).

The management information control unit 108 sets the service ID = 2 to M_Get_con
Recognize the f service and create a transfer syntax of M_Get_conf according to the protocol format reference table 409 (step 1004). On the other hand, the management information communication protocol control unit 102 of the PBX network management device 204 issues a PDU disassembly request to the management information control unit 108 in steps 1101 and 1102 by the same processing as described above, and parses the disassembled parameter list. As a result (step 1103), the management information communication protocol control unit
102 passes the parameter list to the management function execution control unit 103 (step 1104). The management function execution control unit 103 notifies the obtained attribute value to the management information control unit object update function 306 (step 1105).

On the other hand, the object update function 306
In 201, the attribute value table 404 in the management information database 301 is searched and compared with the current value. If the value matches, the value is left as it is. If the value does not match, the current value is updated to the notification attribute value. Upon receiving the update completion notification, the management function execution control unit 103
Class identifier, instance HOS, attribute identifier (Operational State ID = 21, Adminis
trative State ID = 1), attribute value information (for example, Operational State Value: Active = 3, Administrati
ve State Value: Unlock = 1) is notified (step 120).
2).

The man-machine interface 107 uses the management information control unit display name conversion processing function 302 to
Converted to the display name using the display name conversion table 408, C
Status inquiry result on RT (Tokyo.PBX.No.1: Operational Stat)
e = Active, Administrative State = Unlock) is displayed (steps 1203, 1204).

According to the above-described embodiment, the management information on the management object is collectively managed by the management information control unit, so that the management manager and other modules of the management agent are not affected, and the OS
By using a database structure that reflects the template definition of the object-oriented design of I as it is, flexibility and easiness of change can be guaranteed. In addition, the interface function group is made into a building block for each function module, the version number management function of the database that guarantees the consistency of the configuration information between the management manager and the management agent, and the internal unification of the object identifiers and instance expressions that represent multiple expressions The conversion function to code, the function to provide a high-speed search method for the management information database by binary tree (binary tree) search, and the processing method have the effect of realizing a scalable, effective and efficient interface function group. .

Next, as another embodiment of the present invention, the attribute value information table of the management information database is divided into an attribute value that is dynamically updated at the time of operation and an attribute value that is statically set in advance for management and operation. This case will be described with reference to FIGS. 1 to 3 and FIGS.

The system configuration and operation are the same as those in the above-described embodiment, except that the tenth
As shown in the figure, in the attribute value information table, the attribute value information having dynamic update is stored in the core memory 1301, and the static attribute value is stored in the file 1302. Search for static attribute value
A file address 1305 is stored in the above attribute value information table 1303 corresponding to the attribute identifier 1304, and the attribute value 1306 on the file is pointed based on this address.

Hereinafter, an example of the operation will be described with reference to FIG. 10 and FIG. FIG. 11 is an operation flowchart of the management manager when receiving an alarm report. When the PBX network management device 204 notifies the management manager 208 of the alarm report (step 1401), the management information communication protocol control unit 102 of the management manager 208 receives the alarm report in step 1402.
It requests the management information control unit 108 to disassemble the alarm report PDU. The management information control unit 108 sets the alarm report P
The DU is decomposed, and the result is notified to the management information communication protocol control unit 102 as a parameter list (step 140).
3). The management information communication protocol control unit 102 passes the parameter list to the management function control unit 103 (step 1404),
The management function execution control unit 103 requests the management information control unit event information addition function 304 for additional information (installation location, contact information, etc.) using the instance information and the event type identifier in the alarm report parameter list as search keys. (Step 1405).

The management information control unit event information addition function 304 extracts the additional information 1306, which is a static attribute, from the file using the file address pointer 1305, and notifies the management function execution control unit 103 of the result (step 1406).
Upon receiving this, the management function execution control unit 103 notifies the man-machine interface control unit 107 of the alarm parameter list and the obtained additional information 1306 (step 140).
7). The man-machine interface control unit 107
Instance information, management information control section display name conversion function
The information is converted into a display name by 302, and in step 1408, the alarm information including the additional information 1306 is displayed on the CRT.

According to the above embodiment, the dynamic attribute value and the static attribute value are divided and stored in the memory, and the information frequently searched and updated is stored in the core memory.
By providing information with a low update frequency on a file, there is an effect that efficient memory use can be realized.

Next, as another embodiment of the present invention, when the configuration of the management object managed by the management agent is changed,
The correspondence of the management manager will be described with reference to FIGS. 1 to 4 and FIG.

FIG. 12 shows a management information control unit 10 in consideration of a dynamic configuration change.
It is a block diagram of 8A. The system configuration and operation are the same as those of the first embodiment described above, but the configuration of the management information control unit 108A of the management manager 208 is different from that of the first embodiment in that the management information Function 1501
Is provided so that access to the management information database 301 of each interface function is managed.

Regarding the operation of the present embodiment, the
When the configuration change (object creation / deletion) of the management object is notified to the management manager 208 from 2,204,207, the management information execution control unit 1501 described above executes the instance information 403, the attribute value information table By rewriting 404 by the object registration / deletion function 303, it is possible to cope with a configuration change. The instance information 403 and the attribute value information table 404 are independently configured as individual information tables for each management agent, as described in the above-described embodiment.

At this time, the management information execution control unit 1501 rejects access to the instance information 403 and the attribute value information table 404 from another interface function to the configuration change target management agent until the configuration change (table rewrite) is completed.

According to the above embodiment, even when a configuration change of a management object in a management agent occurs, the management manager can continue to operate the other management agents while rewriting the management information on the configuration change target management agent. Thus, an excellent effect that an object configuration change in the management agent that is online can be dealt with can be obtained.

Hereinafter, still another embodiment of the present invention will be described. In this embodiment,
In the attribute value information table on the management information database, the state attribute (Operational State,
In the case of providing a field for storing the current value and the steady value (default value) of the Administrative State, and inquiring only the instance and attribute value having the current value different from the steady value, in the case of the difference state inquiry, FIG. This will be described with reference to FIGS. 4 and 13.

The system configuration and operation are the same as those of the first embodiment described above, except that a field for storing the steady value and the current value of the state attribute is provided in the attribute value information table 404 on the management information database 301. In each instance table of table group 403,
The difference is that a forward pointer 421 is provided. As shown in FIG. 13, the forward pointer 421 points to the next instance in the instance tree representation when all lower-level instances included in a specified instance are addressed so that they can be pointed like a single stroke. Address pointer.

The operation of the present embodiment is such that when the management information control unit object inquiry function 305 receives a state difference inquiry request for a specified instance or less, the object inquiry function 305 traces the forward pointer 421 from the specified instance, Is performed for all instances including a search for a state attribute identifier 424 having a different current value and an attribute value 425, and a difference state attribute identifier 424 and an attribute value 425 are returned to the requestor as an inquiry result for each instance.

According to the above embodiment, when starting the management manager,
The difference status inquiry function is exchanged when the status inquiry is made to each management agent or when the management manager makes a status inquiry to its own management information database and creates a status display screen on the CRT. The amount of management information is efficiently reduced, and the use of the forward pointer has an effect that a high-speed search of the management information database can be realized.

The above embodiments are merely examples of the present invention, and it goes without saying that the present invention is not limited to these embodiments.

〔The invention's effect〕

As described above in detail, according to the present invention, a management agent that manages each device of an information network configured by connecting a plurality of communication devices and information processing devices to each other, and interconnects with the management agent In a network management system that centrally manages a network by exchanging management information on a management object existing in each device with a management manager to be managed,
A database storing the management information and a management information control unit having an interface function group provided by using the database are provided in common with the same specifications in the management manager and the management agent, and the management information control unit By managing the management information collectively, the management information including the configuration of the flexible management information database and the effective and efficient interface function using this database on the actual network management system This has a remarkable effect that a network management system having a control function can be realized.

In addition, the management information database is configured as described in claim 3 so that the management information database configuration directly reflects the management information definition method based on the object-oriented design of OSI, thereby providing expandability and easiness of change. A database can be realized, and by grouping instance information for each agent, if a configuration change occurs in a managed object in any agent during operation, the configuration change target agent is temporarily operated to update the table Will be stopped,
There is an effect that the operation of another agent can be continued.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a network management device common to a management manager and a management agent to which a network management system according to an embodiment of the present invention is applied. FIG. 2 is a diagram showing a configuration example of the entire network management system. 3 is a diagram showing a configuration example of a management information control unit in the network management device, FIG. 4 is a diagram showing a configuration example of a management information related table in a management information database, and FIG. 5 is an instance address pointer on an instance tree. FIG. 6 is a flowchart of a start operation of the manager, FIG. 7 is a flowchart of a state inquiry request operation of the manager, and FIG. 8 is a flowchart of a state inquiry request reception operation of the PBX network management device. , FIG. 9 is a flowchart showing the operation of receiving the status inquiry result of the management manager, and FIG. 10 is an attribute value information table in the management information database. Diagram, FIG. 11 alarm reporting reception operation flow diagram of the manager, FIG. 12 shows a configuration example of the management information control unit in consideration of the dynamic configuration changes,
FIG. 13 is a diagram showing a one-stroke search method of an instance. 101: network management device, 102: management information communication protocol control unit, 103: management function execution control unit, 107: man-machine interface control unit, 108, 108A: management information control unit, 202:
Transmission network management device, 204: switching network management device, 207: information processing network management device, 208: management manager, 301: management information database, 302: display name conversion processing function, 303: object registration / deletion function, 304: event Information addition function, 305: Object inquiry function, 306: Object update function, 307: Object creation version number management function, 308: Operation check function, 309: PDU format check / conversion function, 1201: Management information execution control unit.

──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Michio Suzuki 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Inside Hitachi, Ltd.System Development Laboratory Co., Ltd. (72) Ryoichi Sasaki 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Hitachi Systems Development Laboratory (72) Inventor Yasuhiro Tanaka 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Hitachi Systems Development Laboratory Co., Ltd. (72) Inventor Masato Saito 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Shares (72) Inventor Shuji Fujino 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Inside Hitachi Software Co., Ltd. (72) Keizo Mizuguchi 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa, Japan Shares Hitachi, Ltd. Software Engineer (56) References JP-A-2-231184 (JP, A) JP-A-62-24377 (JP, A) JP-A-1-279340 (JP, A) JP-A 1-288038 (JP, A) JP-A-2-205153 (JP, A) JP-A-2-288527 (JP, A) IEICE technical report IN89-69 IEICE technical report IN90-56 (58) Fields surveyed (Int. Cl. ⁷ , DB Name) H04L 12 / 24,12 / 26

Claims (11)

(57) [Claims] 1. A sub-network management device for managing each device of an information network configured by interconnecting a plurality of communication devices and information processing devices, and an integrated network management interconnected with the sub-network management device. A network management system that centrally manages a network by exchanging management information about a management object existing in each device with a device, and a database storing the management information and a database using the database. A management information control unit having a group of provided interface functions is provided in common with the same specifications in the integrated network management device and the sub-network management device, and the management information is collectively managed by the management information control unit. A class information serving as common information for the entire management object, Network management characterized by comprising a group of tables defining and storing tribute information and operation information, and a group of tables defining and storing managed object instance information and attribute value information, which are individual information for each actual managed object instance. system. 2. The integrated network management apparatus according to claim 2, wherein the management information control unit exchanges an object identifier, which is exchanged in communication between the integrated network management device and the sub-network management device of the information network, with a code expression different for each specification, in the integrated network. 2. The apparatus according to claim 1, further comprising means for converting into a unified code that can be handled by a unified code in the management device and the sub-network management device.
A network management system according to claim 1. 3. The management information database has a table group in which a communication protocol format for exchanging management information between an integrated network management device and a sub-network management device of the information network is defined for each service type. 2. The network according to claim 1, wherein the management information control unit has means for executing assembly / disassembly / check of a protocol data unit by referring to the table when issuing / receiving each protocol service. Management system. 4. The management information database uses any one of the object instance information expressions different for each specification among the management information exchanged between the integrated network management device and the sub-network management device of the information network. 2. The network management system according to claim 1, wherein an instance expression identifier indicating whether or not an instance expression is provided is provided, and the management information control unit is provided with means for converting between instance expressions. 5. The management information database according to claim 1, wherein the inclusion relation between instances of the object instance information and the inheritance relation between the classes of the class information are represented by inter-table connection relation pointers on the management information database. Network management system. 6. The management information database divides and manages managed object instance information and attribute value information, which are individual information for each managed object, as a group of tables defined and stored for each sub-network management device of the information network. The network management system according to claim 1, wherein the management is performed. 7. An inter-table connection pointer is provided in an object instance information table for specifying a specified object instance and specifying all object instances included in a specified base object instance on the management information database. The network management system according to claim 1, wherein: 8. The management information database defines and manages version numbers for a table group of instance information and attribute value information, which are individual information, for each sub-network management device of the information network. 2. The network according to claim 1, wherein, when the integrated network management device and the sub-network management device of the information network exchange management information, the units mutually confirm version numbers when setting an association. Management system. 9. The management information control unit refers to information defined in a table group on the management information database, and manages information exchanged between the integrated network management device and the sub-network management device of the information network. 2. The network management system according to claim 1, further comprising means for checking a data type and an allowable value of information and an operation check for each sub-network management device of the information network. 10. The management information control unit can set both a steady value and a current value for each attribute on an attribute value information table that is individual information for each instance in the management information database. 2. The network management system according to claim 1, further comprising: means for resetting to a steady value, and means for searching for and inquiring of an attribute value having a current value different from the steady value. 11. The management information control unit according to claim 1, wherein said management information in said management information database is dynamically changed information,
2. The network management system according to claim 1, wherein the network management system divides the information into statically set information and manages the information.