JPH11134230A - Network manager system - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To realize a management operation transaction process without increasing memory in a network manager system for performing network maintenance and operation management. SOLUTION: Managed object 91, 92, 13
The management operation interfaces 31, 32, 33, 34, and 3m corresponding to 1, 132, and 13m are generated in the memory area by the management operation interface management unit 2 only when executing the transaction processing. Management application 1
1, 12, 1n perform a management operation by transaction processing on the management target object via the generated management operation interface. The generated management operation interfaces 31, 33 are stored in the backup areas 31-1, 33.
Save the data for rollback to -1. The management operation interfaces 31, 32, 33, 34 and 3m do not depend on the communication protocols 4 and 5. The management operation interface management unit 2 has a function of processing a deadlock in generation of the management operation interface.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a network manager system for managing and operating a network, and more particularly, to a communication protocol CM defined by OSI.
IP (Common Management Info)
Communication Protocol (SNMP) (Simple N)
network Management protocol
1) The present invention relates to a network manager system for managing a network by using 1) and the like.

[0002] In recent years, transmission devices constituting a network,
It is required to manage communication equipment such as exchanges and routers or computers in an open environment. Therefore, the communication protocol CMIP or S defined by OSI or IETF
It is required to manage communication facilities or computers constituting a network using NMP.

A network manager system includes a plurality of management applications for performing management operations on an agent system, which is a managed system. Each of the plurality of management applications performs management operations such as a change in network configuration. The network manager system has to execute these processing requests simultaneously and at high speed, and therefore, the network manager system has to execute multiple processing commands consisting of a plurality of management commands for It is necessary to configure so that a plurality of transaction processes composed of commands can be executed in parallel.

[0004] In the communication protocol CMIP or SNMP, a managed object (MO:
(Managed Object). The object to be managed (MO) has data called attributes, and there are a plurality of types of attributes. In the CMIP communication protocol, the management operation of the network manager system for each managed object (MO) is defined for each type of managed object (MO), and is classified into the following five.

1) Generate a management object (MO). 2) Delete the managed object (MO). 3) Write the attribute value of the object to be managed (MO). 4) Read the attribute value of the object to be managed (MO). 5) Cause the managed object (MO) to execute a predetermined process.

The communication protocol SNMP is classified into the following two types. 1) Write the attribute value of the object to be managed (MO). 2) Read the attribute value of the object to be managed (MO).

[0007] In addition to these, the object to be managed (M
The notification of the event from O) is specified. or,
A specific managed object (MO) in a management operation
Is specified in the management information tree (MIT: Mana).
The information is specified by a name given by a tree structure naming rule called a “gement Information Tree”, but the naming rule by the management information tree (MIT) differs depending on each communication protocol.

[0008]

2. Description of the Related Art Communication protocol CMIP or SNMP
Does not define a command for processing a process consisting of a plurality of management operation commands as a transaction, so that a general agent system cannot recognize a process consisting of a plurality of management operation commands as a transaction. , A series of management operations cannot be executed as a transaction.

Conventionally, in order to solve such a problem,
A management operation interface (ProxyMO) having an interface function for each management target object (MO) is created in the network manager system for each management target object (MO), and the management operation interface (ProxyMO) is created when the transaction processing is executed. Lock processing has been performed to prevent other transaction processing from accessing the managed object (MO) via the management operation interface (ProxyMO), thereby implementing transaction processing.

[0010]

The management operation interface (ProxyMO) is a management object interface (M
O) has the same operation interface as the management operation interface (ProxyMO). The management operation interface (ProxyMO) is defined in the object-oriented manner similarly to the management object (MO), and generating the management operation interface (ProxyMO) means that the management operation interface (ProxyMO) In the memory area.
An information storage unit for rollback processing for returning changed data to the original state due to incomplete transaction processing is provided in each management operation interface (ProxyMO).

For this reason, the object to be managed (MO)
Management operation interfaces (ProxyM)
O) must be generated, and if the number of objects to be managed (MO) becomes enormous, the number of management operation interfaces (ProxyMO) also becomes enormous, and a large amount of computer resources such as a memory of a network manager system are required. The problem had arisen.

[0012]

A network manager system according to the present invention comprises: (1) a network manager system for instructing an agent system, which is a managed system, to perform a management operation on a managed object; A management operation interface corresponding to the managed object,
A lock processing unit for the management operation interface, a storage area for holding backup data for rollback, and an agent system that does not have a transaction processing function consisting of a plurality of management operations. A network manager system capable of performing transaction processing, wherein the network manager system includes a management operation interface corresponding to a management target object to be operated at the start of transaction processing or immediately before execution of a management operation. A management operation interface management unit that creates a part or all of the memory to secure its memory area and deletes the data at the end of the transaction processing; and stores backup data for rollback in the management operation interface that is generated and deleted. An area once after storing the agent system backup data for rollback to read the area, in which a change operation unit for performing the change operation of the managed objects.

(2) As the management operation interface, a management operation interface with a temporary name is generated in advance and its memory area is reserved, and only during the execution period of transaction processing, the management operation interface is created. A name change unit that replaces the temporary name with a part or all of the name of the management operation interface corresponding to the managed object to be operated in the transaction processing;
In the management operation interface having the temporary name, an area for storing backup data for rollback is provided, and once the backup data for rollback is read from the agent system and stored in the area,
A change operation unit for performing a change operation on the management target object.

(3) The management operation interface is named according to a naming rule independent of a communication protocol, and the name of the management operation interface assigned according to a naming rule independent of the communication protocol is assigned to each communication protocol. It is provided with a management operation interface name conversion unit for converting to a name based on a dependent naming rule.

(4) The management operation interface is generated before the management operation by the transaction processing is executed, or is given a temporary name and is generated before the management operation by the transaction processing is executed. ,
Alternatively, the number of management operation interfaces to which temporary names are assigned is changed in accordance with generation or deletion notification of a managed object from the agent system.

(5) An access frequency counting unit for counting the number of times of the management operation access to the management operation interface for each management operation interface, wherein the management operation interface having a large number of access times is always generated. It is.

(6) The management operation interface has a flag for setting a data change prohibition for an operation cancellation request generated after the transaction processing is completed, and the management operation is performed until the flag is turned off. The interface is maintained and backup data for rollback is retained.

(7) A deadlock detection function is provided in the network manager system. When a transaction executed by the management application executes a lock process on the management operation interface, the lock process is waited for by a lock of another transaction. In this case, when deadlock detection processing is performed and deadlock occurs due to waiting for lock processing,
When a transaction that includes a lock operation that is being held is rolled back, or when the transaction is terminated, a lock held by the transaction on the management operation interface is released, and a plurality of other lock-waiting transactions attempt to acquire the lock, the individual The deadlock detection process is performed on the lock of a certain lock. If a deadlock occurs due to a certain lock, the lock is yielded to a transaction that attempts to acquire another lock, and a deadlock occurs in all cases. Is to roll back all transactions.

(8) As the management operation interface, there is provided a management operation interface having a function corresponding to an event distribution selection unit for controlling the distribution of event notifications in the agent system. The distribution screening department
It has a management application in the network manager system and a distribution control function of event notification of the agent system.

(9) A plurality of agent systems, a management operation interface management information tree for managing names of management operation interfaces corresponding to each agent system, a plurality of management applications, and a management application for realizing each management application A management application realization object management information tree that manages the names of realization objects; and an integrated management information tree in which the management application realization object management information tree and the management operation interface management information tree are combined in different combinations for each management application. Each management application has only the management operation interface accessed by itself under the name management of the management application.

[0021]

FIG. 1 is a diagram illustrating the principle of the present invention. 1 is a network manager system, 11 to 1n
Denotes a management application, 2 denotes a management operation interface (ProxyMO) management unit, 21 denotes a management operation interface management information tree (ProxyMOMIT), 22 denotes a presence management operation interface (ProxyMO) management unit, and 23 denotes a management operation interface (ProxyMO).
The generation / deletion unit, 31 to 3m is a management operation interface (P
(roxyMO), 31-1 and 33-1 are backup areas, 4 is an SNMP communication protocol termination unit of the network manager system, 5 is a CMIP communication protocol termination unit of the network manager system, 6 is an SNMP communication protocol termination unit of the agent system, 11 Is the CMIP communication protocol termination part of the agent system,
8 and 12 are execution control units in the agent, 81 and 121 are management information trees, 91, 92, 131, 132 and 13m
Is the object to be managed (MO), 101, 102, 1
41, 142, and 14m are managed entities.

Each of the management applications 11 to 1n operates independently of each other, and requests execution of a plurality of management operations as transaction processing. The management operation interface (ProxyMO) management unit 2 only executes while the transaction processing is being executed.
A management operation interface having a name corresponding to the management object (MO) to be operated is generated, and its memory area is secured.

The management operation interface management information tree (ProxyMOMIT) 21 manages the names of all management operation interfaces. The presence management operation interface (ProxyMO) management unit 22 includes a management operation interface (Prox) that exists in the network manager system (that is, a memory area is reserved).
yMO) name and management operation interface (Proxy)
MO), and converts the name of the management operation interface (ProxyMO) into a pointer to the memory area.

The presence management operation interface (Proxy)
MO) management unit 22 includes a management operation interface (Pro)
xyMO) receives a request to retrieve a pointer from the name of the management operation interface (Pr
(oxyMO) is present, the value of the pointer of the memory area is returned. Otherwise, the management operation interface (ProxyMO) generation / erase unit 23 is instructed to secure the memory area. The value of the pointer is returned. When the management operation interface (ProxyMO) becomes unnecessary, release of the memory area is performed by the management operation interface (ProxyMO).
A command is issued to the generation / erase unit 23.

Management operation interface (ProxyM)
O) 31 to 3m have an operation interface function for a managed object (MO) in the network manager system, and a management operation interface (ProxyM)
O) is called from the management application by the pointer to the memory area, and functions as an operation interface for the corresponding managed object (MO).

In the figure, the management operation interfaces (ProxyMO) 32, 34, and 3m indicated by dotted lines indicate management operation interfaces (ProxyMO) that have not been generated, and the management operation interface (ProxyMO) is indicated by solid lines.
O) 31, 33 indicate the generated management operation interface (ProxyMO).

When the management operation from the management application is a data change operation of the management object (MO), the management operation interface (ProxyMO) 3
As an internal operation of the devices 1, 33, a protocol such as CMIP or SNMP is used, and in preparation for rollback in transaction processing, data of a management target object (MO) corresponding to a change operation is once read to back up backup data. After performing the process of securing data in the management objects 31-1 and 33-1, a command to perform a data change operation on the management target object (MO) is issued using a protocol such as CMIP or SNMP.

Next, a specific operation will be described. In the following description, the numbers enclosed in parentheses are shown in the figure (
The path corresponding to the number in parentheses) indicates the path through which data such as a processing request or command is transmitted. First, the management application 12 requests a pointer to the management operation interface (ProxyMO) from the management operation interface (ProxyMO) management unit using the name of the ProxyMO3 (1). The management operation interface (ProxyMO) management unit 2 manages the management operation interface management information tree (Pr).
(oxyMOMIT) 21 after confirming that the name exists, and then the presence management operation interface (ProxyMO)
The information of the management unit 22 is searched, and it is confirmed whether or not the pointer of the memory area of the management operation interface (ProxyMO) 33 with the name of ProxyMO3 exists (2).

If the management operation interface (ProxyMO) 33 of the name of the ProxyMO3 exists, that is, if a pointer exists, the value of the pointer is returned to the management application 12, and the management operation interface (ProxyMO) 33 of the corresponding name is returned. If it does not exist, that is, if the pointer does not exist, it instructs the management operation interface (ProxyMO) generation and deletion unit 23 to generate the management operation interface (ProxyMO). (3).

Management operation interface (ProxyM)
O) The generation / erase unit 23 generates the management operation interface (ProxyMO) 33 including the backup area (4), and stores the pointer in the presence management operation interface (Pr).
After registering with the (oxyMO) management unit 22, the value of the pointer of the management operation interface (ProxyMO) 33 with the name of ProxyMO3 is returned to the management application 12. The management application 12 calls the management operation interface (ProxyMO) 33 having the name of ProxyMO3 based on the value of the pointer (5).

When the data of the corresponding managed object (MO3) 131 is changed, the management object interface (MO3) necessary for rollback is executed by the management operation interface (ProxyMO) 33 of the name of ProxyMO3.
3) The data of 131 is stored in the management operation interface (Pro
xyMO) 33, the management operation interface (ProxyMO) 33
The communication protocol (CMI)
P) 5 is read from the managed object (MO3) 131 of the managed entity 141 via the intra-agent execution control unit 12 of the agent system (6),
(7), (8), (9). Thereafter, a data change to the managed object (MO3) 131 of the managed entity 141 is transmitted using the communication protocol (CMIP) 11 (10), (11), (12), and (13).

The next command to be processed as a transaction process is similarly issued from the management application 12 (14), and the management operation interface (Prox) has already been issued.
If (yMO) exists, processing excluding the generation processing is performed.

After the transaction processing is completed, the management operation interface (ProxyMO) is deleted, and the pointer is changed to the existence management operation interface (ProxyM).
O) It is deleted from the management unit 22. When the transaction processing is rolled back, the management operation interface (ProxyMO) executes the rollback processing for setting the backup data to the management target object (MO).

According to the present invention, for an agent system that does not support transaction processing, a management operation including a plurality of commands that must be operated as transaction processing can be realized without increasing the memory of the network manager system. Can be.

FIG. 2 is an explanatory diagram of the first embodiment of the present invention. The same functional units as those in FIG. 1 are denoted by the same reference numerals. Reference numeral 221 denotes a transaction participation management operation interface (ProxyMO) management unit, and reference numerals 31-2 and 33-2 denote lock information units.

The management operation interface management information tree (ProxyMOMIT) 21 manages all management operation interface (ProxyMO) names.
Management information trees (MIT1, MIT) of the execution control units 8 and 12 in the agents of all the managed agent systems.
2) 81 and 121 are combined.

The presence management operation interface (Proxy)
The MO) management unit 22 is a management operation interface (ProxyMO) 3 that exists in the network manager system (that is, has a memory area).
1, 33 and their memory areas are managed. From the name of the management operation interface (ProxyMO),
Performs conversion to a pointer to a memory area.

The transaction participation management operation interface (ProxyMO) management unit 221 is called from the management application at the start of transaction processing, generates a transaction ID that is an identifier of a transaction, and locks the management operation interface (locked during transaction processing). Proxy MO) name or pointer is managed in a list for each transaction ID. Also, rollback and commitment processing of the specified transaction ID is performed.
Here, the commitment process is a process for terminating the transaction process normally and completing the data change.

Management operation interface (ProxyM)
O) The management unit 22 returns a pointer to the memory area if the management operation interface (ProxyMO) with the specified name exists, and if not, the management operation interface (ProxyMO)
After instructing the generation / erase unit 23 to secure a memory area, the pointer is returned. Also, commitment,
Management operation interface (Pro
When the xyMO) becomes unnecessary, the management operation interface (ProxyMO) generation / erase unit 23 is instructed to release the memory area.

Management operation interface (ProxyM)
O) Reference numerals 31 to 3m denote operation interfaces to objects to be managed (MO) in the network manager system. Management operations are called from the management application based on pointers in the memory area of the management operation interface (ProxyMO).

Management operation interface (ProxyM)
O) In the call of 31 to 3m, as auxiliary information,
A transaction ID is added to the lock information part 31 of the management operation interface (ProxyMO) 31 to 3m.
Information indicating which transaction process is locked is written in the list of −2, 33-2, and the management operation interfaces (Proxy MO) 31, 33 are locked.

When a management operation having another transaction ID attempts to access the locked management operation interface (ProxyMO) 31, 33,
The lock processing is waited, and the parallel execution control is performed.

In the case of a data change operation on the management object (MO), the internal operation uses the communication protocol CMIP or SNMP, etc., and temporarily stores the data of the management object (MO) corresponding to the change operation. And the backup data is read from the backup area 31-
After performing the process of securing the data in the management object 1, 33-1, the data change operation to the management target object (MO) is performed using the communication protocol CMIP or SNMP.

Next, a specific operation will be described. The management application 12 performs an operation of starting a transaction to the transaction participation management operation interface (ProxyMO) management unit 221 to acquire a transaction ID. Next, a pointer to the management operation interface (ProxyMO) is requested to the management operation interface (ProxyMO) management unit 2 using the name of the management operation interface (ProxyMO) (1).

Management operation interface (ProxyM)
O) The management unit 2 checks whether a name exists in the management operation interface management information tree (ProxyMOMIT) 21 and then checks the presence management operation interface (Proxy).
MO) The information of the management unit 22 is searched to check whether a pointer to the memory area of the management operation interface (ProxyMO) exists (2).

Management operation interface (ProxyM)
O) exists, that is, if a pointer exists,
Return the pointer of the corresponding management operation interface (ProxyMO) to the management application, and if the management operation interface (ProxyMO) does not exist,
That is, if the pointer does not exist, the management operation interface (ProxyMO) generation and deletion unit 23 is instructed to generate the management operation interface (ProxyMO) (that is, to secure a memory area) (3).

Management operation interface (ProxyM)
O) The generation / erase unit 23 includes a management operation interface (P) including a lock information unit 33-2 and a backup area 33-1.
(ProxyMO) 33 is generated (4), and a pointer is stored in the presence management operation interface (ProxyMO) management unit 22.
After that, a pointer to the management operation interface (ProxyMO) is returned to the management application 12.

The management application 12 adds a transaction ID as auxiliary information based on the value of the pointer, and adds a transaction ID to the management operation interface (ProxyMO).
33 management operations are called (5).

Management operation interface (ProxyM)
O) 33 compares the transaction ID with the lock information and, if the transaction has already been locked, enters the execution of the management operation. If the transaction is already locked by another transaction, the transaction participation management operation interface (Proxy
MO) The management operation interface (ProxyMO) is registered in the list for each transaction ID of the management unit 221 and the transaction is suspended (5 ').

If it is not locked, its own transaction ID is written in the lock information section, and the transaction participation management operation interface (ProxyM)
O) Register the management operation interface (ProxyMO) in the list for each transaction ID of the management unit 221;
Enter management operations.

In the management operation for changing the data of the management object (MO), the management object (MO)
The data of the managed object (MO) necessary for rolling back the change of the management protocol is used as the internal operation of the management operation interface (ProxyMO) as the communication protocol C.
Reading from the agent system using MIP (6), (7), (8), (9). Thereafter, a data change for the managed object (MO) is transmitted using CMIP (10), (11), (12), (1).
3). In a management operation that does not change the data of the managed object (MO), information for rollback is not read.

The next management operation to be processed as a transaction is also issued from the management application (1).
4) The management operation interface (ProxyM)
If O) exists, processing excluding the generation processing is performed. After the transaction processing is completed, the management operation interface (ProxyMO) is deleted and the pointer is deleted from the existence management operation interface (ProxyMO) management unit 22.

An instruction (2) from the management application 12
If the transaction processing is rolled back (returned to the state before the start of the transaction processing) according to 5), the transaction participation management operation interface (P
(roxyMO) management unit 221 transmits the transaction ID
The management operation interface (Pro
xyMO) to perform a rollback process of setting backup data as a management object (MO) (26). If another transaction is not accessing the management operation interface (ProxyMO), the memory area of the management operation interface (ProxyMO) is released and the existence management operation interface (P
The management operation interface (ProxyMO) and the pointer are deleted from the (roxyMO) management unit 22.

In the case of commitment (normal termination), the transaction participation management operation interface (Prox
The search for the management operation interface (PMO) is performed when another transaction does not access the management operation interface (ProxyMO).
The memory area of the proxy MO is released, and the management operation interface (Proxy MO) and the pointer are deleted from the existence management operation interface (Proxy MO) management unit 22.

Some management operation interfaces (Prox
In the case of performing generation and elimination only for the yMO), the existence management operation interface (ProxyMO) management unit 22
A table for registering a management operation interface (ProxyMO) that does not perform generation and deletion every time, and a management operation interface (ProxyMO) that does not perform generation and deletion every time from the management application is stored in a table of the existence management operation interface (ProxyMO) management unit 22. Register with. The management operation interface (ProxyMO) which does not perform generation and deletion every time is generated when the system is started up and the like, and the management operation interface (ProxyM) is generated.
O) The generation / erase unit 23 transmits the management operation interface (P
(RoxyMO) is controlled not to be erased.

The always existing management operation interface (ProxyMO) can hold the operation result of the previous data change to the management object (MO) as backup data. The processes (17) and (10) for reading data from the object (MO) can be reduced, and the process can be speeded up. Also, by using this backup data as cache data when reading data, it is possible to return a response to the management application at high speed.

As a management operation interface (ProxyMO) that is always present, a management operation interface (ProxyMO) with a large number of accesses and a management operation interface (ProxyM) with a large number of times of changing the value are used.
O) and the like.

According to the present invention, a management operation including a plurality of commands that must be processed as a transaction for an agent system that does not support the transaction processing can be performed without increasing the memory in the network manager system. Become.

Further, by controlling the number of management operation interfaces (ProxyMO) that are always present, it is possible to reduce the amount of memory and adjust the trade-off between processing required for generation and deletion and data backup processing. More optimal realization becomes possible.

FIG. 3 is an explanatory diagram of the second embodiment of the present invention. 1 or 2 are denoted by the same reference numerals. 222 is a kana management operation interface (P
The (roxyMO) name conversion unit 223 is a pseudonym management operation interface (ProxyMO) management unit. 4A and 4B are explanatory diagrams of a pseudonym management operation interface management information tree. FIG. 4A shows a real name management operation interface management information tree (a pseudonym ProxyMOMIT), and FIG. 4B shows a pseudonym management operation interface management information tree (a proxy).
MOMIT), each circle indicates a name, and indicates that the name has a hierarchical tree structure.

In the embodiment of FIG. 3, the pseudonym management operation interface management information tree (Prox
A plurality of management operation interfaces (ProxyMO) having shaded names on yMOMIT) are generated to provide a memory area, and a temporary name (for example, network)
A, nodeA, rackA, etc.) are registered in the presence management operation interface (ProxyMO) management unit 22.

Management operation interface (ProxyM)
When a pointer for accessing the memory area of O) is requested from the management application (1), (2), the pseudonym management operation interface (ProxyMO) name conversion unit 222 transmits the presence management operation interface (Pr).
The management operation interface (ProxyMO) with the temporary name of the class corresponding to the class of the managed object that receives the management operation in the management unit 22 (oxyMO) is replaced with the management operation interface (ProxyMO) that is actually accessed. Name (network1, nod
e1, rack1, etc.) (3), and returns a pointer to the management application to access the accessed management operation interface (ProxyMO) to the management application.

Thus, the management operation interface (P
It is possible to replace the process required for generating (roxyMO) (securing memory) with the process of only renaming, thereby improving the performance. When the transaction processing is completed, the name is changed to the original temporary name.

Some management operation interfaces (Prox
When renaming is performed only for the yMO), a table for registering the management operation interface (ProxyMO) that does not perform the name renaming is provided in the pseudonym management operation interface (ProxyMO) management unit 223, and the name is changed from the management application. The management operation interface (ProxyMO) that does not perform the replacement is registered in this table, and the management operation interface (Pr
oxyMO) is managed by the name in the presence management operation interface (ProxyMO) management unit 22.

In this embodiment, if the management operation interface (ProxyMO) generated in advance becomes insufficient, one or a plurality of management operation interfaces (ProxyMO) with temporary names are generated. , Managed objects (M
O) corresponds to an increase in the number.

For the management operation interface (ProxyMO) whose name is not changed, the operation result of the previous data change to the management object (MO) is retained as backup data, so that the management object interface (MO) is temporarily changed when the data is changed. ), The processes (19) and (10) for reading data can be reduced, and the process can be sped up. Also, by using this backup data as cache data when reading data, it is possible to return a response to the management application at high speed.

As a management operation interface (ProxyMO) whose name is not rewritten, a management operation interface (ProxyMO) with a large number of access times and a management operation interface (ProxyM) with a large number of times of changing the value are used.
O) and the like. FIG. 5 is an explanatory diagram of the third embodiment of the present invention. The same functional units as those in FIG. 1, FIG. 2, or FIG. 3 are denoted by the same reference numerals. Reference numeral 24 denotes a protocol independent management information tree (MIT), and reference numeral 25 denotes a communication protocol compatible management information tree (CMIPMIT / SNMPMIT) name conversion unit.

In the embodiment shown in FIG. 5, a protocol-independent management information tree (MIT) that does not depend on a communication protocol is used.
24, and a communication protocol compatible management information tree (CMI) for converting a name using a management information tree (MIT) corresponding to a communication protocol (CMIP or SNMP).
PMIT / SNMP MIT) name conversion unit 25 is provided.
The management application uses a name based on the protocol-independent management information tree (MIT) 24 to specify the management operation interface (ProxyMO).

The communication protocol correspondence management information tree (CM
The IPMIT / SNMPMIT name conversion unit 25 manages the management operation interface (ProxyM) according to each protocol.
O), and extracts a pointer corresponding to the memory area of the management operation interface (ProxyMO) based on the converted name and returns it to the management application.

According to this embodiment, the naming rule of the managed object (MO) and the naming rule of the management operation interface (ProxyMO) are protocol independent, and the managed object (MO) that is completely protocol independent. Access becomes possible.

Next, a fourth embodiment of the present invention will be described. This embodiment differs from the embodiment shown in FIG. 2 in that when a management object (MO) creation notification and a management object (MO) deletion notification are received from the agent system, a management operation interface management information tree (ProxyMOMIT) is received. ) 21 to add or delete a new name, and perform the management operation interface (Prox).
yMO) management unit 2 with a management operation interface (Prox
yMO), the number of management operation interfaces (ProxyMO) or the number of management operation interfaces (ProxyMO) of a specific class, etc.
Management operation interface to exist (ProxyMO)
Is provided, and when the number of management operation interfaces (ProxyMO) in the management operation interface management information tree (ProxyMOMIT) 21 changes, the management operation interface (Pro
xyMO) can be added or deleted, the trade-off between generation and erasure overhead and the amount of memory can be adjusted, and the memory area can be used effectively by optimally controlling the number of management operation interfaces (ProxyMO).

Next, a fifth embodiment of the present invention will be described. This embodiment differs from the embodiment shown in FIG. 2 in that the management operation interface (ProxyMO) management unit 2 includes an access frequency counting unit for counting the number of times of access to the management operation interface (ProxyMO), and an access at a fixed time period. A presence management operation interface (ProxyMO) changing unit that changes an existing management operation interface (ProxyMO) based on the number of times is provided.

The access number counting unit counts the number of pointer requests of each management operation interface (ProxyMO). Presence management operation interface (ProxyM
O) The change unit investigates the number of accesses at a fixed time period,
Management operation interface (Prox
yMO) from the top. Alternatively, a management operation interface (ProxyMO) having a certain number of access times or more is provided. As the number of times of access, a total number of times, the number of times per unit time, and the like are used. Thereby, the management operation interface (Pr
oxyMO) alone, and by dynamically controlling the number thereof, it is possible to speed up processing and reduce memory by efficiently using memory.

FIG. 6 is an explanatory diagram of a sixth embodiment of the present invention. In the figure, the same reference numerals are given to the same functional units as those in FIG. 1, FIG. 2, FIG. 3 or FIG. Reference numeral 15 denotes a disk for storing processing results.

In this embodiment, there is a storage 15 for storing the processing result when the transaction processing is completed, and the processing result is backed up to the disk 15 when the transaction processing is committed (normally completed) (27). Management operation interface (ProxyMO)
Has a flag to set the data change prohibition for the operation cancellation request that occurs after the transaction processing is committed, and until this flag is turned off,
The backup data for rollback (returning to the state before the start of the transaction processing) is held in the management operation interface (ProxyMO).

The operation cancellation request is realized by the management application calling the rollback interface of the transaction participation management operation interface (ProxyMO) management unit 221. The flag for prohibiting data change is called from the management application via the transaction participation management operation interface (ProxyMO) management unit 221.

FIG. 7 is an explanatory diagram of the seventh embodiment of the present invention. In the figures, FIG. 1, FIG. 2, FIG. 3, FIG. 5 or FIG.
The same functional units are denoted by the same reference numerals. This embodiment relates to avoiding a deadlock in lock processing for a management operation interface (ProxyMO) during transaction processing. First, the occurrence of deadlock will be described with reference to FIG.

FIG. 8A shows a first case in which deadlock occurs. In FIG. 8A, transaction 1 is a management operation interface (Proxy)
MOA) performs a lock setting (1), transaction 2 sets a lock on the management operation interface (ProxyMOB) (2), and then transaction 1 attempts to set a lock on the management operation interface (ProxyMOB), and lock processing is performed. Is waiting by the lock of the management operation interface (ProxyMOA) (3), the transaction 2 tries to set the lock on the management operation interface (ProxyMOA), and is waited by the lock of the management operation interface (ProxyMOA) (4). The transactions 1 and 2 are in a state of waiting for the release of the lock with each other, and a deadlock occurs.

FIG. 8B shows a second case in which deadlock occurs. In FIG. 8B, when the transaction 3 that has secured the lock of the management operation interface (ProxyMOB) waiting for lock processing from two or more transactions releases the lock of the management operation interface (ProxyMOB). , In the other two transactions, transaction 1 is the management operation interface (ProxyMO
A) holding the lock of A) and two management operation interfaces (ProxyMOA), (P
In the case where both lock processing to the proxy MOB (roxyMOB) is waiting (this occurs when the transaction is further divided and executed in parallel), the lock to the management operation interface (ProxyMOB) is set to the transaction 2. Is ensured, the state becomes the same as in case 1 and a deadlock occurs.

In the embodiment shown in FIG. 7, the transaction participation management operation interface (ProxyMO) management unit 2
21 is added to the deadlock detection function shown in FIG. 9 and FIG. 10. In the first case where a deadlock occurs, when the lock processing enters a wait state, the transaction 1 which becomes a deadlock is rolled back. In the second case in which the deadlock occurs, the deadlock is avoided by making the transaction 1 secure the lock.

FIG. 9 is a flowchart of the deadlock detecting function. When the deadlock occurs in the first case shown in FIG. 8A, a registration (5 ') operation of the transaction participation management operation interface (ProxyMO) associated with the management operation (5) is performed in step S1, and a step S2 is performed. In the management operation interface (Pr
oxyMO) is locked, and if not locked, a lock is set in step S3, the management operation interface (ProxyMO) is registered in the list of own transaction IDs, and step S1 is executed.
The processing is continued by 1.

If it is determined in step S2 that the transaction ID is locked, it is determined in step S4 whether the transaction IDs are the same.
In step S5, the management operation interface (ProxyMO) is registered in the list of own transaction IDs,
The process is continued in step S11. Step S
If it is determined in step 4 that the transaction IDs are not the same, it is determined in step S6 whether the locked transaction is waiting. If not, the management operation interface is added to the list of own transaction IDs in step S7. (Proxy
MO), and waits for a lock process in step S8.

If it is determined in step S6 that the locked transaction is waiting, the management operation interface (Pr) causing the locked transaction to wait is determined in step S9.
The ID of the transaction that secures the lock (oxyMO) determines whether or not the transaction is about to perform lock processing, and causes the management operation interface (Pro) to wait for the locked transaction.
If the ID of the transaction securing the xyMO lock is not the transaction for which lock processing is to be performed, the management operation interface (ProxyM) is added to the list of own transaction IDs in step S7.
O) is registered, and a lock process is waited in step S8.

In step S9, it is determined that the ID of the transaction securing the lock of the management operation interface (ProxyMO) that causes the waiting of the locked transaction is the transaction for which lock processing is to be performed. If it is determined, the transaction to be locked is rolled back in step S10, the transaction is deleted, and the process is continued in step S11.

FIG. 10 is a flowchart of the deadlock detecting function. When the deadlock occurs in the second case shown in FIG. 8B, the lock release accompanying the end of the transaction is started in step S21, and the lock released in step S22 waits for two or more transactions. It is determined whether or not two or more waits have been made, and the lock is released in step S23, the lock is transferred to another transaction, and the process is continued in step S31. Step S22
If you decide not to wait two or more times,
At step S24, it is determined whether all the waiting transactions are waiting for a plurality of lock acquisitions. If not waiting for a plurality of lock acquisitions, the locks are released at step S25, and one lock is acquired. The transaction is transferred to the waiting transaction, and the process is continued in step S31.

If it is determined in step S24 that the user is waiting for a plurality of locks, step S2
6, a transaction that is a candidate for transferring one lock is selected, and in step S27, it is determined whether a transaction waiting for a candidate transaction to wait for another lock is waiting for a lock to be released. If not waiting, step S
The lock is released by 28 and the lock is transferred to the candidate transaction, and the process is continued in step S31.

If it is determined in step S27 that the transaction is waiting due to the lock to be released, it is determined in step S29 whether all transactions have been checked. If not, the process proceeds to step S29. In S30, a transaction that is a candidate for transferring another lock is selected, and the process returns to step S27.

If it is determined in step S29 that all transactions have been checked, all transactions are rolled back in step S30, and the process is continued in step S31. The lock process is performed by operating the management operation interface (ProxyMO) by operating the management operation interface (ProxyMO).
If the process is called inside the application, there is no need to describe the lock process and the process to avoid deadlock in the management application.

FIG. 11 is an explanatory view of the eighth embodiment of the present invention. In the figures, FIG. 1, FIG. 2, FIG. 3, FIG. 5, FIG.
Alternatively, the same reference numerals are given to the same functional units as those in FIG.
Reference numeral 20 denotes an event handler, and reference numeral 40 denotes a management operation interface: an event delivery selection unit (ProxyMOEFD).

In this embodiment, an event distribution and selection unit (EFD: EventForwardingDi) for managing the notification of an event in the agent system.
A management operation interface having the same operation interface as the scriminator 81: an event distribution selection unit (ProxyMOEFD) 40 is provided in the network manager system 1.

Management operation interface: The event delivery selection unit (ProxyMOEFD) 40 analyzes an operation for managing the notification, and stores the event handler 20 in the network manager system and the event delivery selection unit (EFD) in the agent system. A process for setting a filtering condition of the notification and designating a management application for distributing the event is performed on 81. The value set in the event distribution selection unit (EFD) 81 in the agent system is the management operation interface (ProxyMO)
Is set to a value different from the received value.

The specific operation will be described below. Management operation interface: Event delivery selection unit (Proxy
MOEFD) 40 from the management application 14 and the management application 12 from the management object M
The warning notification generated from O1, MO2, MO3, MO4, and MO5 is distributed. The management application 13 has M
A setting is made to distribute the alarm notification generated from O2, MO3, and MO6.

Management operation interface: The event delivery selection unit (ProxyMOEFD) 40 analyzes the above setting, and transmits the data to the management application 12 and the management application 13 in the event handler 20. To set filtering conditions for data distribution. In the event distribution selection unit (EFD) 81 in the agent system, a setting is made to notify the management application of an alarm notification of the managed objects MO1 to MO6.

Thus, when the distribution management application is set in the event distribution selection unit (EFD) 81 in the agent system using the conventional operation interface, the distribution management application is required because it is different. , It is possible to reduce the communication volume between the network manager system and the agent system while reusing the management application created in the past and improve the performance. .

FIG. 12 is an explanatory diagram of the ninth embodiment of the present invention. 1 is a network manager system, 1
1, 12 are management applications; 111, 121 are integrated management information trees; 21, 22, 23 are agent operation interfaces (ProxyAgent);
2, 33 are agent systems, 311, 321, 3
31 is a management information tree in the agent system.

In the figure, a black circle indicates an application realizing object, a double circle indicates a pointer area, and a shaded circle indicates a management operation interface (ProxyM).
O), hatched circles indicate managed objects (MO),
A dotted frame indicates a virtual management information tree.

The complex management application in the network manager system includes a plurality of management application realization objects (MGO: ManagingObject).
ect), the management application includes a management application realization object (MGO) related to the management application and a management operation interface (Pro).
This is realized by a function call (message passing) with the object to be managed (MO) via xyMO).

The management application realizing object (MGO) and the management operation interface (ProxyM)
O), it is necessary to manage the mutual processing as a transaction, and in order to easily realize the transaction processing, the management method of the name of the object used in the transaction processing must be managed by the management operation interface (Pro
xyMO) and the management application realization object (MGO).

Therefore, an integrated management information tree (MIT) for integrated management of the names of the management application realizing object (MGO) and the object to be managed (MO).
Will be realized. However, when a plurality of management applications use one integrated management information tree (MIT), there is a possibility that an operation error or a bug accesses a management operation interface (ProxyMO) that should not be accessed.

Also, an integrated MI for each management application
In the case where T is realized and management operations are individually performed, names are added and deleted depending on generation and deletion of the management operation interface (ProxyMO). ) Is a redundant management operation interface (ProxyM
O) Name management operation occurs and the performance is reduced.

In the embodiment of the present invention, the name of the management operation interface (ProxyMO) is added or deleted for each of the agent systems 31 to 33 in accordance with the generation and deletion of the managed object (MO) in the agent system. Agent operation interface (Prox
yAgent) 21 to 23 are provided in the network manager system, and a management operation interface (Proxy)
MO), the management operation interface management information tree (ProxyMOMIT) of 211 to 231 and the management information tree (MIT) of the management application realization object (MGO) are separated, and the management operation interface (ProxyMO) required by the management application is separated. The management operation interface management information tree (ProxyMOMIT) that manages the name of the management application is pointed from the management information tree MIT of the management application realization object (MGO), thereby realizing the integrated MITs 111 and 121 for each management application.

As a result, the management operation interface (P
(roxyMO) management can be unified, and the management operation interface management information tree (Pro
xyMOMIT), it is possible to prevent an unnecessary management operation interface (ProxyMO) from being accessed from the management application, thereby preventing access to the wrong management target object (MO) due to misoperation or the like. Can be prevented, and the reliability of the system is improved.

[0103]

As described above, according to the present invention,
By executing a management operation consisting of a plurality of commands that must be operated as a transaction for an agent system that does not support transaction processing through a management operation interface (ProxyMO) generated when transaction processing is requested, This can be realized without increasing the memory in the network manager system.

A management operation interface (ProxyMO) generated before the management operation is executed or a management operation interface (ProxyM) with a temporary name is generated.
O) by changing the number of O) according to the notification of generation and deletion of the managed object (MO) from the agent system, the management operation interface (ProxyMO)
Memory area can be used efficiently, and performance can be improved. Also, by using the backup area for rollback processing as a data restoration memory when a cancel operation is performed, the cancel operation can be realized with a small amount of memory.

Further, by providing a function unit for converting a management operation interface name independent of the communication protocol into a management operation interface name dependent on the communication protocol, the management application can use a management operation interface name independent of the communication protocol. The management object can be accessed, and the reusability and development efficiency of the management application can be improved.

The management operation interface (Proxy)
By performing processing for deadlocks that rarely occur when setting the MO) by using a device other than the management application, the reusability and development efficiency of the management application can be improved.

Further, by providing the function of selecting and distributing event notifications to each management application in the network manager system, the amount of event notifications distributed from the agent system to the network manager system can be reduced.

In addition, each management application has only the management operation interface accessed by itself under the integrated management information tree under the name management of the management application, thereby reducing malfunctions and performing integrated name management with a small processing amount. It can be carried out.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is an explanatory diagram of the first embodiment of the present invention.

FIG. 3 is an explanatory diagram of a second embodiment of the present invention.

FIG. 4 is an explanatory diagram of a pseudonym management operation interface management information tree.

FIG. 5 is an explanatory diagram of a third embodiment of the present invention.

FIG. 6 is an explanatory diagram of a sixth embodiment of the present invention.

FIG. 7 is an explanatory diagram of a seventh embodiment of the present invention.

FIG. 8 is an explanatory diagram of first and second cases in which deadlock occurs.

FIG. 9 is a flowchart of a deadlock detection function.

FIG. 10 is a flowchart of a deadlock detection function.

FIG. 11 is an explanatory diagram of an eighth embodiment of the present invention.

FIG. 12 is an explanatory diagram of a ninth embodiment of the present invention.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 Network manager system 11-1n Management application 2 Management operation interface (ProxyMO) management part 21 Management operation interface management information tree (Pro
xyMOMIT) 22 Presence management operation interface (ProxyMO)
Management unit 23 Management operation interface (ProxyMO) generation and deletion unit 31-3m Management operation interface (ProxyM)
O) 31-1, 33-1 Backup area 4 SNMP communication protocol terminal of network manager system 5 CMIP communication protocol terminal of network manager system 6 SNMP communication protocol terminal of agent system 11 CMIP communication protocol terminal of agent system 8 , 12 agent execution control unit 81, 121 management information tree 91, 92, 131, 132, 13m managed object (MO) 101, 102, 141, 142, 14m managed entity

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁶ Identification symbol FI H04L 12/26 (72) Inventor Yuki Fujii 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited (72 ) Inventor Takafumi Nakajo 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited

Claims (9)

[Claims] 1. A network manager system for instructing an agent system, which is a managed system, to perform a management operation on a managed object. In the network manager system, a management operation interface corresponding to each managed object, and the management operation interface A transaction processing consisting of a plurality of management operations is performed for an agent system that has a lock processing unit for A network manager system that enables a managed object to be operated at the start of transaction processing or immediately before execution of a management operation. A management operation interface management unit that generates a part or all of the corresponding management operation interface, secures its memory area, and deletes it at the end of the transaction processing. After storing the backup data for rollback from the agent system once and storing it in the area,
A network manager system, comprising: a change operation unit for performing a change operation on a management target object. 2. A management operation interface with a temporary name is generated in advance as the management operation interface and its memory area is reserved, and the temporary name of the management operation interface is maintained only during the execution of transaction processing. A name change unit for renaming a part or all of a management operation interface corresponding to a management target object to be operated in transaction processing; and a backup data for rollback in the management operation interface having the temporary name. After reading the backup data for rollback from the agent system and storing it in the area,
The network manager system according to claim 1, further comprising: a change operation unit that performs a change operation on the management target object. 3. A method for naming the management operation interface according to a naming rule independent of a communication protocol,
2. A management operation interface name conversion unit for converting a name of a management operation interface given by a naming rule independent of the communication protocol into a name by a naming rule dependent on each communication protocol. Or the network manager system according to 2. 4. The management operation interface is generated before the management operation by the transaction processing is performed, or is given a temporary name, and is generated before the management operation by the transaction processing is performed. 2. The number of management operation interfaces to which a name is assigned is changed according to a generation or deletion notification of a managed object from an agent system.
The network manager system according to any one of claims 1 to 3. 5. An apparatus according to claim 1, further comprising an access frequency counting unit for counting the number of times the management operation interface accesses the management operation interface for each management operation interface, wherein the management operation interface having a large number of access times is always generated. The network manager system according to any one of claims 1 to 4, wherein 6. The management operation interface further includes a flag for setting a data change prohibition for an operation cancellation request generated after the transaction processing is completed, and the management operation interface continues until the flag is turned off. 6. The network manager system according to claim 1, wherein backup data for rollback is retained. 7. A deadlock detection function is provided in the network manager system, and when a transaction executed by a management application executes a lock process on a management operation interface, a lock process of another transaction causes the lock process to wait. If deadlock detection processing is performed and a deadlock occurs due to waiting for lock processing, the transaction including the locked lock processing is rolled back, and the transaction is terminated. When a lock is released and multiple other lock-waiting transactions attempt to acquire the lock, deadlock detection processing is performed for each lock. Transfer a lock to a transaction that attempts to acquire another lock, and roll back all transactions when a deadlock occurs in all cases. The network manager system according to any one of the above. 8. The management operation interface according to claim 1, further comprising: a management operation interface corresponding to an event distribution selection unit that controls distribution of event notifications in the agent system; and the management operation interface includes an event distribution selection unit. The network manager system according to any one of claims 1 to 7, further comprising a distribution control function of an event notification of a management application and an agent system in the manager system. 9. A management operation interface management information tree for managing a plurality of agent systems, management operation interface names corresponding to each agent system, a plurality of management applications, and a management application realization object for realizing each management application. A management application realization object management information tree for managing names, and an integrated management information tree obtained by changing the combination of the management application realization object management information tree and the management operation interface management information tree for each management application, 9. The method according to claim 1, wherein each management application puts only the management operation interface accessed by itself under the management of the name of the management application. Network manager system.