JP3479251B2 - Network management information collection method and network management information collection method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management information collecting method and a network management information collecting method,
In particular, it relates to a MIB collecting method and a MIB collecting method of an agent that implements SNMP.

[0002]

2. Description of the Related Art An example of a conventional network management information collecting system is described in Japanese Patent Laid-Open No. 11-4222. As shown in FIG. 6, the manager is an SNMP (Simple Network M) connected to the network.
management protocol: a device compatible with a protocol connected to the network to monitor the device connected to the network. SNMP
The device managed by is MIB (Management)
A variable called an Information Base) that represents the state of the device and a program called an agent for operating the variable are prepared. MIB is
IETF (Internet Engineering)
MIB (Standard MIB) officially issued by Task Force and MIB (Vendor M) defined uniquely by the vendor.
IB). In this conventional network management information collection method, a manager (network management device) collects MIBs of network devices composed of a plurality of agents (managed devices). The collection means, the alarm reception processing unit that receives traps (alarms) transmitted from the agent to the manager autonomously and asynchronously, and the MIB reception to the management agent when the alarm is received by the alarm reception processing unit. It is composed of a state detection unit for instructing collection.

Then, the manager uses the polling and the alarm together to perform the standard MI defined by the agent.
B and vendor MIB are collected, and the state change of the agent is detected.

[0004]

However, in the above-described conventional technique, the manager always collects all the MIBs that the agent can manage by the device configuration regardless of the device configuration of the agent. Therefore, the MIB acquisition of the manager is delayed. However, there is a drawback that the detection of the state change is delayed.

That is, when a certain MIB manages an agent which is present or absent depending on the configuration in the device, even if the MIB corresponding to the device is removed and the corresponding MIB is lost, the manager is installed 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 has been removed, but also transmission of the request result is delayed. If there are a plurality of MIBs that exist depending on the configuration in the device, 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 component parts of the above-mentioned device are detached during operation and the manager is notified of the change in the configuration by the SNMP trap, the MIB collection request to the agent is not changed in the conventional network information collection method. The detection of the state change of is still delayed.

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 agents that exist depending on the internal configuration of the device, but the management agents are limited. Therefore, if another SNMP agent is managed by a manager, another network management information collection program must be newly 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 changes from an agent implementing SNMP to a MIB.
In the network management information collecting method for collecting information, the MIB that can be acquired from the agent for each device type of the agent and the value of the specific MIB acquired from the agent are used as conditions, and the information is collected when the conditions are met. A management table defining a MIB, a management recording table that records at least the IP address of the agent, the management table to be used, the collection information including the MIB to be collected and the value thereof, 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 acquired from the agent, and the management table that matches the acquired MIB value of the device type is stored in the management table. The M collected and recorded collecting MIB is extracted and collected. When the MIB value corresponding to B is received from the agent, it is determined whether or not the condition described in the management table is satisfied, and if the condition is matched, another MIB is newly collected according to the condition and the collected information is collected in the collection recording unit. It is characterized in that it is configured to include a control means for recording.

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

In a third invention of the present application, the control means of the first invention receives the SNMP trap from the agent, and the MI recorded in the trap is changed.
The collected MIB is extracted from the management table recorded in the collection recording unit by referring to the collection recording unit by B, its value, and the IP address of the issuing source agent, and the MIB of the MIB is extracted in the same manner as when the agent is registered. It is characterized by collecting.

In a fourth invention of the present application, the manager is the SNM.
In a network management information collecting method for collecting MIBs from an agent that implements P, the MIB that can be acquired from the agent for each device type of the agent and the value of the specific MIB that is acquired from the agent are set as conditions. The M to be collected when there is a match
A management table that defines an IB, a management recording table that records at least the IP address of the agent, the management table that is used, the collection information that includes the MIB to collect and its value are prepared. 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 acquired from the agent and is managed from the management table that matches the acquired MIB value of the device type. When the collected MIB value recorded in the table is extracted and the collected MIB value corresponding to the MIB is received from the agent, it is determined whether or not the condition described in the management table is satisfied, and if the condition is satisfied, another condition is newly determined according to the condition. And collect the collected information in the collection recording unit. And wherein the door.

In a fifth invention of the present application, the manager of the fourth invention receives a polling request, and refers to the collecting and recording unit based on the IP address of the agent in the polling request, and records in the collecting and recording unit. It is characterized in that the collected MIB is extracted from the created management table and the MIB is collected in the same manner as when the agent is registered.

In a sixth invention of the present application, the manager of the fourth invention receives the SNMP trap from the agent, and there is a change recorded in the trap.
The collection and recording unit is referred to by the IB, its value, and the IP address of the issuing agent, and the collected MIB is extracted from the management table recorded in the collection and recording unit. It is characterized by collecting.

[Operation] The present invention provides a structure for collecting management information in a network management system using SNMP, in accordance with the structure of a device connected to the network.

In FIG. 1, a manager 11 is an SNMP (Simple Network) connected to a network.
rk Management Protocol: A device compatible with a protocol for monitoring a device connected to the network via the network) is managed.
Devices managed by SNMP are MIB (Management
A variable called an ent Information Base) that represents the state of the device and a program called an agent 1 for operating the variable are prepared.
MIB is IETF (Internet Engine)
ering Task Force) officially issued MIB (standard MIB) and MIB uniquely defined by the vendor.
(Vendor MIB). The collection condition recording unit 5 records a management table 7 that defines MIBs that can be collected when the MIBs that can be acquired from the agent and the values of the specific MIBs acquired from the agent are the conditions and the conditions are met.

For example, it is assumed that a personal computer of an Internet connection 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 a personal computer, there are a graphic card for enhancing screen display capability, a sound board for producing good sound, a SCSI board for connecting peripheral devices, a LAN card for connecting to a computer network, and the like. All of these components may be attached depending on the personal computer to be connected, or each may be connected. In addition, the personal computer of Company A has 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. The management table for company A is a graphic card, a sound board,
The definition of a standard MIB for checking whether or not a SCSI board or LAN card is installed and the definition of a standard MIB that represents detailed information such as resolution information of the graphic card when a graphic card is installed are defined. Similarly, the management table for company B is a graphic card, sound board,
It defines a vendor MIB for checking whether a SCSI board or a LAN card is installed and a collection of a vendor MIB when a graphic card is installed.

When the IP address of the agent is input by the input means 10, 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 the graphic card, sound board, SCSI board, and LAN card is checked with the standard MIB. When a graphic card is attached to the acquired MIB value, detailed information of the graphic card is collected. Moreover, in order to detect the update of the configuration information of the personal computer, the information is collected again after a certain period of time. In this way, only the MIB held by the agent is accurately collected.

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

In this way, the MIB for each agent
It is possible to reduce the number of MIB inquiries that are not managed by the agent without creating a collection program, and to collect accurate information according to the agent configuration.

[0020]

BEST MODE FOR CARRYING OUT THE INVENTION 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, the network management information collecting method of the present invention comprises an input device 10 such as a keyboard,
From the output device 12 that outputs the results of management information collection of agents on a screen, a manager 11 that is a network management device that implements an SNMP manager, and an agent 1 that is a managed device that implements SNMP to be managed. It is configured.

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

Each of these means operates roughly as follows.

The alarm reception processing section 2 includes an agent 1
Receives an 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 the MIB value by using the SNMP protocol in the agent 1, records the collected MIB value in the information recording section 6, and controls it. Notify the means 4. For example,
MIB-II, which is a standard MIB, "Reference: Management
ent Information Base forN
network Management of TCP /
IP-based internets: MIB-I
I ”, the agent 1 has the MIB“ ifType ”.
It is assumed that "e" is managed. “IfType” is an array type MIB, and the first element of the “ifType” is “softwar”.
eLoopback (24) ", secondly" ether "
It has a value of "netCsmacd (6)". When a request for collecting “ifType” of the agent 1 is received from the control means 4, Get_Next of the SNMP protocol is received.
Use the request to get the value of "ifType". The first GET_Next request is the MIB value “24” of “ifType.1” that indicates the first element of the array.
Can be obtained, and then Get_Ne with "ifType.1"
When the xt request is executed, the value “6” of “ifType.2” can be acquired. Finally, when the Get_Next request is executed with "ifType.2", "ifType"
The MIB value that is not an element of “e” is acquired, and “ifType” is acquired.
It can be seen that there is no e "value. In this way, all "ifType" MIB values are collected.

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

When collecting the MIB of the agent 1, the IP address of the agent 1 from the input device 10 (used in the Internet Protocol 32)
Bit address information) is received. In order to check which MIB is defined by the agent having the input IP address, the control unit 4 determines all the device conditions from the MIB collection information (management table 7) for each agent recorded in the collection condition recording unit 5. , The MIB value is acquired from the agent. A management table with the acquired device type MIB value as a condition 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. When the conditions are not met, NG is output to the output device 12. When the collected MIB value is received from the collecting means 3, it is judged whether or not the condition described in the management table described above is met, and if the condition is matched, a new MIB is requested to be collected to the collecting means 3 according to the condition. To do.

Also, when the SNMP trap received from the alarm reception processing unit 2 matches the condition in the above-mentioned management table, the MIB collection request and the like are similarly performed according to the condition.

The collection condition recording unit 5 records a plurality of management tables 7, and, for example, GUI (Graphical).
It is configured to register, modify, and delete the management table online via the User Interface). At the time of registration, the syntax check of the management table is performed.
It is configured so that it cannot be registered when an error occurs.

The management table 7 records which MIB is to be collected when the value matches the MIB defined by the agent. At least M indicating the device type
IB and the value are recorded as conditions. The MIB can be described by a character string or a mnemonic character string in which a decimal number is separated by ". (Dot)". For example, "1.3.6.1.4.
1.11.2.17.2.1.0 "and" sysObje
ctID. 0 ". If the MIB having an array type or the like cannot be specified," ifType. * "Or"
ifType. A description such as [1-10] "in which the elements of the array are not fixed can be made.

The value is composed of a type and a character string. For example, the integer type 10 or the OCTED STRING type "A" is used.
BC ", OBJECT type" 1.3.6.1.4.1.
1.1 ”is INTEGER“ 10 ”, ST respectively
RING "ABC" or OBJECTID "1.3.
6.11.4.1.1 ”can be described as a condition, and a combination of a plurality of conditions can be described as one condition. For example, "sysObjectID.0 ==
OBJECTID "1.3.6.1.4.1.1.1.
1 ”” and “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 the vendor M.
For example, the standard MIB “s” is not used as a direct condition.
It may be described under the condition of "ysObjectID" MIB. The “sysObjectID” MIB is an MIB that 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"
The condition may be described by combining "ectID" with other standard MIB. This is because if the vendor MIB is defined as the device type, an invalid request will be made to an agent that does not define the MIB in the determination of the device type.

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.), agent's IP address, and collected time are recorded. The recorded information is used when the conditions are combined in the conditional expression description of the management table 7 described above. For example, in the above conditional expression example, “ifType. *
￣ INTEGER “10” && sysObje
ctID. 0! = OBJECTID "1.3.
When the condition definition for comparing the two MIB values is described in the management table, the control unit 4 receives the “ifType” MIB value from the collection unit 3. Then, the “sysObjectID” MIB value is searched from the information recording unit 6 to check whether the conditions match.

The collection / recording unit 8 records the agent information currently registered, the management table to be used, the MIB to be collected, the state of whether or not the MIB is being collected, and the like.

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

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

When a request for registration of the IP address of the agent 1 is made from the input device 10, the IP address is supplied to the control means 4 (branch). The control means 4 confirms in the collection storage unit 8 whether the IP address has already been registered (step 1). If the IP address has already been registered, an error is output (step 6) and the process ends. If the IP address is not registered, the 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 acquired from the agent (step 2). Next, a management table satisfying the conditions 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, the MIB defined in the management table is detected, the MIB is recorded in the collection storage unit 8, and the collection means 3 is requested (step 5).

When the collecting 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 the management table corresponding to the IP address from the collection storage unit 8 and searches the conditions described in the management table (step 100). The collection storage unit 8 collects all the conditions corresponding to the received MIB value and collects the MIBs when the conditions are met.
If the MIB is unregistered or not collected, it is stored in the collection storage unit 8 and an acquisition request is made to the collection unit 3. The collection MIB recorded in the non-conforming condition is searched from the collection storage unit 8, and if the collection is in progress, the collection means 3 stops the collection and deletes the stored information (step 101).

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

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

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

Next, a specific example will be described.

As shown in FIG. 3, it is assumed that the manager manages the state of the cable connected to the concentrator A1 that supports the SNMP protocol connected to the network. This concentrator A1 is an ATM (Async
When it is used for the purpose of connecting a hornous transfer mode network, a line card A having two optical fiber cable connection ports A5 in the insertion port A2.
3 can be mounted, and when used for the purpose of Ethernet connection, the 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 that indicates the concentrator A1
, And has a value of "1.3.6.1.4.1.424242.1.1".

* "SLOT-TYPE" MIB: A STRING type (character string type) MIB representing the type of line card installed in the insertion slot A2 (line card A3 for ATM network or line card A4 for Ethernet). * "LINF-STATUS" MIB: array type MIB that represents the connection state of the optical fiber cable at the connection port A5 * "SLINF-STATUS" MIB: connection port A6
Array type MI that shows the connection status of the twisted pair cable
The B collection condition recording unit 5 records the management table B1 (FIG. 4). The management table B1 indicates that the device type determination is “s”.
"ysObjectID" MIB is required, and "sysO
objectID ”MIB value is“ 1.3.6.1.4.
If it is 1.4242.1.1 "," SLOT-
TYPE "MIB is defined as being 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”,
Records the conditions for collecting the "SLINF-STATUS" MIB.

From the input device 10 to the IP of the agent A1
When the address 10.10.10.10 is entered, the "sysObjectID" MIB which is the 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 to detect
The value of “sysObjectID” “1.3.6.1.
4.1.424.2.1.1 "(step 2 in FIG. 2). Then, the management table B1 whose condition is the acquired device type MIB value is searched (step 3), and the IP address of the agent A1 is acquired. The management table information B1 is recorded in the collection storage unit 8 (step 4, 1 in FIG. 5.) 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 collection request. The collecting means 3 is
When the agent 1 is requested to send the "SLOT-TYPE" MIB to the agent 1, the type "A" of the line card installed in the insertion slot A2
3 ”or“ A4 ”is returned. When the collecting means 3 receives the MIB value “A3” from the agent 1, the collecting table 3 acquires the management table B1 stored in the collecting storage unit 8 and collects the “SLOT-TYPE” MIB value in the management table as a condition. MIBs "LINF-STATUS" and "S
“LINF-STATUS” is acquired, “LINF-STAUS” whose condition is true is stored in the collection storage unit 8 (3 in FIG. 5), and a collection request is made. The condition is false "SLIN
The F-STATUS "MIB is not stored in the collection storage unit 8 and therefore is not processed as it is. When the collection unit 3 receives the collection completion of all the "LINF-STATUS" MIBs, it registers the next polling cycle of the agent 1.

The agent A1 sends "SLOT-TYP
E "Supports the SNMP trap to notify the change of MIB, and the agent A1 is the manager's IP.
If the address is registered as a trap destination, changing from line card A3 to A4 will result in "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" with the condition of "T-TYPE" MIB value
"ATUS" MIB and "SLINF-STATUS" MI
B is acquired 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, and if the MIB is currently being collected by the collection means 3, a collection stop request is issued. Then, from the collecting and recording unit 8, "LINF-STATUS" M
Delete the IB. (Fig. 5-4) If agent A1
Even if does not support SNMP trap, it is determined by periodic polling that the "SLOT-TYPE" MIB value is changed, and the line card is changed from "A3" to "A4" in the same manner as when receiving the SNMP trap. Is "LI
From the information collection of the "NF-STATUS" MIB, select "SLIN".
F-STAUS ”MIB information collection and change.

[0049]

As described above, the first effect of the present invention is that the MIB collected when the agent information is changed.
It is possible to solve the problem that the MIB acquisition of the manager of the prior art is delayed by automatically switching the.

A second effect is that by preparing a management table in which which MIB is collected for each device type of the agent is prepared, it is possible to manage various connected devices that support the SNMP protocol connected to the network. .

[Brief description of 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 showing a configuration example of a management table of the present invention.

FIG. 5 is a diagram showing an example of the configuration of a collector unit of the present invention.

FIG. 6 is a block diagram showing an embodiment of a conventional technique.

[Explanation of symbols]

1 agent 2 Alarm reception processing section 3 collection means 4 Control means 5 Collection condition recording section 6 Information recording section 7 management table 8 Collection and recording section 10 Input means 11 manager 12 Output device

─────────────────────────────────────────────────── ─── Continuation of front page (58) Fields surveyed (Int.Cl. ⁷ , DB name) G06F 13/00 H04L 12/56

Claims (6)

(57) [Claims] 1. In a network management information collecting method in the case where a manager collects MIBs from agents implementing SNMP, the MIBs that can be acquired from the agent and the specific MIBs acquired from the agent are classified according to the device type of the agent. A management table defining the MIB to be collected when the value is a condition and the condition is met, at least the IP address of the agent, the management table to be used, the collected information including the MIB to be collected and the value thereof is recorded. When the IP address of the agent to be registered is received from an input device provided in advance, the collection and recording unit is included, and the MIB value of the device type of the agent having the IP address is acquired from the agent and the device type is acquired. Is the management table that matches the MIB value? When the collected MIB value recorded in the management table is extracted from the agent and the collected MIB value corresponding to the MIB is received from the agent, it is determined whether or not the condition described in the management table is met, and if the condition is met, the condition is followed. A network management information collecting method comprising a control means 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 I of 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 the P address, and the MIB is collected in the same manner as when the agent is registered. The method for collecting network management information according to item 1. 3. The control means sends S from the agent.
Upon receipt of the NMP trap, the management recorded in the collection recording unit by referring to the collection recording unit by the MIB and the value of the change recorded in the trap and the IP address of the agent that issued the management. 2. The network management information collecting method according to claim 1, wherein the collected MIB is extracted from the table and the MIB is collected in the same manner as when the agent is registered. 4. A method for collecting network management information in the case where a manager collects MIBs from agents implementing SNMP, wherein the MIBs that can be acquired from the agent and the specific MIBs acquired from the agent are classified by device type of the agent. A management table defining the MIB to be collected when the value is a condition and the condition is met, at least the IP address of the agent, the management table to be used, the collected information including the MIB to be collected and the value thereof is recorded. A collecting and recording unit is provided, and when the manager receives the IP address of the agent to be registered from the input device provided in advance,
MI of the device type of the agent having a P address
The device type M obtained by acquiring the B value from the agent
From the management table that matches the IB value, the collected 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 or not the condition described in the management table is satisfied, and if the condition is matched, another MIB is newly collected according to the condition and the collected information is collected in the collection recording unit. A method for collecting network management information, characterized by recording the information. 5. The manager receives the polling request, and receives the I of 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 the P address, and the MIB is collected in the same manner as when the agent is registered. The method for collecting network management information according to item 4. 6. The manager receives an SNMP trap from the agent, and refers to the collection / recording unit by the MIB that has changed recorded in the trap, its value, and the IP address of the agent that issued the MIB. 5. 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 the agent is registered.