JP2001202304A - System and method for collecting network managing information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve a problem that the MIB acquisition of a manager is delayed. SOLUTION: With the values of an MIB, which can be acquired from an agent 1, and a specified MIB acquired from this agent as conditions, for each device class of this agent, a managing table 7 defines the MIB to be collected in the case of coincidence to these conditions. When the IP address of the agent of a register object is received from an input device 10, a control means 4 acquires the MIB value of the device class of an agent having this IP address from the agent 1 through a collection means 3 and extracts the collected MIB recorded in the managing table from the managing table coincident to the acquired device class MIB value and when the MIB value corresponding to this collected MIB is received from the agent through the collection means 3, it is discriminated whether the MIB value is coincident to the conditions described in the managing table 7 or not. In the case of coincidence, according to these conditions, the other MIB is newly collected and collected information is recorded in a collection recording part.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a network management information collection method and a network management information collection method.
In particular, the present invention relates to a MIB collection method and a MIB collection method for an agent implementing SNMP.

[0002]

2. Description of the Related Art An example of a conventional network management information collecting method is disclosed in Japanese Patent Application Laid-Open No. H11-4222. As shown in FIG. 6, a manager connects to a network by using an SNMP (Simple Network M).
management (a protocol for monitoring devices connected to the network via the network). SNMP
Devices managed by MIB are managed by MIB (Management
There is provided a variable called an Information Base, which represents the state of the device, and a program called an agent for operating the variable. MIB is
IETF (Internet Engineering)
Task Force), an officially issued MIB (Standard MIB) and a vendor-specific MIB (Vendor M)
IB). In this conventional network management information collection method, an MIB in which a manager (network management device) collects MIBs from a manager to an agent in order to collect MIBs of network devices including a plurality of agents (managed devices). A collection unit, an alarm reception processing unit that receives a trap (alarm) transmitted autonomously and asynchronously from the agent to the manager, and an MIB reception request to the management agent when the alarm is received by the alarm reception processing unit. And a state detection unit for instructing collection.

[0003] The manager uses the standard MI defined by the agent together with the polling and the alarm.
B and the vendor MIB are collected, and a change in the state of the agent is detected.

[0004]

However, in the prior art described above, the manager always collects all MIBs that can be managed by the agent according to the device configuration, regardless of the device configuration of the agent. However, there is a disadvantage that detection of a state change is delayed.

That is, when managing an agent in which a specific MIB exists due to the configuration in the device, even if the component of the device is removed and the corresponding MIB is lost, the manager is managed in the same manner as the device to which the component is attached. Makes an MIB acquisition request to the agent, so that not only an invalid MIB acquisition request is transmitted to the agent whose component is removed, but also the transmission of the request result is delayed. If there are a plurality of MIBs that exist in the apparatus depending on the configuration, or if there are a plurality of such agents on the network, the acquisition of the MIB by the manager is delayed, and the detection of the state change is delayed. In addition, even if the components of the above-described apparatus are attached and detached during operation and the change in the configuration is notified to the manager by the SNMP trap, the MIB collection request to the agent is not changed by the conventional network information collection method. The fact that the detection of the state change is delayed.

[0006] The problem of the invalid SNMP acquisition request described above can be prevented if a certain MIB creates a network management information collection program limited to the presence or absence of an agent due to the configuration in the apparatus. Therefore, if another SNMP agent is managed by the manager, a new network management information collection program must be created, and various connected devices that support the SNMP protocol connected to the network must be managed. There is also a problem that it becomes difficult.

[0007]

According to a first aspect of the present invention, a manager sends a MIB from an agent implementing SNMP.
In the network management information collection method when collecting the information, the MIB that can be obtained from the agent and the value of a specific MIB obtained from the agent are collected for each device type of the agent when the conditions are met. A management table defining MIBs, at least an IP address of the agent, the management table to be used, a collection recording unit for recording collection information including the MIBs to be collected and their values, and an input device provided in advance. When the IP address of the agent to be registered is received, the MIB value of the device type of the agent having the IP address is obtained from the agent and the management table that matches the obtained device type MIB value is stored in the management table. The M collected and extracted from the collected MIB When the MIB value corresponding to B is received from the agent, it is determined whether the condition matches the condition described in the management table. If the condition is met, another MIB is newly collected according to the condition, and the collection information is stored in the collection recording unit. Characterized by including a control means for recording

According to a second aspect of the present invention, in the first aspect, the control means receives a polling request, refers to the collection and recording unit based on an IP address of the agent in the polling request, and sends the collected and recorded data to the collection and recording unit. The collected MIB is extracted from the recorded management table, and the MIB is collected in the same manner as when the agent is registered.

[0009] In a third aspect of the present invention, in the first aspect, the control means receives an SNMP trap from the agent and changes the MI recorded in the trap.
B, its value, and the IP address of the issuing agent, referencing the collection recording unit, extracting the collection MIB from the management table recorded in the collection recording unit, and extracting the collection MIB in the same manner as when registering the agent. It is characterized by collecting.

In a fourth aspect of the present invention, the manager is an SNM.
In the network management information collecting method for collecting MIBs from an agent having P, the MIB is obtained from the agent for each device type of the agent and the value of a specific MIB obtained from the agent is used as a condition. The M to collect if they match
An IB defined management table, at least an IP address of the agent, the management table to be used, a collection recording unit for recording collection information including the collected MIB and its value, and the manager is provided in advance. When the IP address of the agent to be registered is received from the input device, the MIB value of the device type of the agent having the IP address is obtained from the agent, and the management is performed from the management table that matches the obtained MIB value of the device type. When the collected MIB value recorded in the table is extracted and the MIB value corresponding to the collected MIB is received from the agent, it is determined whether or not the condition matches the condition described in the management table. And collecting the collected information in the collection recording unit. And wherein the door.

According to a fifth aspect of the present invention, in the fourth aspect, the manager receives a polling request, refers to the collection and recording unit based on the IP address of the agent in the polling request, and records the data in the collection and recording unit. The collected MIB is extracted from the management table, and the MIB is collected in the same manner as when the agent is registered.

According to a sixth aspect of the present invention, in the fourth aspect, the manager receives an SNMP trap from the agent, and the M which has been recorded in the trap has a change.
The collection MIB is extracted from the management table recorded in the collection recording unit by referring to the collection recording unit based on the IB, its value, and the IP address of the issuing agent, and the MIB is registered in the same manner as when registering the agent. It is characterized by collecting.

[Operation] The present invention provides a configuration in which management information can be collected according to the configuration of devices connected to a network in a network management system using SNMP.

Referring to FIG. 1, a manager 11 is an SNMP (Simple Network) connected to a network.
rk Management Protocol: a protocol for monitoring devices connected to the network via the network.
Devices managed by SNMP are MIBs (Managem
A variable called “ent Information Base” indicating the state of the device and a program called an agent 1 for operating the variable are prepared.
The MIB is based on IETF (Internet Engineering).
erring Task Force) and the vendor-specific MIB (Standard MIB)
(Vendor MIB). The collection condition recording unit 5 records a management table 7 that defines an MIB to be collected when the condition is met, based on the MIB that can be obtained from the agent and the value of a specific MIB obtained from the agent.

For example, it is assumed that a personal computer of an Internet service provider (provider) is used as a manager, and the manager manages configuration information of a personal computer (agent) connected to the provider. As components of the personal computer, there are a graphic card for enhancing the screen display capability, a sound board for producing good sound, a SCSI board for connecting peripheral devices, and a LAN card for connecting to a computer network. All of these components may be mounted depending on the personal computer to be connected, or each may be connected. Company A's personal computer is a standard MI
The configuration information of the personal computer is defined by B, but the personal computer of the company B defines the configuration information by the vendor MIB.

At this time, the management table 7 defines a management table for company A and a management table for company B, and the management table for company A includes a graphic card, a sound board,
The definition of the standard MIB for checking whether or not the SCSI board and the LAN card are installed and the collection of the standard MIB indicating detailed information such as resolution information of the graphic card when the graphic card is installed are defined. Similarly, the management table for Company B includes a graphic card, a sound board,
The definition of a vendor MIB for checking whether a SCSI board or a LAN card is mounted and the collection of a vendor MIB when a graphic card is mounted are defined.

When the input means 10 inputs the IP address of the agent, the control means 4 acquires the device type MIB value from the agent. At this time, the device type MIB
However, in the case of Company A, the presence or absence of a graphic card, a sound board, a SCSI board, and a LAN card is checked using a standard MIB. When a graphic card is attached to the acquired MIB value, detailed information of the graphic card is collected. Further, in order to detect the update of the configuration information of the personal computer, the information is collected again after a certain period. In this way, only the MIB of the agent is collected accurately.

When the MIB value is changed by registering the manager 11, the agent 1 can autonomously and asynchronously notify the manager 11 of the SNMP trap. The manager 11 waits for the SNMP trap from the agent in the alarm reception processing unit 2. S
When receiving the NMP trap, the control unit 4 collects the collected MI.
The collection condition storage unit 5 analyzes whether the change of B is necessary, and when the change of the collection MIB is detected, the MIB to be automatically collected is changed. For example, according to the above example, the content of the alarm is the content attached to the sound board of the personal computer of Company A, and
Agent 1 that generated the NMP trap
If the information is managed in step 1, information is collected using a standard MIB representing detailed information of the sound board.

In this way, the MIB for each agent
This eliminates the need to create a collection program, reduces MIB inquiries not managed by the agent, and enables accurate information collection according to the configuration of the agent.

[0020]

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

FIG. 1 is a block diagram showing an embodiment of the present invention.

Referring to FIG. 1, a network management information collecting method according to the present invention includes an input device 10 such as a keyboard,
An output device 12 that outputs a result of agent management information collection on a screen or the like, a manager 11 that is a network management device equipped with an SNMP manager, and an agent 1 that is a managed device equipped with SNMP to be managed. It is configured.

The manager 11 includes an alarm reception processing unit 2 for receiving a state change from the agent 1, a collecting unit 3 for collecting management information of the agent 1, and a control unit 4 for controlling the collection of the MIB of the agent 1. .

Each of these means operates as follows.

The alarm reception processing unit 2 includes an agent 1
Receives the SNMP trap issued autonomously and asynchronously, and notifies the control means 4.

The collection means 3 receives the MIB acquisition request from the control means 4, collects MIB values using the SNMP protocol in the agent 1, records the collected MIB values in the information recording unit 6, Notify the means 4. For example,
MIB-II "Reference Managem" which is a standard MIB
ent Information Base for N
network Management of TCP /
IP-basedinternets: MIB-I
I ”, the agent 1 receives the MIB“ ifType
"e" is managed. “IfType” is an array-type MIB, and “softwar” is included in the first element.
eLoopback (24) "and secondly" ether
netCsmacd (6) ". When receiving a request for collecting “ifType” of the agent 1 from the control unit 4, Get_Next of the SNMP protocol is received.
Get the value of “ifType” using the request. The first GET_Next request has an MIB value “24” of “ifType.1” indicating the first element of the array.
Can be obtained, and then “GetType.1”
When the xt request is executed, the value “6” of “ifType.2” can be obtained. Finally, when the Get_Next request is executed in “ifType.2”, “ifType.
e), the MIB value which is not an element of “eType” is obtained.
It can be seen that there is no value of "e". In this way, the values of all “ifType” MIBs are collected.

The control means 4 registers the agent registration and deletion request from the input device 10 and the MI acquired from the collection means 3.
A B value or an SNMP trap from the alarm reception processing unit 2 and, if necessary, an MIB acquisition request
To do.

When collecting the MIB of the agent 1, the IP address of the agent 1 (32 used in the Internet Protocol) is input from the input device 10.
Bit address information). The control unit 4 checks all the device conditions from the MIB collection information (management table 7) for each agent recorded in the collection condition recording unit 5 in order to check which MIB is defined by the agent having the input IP address. And retrieves the MIB value from the agent. A management table conditioned on the acquired device type MIB value is searched from the collection condition recording unit 5, and if they match, the collection MIB recorded in the management table is extracted and requested to the collection unit 3. If the conditions do not match, NG is output to the output device 12. When the collected MIB value is received from the collection unit 3, it is determined whether or not the condition matches the condition described in the management table. If the condition is met, another collection of another MIB is requested to the collection unit 3 according to the condition. I do.

Also, when the SNMP trap received from the alarm reception processing unit 2 matches the condition in the above-mentioned management table, a request to collect MIB is made in accordance with the condition.

The collection condition recording unit 5 records a plurality of management tables 7 and, for example, a GUI (Graphical).
The management table is configured to be registered, modified, and deleted online through a User Interface). At the time of registration, a syntax check of the management table is performed.
In case of an error, it is configured not to be registered.

The management table 7 records which MIB is to be collected when the value matches the MIB defined by the agent. At least M representing the device type
IB and value are recorded as conditions. The MIB can be described by a character string or a mnemonic character string in which decimal numbers are separated by ". (Dot)". For example, "1.3.6.1.4.
1.11.2.2.17.2.1.0 "or" sysObject "
ctID. 0 ". In the case where an MIB having an array type or the like cannot be specified," ifType. * "And"
ifType. A description that does not fix the elements of the array, such as [1-10] ", can be used.

The value is composed of a type and a character string. For example, an integer 10 or an OCT STRING type "A"
BC ", OBJECT type" 1.3.6.1.4.1.
1.1 "means INTEGER" 10 "and ST
RING "ABC" or OBJECTID "1.3.
6.1.4.1.1.1 ". The condition can describe a comparison operator (matching, mismatching, including, not including), and the like, and a combination of a plurality of conditions can be described as one condition. For example, "sysObjectID.0 ==
OBJECTID "1.3.6.4.1.1.1.
1 "" or "ifType.*@INTEGER"
10 "&& sysObjectID.0! = OB
JECTID "1.3.6.1.4.1.1.1""
And so on.

The MIB condition indicating the device type is as follows:
The IB is not directly used as a condition. For example, the standard MIB “s
ysObjectID "MIB may be described as a condition. The “sysObjectID” MIB indicates which vendor information of the agent is defined, and generally has a different value for each device. If there is an agent that is a different device but has the same “sysObjectID” MIB value, “sysObj
It is preferable to describe the condition by combining “ectID” with other standard MIBs. This is because, if the vendor MIB is defined as the device type, the determination of the device type becomes an invalid request for an agent that does not define the MIB.

The information recording unit 6 records the MIB value acquired from the agent 1. Contents to be recorded are MIB, array type element, value, value type (INTEGER type, OB
JECT type, OCTET STRING type, etc.), the IP address of the agent, and the collection time are recorded. The recorded information is used when combining the conditions in the description of the conditional expression in the management table 7 described above. For example, in the above example of the conditional expression, “ifType. *
￣ INTEGER "10"&& sysObject
ctID. 0! = OBJECTID "1.3.
6.1.4.1.1.1 "" and a condition definition for comparing two MIB values are described in the management table, and the control unit 4 receives the "ifType" MIB value from the collection unit 3. Then, the MIB value of “sysObjectID” is searched from the information recording unit 6 to confirm whether the condition matches.

The collection recording unit 8 records currently registered agent information, management tables to be used, MIBs to be collected, and whether or not the MIBs are being collected.

Next, the operation of the embodiment of the present invention will be described in detail with reference to the flowcharts of FIGS.

The control means 4 waits for the supply of an event from the input device 10, the collection means 3, the alarm reception processing unit 2, and the like. (Step 0 in FIG. 2).

When the input device 10 requests registration of the IP address of the agent 1, the IP address is supplied to the control means 4 (branch). The control unit 4 checks whether the IP address has already been registered in the collection storage unit 8 (step 1). If the IP address has already been registered, an error is output (step 6) and the process ends. If the IP address has not been registered, an MIB for determining the device type is extracted from all the management tables registered in the collection condition recording unit 5, and the MIB value is obtained from the agent (step 2). Next, a management table that satisfies the condition is searched from the acquired device type determination MIB value (step 3). When the management table is detected, the IP address of the agent and the management table information are stored in the collection storage unit 8 (step 4). Next, an MIB defined in the management table is detected, the MIB is recorded in the collection storage unit 8, and a request is made to the collection unit 3 (step 5).

When the collection unit 3 acquires the MIB value, the acquired MIB value is recorded in the information storage unit 6, and the IP address of the agent and the MIB value are supplied to the control unit 4 (branch). The control unit 4 obtains a management table corresponding to the IP address from the collection storage unit 8, and searches for a condition described in the management table (step 100). All the conditions corresponding to the received MIB value are acquired, and for the MIB to be collected when the condition is satisfied, the collection storage unit 8
If the MIB is an unregistered or uncollected MIB, the MIB is stored in the collection storage unit 8 and an acquisition request is made to the collection unit 3. The collection MIB recorded under the unsuitable condition is searched from the collection storage unit 8, and if collection is being performed, collection is stopped by the collection unit 3 and the storage information is deleted (step 101).

When all the MIBs requested by the collection means 3 have been collected, the IP address and MIB of the terminated agent are collected.
Is supplied to the control means 4 (branch). When all MIBs of the agent 1 have been collected, the next polling cycle is set (step 102).

When the alarm reception processing unit 2 receives the SNMP trap from the registered agent, the control unit 4
Supply the trap to (branch). The control means 4
The above-described processing (branch) is performed based on the changed MIB recorded in the trap, its value, and the IP address of the issuing agent.

When the polling cycle time to the agent 1 is reached (branch), the MIB registered in the collection recording unit 8
Is requested to the collecting means 3 again (step 105).

Next, a specific example will be described.

As shown in FIG. 3, for example, it is assumed that the manager manages the state of the cable connected to the concentrator A1 supporting the SNMP protocol connected to the network. This concentrator A1 is an ATM (Async)
(Transfer Mode) When used for connection of a network, a line card A having two optical fiber cable connection ports A5 at the insertion port A2.
3 and can be used for Ethernet connection purposes, it is assumed that a line card A4 having four twisted pair cable connection ports A6 can be mounted in the insertion port A2. This concentrator A1 defines the following MIB of A1 '.

* "SysObjectID" MIB:
OBJECT type MIB indicating the line concentrator A1
And has a value of “1.3.6.1.4.1.4242.1.1.1”.

* "SLOT-TYPE" MIB: a string type (character string type) MIB indicating the type of line card (line card A3 for ATM network or line card A4 for Ethernet) attached to the insertion slot A2. * "LINF-STATUS" MIB: an array type MIB indicating the connection state of the optical fiber cable at the connection port A5 * "SLINF-STATUS" MIB: a connection port A6
Array type MI indicating the connection state of the twisted pair cable
B The collection condition recording unit 5 records a management table B1 (FIG. 4). The management table B1 indicates that the determination of the device type is “s
ysObjectID "MIB is required, and" sysO
object ID "MIB is" 1.3.3.6.1.4.
1.42.4.1.1 ", the" SLOT-
TYPE "MIB is defined to be collected. further,
If the value of the “SLOT-TYPE” MIB is “A3”, the “LINF-STATUS” MIB is collected and “S
If the value of “LOT-TYPE” MIB is “A4”,
“SLINF-STATUS” MIB conditions are recorded.

From the input device 10, the IP address of the agent A1
When the address 10.10.10.10 is input, the "sysObjectID" MIB, which is a device type condition, is detected from the management table group recorded in the collection condition recording unit 5, and the agent 1 uses the SNMP protocol,
The value of “sysObjectID” “1.3.6.1.
4.1.2.42.1.1.1 "is obtained (step 2 in FIG. 2). Next, the management table B1 whose condition is the obtained device type MIB value is searched (step 3), and the IP address of the agent A1 is obtained. Then, the management table information B1 is recorded in the collection storage unit 8 (step 4, 1 in FIG. 5), and the collection MIB “SLOT-TYPE” is acquired from the management table B1 and stored in the collection storage unit 8 (2 in FIG. 5). ), "SLOT-
TYPE "MIB is requested to be collected. The collecting means 3
When the "SLOT-TYPE" MIB is requested from the agent 1, the type of the line card "A
Returns "3" or "A4". When the collection unit 3 receives the MIB value “A3” from the agent 1, the collection unit 3 acquires the management table B 1 stored in the collection storage unit 8 as described above, and collects the data based on the “SLOT-TYPE” MIB value in the management table. MIB "LINF-STATUS" and "S
LINF-STATUS "is acquired, and" LINF-STATUS "for which the condition is true is stored in the collection storage unit 8 (3 in FIG. 5), and a collection request is made. "SLIN" condition is false
Since the “F-STATUS” MIB is not stored in the collection storage unit 8, the process is not performed as it is. When the collection unit 3 receives the completion of collection of all “LINF-STATUS” MIBs, it registers the next polling cycle of the agent 1.

When the agent A1 enters the "SLOT-TYP"
E "Supports SNMP trap for notifying MIB change, and agent A1 is the manager's IP
If the address is registered as a trap destination, if the line card is changed from A3 to A4, "SLOT-TYPE"
Is notified to the manager 11 by an SNMP trap. Alarm reception processing unit 2 that received the SNMP trap
Is supplied to the control means 4. The control unit 4 acquires the “SLOT-TYPE” MIB value “A4” and the IP address of the agent A1 from the alarm, and detects the management table B1 from the collection storage unit 8. "SLO" in the management table
“LINF-ST” subject to “T-TYPE” MIB value
ATUS "MIB and" SLINF-STATUS "MI
B, and the condition is true “SLINF-STAU”
S ”is stored in the collection storage unit 8, and a collection request is made. The “LINF-STATUS” MIB whose condition is false is stored in the collection storage unit 8 at the time of registration. If the MIB is currently being collected by the collection unit 3, a collection stop request is made. Then, "LINF-STATUS" M
Delete IB. (FIG. 5-4) If Agent A1
If the "SLOT-TYPE" MIB value is determined by periodic polling even if the SNMP card does not support the SNMP trap, and the line card is changed from "A3" to "A4" in the same manner as the reception of the SNMP trap Is "LI
NF-STATUS ”MIB information collection to“ SLIN
F-STAUS ”MIB information collection and change.

[0049]

As described above, the first effect of the present invention is that the MIB to be collected in accordance with the change of the agent information is changed.
Is automatically switched, it is possible to solve the problem that the acquisition of the MIB by the conventional manager is delayed.

The second effect is that, by preparing a management table that records which MIBs are collected for each device type of the agent, it is possible to manage various connected devices supporting the SNMP protocol connected to the network. .

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of the present invention.

FIG. 2 is a flowchart showing the operation of the present invention.

FIG. 3 is a reference diagram for explaining the operation of the present invention.

FIG. 4 is a diagram illustrating a configuration example of a management table according to the present invention.

FIG. 5 is a diagram showing an example of the configuration of a collecting machine according to the present invention.

FIG. 6 is a block diagram showing an embodiment of the related art.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Agent 2 Alarm reception processing part 3 Collection means 4 Control means 5 Collection condition recording part 6 Information recording part 7 Management table 8 Collection and recording part 10 Input means 11 Manager 12 Output device

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B089 GA11 GA21 GB02 HB06 JA36 JB15 JB22 KA04 KB04 KC28 KC53 5K030 GA02 GA14 HA08 HB08 LA08 LD17 MC07 MD08 9A001 BB04 CC06 CC07 JJ12 KK56 LL09

Claims (6)

[Claims] 1. A network management information collection method in which a manager collects MIB from an agent in which SNMP is installed. In the network management information collection method, the MIB which can be obtained from the agent for each device type of the agent and the specific MIB obtained from the agent A management table that defines the MIB to be collected when the value matches the condition based on a value, a collection information including at least the IP address of the agent, the management table to be used, the MIB to be collected, and the value are recorded. A collecting and recording unit, and upon receiving the IP address of the agent to be registered from an input device provided in advance, obtaining the MIB value of the device type of the agent having the IP address from the agent, and obtaining the obtained device type Whether the management table matches the MIB value When the collected MIB value recorded in the management table is extracted and the MIB value corresponding to the collected MIB is received from the agent, it is determined whether or not the condition matches the condition described in the management table. A network management information collection method, comprising a control unit for newly collecting another MIB and recording the collected information in the collection recording unit. 2. The control means receives a polling request, and receives the polling request from the agent in the polling request.
The collection MIB is extracted from the management table recorded in the collection recording unit by referring to the collection recording unit based on a P address, and the MIB is collected in the same manner as when registering the agent. Item 2. The network management information collection method according to Item 1. 3. The control means receives an S from
In response to the NMP trap, the MIB recorded in the trap, the value of the MIB, the value of the MIB, and the IP address of the issuing agent are referred to the collection recording unit, and the management recorded in the collection recording unit is performed. 2. The network management information collection method according to claim 1, wherein the collection MIB is extracted from a table, and the MIB is collected in the same manner as when registering the agent. 4. A network management information collection method in which a manager collects MIBs from an agent implementing SNMP. In the network management information collecting method, the MIB which can be obtained from the agent for each device type of the agent and the specific MIB obtained from the agent A management table that defines the MIB to be collected when the value matches the condition based on a value, a collection information including at least the IP address of the agent, the management table to be used, the MIB to be collected, and the value are recorded. And a collection / recording unit. When the manager receives the IP address of the agent to be registered from an input device provided in advance, the manager
MI of the device type of the agent having a P address
The B value is obtained from the agent and the obtained device type M is obtained.
From the management table that matches the IB value, a collection MIB recorded in the management table is extracted and collected.
When the MIB value corresponding to B is received from the agent, it is determined whether the condition matches the condition described in the management table. If the condition is met, another MIB is newly collected according to the condition, and the collection information is stored in the collection recording unit. Recording network management information. 5. The manager receives a polling request, and receives the polling request from the agent in the polling request.
The collection MIB is extracted from the management table recorded in the collection recording unit by referring to the collection recording unit based on a P address, and the MIB is collected in the same manner as when registering the agent. Item 4. The network management information collection method according to Item 4. 6. The manager receives an SNMP trap from the agent, and refers to the collection and recording unit based on the MIB recorded in the trap, its value, and the IP address of the issuing agent. The network management information collection method according to claim 4, wherein the collection MIB is extracted from the management table recorded in the collection recording unit, and the MIB is collected in the same manner as when registering the agent.