JPH1051451A - Network management system and management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the reliability of a trap by preventing missing of the trap and to surely send the trap. SOLUTION: A management manager section 10 collates management information added to a trap informed by a management agent section 20 with management information added to the trap informed in the past by the management agent 20 and when there is a contradiction between them, the management manager section 10 requests re-transmission of the trap to the management agent section 20, the management agent section 20 receiving a re-transmission request receives trap re-transmission information and the management agent section 20 executes re-transmission of the trap to the management manager. Trap management information is added to a variable binding of the trap informed to the management manager by a management agent to inform the trap to the manager and the trap informed to the management manager section 10 is stored in cross reference with the trap management information and the trap requested from the management manager section 10 is sent again.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management system and management method, and more particularly to a network management system and management method using a simple network management protocol (SNMP) as a network protocol.

[0002]

2. Description of the Related Art Conventionally, in a network management system, a management agent, which is a managed device connected to a network, notifies a management manager, which is a management device, of information on a failure or status change occurring in the management agent. UDP as lower layer protocol
(A user diagram protocol).

As such a network management system, there is, for example, a system for collecting and storing network information described in Japanese Patent Application Laid-Open No. 64-35644. This system uses a temporary storage file for each maximum propagation delay time of the network, refers to the events that have occurred at each node on the network, and allows the administrator or the management program that monitors and manages the network to perform processing quickly and easily. To

[0004]

However, the conventional network management system has a problem that even if the network is managed using a simple network management protocol (SNMP) as a network management protocol, the network management system is not used. The management agent, which is the target device, uses a trap as notification means for notifying the management manager, which is the management device, of the occurrence of a failure or a state change, and the trap is a lower layer protocol U.
Since the DP was used, there was no guarantee that the data would reach the management manager, and there was a problem in reliability.

In such a conventional management system,
A trap that notifies the management agent that cannot communicate from the management manager has not reached the management manager. In this case, it is not possible to notify the management manager, which is inconvenient for the manager.

Further, in the conventional management system, when a trap is lost on a transmission line, the transmitted trap cannot be confirmed because the SNMP trap uses UDP as a lower layer protocol, and the trap transmission is not performed. Both the management agent on the side and the management manager on the trap receiving side cannot recognize the disappearance of the trap.

An object of the present invention is to provide a highly reliable network management system and management method for preventing a communication trap from being lost from a management agent managed by a management manager.

It is another object of the present invention to enable reliable transmission of communication traps using a simple network management protocol.

It is still another object of the present invention to enable traps generated in a management agent to be automatically collected after communication is restored.

[0010]

As means for solving the above-mentioned problems, a network management system and a network management method of the present invention include a first management information added to a trap notified by a communication agent; The management agent checks the second management information added to the trap notified in the past in the management manager, and if a contradiction is detected between both the first and second management information, the management is performed as necessary. The manager requests the management agent to resend the trap, the management agent having received the resend request receives the trap resend information, and executes the trap resend from the management agent to the management manager.

Specifically, the management agent adds trap management information to variable-binding of the trap notified to the manager and notifies the manager of the trap, and notifies the manager of the trap. Trap holding means for holding a trap in association with trap management information,
Trap resending means for resending a trap requested by the management manager.

[0012] The management manager analyzes management information added to the trap notified from the management agent, and management means for managing the past trap management information notified from the management agent for each management agent to be managed. And a retransmission requesting unit for requesting the management agent to retransmit a necessary trap.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A network management system and a network management method according to an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a network management system according to one embodiment of the present invention. In FIG. 1, the network management system includes a management manager unit 10 and a management agent unit 20. The management manager unit 10 includes a trap number management unit 11, a trap analysis unit 12, a trap log unit 13, and a trap reception unit 1.
4 and a trap retransmission request unit 15.

The trap number management unit 11 is a simple network management protocol (SNMP) received from the management agent unit 20 and received in the past.
Variable Binding (Variable-
The management information added to the (Binding) field is managed in association with a management agent to be managed. The trap analyzer 12 analyzes management information added to the received SNMP trap. Trap log section 13
Accumulates traps sent from all the management agent units 20. The trap receiving unit 14 receives the SNMP trap notified from the management agent unit 20. The trap receiving unit 14 receives the SNMP trap notified from the management agent unit 20. Further, the trap retransmission request unit 15 requests the management agent unit 2 to retransmit a necessary trap.

On the other hand, the management agent section 20 includes a state change detection section 21, a trap transmission section 22, a command processing section 2
3, a trap generation unit 24, a trap retransmission unit 25, and a trap holding unit 26.

The state change detecting section 21 detects a state change of itself. The trap transmitting unit 22 transmits the generated trap to the management manager unit 10. Command processing unit 2
3 receives an SNMP command from the management manager unit 10. The trap generation unit 24 includes the management manager unit 1
SNM by adding trap management information to the variable bind dening field of the SNMP trap notifying 0
Generate a P trap. The trap resending unit 25 resends the SNMP trap requested from the management manager unit 10. The trap holding unit 26 holds the SNMP trap notified to the management manager unit 10 in association with the trap management information.

Next, a network management system according to an embodiment of the present invention will be described with reference to the flowcharts of FIGS. FIG. 1 is referred to in the description of these flowcharts. In the following flowchart, for example, step 201 will be described as S201.

First, in this embodiment, a state change occurs, and in S201, the management agent unit 20
, The state change detection unit 21 detects the state change of itself.
Next, proceeding to S202, the trap generator 24
The occurrence of the state change and its contents are notified. Next, the process proceeds to S203, where the state change detection unit 21 is
Generates a trap based on information received from. At this time, the SNMP trap holding unit 26 is referred to. Further, in S204, the management number of the latest trap is acquired. In step S205, the state change information received from the latest trap number and state change detection unit 21 is added to the barrier blue binding field of the SNMP trap to generate a trap. The trap generated in this way is transferred to the trap transmitting unit 22. Next, the process proceeds to S206, where the trap management information of the trap holding unit 26 is updated.

In step S207, the trap transmitting unit 22 having received the SNMP trap changes the
Send an SNMP trap to 0 to notify the trap.
Next, in S208, the management manager unit 10 receives the SNMP trap transmitted from the management agent unit 20 by the trap receiving unit 14, and transfers the SNMP trap to the trap analysis unit 12. Proceed further to S209, SNMP
The trap analysis unit 12 that has received the trap transfer refers to the trap number management unit 11 and acquires the information of the trap number last received in S210 from the management agent unit 20 that has generated this trap. Next, S2
At 11, the latest management information from the trap is acquired by referring to the latest trap management information added to the barrier binding field of the SNMP trap newly received from the management agent unit 20. Next, S2
In step S211, the information of the trap number acquired in step S21 is compared with the information of the latest management information acquired. Next, the subsequent processing shown in FIG.

In the flowchart shown in FIG.
In S301, it is determined whether or not there is a contradiction in the result of the comparison and collation. If there is no inconsistency in the result of the comparison / collation (YES in S301), S31
In step S314, the trap analysis unit 12 instructs the management agent unit 20 of the trap number management unit 11 to update the trap log information. In step S314, the trap number management unit 11 receives the instruction.
Is updated and the trap management information in the management agent unit 20 is updated, and the process ends.

In S301, if there is any inconsistency in the result of the comparison and collation (NO in S301), the process proceeds to S315, where the trap analysis unit 12 sends the trap retransmission request unit 15 and the management agent unit 21 Command to execute a retransmission request for a new trap,
Proceeding to 316, a trap retransmission request instruction is received. Subsequently, in S317, the received trap bond transmission request unit 15 requests the management agent unit 20 to retransmit the necessary trap. Next, proceeding to S318, the management agent unit 20 receives the trap retransmission request from the trap retransmission request unit 15 of the management manager unit 10 in the command processing unit 23. In step S319, the command processing unit 23 that has received the trap retransmission request instructs the trap retransmission unit 25 to retransmit a necessary trap. next,
Proceeding to S320, read out and re-send the designated trap. That is, the trap retransmitting unit 25 receiving the trap retransmission instruction acquires the necessary trap from the trap holding unit 26, and transmits the trap to the trap transmitting unit 2.
Hand over to 2.

Next, the process proceeds to S321, where the trap retransmitting unit 2
Trap sending unit 22 that has received the SNMP trap from 5
Retransmits the SNMP trap to the management unit 10. When the processing of S312 is completed, the processing of S207 in FIG. 2 is executed again according to the instruction of B.

Next, a network management system according to an embodiment of the present invention will be described with reference to FIGS. The description of these drawings will also be made with reference to the block diagram of FIG.

FIG. 4 shows the trap holding unit 26 shown in FIG. 1 together with the last received trap management number as the trap management information of the trap notified to the management manager unit 10 in the past.
To hold. For example, when the management number is 1, the held content is port down, and when the management number is 2, the held content is port up. When the management number is "n-1", the held content can be set to, for example, a card temperature abnormality of a memory card or the like.

FIG. 5 shows a list of the last received trap management numbers for the agents, which are stored in the trap storage unit 26. For example, the agent 20 holds the last received trap management number N, the agent 21 holds the last received trap management number X, and the agent 22 holds the last received trap management number Y.

Next, the operation of the network management system according to the embodiment of the present invention will be described in detail with reference to FIGS. This operation will be described with reference to FIG.

First, a state change is generated, and in step S610, the state change is detected by the state change detection unit.
Next, the process proceeds to S612, where the status change is notified to the trap generator 24. Further, the process proceeds to S614, where the trap holding unit receives the trap generated by the trap generation unit, and holds the trap. This is because, when the trap management information last received from the management agent unit 20 by the management manager unit 20 is stored in the trap number storage unit 26 in the trap number management unit 11, a state change occurs in the management agent unit 20. . At this time, the state change detection unit 21 notifies the trap generation unit of both the occurrence and the content of the state change.

In S616, the trap generator 24
Refers to the trap holding unit 26 when the contents shown in FIG. 4 are reached, and the management number of the trap notified last is "n-1".
Therefore, the latest trap management number n is obtained. In S618, the trap generator 24 generates a trap according to the latest trap management number.

Subsequently, the flow advances to S620, where the trap generation unit 2
4. The variable of the generated SNMP trap
The management number n is added to the binding and the trap transmission unit 22 is added.
And updates the content of the trap holding unit 26 by adding the trap managed by the trap management number n.

Next, the process proceeds to S622, where a trap is notified to the management manager unit 10, and then the process proceeds to S624, where the trap receiving unit 14 receives the trap. When the management manager unit 10 receives the SNMP trap from the management agent unit 20 by the trap receiving unit 14, the trap receiving unit 14 passes the received trap to the trap analyzing unit 12. Next, S62
In 6, the trap analysis unit 12 refers to the trap number management unit 11 having the contents shown in FIG. 5 and proceeds to S630 to acquire the trap management number N corresponding to the management agent unit 20.

Next, in S632, it is determined whether or not the track management number N is acquired and the value obtained by adding 1 to the trap management number N is an integer n (n is a natural number of 2 or more). Here, it is for acquiring the trap management number N and confirming whether there is no contradiction between the trap management number N and the integer n. For example, if the integer n is equal to “N + 1” (YES in S632), the process proceeds to A in FIG. Also, the integer n is not equal to “N + 1” (S632
(NO), the process proceeds to B in FIG.

In S632, the integer n is changed to “N +
If it is equal to "1" (YES in S632), the process proceeds to S710, where the trap analysis unit 12 changes the management number information on the management agent from N to n, and when n is larger than [N + 1]. Indicates that the trap analysis unit 12 requests the trap retransmission request unit 15 to request the management agent unit 20 to retransmit traps from the trap management numbers “N + 1” to n.

On the other hand, if the integer n is not equal to "N + 1" (NO in S632), the process proceeds to B in FIG. At this time, if n is smaller than “N + 1” (NO in S720), the process proceeds to S712 as an error process.
Then, the management number information on the management agent unit 20 of the trap number management unit 11 is updated to n, and the above processing is completed.

In S720, the integer n is changed to “N +
If it is equal to “1” (YES in S632), the process proceeds to S722, in which the trap retransmission request unit 15 receiving the instruction from the trap analysis unit 12 sends the trap management number “ The retransmission request signals for the traps from "N + 1" to n are transmitted using the SNMP command. Then, the process proceeds to S724, where a trap retransmission request is received. The process further proceeds to S726, and after transmitting a trap retransmission request, a trap retransmission request signal is received in S728. In the processing so far, in the management agent unit 20, in the command processing unit 23,
It receives the trap retransmission request signal from the trap management number “N + 1” to the integer n and notifies the trap retransmission unit 25 of the trap retransmission request.

In step S732, the trap retransmitting unit 25, having received the trap retransmission request signal, refers to the trap held in the trap holding unit 26 in advance, generates a trap having a corresponding trap management number, and transmits the trap. SNMP from unit 22 to management manager unit 10
Request to send traps. This also allows SNMP
Trap transmission unit 22 that has received a trap transmission request signal
Is the SNM to the management unit 10 in S734.
Execute retransmission of the P trap. At this time, the process returns to S622 of FIG. 6 again by C.

In the embodiment described above, the case of one management agent unit 20 and one management manager unit 10 has been described. However, the present invention may be implemented without departing from the scope of the present invention. It goes without saying that the example is not limited to this, and there is no restriction on the number of both.

[0037]

As described above, according to the network management system and management method of the present invention, trap management information is added to a variable binding field of an SNMP trap, and a management manager section is provided for each management agent section. By comparing the two pieces of trap management information based on the trap management information, the management manager unit can recognize the missing trap.
It is possible to prevent the SNMP trap from being lost due to the disappearance of the trap on the transmission line.

According to the present invention, retransmission is performed only when inconsistency occurs between the management information added to the trap of the management agent unit and the management information possessed by the management manager. Traffic can be reduced.

Further, according to the present invention, since the trap for notifying the state change that occurred while communication with the management manager unit is not possible is lost on the transmission line, the trap is added to the SNMP trap notified after the communication is restored. Since a conflict occurs between the management information and the management information of the management manager section, retransmission of the missing trap is automatically executed. It is possible to obtain effects such as the ability to automatically collect SNMP traps in the economy.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a network management system and a management method according to an embodiment of the present invention.

FIG. 2 is a flowchart illustrating an operation of the network management system shown in FIG. 1;

FIG. 3 is a flowchart following the flow shown in FIG. 2;

FIG. 4 is a diagram illustrating data stored in a storage unit of the network management system illustrated in FIG. 1;

FIG. 5 is a diagram showing data stored in a storage unit of the network management system shown in FIG. 1;

FIG. 6 is a flowchart illustrating a more specific operation of the network management system shown in FIG. 1;

FIG. 7 is a flowchart following the flow shown in FIG. 6;

[Explanation of symbols]

 Reference Signs List 10 management manager section 11 trap number management section 12 trap analysis section 13 trap log section 14 trap reception section 15 trap retransmission request section 20 management agent section 21 state change detection section 22 trap transmission section 23 command processing section 24 trap generation section 25 trap retransmission Unit 26 Trap holding unit 120 Call signal 121 Detection signal

Claims (5)

[Claims] 1. A collating means for collating in a management manager first management information added to a trap notified by a communication agent and second management information added to a trap notified by the management agent in the past. Retransmission request means for requesting the management agent to resend the trap from the management manager as necessary when an inconsistency is detected between both the first and second management information collated by the collation means. Executing means for receiving the trap retransmission request by the management agent receiving the trap retransmission information, and executing the trap retransmission from the management agent to the management manager. Network management system. 2. The management agent includes: notification means for adding trap management information to a variable binding of a trap to be notified to a management manager to notify the manager of the trap; and trap management information of the trap notified to the management manager. 2. The network management system according to claim 1, further comprising: a trap holding unit that associates and holds the trap; and a trap retransmission unit that retransmits a trap requested by the management manager. 3. 3. The management manager manages the past trap management information notified by the management agent for each management agent to be managed, and adds the management information to the trap notified by the management agent. The network management system according to claim 1, further comprising: an analysis unit configured to analyze the management information; and a retransmission request unit configured to request the management agent to retransmit a necessary trap. 4. A step of collating in the management manager the first management information added to the trap notified by the communication agent and the second management information added to the trap notified by the management agent in the past. Requesting a retransmission of the trap from the management manager to the management agent as necessary when an inconsistency is detected between both the first and second management information; Receiving the trap resend information from the management agent and executing the trap resend from the management agent to a management manager. 5. The method according to claim 1, wherein the management agent adds trap management information to a variable binding of the trap to be notified to a manager, and notifies the manager of the trap. Re-sending the trap requested from the management manager; andthe management manager, for each of the management agents, which manages the past trap management information notified from the management agent. A management step; analyzing management information added to the trap notified from the management agent; and requesting the management agent to retransmit a necessary trap. Item 4. Network network according to item 4. Method.