KR20090008030A - Consistent state view providing system and method in network of snmp base - Google Patents

Abstract

A system for providing consistent state view information in an SNMP-based network and a method thereof are provided to enable an SNMP administrator to offer the consistent state view for information of a table. When the first request message for consistent state view management is received from an external management system(100), an agent(200) generates the first copying table(220) after copying an inside table(210). In case the first request message deviates from the index range of the first copying table, the agent deletes the first copying table after determining that the processing for the first request message is perfectly completed. If a following request message is not received for a predetermined time from the external management system while the inquiry is being performed on the first copying table, the agent deletes the first copying table.

Description

System and method for providing fixed state information in a SSN-based network {consistent state view providing system and method in network of SNMP base}

The present invention relates to a system and method for providing fixed status information in an SNMP-based network.

In general, SNMP is playing a key role in improving and maintaining a company's competitiveness, and as the size and complexity of the network become larger, efforts and costs for efficient operation are also increasing.

However, the emergence of multi-vendor and multi-protocol products, increased network complexity, frequent changes in the network environment, increased need for distributed management, and centralized mapping of logical maps and equipment ( By changing the network technical environment such as increasing the need for control and monitoring, increasing the demands of users, minimizing downtime, reducing administrative costs, lack of human resources, and improving network services. Efficient network management required the need for standardization work.

As a result, in early 1988, the Internet Architecture Board (IAB) began standardization.

At this time, it was decided to adopt SNMP that developed SGMP as a standard among high level entity management system (HEMS), simple gateway monitoring system (SGMP), and common management information protocol / services (CMIP / CMIS).

SNMP started this way and was easy to implement, making it the most common network management protocol today.

Here, in SNMP, it is the basic of network management to transmit / receive specific information between manager and agent. Specific information and resources to be managed are called objects. The collection of these objects is called a MIB.

Each object is represented as an array of numbers called an object identifier (OID), where each step of the number is given a letter name.

In such a conventional SNMP-based network management system, when managing network equipment using SNMP, in order to query a large amount of data, the GET-NEXT (or GET-BULK) request must be repeatedly repeated. In other words, the size of SNMP packet using UDP is limited to 2-4K bytes, and there is no command such as GET-TABLE to read only table values.

However, since each request is processed automatically, if the data is changed in the process of repeating the request, the information obtained by the administrator is not a consistent information at one moment, but information about a part of the moment that is changed dynamically. .

In particular, when an alarm audit-like operation is performed to correct trap loss due to the characteristics of UDP, there is a problem in that information of an alarm occurring at a specific moment cannot be found like a snap-shot.

The conventional SNMP-based network management system is implemented with an external management system 1 and an agent 2, and the agent 2 includes an internal table 210 as shown in FIG. 1A.

The GET-NEXT is transmitted from the external management system 1 to the agent 2. As shown in FIG. 1B, the index is not specified in the GET-NEXT, and only OIDs for valueB and valuaC are designated.

Then, the agent 2 refers to the internal table 210 and transmits in response a value (100, 10) of the first row assigned "1" as an index to valueB and valuaC.

Subsequently, the external management system 1 performs a GET-NEXT using the index "1 '" from the response of the agent 2 as shown in FIG. 1C.

Then, the agent 2 refers to the internal table 210 and transmits, as a response, the values 300 and 30 of the second row in which "3" is assigned as an index to valueB and valuaC.

If a new row with a new index " 2 " is added to the internal table 210 as shown in FIG. 1D, the index " 3 " Second GET-NEXT.

However, the external management system does not know that a new row with index "2" has been created.

Also, the Row value at index "7" is changed as shown in Fig. 1F.

Thereafter, as shown in FIG. 1G, the agent 2 performs a fourth GET-NEXT using the index "5" of the response.

Then, the agent 2 refers to the internal table 210 and transmits, as a response, the values 777 and 77 of the fourth row assigned "7" as an index to valueB and valuaC. If the index "7" has not been modified, the agent 2 provides 700 and 70 as values of the fourth row.

Meanwhile, as shown in FIG. 1H, after the row having an index of "9" in the internal table 210 of the agent 2 is extinguished, the external management system 1 returns the index "of the response" as shown in FIG. 1I. When the fifth GET-NEXT is performed using the 7 ", the agent 2 determines that the inquiry about the internal table 210 is finished because the purpose of the internal table 210 is included as a response, and the external management system 1 ) No longer sends the request.

Accordingly, the value that the external management system 1 inquires from the agent 2 is as shown in FIG. 1J.

On the other hand, other methods have been proposed to solve the above problems.

There are SNMP-based network management systems using TCP, network management systems using FTP, network management systems using other protocols, and network management systems using HTTP. However, these management systems have to change the SNMP protocol or use another protocol. There was this.

Accordingly, the present invention is to solve the above-mentioned conventional problems, an object of the present invention by providing a fixed state information (Consistent State View) for the information of the table to the SNMP manager, the exact information at the point of request for inquiry It is to provide a fixed state information providing system and method in an SNMP-based network that can provide.

In addition, SNMP-based networks can use a protocol other than SNMP to provide a consistent state view, or provide a solution that does not violate the current standard without adding new protocols that are not in the standard. To provide a fixed state information providing system and method in the present invention.

According to an aspect of a system for providing fixed state information in an SNMP-based network according to the present invention for achieving the above object, a first request message for managing fixed state view from an external management system is provided. Upon receipt, the internal table is copied to generate a first copy table, while the processing of the first request message received from the external management system includes an agent processing through the first copy table.

Here, the first request message received by the agent is an SNMP GET-NEXT (Bulk) message.

In addition, when the first request message received through the external management system is out of the index range of the first copy table, the agent performs all processing on the first request message received from the external management system. It is determined that the first copy table is deleted.

And when the agent does not receive a subsequent request message from the external management system for any time while receiving the first request message from the external management system and performing an inquiry on the first copy table, the first copy table. Delete it.

When the agent receives the first request message from at least one external management system at the same time, the agent creates and shares one first copy table.

On the other hand, when the agent receives the first request message from any external management system to generate the first copy table, the agent then ends by transmitting an error message to the other external management system that has transmitted the first request message. .

The agent then determines the external management system at a TCP / IP layer, such as an IP address.

The agent, when receiving the first request message from at least one external management system, generates a first copy table each time the first request message is received.

According to an aspect of the method for providing fixed state information in an SNMP-based network according to the present invention, when the agent receives a first request message for managing fixed state view from an external management system, Copying the table to generate a first copy table; And after the agent inquires of the first copy table, responds to the corresponding external management system.

Here, the first request message is a GET-NEXT (Bulk) message of SNMP.

And when the agent inquires the first copy table and responds to the corresponding external management system, when the first request message received through the external management system is out of an index range of the first copy table. The agent determines that the agent has performed all processing for the first request message received from the external management system and deletes the first copy table.

In addition, when the agent inquires the first copy table and responds to the corresponding external management system, any time during which the agent receives the first request message from the external management system to perform an inquiry on the first copy table. If a subsequent request message has not been received from the external management system during this time, the first copy table generated by the agent is deleted.

Here, the step of copying the internal table by the agent to generate the first copy table may include: when the agent receives the first request message from at least one external management system at the same time, the agent generates one first copy table and shares the same. do.

The method may further include terminating by sending an error message to another external management system that has transmitted the first request message when receiving the first request message from any external management system to generate the first copy table. It includes more.

And wherein the agent determines the external management system at a TCP / IP layer, such as an IP address.

Meanwhile, in the agent copying the internal table and generating the first copy table, when the first request message is received from at least one external management system, the agent makes a first copy whenever the first request message is received. Create each table.

As described above, according to the system and method for providing fixed status information in an SNMP-based network according to the present invention, by providing consistent status information of a table from an SNMP external management system, it is possible to guarantee the consistency of the inquired information. It works.

Also, in providing consistent status information, it is possible to apply other protocols besides SNMP or to apply new protocols that are not in the standard, and does not violate existing standards. Therefore, it can be applied to existing systems without additional external interfaces. It has an effect.

Therefore, it solves the problem of not providing consistent status information in the SNMP network, and when designing a new system, it is possible to implement the characteristics that could be realized by using other protocols by using only SNMP, which reduces development period / effort and external management. There is an excellent effect to simplify the communication between the system and the agent.

Hereinafter, a preferred embodiment of a fixed state information providing system in an SNMP-based network according to the present invention will be described in detail with reference to the accompanying drawings. At this time, it will be understood by those of ordinary skill in the art that the system configuration described below is a system cited for the purpose of the present invention and does not limit the present invention to the following system.

2 is a diagram illustrating a configuration of a system for providing fixed state information in an SNMP-based network according to the present invention. The system for providing fixed state information in an SNMP-based network according to the present invention is an external management system 100. Agent 200. Here, the agent 200 may include an internal table 210 and a first copy table 220.

When the agent 200 receives the first request message for managing the fixed state view from the external management system 100, the agent 200 copies the internal table 210 to the first request message. Create a copy table 220.

The first request message received from the external management system 100 is processed through the first copy table 220. Here, the first request message received by the agent 200 is a GET-NEXT (Bulk) message of SNMP.

The agent 200 is received from the external management system 100 when the first request message received through the external management system 100 is out of an index range of the first copy table 220. The first copy table 220 is deleted by determining that all processing for the first request message has been performed.

In addition, the agent 200 receives a first request message from the external management system 100 and subsequently performs an inquiry from the external management system 100 during any time during the inquiry on the first copy table 220. If the request message is not received, the first copy table 220 is deleted.

When the agent 200 receives the first request message from at least one external management system 100 at the same time, the agent 200 generates and shares one first copy table 220.

On the other hand, when the agent 200 receives the first request message from any external management system 100 and generates the first copy table 220, the agent management system transmits the first request message. At 100-1, an error message is sent to terminate.

The agent 200 determines the external management system 100 in a TCP / IP layer such as an IP address.

Meanwhile, when the agent 200 receives the first request message from at least one external management system 100, the agent 200 may generate the first copy table 220 each time the first request message is received.

General functions and detailed operations of the above-described elements will be omitted, and the operations will be described based on operations corresponding to the present invention.

First, upon receiving a first request message for managing fixed state view from an external management system 100, the agent 200 copies the internal table 210 to the agent 200. 1 Create a copy table 220.

Here, the MIB of the internal table 210 is as shown in Figure 1a.

Here, the GET-BULK request is the same as performing multiple GET-NEXTs at once by specifying the MAX-REPEAT value, so only the method of using the GET-NEXT will be described.

After generating the first copy table 220, the agent 200 refers to the first copy table 220 for a GET-NEXT (first request message) received from the external management system 100. An SNMP response message thereof is transmitted to the external management system 100. This operation continues until the agent 200 receiving the first request message from the external management system 100 ends the operation for the GET-NEXT.

That is, since the external management system 100 does not know the index information of the internal table 210, the external management system 100 does not specify an index, specifies an OID for valueB and valueC, and transmits a GET-NEXT to the agent 200.

Then, the agent 200 refers to the first copy table 220 copied without referring to the internal table 210, and sends an SNMP response message to the value of the first row to which “1” is assigned as an index of valueB and valueC. To the external management system 100.

Then, the external management system 100 checks the index information "1" of the internal table 210 through the SNMP response message of the agent 200 and transmits a second GET-NEXT to the agent 200.

Then, the agent 200 refers to the copied first copy table 220 to the external management system 100 as an SNMP response message for the value of the second row to which "3" is assigned as an index of valueB and valueC. send.

The above operation is repeated and provided to the external management system 100 up to the index information "9" existing in the first copy table 220.

The agent 200, when the first request message received through the external management system 100 is out of the index range of the first copy table 220, from the external management system 100. The first copy table 220 is deleted by determining that all processing for the received first request message has been performed.

Meanwhile, the internal table 210 is updated by the agent 200 regardless of the first copy table 220.

If the index information "2" is additionally included as shown in FIG. 1D, the value value of the index is changed as shown in FIG. 1F, or the index information and value value are deleted as shown in FIG. 1H, Only the internal table 210 is changed according to the state, and the copied first copy table 220 is not changed.

Accordingly, the external management system 100 can query the information at the time of performing the initial GET-NEXT as shown in FIG. 1A.

If the first request message is received from the external management system 100 and a subsequent request message is not received from the external management system 100 for any time during the inquiry on the first copy table 220. In this case, the agent 200 deletes the first copy table 220.

If the first request message is simultaneously received from at least one external management system 100, the agent 200 generates one first copy table 220 and shares it.

On the other hand, the agent 200 receives the first request message from any external management system 100 to generate the first copy table 220 and then the first request message from the taboo management system 100-1. If is received, the error message is sent to the other part management system 100-1 and terminates.

The agent 200 determines the external management system 100 in a TCP / IP layer such as an IP address.

Meanwhile, when the agent 200 receives the first request message from at least one external management system 100, the agent 200 may generate the first copy table 220 each time the first request message is received.

Next, a method of providing fixed state information in an SNMP-based network according to the present invention having the above configuration will be described with reference to FIG. 3.

First, when the agent 200 receives the first request message for managing the fixed state view from the external management system 100, the agent 200 copies the internal table 210 to the first copy table 220. To generate (S1). Here, the first request message is a GET-NEXT (Bulk) message of SNMP.

Subsequently, the agent 200 queries the first copy table 220 and responds to the corresponding external management system 100 (S2).

Subsequently, when the first request message received through the external management system 100 is out of an index range of the first copy table 220, the agent 200 receives from the external management system 100. The first copy table 220 is deleted by determining that all processing for the first request message has been performed (S3).

On the other hand, a subsequent request message is not received from the external management system 100 during any time during the receiving of the first request message from the external management system 100 and performing an inquiry on the first copy table 220. If not, the first copy table 220 generated by the agent 200 is deleted.

The agent 200 may copy the internal table 210 to generate the first copy table 220 when the first request message is simultaneously received from at least one external management system 100. Agent 200 generates one first copy table 220 and shares it.

If the method, when receiving the first request message from any external management system 100 to generate the first copy table 220, and then, the other part management system 100-transmitted the first request message. 1) ends by sending an error message.

In the method for providing fixed state information in the SNMP-based network, the agent 200 determines the external management system 100 in a TCP / IP layer such as an IP address.

On the other hand, when the agent 200 copies the internal table 210 to generate the first copy table 220, when the first request message is received from at least one external management system 100, the agent Each time 200 generates the first copy table 220 each time a first request message is received.

Although the present invention has been described in detail only with respect to the specific embodiments described, it will be apparent to those skilled in the art that various changes and modifications can be made within the scope of the present invention, and such modifications and modifications belong to the appended claims. .

1A is a diagram illustrating an internal table in a system for providing status information in a conventional SNMP-based network.

1B, 1C, 1E, 1G, and 1I are diagrams illustrating a configuration and operation of a system for providing status information in a conventional SNMP-based network.

Figure 1d is a view showing the index information is added to the internal table in the state information providing system in a conventional SNMP-based network.

1F is a view showing a state in which index information is changed in an internal table in a state information providing system in a conventional SNMP-based network.

Figure 1h is a view showing a state in which the index information is deleted in the internal table in the state information providing system in a conventional SNMP-based network.

FIG. 1J is a diagram illustrating information queried from an agent by an external management system in a state information providing system in a conventional SNMP-based network.

FIG. 2 is a functional block diagram illustrating a detailed configuration of an optical network terminal in a system and method for providing fixed status information in an SNMP-based network according to FIG. 1.

3 is a flowchart illustrating a method of providing fixed status information in an SNMP-based network according to the present invention.

<Explanation of symbols for the main parts of the drawings>

100: external management system 200: agent

210: internal table 220: first copy table

Claims (16)

In the fixed status information providing system in the SNMP-based network, Upon receiving a first request message for managing fixed state view from an external management system, the internal table is copied to generate a first copy table, and the first request message received from the external management system is copied. The system for providing fixed status information in an SNMP-based network includes an agent processing through the first copy table. The method of claim 1, The first request message received by the agent is Fixed status information providing system in the SNMP-based network, characterized in that the GET-NEXT (Bulk) message of SNMP. The method of claim 1, The agent, When the first request message received through the external management system is out of the index range of the first copy table, it is determined that all processing for the first request message received from the external management system is performed. 1 Fixed state information providing system in the SNMP-based network, characterized in that for deleting the copy table. The method of claim 1, The agent, Deleting the first copy table when a subsequent request message is not received from the external management system for any time while receiving the first request message from the external management system and performing an inquiry on the first copy table. System for providing fixed status information in an SNMP-based network. The method of claim 1, The agent, When receiving a first request message from at least one external management system at the same time, a fixed state information providing system in the SNMP-based network, characterized in that for generating a first copy table and sharing it. The method of claim 1, The agent, When receiving the first request message from any external management system to generate the first copy table, the SNMP-based characterized in that the end of the transmission by sending an error message to the other external management system that sent the first request message. System for providing fixed status information in a network of networks. The method of claim 6, The agent, Fixed status information providing system in the SNMP-based network, characterized in that for determining the external management system in the TCP / IP layer such as IP address. The method according to any one of claims 1 to 5, The agent, And receiving a first request message from at least one external management system, each time generating a first copy table each time a first request message is received. In the SNMP-based network management method, If the agent receives a first request message for managing fixed state view from an external management system, copying an internal table to generate a first copy table; And And providing, by the agent, the inquiry of the first copy table, and responding to the corresponding external management system. The method of claim 9, The first request message, Method for providing fixed status information in an SNMP-based network, characterized in that the GET-NEXT (Bulk) message of SNMP. The method of claim 10, After the agent queries the first copy table and responds to the corresponding external management system, If the first request message received through the external management system is out of the index range of the first copy table, it is determined that the agent has performed all processing for the first request message received from the external management system. And providing the fixed state information in the SNMP-based network, wherein the first copy table is deleted. The method of claim 10, After the agent queries the first copy table and responds to the corresponding external management system, The first copy table generated by the agent when a subsequent request message is not received from the external management system for any time while receiving a first request message from the external management system and performing an inquiry on the first copy table. Fixed status information providing method in the SNMP-based network, characterized in that for deleting. The method of claim 10, The agent copying the internal table to create a first copy table, And when the first request message is received from at least one external management system at the same time, the agent creates and shares one first copy table. The method of claim 10, The method, If receiving the first request message from any external management system to create a first copy table, and then further comprising the step of sending an error message to the other external management system that sent the first request message to terminate the SNMP; A method of providing fixed state information in a based network. The method of claim 14, The method, And the agent determines the external management system at a TCP / IP layer such as an IP address. The method according to any one of claims 9 to 13, The agent copying the internal table to create a first copy table, When the first request message is received from at least one external management system, the agent generates a first copy table each time the first request message is received, providing fixed status information in the SNMP-based network. Way.

Images