JP2003006067A - Program and device for supporting collection of management information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To collect management information from a managed device of a new specification by using the existing network management function. SOLUTION: A device 2 for supporting collection of management information acquires a management information acquisition request from a network managing device 1 (a step S1). Next, the device 2 for supporting collection of management information coverts the acquired management information acquisition request (a step S2) according to a first conversion rule preliminarily defined by being associated with the managed device at a destination of the acquired management information acquisition request and transmits it to the managed device at the destination (a step S3). In addition, the device 2 for supporting collection of management information acquires management information transmitted from any of a plurality of managed devices 3a, 3b, 3c., etc., (a step S4). Next, the device 2 for supporting collection of management information converts the acquired management information (a step S5) according to a second conversion rule preliminarily defined by being associated with a managed device at a transmitting origin of the acquired management information and transfers it to the network managing device 1 (a step S6).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management information collection support program and a management information collection support apparatus for supporting management information collection processing from devices on a network, and particularly to management information collection from a plurality of devices having different specifications. The present invention relates to a management information collection support program and a management information collection support device.

[0002]

2. Description of the Related Art With the progress of information and communication technology, the range of use of networks is expanding. When business using a network becomes common, high reliability is required for communication via the network.

Therefore, a network management system is used for centrally managing the states of the devices connected to the network. By using the network management system, it is possible to centrally manage the statuses of a large number of computers such as routers arranged at remote locations at one place.

Generally, a network management system is
A network management module (manager) on the managing side (network management device), a managed module (agent) on the managed side (managed device), and a management information base (MIB: Manageme) of the managed module.
nt Information Base). The network management module has grasped the state of the side to be managed by transmitting / receiving a message to / from the managed module and acquiring the management information value in the management information base.

By the way, in a large-scale network system, managed devices manufactured by different manufacturers are connected to the network. If the manufacturer of the managed device is different,
There will also be differences in the specifications of the managed modules and management information that are installed. The specifications of the managed modules and management information to be mounted are different depending on the model and the version of the same model even for the products of the same manufacturer.

Therefore, when implementing the network management module, the following has been done in order to deal with the managed modules having different specifications and the plurality of managed devices having management information.

The network management module was designed / developed according to the content of the management information that the managed module suggests to support. Contents of management information acquisition processing in the network management module in order to correctly acquire the management information value from the managed module in the network management module when the supported management information is changed due to standardization of management information, version upgrade of the managed module, etc. Had been changed.

The managed module may be implemented differently from the management information assumed by the network management module. In that case, the network management module discriminates the type of the managed module and executes the process according to the type.

The managed module at the initial stage of development is
It may operate differently from the definition of existing management information.
In this case, when the test for acquiring the management information value is executed in the network management module, a special process for the test is inserted into the network management module, or a simulator dedicated to the test is used.

[0010] The above-mentioned technique copes with a change in the specification of the managed module by changing the network management module. However, each managed module has various kinds of management information according to its type and version. Therefore, when the difference in management information of a plurality of managed modules is absorbed by one network management module, the processing in the network management module becomes complicated. Complicated processing is a factor that reduces the processing performance of the network management module.

In some cases, it may be difficult to modify the network management module. For example, when the network administrator who uses the network management module does not have the copyright of the program code of the network management module, or when the network management module should not be changed frequently from the viewpoint of maintaining reliability. .

Therefore, the following techniques have been proposed in order to deal with a change in specifications of the managed module without modifying the network management module. -If it is difficult to modify the network management module, install the management information conversion device inside each managed module or in front of each managed module. The network management module acquires the management information from the managed module by making these management information conversion devices communication partners. As an example of this, Japanese Patent Laid-Open No. 167636/1993
And Japanese Patent Laid-Open No. 7-250123.

Further, managed modules having the same function are grouped, and sub-managers for managing the same managed module in a bundle under the network management module are arranged for each group. The sub-manager acquires information from the subordinate managed module and passes it to the network management module. Japanese Patent Laid-Open No. 9-51347 discloses such an example.

[0014]

However, JP-A-5-1 is used.
When the conversion device is arranged in the managed module or in front of the managed module as in Japanese Patent No. 67636 or Japanese Patent Laid-Open No. 7-250123, the conversion device is required for the managed module.

Also, when installing a device corresponding to a sub-manager as in Japanese Patent Laid-Open No. 9-51347, a sub-manager corresponding to the type of the managed module is required.

As described above, if a plurality of converters and sub-managers are installed, the cost for network management increases. Moreover, when a device corresponding to the sub-manager is newly installed, the network management module has a mechanism for communicating with the sub-manager, a mechanism for requesting the sub-manager to obtain information from the managed module, and a result obtained by the sub-manager. It is necessary to incorporate a unique mechanism such as a mechanism for receiving. Therefore, changing the network management module requires work, and cannot be applied when it is difficult to change the network management module.

The present invention has been made in view of the above circumstances, and a management information collection support program and a management information collection support program capable of collecting management information from a managed device having a new specification by using an existing network management function. An object is to provide a management information collection support device.

[0018]

In order to solve the above problems, the present invention provides a management information collection support program as shown in FIG. The management information collection support program of the present invention is provided with a plurality of managed devices 3 via the network 4.
It is a program for supporting collection of management information by the network management device 1 connected to a, 3b, 3c, ....

The management information support program of the present invention acquires a management information acquisition request addressed to any of the plurality of managed devices 3a, 3b, 3c, ... From the network management device 1 to the computer (step S1), the acquired management information acquisition request is converted according to a first conversion rule defined in advance in association with the managed device that is the destination of the acquired management information acquisition request (step S2), and the converted management information is converted. An acquisition request is transmitted to the destination managed device (step S3), and a plurality of managed devices 3a, 3b, 3c, ...
The management information transmitted to the network management device 1 from any of the above is acquired (step S4), and according to the second conversion rule defined in advance in association with the managed device that is the transmission source of the acquired management information. , The acquired management information is converted (step S5), the converted management information is passed to the network management device (step S6), and the processing is executed.

As a result, the management information acquisition request output from the network management device 1 to any of the plurality of managed devices 3a, 3b, 3c, ... Is converted according to the destination managed device. After that, it is transmitted to the destination managed device. The management information output to the network management device 1 from any of the plurality of managed devices 3a, 3b, 3c, ... Is converted to the network management device 1 after being converted according to the managed device of the transmission source. Passed.

In order to solve the above problem, a plurality of managed devices 3a, 3b, 3c,
In the management information collection support device 2 for supporting the collection of management information by the network management device 1 connected to the network management device 1, any of the plurality of managed devices 3a, 3b, 3c, ... A request acquisition unit for acquiring a management information acquisition request addressed to or, and a request acquisition unit according to a first conversion rule defined in advance in association with the managed device that is the destination of the management information acquisition request acquired by the request acquisition unit. Request conversion means for converting the management information acquisition request acquired by the request acquisition means, acquisition request transmission means for transmitting the management information acquisition request converted by the request conversion means to the destination managed device, and a plurality of managed devices 3a, 3b, 3c, ..., Management information acquisition means for acquiring the management information transmitted to the network management device 1, and transmission of the management information acquired by the management information acquisition means. Management information converting means for converting the acquired management information and the management information converted by the management information converting means according to the second conversion rule defined in advance in association with the managed device A management information delivery support device 2 is provided, which is provided with a management information delivery means.

According to such a management information collection support device 2, the network management device 1 to the plurality of managed devices 3
The management information acquisition request output to any of a, 3b, 3c, ... Is converted according to the destination managed device, and then transmitted to the destination managed device. The management information output from any of the plurality of managed devices 3a, 3b, 3c, ... To the network management device 1 is converted to the managed device of the transmission source, and then converted to the network management device 1. Passed.

[0023]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the principle of the present invention. The management information collection support program of the present invention includes a plurality of managed devices 3a, 3b, 3c, ...
.. is a program for supporting the collection of management information by the network management device 1 connected to. The computer can be caused to function as the management information collection support device 2 by causing the computer to execute the management information collection support program of the present invention.

The management information collection support device 2 has a conversion rule 2
a is previously defined. The conversion rule 2a includes a conversion rule (first conversion rule) of a management information acquisition request addressed to any of the plurality of managed devices 3a, 3b, 3c ,.
A conversion rule (second conversion rule) of the management information output from the plurality of managed devices 3a, 3b, 3c, ... Is included.

The management information collection support device 2 acquires a management information acquisition request addressed to any of the plurality of managed devices 3a, 3b, 3c, ... From the network management device 1 according to the management information support program (step S1). next,
The management information collection support device 2 converts the acquired management information acquisition request according to a first conversion rule defined in advance in association with the managed device that is the destination of the acquired management information acquisition request (step S2). Then, the management information collection support device 2 transmits the converted management information acquisition request to the destination managed device (step S3).

Further, the management information collection support device 2 acquires the management information transmitted from any of the plurality of managed devices 3a, 3b, 3c, ... To the network management device 1 (step S4). Next, the management information collection support device 2
According to the second conversion rule defined in advance in association with the managed device that is the transmission source of the acquired management information,
The acquired management information is converted (step S5). Then, the management information collection support device 2 passes the converted management information to the network management device 1 (step S6).

As a result, the management information acquisition request output from the network management device 1 to any of the plurality of managed devices 3a, 3b, 3c, ... Is converted according to the destination managed device. After that, it is transmitted to the destination managed device. The management information output from any of the plurality of managed devices 3a, 3b, 3c, ... To the network management device 1 is converted to the managed device of the transmission source, and then converted to the network management device 1. Passed.

As described above, according to the present invention, the network management device 1 to the managed devices 3a, 3b, 3c, ...
Management information acquisition request addressed to the managed devices 3a, 3b, 3c,
... and the management information addressed to the network management device 1,
It is converted by the management information collection support device 2. Therefore, in the network management device 1, the managed devices 3a, 3a
It suffices to issue a management information acquisition request with b, 3c, ... That is, it is not necessary to mount a communication interface with the management information collection support device 2 on the network management device 1.

Moreover, the definition of the management information in the network management device 1 and the managed devices 3a, 3b, 3c ,.
If the conversion rule according to the difference from the definition of the management information in (3) is defined in the conversion rule 2a of the management information collection support device 2, the difference in the definition content can be absorbed by the management information collection support device 2. This is very simple because it does not involve complicated processing such as changing the program, and the frequent changes do not impair the reliability of network management.

Furthermore, the conversion rule is that the managed devices 3a, 3
Since they are managed in association with b, 3c, ..., The conversion rules corresponding to a plurality of management devices can be centrally managed by the management information collection support device 2. Here, if the address of the managed information on the network and the conversion rule are associated with each other, the network management device 1 and the managed devices 3a, 3b,
The conversion rule can be specified by the information of the destination and the source in the communication with the 3c, .... This eliminates the need for the network management device 1 to include special information for specifying the conversion rule in the management information acquisition request. That is, it is not necessary to change the processing content in the network management device 1.

With such a network management system, the devices on the network can be managed.
For example, by setting a large number of routers arranged on the network as managed devices, the state of the routers installed at remote locations can be managed at the center where the network management device is arranged.

The embodiment of the present invention will be specifically described below assuming that a managed device such as a router is managed in a center. In the following embodiments, the functions of the network management device 1 and the management information collection support device 2 are implemented as a network management module and a management information collection support module in one network management device, respectively.

FIG. 2 is a diagram showing a configuration example of the network management system. The network management system includes a network monitoring device 100, managed devices 200, 200.
a, 200b, ..., And terminal devices 21, 22, ...
・ Composed of Managed devices 200, 200a, 200
b, ... Are connected to the network monitoring device 100 via the network 10. Terminal devices 21 and 2
2, ... Are connected to the managed device 200 via the network 10a.

The network monitoring device 100 is arranged in a center for monitoring the network. The network monitoring device 100 includes managed devices 200, 200.
a, 200b, ... Collects the management information held in the managed devices 200, 200a, 200b ,.
The state of can be managed.

Managed devices 200, 200a, 200b,
Have a managed module and a management information base (MIB) that are individually designed. The managed devices 200, 200a, 200b, ... Include a dial-up router, a broadband access router, a remote router, and the like. Although not shown,
Each managed device 200a, 200 other than the managed device 200
Terminal devices are also connected to b, ... Via a network.

FIG. 3 is a diagram showing a hardware configuration example of the network monitoring device used in the embodiment of the present invention. The network monitoring device 100 includes a CPU (Central P
The entire apparatus is controlled by a rocessing unit) 101. The CPU 101 is connected to the RAM (R
An andom access memory 102, a hard disk drive (HDD) 103, a graphic processing device 104, an input interface 105, and a communication interface 106 are connected.

The RAM 102 temporarily stores at least a part of an OS (Operating System) program and an application program to be executed by the CPU 101. Further, the RAM 102 stores various data necessary for the processing by the CPU 101. HDD103 is O
S and application programs are stored.

A monitor 11 is connected to the graphic processing device 104. Graphic processor 104
Monitors the image according to the instruction from the CPU 101.
Display it on the 1st screen. A keyboard 12 and a mouse 13 are connected to the input interface 105.
The input interface 105 sends a signal sent from the keyboard 12 or the mouse 13 to the CP via the bus 107.
Send to U101.

The communication interface 106 is connected to the network 10. Communication interface 106
Transmits and receives data to and from other computers via the network 10.

With the above hardware configuration,
The processing function of this embodiment can be realized. Although the hardware configuration example of the network monitoring device 100 has been described with reference to FIG. 3, the managed devices 200, 200
The terminals a, 200b, ... And the terminal devices 21, 22 ,.

FIG. 4 is a block diagram showing a functional configuration example of the network management system according to the present embodiment.
In FIG. 4, among the functions of the network monitoring device 100 and the managed devices 200, 200a, 200b, ..., Only the functions related to network management are shown.

The network monitoring device 100 has a network management module (manager) 110 and a management information collection support module 120. The network management module 110 includes managed devices 200, 200.
The management information is collected from a, 200b, ... And the state of the managed devices 200, 200a, 200b ,. The network management module 110 collects management information, so that each managed device 200, 200a, 200
b, ..., A management information request message (management information acquisition request) is transmitted. Then, the network management module 110 receives response messages (including management information) from the managed devices 200, 200a, 200b, ... To the request message. The network management module 110 stores the management information value included in the received response message in the management module list 111.

Further, the network management module 110
Has a management module list 111. The management module list 111 includes identification information of managed modules (for example, managed devices 200, 200a, 200b,
The collected management information is stored in association with (address of ...).

The management information collection support module 120 is arranged between the network management module 110 and the network 10. That is, the network management module 110 and the managed devices 200, 200a, 200b,
The communication with the ... Through the network 10 is always relayed by the management information collection support module 120.

The management information collection support module 120 includes a policy database (DB: Data Base) 121, a request message converter 122, and a request message transmitter 12.
3, a response message receiving unit 124, and a response message converting unit 125.

In the policy DB 121, a conversion policy regarding management information (management information conversion policy) is defined. The management information conversion policy includes conversion rules for request messages and response messages, and arithmetic expressions for converting management information values.

The request message converter 122 intercepts the management information acquisition request message transmitted by the network management module 110. Then, the request message conversion unit 122 uses the policy DB 12
The management information conversion policy defined in 1 is searched using the address of the managed device that is the destination of the request message as a key.

The request message conversion unit 122 determines whether or not conversion processing of the intercepted request message is necessary based on the detected management information conversion policy.
If conversion processing is required, the request message conversion unit 12
2 converts the management information identifier in the request message according to the management information conversion policy and creates a new request message. Then, the request message conversion unit 122 passes the created request message to the request message transmission unit 123.

If the conversion process is not required, the request message conversion unit 122 does not perform the conversion process of the request message and sends the request message to the request message transmission unit 12
Pass to 3.

The request message transmitting section 123 receives the request message received from the request message converting section 122,
The request message is transmitted to the managed device designated as the destination.

The response message receiving unit 124 intercepts the response message output from any of the managed devices 200, 200a, 200b, ... To the network management module 110 in the network monitoring device 100. The response message receiving unit 124 passes the intercepted response message to the response message converting unit 125.

The response message conversion unit 125 searches the management information conversion policy defined in the policy DB 121 using the address of the managed device which is the transmission source of the response message as a key. Then, the response message conversion unit 125
It is determined whether the management information identifier in the response message needs to be converted and whether the management information value has been converted (arithmetic processing).

When the management information identifier needs to be converted, the response message converter 125 converts the management information identifier according to the management information conversion policy defined in the policy DB 121 (reverse conversion to conversion of request message).
I do. When the management information value needs to be converted, the response message conversion unit 125 performs the management information value calculation processing according to the calculation formula defined in the policy DB 121 to convert the management information value.

The response message converter 125 converts the management information identifier and the management information value or the response message after converting either the management information identifier or the management information value into the network management module 110. Pass to.

When it is not necessary to convert the management information identifier and the management information value, the response message conversion unit 125 directly manages the response message sent from the managed device without performing the conversion process. Pass to module 110.

The managed device 200 has a management information base (M
IB) 210 and managed module (agent) 22
It has 0 and. The management information base 210 is status information regarding the status of the managed device 200 and the like. For example, it is information such as the amount of data transferred via the managed device 200 and the congestion status of the network connected to the router.

The managed module 220 searches the management information base 210 in response to the request from the network management module 110, and extracts the management information corresponding to the request. Then, the managed module 220 transmits the extracted management information to the network management module 110.

Managed device 2 other than managed device 200
00a, 200b, ... Have the same function as the managed device 200. FIG. 5 is a diagram showing an example of the data structure of the management module list. The management module list 111 can be represented by, for example, a tabular data structure as shown in FIG.

In the example of FIG. 5, the management module list 11
1 includes columns for managed module, management information identifier, and management information value. In the managed module column, the identification information of the managed device in which the managed module to be managed is mounted is registered. For example,
IP (Internet Protocol) is used as identification information for each router.
Address is used. In the example of FIG. 5, “aaa.aaa.aaa.aaa” and “ccc.ccc.ccc.c” are displayed in the managed module field.
"cc", "ddd.ddd.ddd.ddd", ..., "fff.fff.fff.f
The address "ff" is registered.

In the management information identifier column, the identifier of the management information to be acquired from the managed module (management information identifier)
Is registered in association with the identification information of the managed module. The management information identifier set in the management module list 111 is defined in the network monitoring device 100.

In the example of FIG. 5, "management information identifier # 1" is registered in association with "aaa.aaa.aaa.aaa".
Corresponding to "ccc.ccc.ccc.ccc", "Management information identifier #
3 ”is registered. “Management information identifier # 4” is registered in association with “ddd.ddd.ddd.ddd”. `` Fff.
“Management information identifier # 1” is registered in association with “fff.fff.fff”.

The management information value collected from the managed module is registered in the management information value column in association with the identification information of the managed module. In the example of FIG. 5, “aaa.aa
“120 (unit: number of sheets /
Minutes) ”is registered. “220” is registered in association with “ccc.ccc.ccc.ccc”. `` Ddd.ddd.ddd.dd
“360” is registered in association with “d”. `` Fff.f
“180” is registered in association with “ff.fff.fff”.

FIG. 6 is a diagram showing an example of the data structure of the policy DB. The policy DB 121 can be represented by, for example, a tabular data structure as shown in FIG. In the example of FIG. 6, the policy DB 121 includes columns for a conversion target address, a pre-conversion management information identifier, a post-conversion management information identifier, and an arithmetic expression. Policy DB
A conversion target address in 121, a management information identifier before conversion,
The management information conversion policy is a set of information registered in association with each other in the fields of the converted management information identifier and the arithmetic expression.

An address (for example, an IP address) corresponding to a managed device in which a managed module that should convert a request message or a response message is mounted is registered in the conversion target address column. In the example of FIG. 6, “aaa.aaa.aaa.aaa” and “bbb.b” are entered in the conversion target address column.
"bb.bbb.bbb", "ccc.ccc.ccc.ccc", "ddd.ddd.ddd.d
"dd" and "eee.eee.eee.eee" are registered.

In the pre-conversion management information identifier field, the management information identifier included in the request message is registered in association with the conversion target address. In the example of FIG. 6, “aaa.aa
“Management information identifier # 1” is registered in association with “a.aaa.aaa”. “Management information identifier # 2” is registered in association with “bbb.bbb.bbb.bbb”. `` Ccc.ccc.ccc.
"Management information identifier # 3" is registered in association with "ccc". “Management information identifier # 4” is registered in association with “ddd.ddd.ddd.ddd”. "Eee.eee.eee.eee"
The “management information identifier # 5” is registered in association with.

In the post-conversion management information identifier column, the management information identifier after conversion when the management information identifier registered in the pre-conversion management information identifier is converted is registered in association with the pre-conversion management information identifier. ing. In the example of FIG. 6, “management information identifier # 1” is associated with “management information identifier # 1”.
“A” is registered. “Management information identifier # 2a” is registered in association with “management information identifier # 2”.
“Management information identifier # 3a-1” and “management information identifier # 3a-2” are registered in association with “management information identifier # 3”. "Management information identifier # 4a" is registered in association with "management information identifier # 4". "Management information identifier # 5a" is registered in association with "management information identifier # 5".

In the example of FIG. 6, a plurality of post-conversion management information identifiers “management information identifier # 3a-1” and “management information identifier” are provided for one pre-conversion management information identifier “management information identifier # 3”. # 3a-2 ”is associated. In this case, two management information values corresponding to "management information identifier # 3a-1" and "management information identifier # 3a-2" are added to the request message specifying "management information identifier # 3".
It is meant to be returned in the response message.

In the arithmetic expression column, an arithmetic expression for converting the management information value included in the response message is registered in association with the converted management information identifier. In the example of FIG.
In association with “management information identifier # 1a”, “calculation formula # 1
(Management information identifier # 1a × 60) ”is registered.
Corresponding to "management information identifier # 2a", "N / A (Not A
pplicable) ”is registered. "Management information identifier # 3
"Arithmetic formula # 3" is registered in association with "a-1" and "management information identifier # 3a-2". "Calculation formula # 4" is registered in association with "management information identifier # 4a". In association with “management information identifier # 5a”, “calculation formula #
5 ”is registered.

The contents of the policy DB 121 are the contents of the keyboard 12 and mouse 13 of the network monitoring device 100.
It can be changed by inputting an operation using, for example.

FIG. 7 is a diagram showing an example of the data structure of the management information base. The management information base 210 can be represented by, for example, a tabular data structure as shown in FIG. 7. The example of FIG. 7 is an example of the management information base 210 provided in the managed device 200.

In the example of FIG. 7, the management information base 210 has a management information identifier, a data type, an access mode,
And a column of management information value is provided. The identifier defined for the management information accumulated in the managed device 200 is registered in the management information identifier column. The management information identifier registered in the management information base 210 is defined in the managed device 200.

In the example of FIG. 7, "management information identifier # 1a" and "management information identifier # 1a-" are entered in the management information identifier column.
1 "," management information identifier # 1a-2 "," management information identifier # 1a-3 ", ...," Management information identifier # 1a-1 "
"50" is registered.

In the data type column, the data type (numerical value, character string, date and time, etc.) of the stored management information is registered in association with the management information identifier. In the example of FIG. 6, “data type A” is registered in association with “management information identifier # 1a”. "Management information identifier # 1a-
“Data type B” is registered in association with “1”. "Data type A" is registered in association with "management information identifier # 1a-2". "Management information identifier # 1
“Data type C” is registered in association with “a-3”. "Data type B" is registered in association with "management information identifier # 1a-150".

In the access mode column, the contents of access restrictions on the management information from other devices are set in association with the management information identifier. Access modes include "read-only", "read-write", and "write-onl".
y ”,“ non-accessible ”, etc.

When the access mode is "read-only", the management information can be read but not written. When the access mode is "read-write", the management information can be read or written. When the access mode is "write-only", the management information cannot be read but can be written. When the access mode is "non-accessible", the management information cannot be read or written.

In the example of FIG. 7, "management information identifier # 1a"
The access mode of is "read-only". The access mode of "management information identifier # 1a-1" is "read-write"
Is. The access mode of "management information identifier # 1a-2" is "write-only". "Management information identifier # 1a-
The access mode of "3" is "read-write". The access mode of "management information identifier # 1a-150" is "non-
accessible ”.

In the management information value column, management information is registered in association with the management information identifier. In the example of FIG.
"Management information value ##" is associated with "management information identifier # 1a".
1a (unit: number of sheets / second) ”is registered. "Management information value # 1a-1" is associated with "management information identifier # 1a-1".
-1 "is registered. "Management information identifier # 1a-
“Management information value # 1a-2” is registered in association with “2”. "Management information value # 1a-3" is registered in association with "management information identifier # 1a-3". In association with "management information identifier # 1a-150", "management information value #
1a-150 ”is registered.

Next, the processing in the network management system having the above configuration will be described. First, the network management module 110 transmits a request message to the managed module 220 registered in the management module list 111 at an arbitrary timing.
The network management module 110 specifies the address of the managed device 200 in which the managed module 220 is mounted, as the destination of the request message. Also, the network management module 110 specifies the management information specified by the request message by the management information identifier.

The request message transmitted from the network management module 110 to the managed device 200 is intercepted by the management information collection support module 120. The intercepted request message is transferred to the request message conversion unit 12 of the management information collection support module 120.
The necessity of conversion is determined by 2. If conversion is necessary, the request message conversion unit 122 causes the policy D
The management information identifier is converted according to the management information conversion policy registered in B121, and a new request message is generated.

After that, the request message that does not need to be converted or the converted request message is converted into the request message transmitting unit 1.
23 allows the managed module 22 of the managed device 200 to be managed.
Passed to 0.

Then, by the managed module 220,
The management information value corresponding to the management information identifier included in the request message is extracted from the management information base 210. Then, a response message including the extracted management information value and management information identifier is transmitted from the managed module 220 to the network management module 110.

The response message is intercepted by the response message receiving section 124 of the management information collection support module 120. The response message converter 125 of the management information collection support module 120 determines whether or not the intercepted response message needs to be converted. When the conversion is required, the response message conversion unit 125 converts the management information identifier and / or the management information value according to the management information conversion policy registered in the policy DB 121, and generates a new response message. To be done.

Then, the response message that does not require conversion or the response message after conversion is the response message conversion unit 1
25 to the network management module 110. The process in the management information collection support module 120 will be described below with reference to FIGS. 8 and 9.

FIG. 8 is a flow chart showing the conversion processing of the request message. This process is a process executed by the management information collection support module 120. The processing illustrated in FIG. 8 will be described below in the order of step numbers with reference to the functional configuration illustrated in FIG.

[Step S11] The request message conversion unit 122 determines that the destination address of the request message transmitted by the network management module 110 is the policy DB 12
If it is registered in the conversion target address field of 1,
Intercept the request message.

[Step S12] The request message conversion unit 122 determines the destination managed device based on the destination address included in the request message. That is, the conversion address of the request message is specified by the destination address.

[Step S13] The request message converter 122 determines whether the management information identifier needs to be converted. Whether the conversion is necessary or not is determined by the combination of the destination address and the management information identifier included in the request message when the policy DB 121
It can be determined by whether or not it is registered in the fields of the conversion target address and the management information identifier before conversion. The set of the address and the management information identifier is the policy DB 121.
If it is registered in, it is determined that the management information identifier needs to be converted. The combination of the address and the management information identifier is
If it is not registered in the policy DB 121, it is determined that conversion of the management information identifier is unnecessary.

If it is determined that the management information identifier needs to be converted, the process proceeds to step S14. If it is determined that the management information identifier conversion is unnecessary, the process proceeds to step S15.

[Step S14] The request message converter 122 converts the management information identifier in the request message according to the management information conversion policy registered in the policy DB 121. That is, in the management information conversion policy, the management information identifier included in the request message is
Change to the management information identifier registered in the post-conversion management information identifier field.

[Step S15] The request message transmitting unit 123 receives the request message from the request message converting unit 122 and transmits the request message to the managed device corresponding to the destination address included in the request message.

In this way, the management information identifier in the request message is converted according to the management information conversion policy. FIG. 9 is a flowchart showing the conversion processing of the response message. This process is a process executed by the management information collection support module 120. Below, FIG.
Will be described in order of step number with reference to the functional configuration shown in FIG.

[Step S21] If the sender address of the reply message output from the managed module 220 to the network management module 110 is registered in the conversion target address column of the policy DB 121, the reply message receiving section 124 Intercepts the response message.

[Step S22] The response message conversion unit 125 receives the response message from the response message reception unit 124, and determines the managed module based on the address of the transmission source of the response message. That is, the conversion rule of the response message is specified by the source address.

[Step S23] The response message converter 125 determines whether or not the calculation of the management information value is necessary.
Whether or not the operation is necessary is determined by the fact that the management information conversion policy corresponding to the combination of the transmission source address and the management information identifier included in the response message is registered in the policy DB 121, and the operation information is expressed by the expression. Can be determined by whether or not is registered.

When an arithmetic expression is registered in the management information conversion policy corresponding to the response message, it is determined that the arithmetic expression needs to be converted. When the arithmetic expression is not registered, it is determined that the conversion of the arithmetic expression is unnecessary.

If it is determined that the arithmetic expression needs to be converted, the process proceeds to step S24. If it is determined that conversion of the arithmetic expression is unnecessary, the process proceeds to step S25.

[Step S24] The response message conversion section 125 calculates the management information value according to the calculation formula set in the management information conversion policy corresponding to the response message.

[Step S25] The response message converter 125 determines whether or not the reverse conversion of the management information identifier is necessary. Whether the conversion is necessary or not is determined by the combination of the address of the transmission source and the management information identifier included in the response message in the policy DB1.
It can be determined by whether or not it is registered in the fields of the conversion target address 21 and the management information identifier after conversion 21.

When the combination of the address and the management information identifier is registered in the policy DB 121, it is determined that the management information identifier needs to be converted. When the set of the address and the management information identifier is not registered in the policy DB 121, it is determined that the conversion of the management information identifier is unnecessary.

If it is determined that the management information identifier needs to be converted, the process proceeds to step S26. If it is determined that the management information identifier conversion is unnecessary, the process proceeds to step S27.

[Step S26] The response message conversion unit 125 reversely converts the management information identifier in the response message according to the management information conversion policy corresponding to the response message. That is, the management information identifier of the response message is converted into the pre-conversion management information identifier set in the management information conversion policy corresponding to the response message.

[Step S27] The response message converter 125 returns the response message to the network management module 110. As described above, the managed device 2
Even if the management information identifier of the management information managed in 00 is different from the management information identifier defined in the network monitoring device 100, the network management module 110 recognizes the management information value without being aware of the difference. Can be obtained.

Furthermore, the unit of the management information managed by the managed device 200 is the network monitoring device 10.
Even if the unit of management information defined in 0 is different, the management information value is converted by an appropriate arithmetic expression so that the network management module 110 acquires the management information value without being aware of the unit difference. You can

Next, a specific example of management information collection processing will be described. For example, consider a case where a management information value corresponding to “management information identifier # 1” is acquired from the managed device 200.

As shown in FIG. 5, the management module list 1 managed by the network management module 110
In item 11, there is an item of "management information identifier # 1". On the other hand, as shown in FIG. 7, the management information base 210 of the managed device 200 does not have the item “management information identifier 1”, but has the item “management information identifier # 1a” instead.

The unit of the management information value of the "management information identifier" registered in the management module list 111 is
The number of sheets / minute. On the other hand, the unit of the management information of “management information identifier # 1a” registered in the management information base 210 is the number of sheets / second. That is, the units of the management information value are different.

Therefore, as shown in FIG. 6, the network administrator sets the conversion target address “aaa.aaa.aaa.aaa” (address of the managed device 200) and the pre-conversion management information in the policy DB 121. Identifier "Management information identifier #
1 ", converted management information identifier" management information identifier # 1 "
a ”and the management information conversion policy configured by the arithmetic expression“ management information identifier # 1a × 60 ”.

Then, at a predetermined timing, the network management module 110 causes the managed module 220 of the managed device 200 to acquire the management information value corresponding to the “management information identifier # 1” from the managed device 200. In response, a request message specifying "management information identifier # 1" is transmitted.

FIG. 10 is a diagram showing an example of delivery of a management information acquisition request message in the present embodiment. First,
The request message 41 is output from the network management module 110 to the managed module 220 as a destination.

In the example of FIG. 10, the request message 41 includes the address "aaa." Which indicates the managed module of the managed device 200 mounting the managed module 220 of the destination.
aaa.aaa.aaa "and the management information identifier" management information identifier # 1 "corresponding to the management information to be acquired.

The request message 41 is intercepted by the management information collection support module 120. Then, in the management information collection support module 120, the management information identifier of the request message 41 is converted according to the management information conversion policy registered in the policy DB 121.

As shown in FIG. 6, the address “aaa.aaa.aaa.aaa” of the managed module is registered in the conversion target address of the policy DB 121. Also, the pre-conversion management information identifier corresponding to the conversion target address "aaa.aaa.aaa.aaa" is "management information identifier # 1". This allows
It can be seen that the management information identifier of the request message 41 is the conversion target.

Therefore, the management information collection support module 12
0, the management information identifiers that specify the management information to be acquired are from “management information identifier # 1” to “management information identifier #
1a ”and a new request message 42 is generated.

In the generated request message 42, the managed device 2 mounting the managed module 220 of the destination is installed.
00 address “aaa.aaa.aaa.aaa” and the management information identifier “management information identifier # 1” corresponding to the management information to be acquired.
a ”is included.

The generated request message 42 is passed to the managed module 220. Managed module 220
Is included in the request message 42.
Using “1a” as a search key, the management information base 210 managed by itself is searched. As a result, the management information base 21
The management information value set in the “management information identifier # 1a” in 0 is extracted. Here, it is assumed that the "management information value # 1" corresponding to the "management information identifier # 1a" is 2 (number of sheets / second).

Next, the process of transmitting the response message will be described. FIG. 11 is a diagram showing an example of delivery of a management information acquisition response message in the present embodiment. FIG. 11 shows an example of a response message to the request message 42 shown in FIG.

The managed module 220 acquires the management information value “2” associated with the “management information identifier # 1a” shown in the request message 42 from the management information base 210 and generates the response message 51. . The response message 51 includes the address “aaa.aaa.aaa.aa” indicating the sender.
“A”, the management information identifier “management information identifier # 1a”, and the management information value “2” are included.

The managed module 220 sends the generated response message 51 to the network management module 110. Then, the response message 51 is intercepted by the management information collection support module 120. Then, in the management information collection support module 120, the response message 51 is converted according to the management information conversion policy registered in the policy DB 121.

As shown in FIG. 6, the address "aaa.aaa.aaa.aaa" is registered in the policy DB 121 as the conversion target address. Also, the conversion target address `` aaa.aaa.
The converted management information identifier corresponding to "aaa.aaa" is "management information identifier # 1a". In addition, the address "aaa.aaa.aa
a.aaa ", converted management information identifier" management information identifier # 1 "
Calculation formula # 1 is registered in association with “a”. As a result, it can be seen that the management information identifier of the response message 51 is the conversion target and the management information value needs to be converted.

Therefore, the management information collection support module 12
0, the management information value of the response message 51 is converted according to the management information conversion policy arithmetic expression “management information identifier # 1a (management information value corresponding to the management information identifier # 1a) × 60”, and the response message 52 is generated. To be done.

The response message 52 is the response message 5
Only the management information value is different from 1. In the example of FIG. 11, the management information value of the response message 52 is 120 (2 ×
60).

Further, the management information collection support module 12
0, the management information identifiers of the response message 52 are “management information identifier # 1a” to “management information identifier # 1”.
Is converted to. As a result, a new response message 53 having the converted management information identifier and management information value is generated.

The response message 53 includes the address “aaa.aaa.aaa.aaa” indicating the sender, the management information identifier “management information identifier # 1”, and the management information value “120”.

By displaying the management information collected in this way on the monitor 11 of the network monitoring device 100, the network administrator can manage the plurality of managed devices 200.
It is possible to grasp the states of a, 200b, 200c, ....

FIG. 12 is a diagram showing an example of the monitoring screen of the network monitoring device. As shown in FIG. 12, a plurality of status display screens 61 to 64 are displayed on the monitoring screen 60. Items such as monitoring targets and management information identifiers are displayed on each of the status display screens 61 to 64. The monitoring target is
The address of the managed device is displayed. In the management information identifier, the management information value sent from the managed device according to the management information identifier is displayed.

As described above, even if the definition of the management information in the managed devices 200a, 200b, 200c, ... Is changed due to the standardization of the management information and the version upgrade of the managed module, the management information collection support is provided. The module 120 can intercept the request message and the response message to absorb the difference in the management information. As a result, the network management module 1 can be used without changing the processing in the network management module 110.
It becomes possible for the network management module 110 to collect management information having a definition different from that of 10.

As a result, the maintenance work for managing the network is reduced. That is, according to the present embodiment, when the definition of the management information in the managed device 200 is changed, it is only necessary to register a new management information conversion policy in the policy DB 121. Registration of the management information conversion policy in the policy DB 121 can be easily performed using the editing function of the network monitoring device 100.

Further, although the management information value itself has the same meaning as in a multi-vendor network environment,
Even when there are a plurality of managed devices having management information having different management information definitions (definition of management information identifiers), the managed devices 200a, 200b, 200c, ...・
・ It is possible to acquire management information of common meaning from.
Therefore, it is possible to easily cope with the addition of the managed device to the network.

When the managed device is in the early stage of development, the managed module 220 of the managed device may operate differently from the contents defined in advance.
In this case, by defining a conversion rule for absorbing the malfunction in the policy DB 121, the managed module 220 can be camouflaged to the network management module 110 as if the managed module 220 is operating normally.

As a result, the management information collection test of the network management module 110 can be performed without waiting for the completion of the managed device 200. Moreover, complicated work such as mounting a special process for testing the managed module 220 in the development stage in the network management module 110 is unnecessary. As a result, it is possible to test the cooperation between the managed module 220 and the network management module 110 from an early stage of development, and it is possible to improve work efficiency and reliability.

Further, the network management module 110
When the simulator of the managed device 200 is used for the management information collection test of 1., the management information returned from the simulator is all dummy values. However, if the present embodiment is applied, only management information that is not installed in time can be used as a dummy value, and other management information can use raw data. Therefore, it is possible to correctly test the already implemented functions.

It should be noted that, in order to return a dummy value to the request message from the network management module 110 using this embodiment, the management information collection support module 12
In 0, the management information identifier of the request message is converted by the managed module 220 of the managed device 200 into an existing management information identifier. Then, the existing management information identifier included in the response message from the managed module 220 of the managed device 200 is converted into the management information identifier included in the request message by the management information collection support module 120.

The management information value included in the response message may be passed to the network management module 110 without being converted, or the management information collection support module 120 may use a constant value (dummy value) or a value based on an arithmetic expression. It may be passed to the network management module 110 after being converted to.

Further, in this embodiment, the management information conversion rule (management information conversion policy) is managed in association with the identification information (address on the network) of the managed device, thereby managing a plurality of managed devices. The management information conversion rule is managed by one management information collection support module. As a result, it is not necessary to install a plurality of management information conversion devices for each managed device or each managed device type, and it is possible to reduce costs.

By the way, in the above example, the management information collection support module 1 is installed in the device (network monitoring device 100) in which the network management module 110 is installed.
Although 20 is installed, the network management module 110 and the management information collection support module 120 can be installed in separate devices.

FIG. 13 is a diagram showing a modification of the network management system. In the example of FIG. 13, the network management device 100a mounted with the network management module
And the management information collection support device 100b in which the management information collection support module is mounted are separately provided.

The network management device 100a is connected to the management information collection support device 100b. The management information collection support device 100b has a wide area network 81.
Alternatively, it is connected to a plurality of managed devices 71 to 74 via a network 82 in the premises.

According to the network management system having such a configuration, the request message output from the network management device 100a to any of the managed devices 71 to 74 always relays to the management information collection support device 100b. Therefore, the management information collection support device 100b can intercept the request message and convert the management information identifier. Similarly, the managed devices 71 to 71
Since 74 is also relayed by the management information collection support device 100b, in the management information collection support device 100b,
The response message can be intercepted and the management information identifier and the management information value can be converted.

In the example of FIG. 13, the request message and the response message are physically the management information collection support device 1.
Although the network is constructed to be relayed by 00b, the request message and the response message may be relayed by the management information collection support device 100b depending on the setting of the communication protocol.

The above processing functions can be realized by a computer. In that case, a program (network management module, management information collection support module, managed module) describing the processing contents of the functions that the network management apparatus, the management information collection support apparatus, and the managed apparatus should have is provided. The computer executes the program in response to an operation input or the like. This allows
The processing functions described above are realized on a computer.

The program describing the processing contents can be recorded in a computer-readable recording medium. Computer-readable recording media include magnetic recording devices, optical disks, magneto-optical recording media, semiconductor memories, and the like. The magnetic recording device includes a hard disk device (HDD), a flexible disk (FD), a magnetic tape, and the like. DVD (Digital
Versatile Disc), DVD-RAM (Random Access Mem)
ory), CD-ROM (Compact Disc Read Only Memory),
There are CD-R (Recordable) / RW (ReWritable).
Magneto-optical recording media include MO (Magneto-Optical disc) and the like.

In order to put the program into the market, for example, a DVD or a CD-ROM in which the program is recorded
Portable recording media such as. It is also possible to store the program in the storage device of the server computer and transfer the program from the server computer to another computer via the network.

The computer that executes the program stores the program recorded in, for example, a portable recording medium in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program.

(Supplementary Note 1) In a management information collection support program for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, Management information acquisition request addressed to any one of the managed devices, and the acquired management information according to a first conversion rule defined in advance in association with the managed device that is the destination of the acquired management information acquisition request. Converts the information acquisition request, transmits the converted management information acquisition request to the destination managed device, and acquires the management information transmitted to the network management device from any of the plurality of managed devices. , According to a second conversion rule that is defined in advance in association with the managed device that is the sender of the acquired management information The converted management information is converted, and the converted management information is passed to the network management device,
A management information collection support program characterized by executing processing.

(Supplementary Note 2) The first conversion rule is defined in association with an address on the network of any of the plurality of managed devices, and when converting the management information acquisition request, The management information collection support program according to appendix 1, wherein the first conversion rule is specified by the destination address of the management information acquisition request.

(Supplementary Note 3) The second conversion rule is defined in association with an address on the network of one of the plurality of managed devices, and the management information is converted when the management information is converted. Depending on the address of the sender of the information,
Appendix 1 characterized in that the second conversion rule is specified
Management information collection support program described.

(Supplementary Note 4) In the first conversion rule, the first management information identifier defined by the network management device is converted into the second management information identifier defined by the managed device. Conversion rule is defined, and when converting the management information acquisition request, the first management information identifier included in the management information acquisition request is converted into the second management information according to the first conversion rule. The management information collection support program described in appendix 1, wherein the management information collection support program converts the information identifier.

(Supplementary Note 5) The second conversion rule defines that the second management information identifier is converted by the reverse conversion of the first conversion rule. In this case, according to the second conversion rule, the second management information identifier given to the management information is added to the first management information.
The management information collection support program described in appendix 4, wherein the management information collection support program is converted into the management information identifier.

(Supplementary Note 6) An arithmetic expression for converting the management information acquired as a numerical value is defined in the second conversion rule, and when converting the management information, the second conversion rule is defined. The management information collection support program according to appendix 1, wherein a calculation is performed according to the calculation formula defined in the conversion rule, and the value of the management information is replaced with the result of the calculation.

(Supplementary Note 7) In a management information collection support device for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, the plurality of managed devices are managed by the network management device. A request acquisition unit that acquires a management information acquisition request addressed to any one of the devices, and a first conversion rule defined in advance in association with the managed device that is the destination of the management information acquisition request acquired by the request acquisition unit. And a request conversion unit that converts the management information acquisition request acquired by the request acquisition unit, and an acquisition request transmission unit that transmits the management information acquisition request converted by the request conversion unit to the destination managed device. Management information acquisition means for acquiring management information transmitted to the network management device from any of the plurality of managed devices, Management information conversion means for converting the acquired management information according to a second conversion rule defined in advance in association with the managed device that is the transmission source of the management information acquired by the management information acquisition means; Management information delivery means for delivering the management information converted by the information conversion means to the network management device.

(Supplementary Note 8) The first conversion rule is defined in association with an address on the network of any one of the plurality of managed devices, and the request conversion means is provided with the management information acquisition request. Depending on the destination address,
Supplementary Note 7 characterized by specifying the first conversion rule
Management information collection support device described.

(Supplementary Note 9) The second conversion rule is defined in association with an address on the network of any one of the plurality of managed devices, and the request conversion means is a source of the management information. 8. The management information collection support device according to appendix 7, wherein the second conversion rule is specified by the address of.

(Supplementary Note 10) In the first conversion rule,
A conversion rule for converting the first management information identifier defined by the network management device into the second management information identifier defined by the managed device is defined, and the request conversion means includes the 8. The management information collection support apparatus according to appendix 7, wherein the first management information identifier included in the management information acquisition request is converted into the second management information identifier according to a first conversion rule.

(Supplementary Note 11) The second conversion rule includes:
It is defined that the second management information identifier is converted by the reverse conversion of the first conversion rule, and the management information conversion means is assigned to the management information according to the second conversion rule. 11. The management information collection support device according to appendix 10, wherein the second management information identifier is converted into the first management information identifier.

(Supplementary Note 12) The second conversion rule includes:
An arithmetic expression for converting the management information acquired as a numerical value is defined, and the management information conversion means performs an operation according to the arithmetic expression defined in the second conversion rule to obtain the management information. The management information collection support device according to appendix 7, wherein the value is replaced with the result of the calculation.

(Supplementary Note 13) In a management information collection support method for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, the plurality of managed devices are managed by the network management device. A management information acquisition request for any one of the devices is acquired, and the management information acquisition request is acquired according to a first conversion rule that is defined in advance in association with the managed device that is the destination of the acquired management information acquisition request And the converted management information acquisition request is transmitted to the destination managed device, and the management information transmitted to the network management device from any of the plurality of managed devices is acquired and acquired. The acquired management information is modified according to a second conversion rule that is defined in advance in association with the managed device that is the sender of the management information. The management information collection support method is characterized in that the converted management information is transferred to the network management device.

(Supplementary Note 14) In a computer-readable recording medium recording a management information collection support program for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, A computer that acquires a management information acquisition request addressed to any of the plurality of managed devices from the network management device, and that is defined in advance in association with the managed device that is the destination of the acquired management information acquisition request; According to the conversion rule No. 1, the acquired management information acquisition request is converted, the converted management information acquisition request is transmitted to the destination managed device, and the network management device is transmitted from any one of the plurality of managed devices. The management information transmitted to the management device is acquired and associated with the managed device that is the transmission source of the acquired management information. Converting the acquired management information according to a second conversion rule that is defined in advance, and passing the converted management information to the network management device;
A recording medium characterized by causing a process to be executed.

[0158]

As described above, according to the present invention, the management information acquisition request output from the network management device to any of the plurality of managed devices is converted by the conversion rule according to the destination managed device. Then, the management information output from any of the plurality of managed devices to the network management device,
The conversion is performed according to the conversion rule according to the managed device of the transmission source. Therefore, it is possible to collect the management information from the managed device having the management information defined differently from the network management device while keeping the function of the existing network management device.

[Brief description of drawings]

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

FIG. 2 is a diagram showing a configuration example of a network management system.

FIG. 3 is a diagram showing a hardware configuration example of a network monitoring device used in the embodiment of the present invention.

FIG. 4 is a block diagram showing a functional configuration example of a network management system according to the present embodiment.

FIG. 5 is a diagram showing an example of a data structure of a management module list.

FIG. 6 is a diagram showing an example of a data structure of a policy DB.

FIG. 7 is a diagram showing an example of a data structure of a management information base.

FIG. 8 is a flowchart showing a request message conversion process.

FIG. 9 is a flowchart showing a conversion process of a response message.

FIG. 10 is a diagram showing an example of delivery of a management information acquisition request message in the present embodiment.

FIG. 11 is a diagram showing an example of delivery of a response message for management information acquisition in the present embodiment.

FIG. 12 is a diagram showing an example of a monitoring screen of a network monitoring device.

FIG. 13 is a diagram showing a modification of the network management system.

[Explanation of symbols]

1 Network management device 2 Management information collection support device 2a conversion rules 3a, 3b, 3c Managed device 4 network 10,10a network 21,22 terminal device 100 network monitoring equipment 200, 200a, 200b Managed device

Continued front page    (72) Inventor Shigeharu Sugimoto             4-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa             No. 1 within Fujitsu Limited F term (reference) 5B089 GA11 GB02 JA35 JB14 KA09                       KA13 KH01 KH04                 5K033 BA08 BA11 DA01 DB20 EA07

Claims (5)

[Claims] 1. A management information collection support program for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, comprising: Acquire a management information acquisition request addressed to one of the management devices, and acquire the acquired management information according to a first conversion rule that is defined in advance in association with the managed device that is the destination of the acquired management information acquisition request. A request is converted, the converted management information acquisition request is transmitted to the destination managed device, and management information transmitted to the network management device from any of the plurality of managed devices is acquired; According to the second conversion rule defined in advance in association with the managed device that is the transmission source of the management information,
A management information collection support program for converting the acquired management information, and passing the converted management information to the network management device. 2. The first conversion rule is defined in association with an address on the network of any one of the plurality of managed devices, and the management information acquisition request is converted when the management information acquisition request is converted. The management information collection support program according to claim 1, wherein the first conversion rule is specified by the address of the destination of the information acquisition request. 3. The first conversion rule includes a conversion for converting a first management information identifier defined by the network management device into a second management information identifier defined by the managed device. Rules are defined, and when the management information acquisition request is converted, the first information included in the management information acquisition request is converted according to the first conversion rule.
The management information collection support program according to claim 1, wherein the management information identifier is converted into the second management information identifier. 4. An arithmetic expression for converting the management information acquired as a numerical value is defined in the second conversion rule, and the second conversion is performed when the management information is converted. The management information collection support program according to claim 1, wherein a calculation is performed according to the calculation formula defined in the rule, and the value of the management information is replaced with the result of the calculation. 5. A management information collection support device for supporting collection of management information by a network management device connected to a plurality of managed devices via a network, comprising: According to a first conversion rule that is defined in advance in association with a request acquisition unit that acquires a management information acquisition request addressed to any one of the management information acquisition requests and the managed device that is the destination of the management information acquisition request acquired by the request acquisition unit, A request conversion unit for converting the management information acquisition request acquired by the request acquisition unit; an acquisition request transmission unit for transmitting the management information acquisition request converted by the request conversion unit to the destination managed device; Management information acquisition means for acquiring management information transmitted to the network management device from any of a plurality of managed devices; Management information conversion means for converting the acquired management information according to a second conversion rule defined in advance in association with the managed device that is the transmission source of the management information acquired by the information acquisition means; Management information delivery means for delivering the management information converted by the means to the network management apparatus.