WO2011134238A1

WO2011134238A1 - Method and device for processing simple network management protocol (snmp) request message

Info

Publication number: WO2011134238A1
Application number: PCT/CN2010/077626
Authority: WO
Inventors: 郭红涛; 王义安; 罗小妮; 强伟峰; 王彦华
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-04-27
Filing date: 2010-10-09
Publication date: 2011-11-03
Also published as: CN101834743A

Abstract

The present invention discloses a method and a device for processing a Simple Network Management Protocol (SNMP) request message. The method includes: obtaining the source IP and the Request-ID in the currently received SNMP request message, wherein different SNMP request messages which are received from the same source IP are uniquely identified by different Request-IDs; using the source IP and the Request-ID which are currently obtained as indexes to search in a SNMP management controlling module, wherein the SNMP management controlling module is used for storing information items and the information item includes the source IP and the Request-ID which are included in the previously received SNMP request message; and when the information item that includes the source IP and the Request-ID which are currently obtained is searched out, discarding the currently received SNMP request message. The present invention can effectively avoid the impact to the network element device when the network management device sends a SNMP request message to the network element device in the case that the flooding and the routing loopback exist in the network.

Description

SNMP request message processing method and device

Technical field

The present invention relates to the field of communications, and in particular, to an SNMP (Simple Network Management Protocol) request packet processing method and apparatus. Background technique

Nowadays, the development trend of the network is IP (Internet Protocol), and more and more IP-based devices. IP is not only used to carry traditional broadband services, but also to carry new voice services. The more network devices that use IP, the importance of managing network devices is self-evident. SNMP (Simple Network Management Protocol) is one of the most widely used network device management protocols.

SNMP specifies five protocol data units (PDUs) (that is, SNMP packets) for interaction between the network management device 11 and the network element device (ie, the agent side device) 12. As shown in Figure 1, it is specifically:

1) get-request: sent by the network management device to the network element device, where the network management device extracts one or more parameter values from the network element device;

2) Get the next request (get-next-request): sent by the network management device to the network element device, where the network management device extracts the next parameter value immediately following the current parameter value from the network element device;

3) set request (set-request): sent by the network management device to the network element device, used to set one or more parameter values of the network element device, so the network management device can remotely set the parameters of the network element device by using Set-Request;

4) Get response (get-response): After the network element device receives the get-request, get-next-request or set-request, the network element device returns one or more parameter values to the network management device.

5) Trap operation (trap): A packet sent by the NE device to notify the NMS that certain events occur.

In the above five types of SNMP packets, the first three types of packets are sent by the network management device to the network element device. The latter two types of packets are sent by the network element device to the network management device, and only the Trap type is used. An SNMP packet is an unsolicited message initiated by a network element device. It reports specific events, such as device startup, shutdown, and other changes to the network management device. Through the above five types of SNMP, SNMP provides three basic operations: Get network device information (Get: read operation), set network device parameter values (Set: write operation), and event report (Trap: trap operation) .

Get-request, Get-Next-Request, sent during the interaction between the network management device and the network element device.

The Get-Response and Set-Request protocol messages all contain an identifier (ID) field, which is used to match requests and responses, and SNMP assigns a globally unique ID to each request. For packets sent by the same network management device, the ID will not be duplicated for a short period of time. In this paper, the Get-Request, Get-Next-Request, or Set-Request type sent by the network management device is called the SNMP request, and the Get-Response type of the message sent by the network element device is called SNMP response message.

In the SNMP protocol, when there is a flooding and routing loop in the broadcast domain where the network element device is located, the data packet will be flooded to all the network element devices, and the network element device with the default route to the gateway will The packet is rerouted to the gateway, and the gateway again floods the packet to all network element devices in the broadcast domain. As shown in Figure 2, in the network environment where the above problem occurs, the network management device C sends an SNMP request packet to the network element device D. The SNMP request packet is sent to the network element device D through the intermediate network B. The SNMP request packet is also sent to the network element device A if the secondary encapsulated virtual local area network (VLAN) (QINQ) mechanism is incomplete or other reasons are present in the intermediate network B. If the network element device A If there is a default route to the intermediate network B, then the SNMP request will be sent back to the intermediate network B. Because of the flood of intermediate network B, the SNMP request is sent to the network element device D again. In this way, the network element device D receives many repeated SNMP request messages (the source IP address and ID field in the SNMP request message are the same), and the actual processing of many repeated requests causes the device to be busy. It even affects the normal operation of the device. This situation can be solved by solving the flood problem of the intermediate network B and the problem of the routing loop of the network element device A, but it is not completely guaranteed that the problem does not exist in the network environment.

Summary of the invention

The present invention provides a method and a device for processing an SNMP request packet, which solves the problem of actually processing a large number of repeated requests, and completely avoids the impact of repeated SNMP request packets on the network element device. The present invention provides a method for processing an SNMP request packet, including:

The source IP address and the request identifier (Request-ID) in the received SNMP request are obtained. The different SNMP request packets received from the same source IP address are uniquely identified by different Request-IDs. The current source IP address and Request are obtained. - ID is an index in the SNMP management control block for storing information items, the information items including source IP and Request-ID in the previously received SNMP request message;

When the information item including the current source IP address and the Request-ID is found, the currently received SNMP request packet is discarded.

Preferably, the method further comprises:

When the information item including the currently acquired source IP and Request-ID is not found, the currently obtained source IP and Request-ID are stored as new information items in the SNMP management control block, and the currently received SNMP is processed. Request a message.

Preferably, the method further includes: setting an aging timer corresponding to the information item stored in the SNMP management control block, and deleting the information item corresponding to the aging timer when the aging timer reaches the timing time.

Preferably, the number of different source IPs included in the information item in the SNMP management control block is not greater than the first set number, and the number of different information items of the same source IP is not greater than the second set number.

Preferably, before the storing the currently obtained source IP and the Request-ID as the new information item in the SNMP management control block, the method further includes:

When it is determined that the stored number of different information items including the currently acquired source IP is equal to the second set number, the information item including the currently acquired source IP having the longest storage time is deleted.

The storage of the new information item is skipped when it is determined that the number of different source IPs included in the stored information item is equal to the first set number.

The present invention also provides an SNMP request packet processing apparatus, including:

An SNMP management control block, configured to store an information item, the information item including previously received The source IP address and the request identifier (Request-ID) of the SNMP request.

The identifier information extracting unit is configured to obtain the source IP address and the Request-ID in the currently received SNMP request packet, where different SNMP request packets received from the same source IP are uniquely identified by different Request-IDs;

An identification information searching unit configured to index the currently obtained source IP and Request-ID

Finding in the SNMP management control block;

A packet discarding unit is configured to discard the currently received SNMP request packet when the information item including the currently obtained source IP address and the Request-ID is found.

Preferably, the SNMP request message processing device further includes:

An identification information learning unit, configured to include not including the currently acquired source IP and

When the information item of the Request-ID is used, the currently obtained source IP and Request-ID are stored as new information items in the SNMP management control block;

The message processing unit is configured to process the currently received SNMP request message when the information item including the currently obtained source IP address and the Request-ID is not found.

Preferably, the SNMP request message processing device further includes:

a timer setting unit configured to set an aging timer corresponding to an information item in the SNMP management control block;

An identification information aging unit is configured to delete an information item corresponding to the aging timer when the aging timer arrives at a timing time.

The number of different source IPs included in the information item in the SNMP management control block is not greater than the first set number, and the number of different information items of the same source IP is not greater than the second set number; The unit is further configured to: when determining that the stored number of different information items including the currently acquired source IP is equal to the second set number, deleting the information item including the currently acquired source IP that has the longest storage time; determining the stored information item When the number of different source IPs included is equal to the first set number, the storage of the new information item is skipped.

The SNMP management control block in the device is composed of an IP address queue and a transaction number queue corresponding to an entry in the IP address queue. Different entries in the IP address queue store different source IPs in the information item, and the same source IP address. The Request-ID in the information item is stored in the same transaction number queue. Medium.

The method and the device for processing the SNMP request packet provided by the present invention have the following beneficial effects: The problem of the repeated SNMP request message is solved from the perspective of the network element device, and the flooding and routing loopback may exist in the network. The impact on the NE device when the NMS sends an SNMP request packet to the NE device. BRIEF abstract

FIG. 1 is a schematic diagram of interaction between a network management device and a network element device (ie, a proxy device) in the prior art;

2 is a schematic diagram of a network environment in which a repeated SNMP request packet impacts a network element device in the prior art;

3 is a flowchart of a method for processing an SNMP request packet according to an embodiment of the present invention;

4 is a data structure diagram of an address queue and a transaction number queue according to an embodiment of the present invention; FIG. 5 is a flowchart of processing an SNMP request packet by a network element device according to an embodiment of the present invention;

FIG. 6 is a structural diagram of an apparatus for processing an SNMP request message according to an embodiment of the present invention.

Preferred embodiment of the invention

The SNMP request packet processing method and apparatus provided by the present invention are described in more detail below with reference to the accompanying drawings and embodiments.

SNMP request sent by the network management device ^艮文如 Get-request, Get-Next-Request or

The packet of the Set-Request type is a request packet from the upstream network management device. The agent-side network element device receives the SNMP request packet and processes the SNMP response packet. Therefore, repeated SNMP request packets have a greater impact on the NE device. The method and device for processing the SNMP request packet provided by the present invention are used to solve the impact of repeated SNMP request packets on the network element device in the case that the flooding and the routing loopback exist in the network.

As shown in FIG. 3, the present invention provides a method for processing an SNMP request packet, including: Step S301: Acquire a source IP and a Request-ID in a currently received SNMP request packet, The different SNMP request packets received from the same source IP address are uniquely identified by different Request-IDs. For the same network element device, multiple network management devices may manage the network element device through SNMP. The NE device distinguishes different network management devices by using the source IP address in the SNMP request packet. Different SNMP request packets received from the same source IP address are uniquely identified by different Request-IDs. Therefore, different SNMP request packets sent by the same network management device are distinguished according to the Request-ID in the SNMP request packet. Differentiating different Request requests from different network management devices according to the two pieces of information in the SNMP request message.

Step S302: Perform a search in the SNMP management control block by using the currently obtained source IP and the Request-ID as an index, where the SNMP management control block is used to store the information item, where the information item includes the source IP address of the previously received SNMP request message. And Request-ID.

The source IP address and the Request-ID learning mechanism in the SNMP request packet are set in the network element device, and the source IP address and the Request-ID in the previously received SNMP request message are stored as information items, and each information item includes a source. IP and Request-ID. When each SNMP request packet arrives, the source IP address and the Request-ID are extracted from the packet, and the current source IP address and Request-ID are used as indexes to search in the SNMP management control block.

Step S303, it is determined whether the information item including the currently obtained source IP and Request-ID is found, and if yes, step S304 is performed, otherwise, step S305 is performed;

Step S304: When the information item including the currently obtained source IP address and the Request-ID is found, the currently received SNMP request message is discarded.

The current source IP address and the Request-ID are indexed in the SNMP management control block, and the SNMP management control block determines whether the information source including the currently obtained source IP address and the Request-ID is stored, and the SNMP request can be determined. Whether the packet is a duplicate packet, if it is a duplicate packet, the packet is discarded. Even if there is a flood and routing loopback in the network, it will not cause too much impact on the network element device, thereby completely preventing the packet. The purpose of impacting network element equipment.

Preferably, the embodiment further includes a step S305, when the information item including the currently acquired source IP and the Request-ID is not found, storing the currently obtained source IP and Request-ID as new information items in the The SNMP management control block processes the currently received SNMP request message.

The SNMP management control block does not store the source IP and the current received SNMP request message. There are two cases for the information item of the Request-ID:

1) The information item of the source IP address in the currently received SNMP request message is stored, but the Request-ID stored in the information item is not the Request-ID in the currently received SNMP request message. The SNMP request packet has been received from the network management device corresponding to the source IP address, but the SNMP request packet corresponding to the Request-ID has not been received. Therefore, the SNMP request packet is not duplicated, and the SNMP request packet is processed according to a normal process. .

2) The information of the source IP address in the currently received SNMP request packet is not stored, indicating that the SNMP request packet has not been received from the network management device corresponding to the source IP, so the data packet is not duplicated, and the SNMP is processed according to a normal process. Request a message for processing.

In the embodiment of the present invention, in order to reduce the impact of the network abnormal packet on the network element device by discarding the repeated SNMP request packet, the SNMP request packet processing method is provided, as shown in FIG. 4, the SNMP management. The control block consists of an IP address queue and a transaction number queue corresponding to the entries in the IP address queue. The REQ in FIG. 4 is a shorthand for the Request-ID in this document, and the different REQs in the lower corner indicate different Request-IDs. Different entries in the IP address queue of the SNMP management control block store different source IPs in the information item. Each entry in the IP address queue corresponds to a transaction number queue. The Request-ID in the same source IP information is placed in the same transaction number queue.

Preferably, the embodiment further includes: setting an aging timer corresponding to the information item stored in the SNMP management control block, and deleting the information item corresponding to the aging timer when the aging timer reaches the timing time , that is, the information items learned in the aging SNMP management control block.

In the SNMP management control block of this embodiment, the IP address queue for storing the IP address of the network management device and the initial number of the transaction number queue for storing the Request-ID are empty. To save the storage space of the network element device, the SNMP management control block is preferably stored. The number of different source IPs (the length of the address queue) included in all the information items is not greater than the first set number, and the number of different information items including the same source IP (the length of the transaction number queue) is not greater than the set second number. Taking the above data structure as an example, it is preferable to store at most five IP addresses corresponding to the network management devices. The initial number of the transaction number queue for each IP address used to store the Request-ID is null, and the maximum length is 16 elements.

As shown in FIG. 5, in the embodiment, when the SNMP request packet arrives, the process of processing the SNMP request packet by the network element device specifically includes: Step S501: Extract the source IP and Request-ID fields in the SNMP request packet for the SNMP request message that is newly arrived from the network port.

Step S502: Search, by using the extracted source IP and Request-ID as an index, in the foregoing SNMP management control block;

Step S503, determining that the information items of the source IP and the Request-ID are already present in the SNMP management control block, and if yes, executing step S504, otherwise performing step S505;

Step S504, discarding the currently received SNMP request message, and returning to step S501.

Step S505: The extracted source IP address and the Request-ID are respectively learned into the SNMP management control block, and the aging timer of the information item is set, and the SNMP request packet is delivered to the normal processing flow to continue processing, and the process ends.

In step S502 of the embodiment, when the extracted source IP and the Request-ID are indexed in the SNMP management control block, the IP address queue of the storage network management device IP is preferably first retrieved by using the extracted source IP; If the IP address queue of the network management device IP is empty or the IP address queue of the storage network management device IP is not empty but the source IP address is not available, the request-ID cannot be retrieved. Step S505 is directly performed: First, the extracted source IP address is learned. Go to the IP address queue, learn the extracted Request-ID to the transaction number queue corresponding to the source IP, and set the aging timing of the information item.

In step S502, if the address queue of the storage network management device IP is retrieved by using the extracted source IP, if the address queue of the storage network management device IP is not empty and the source IP is retrieved, the transaction number queue corresponding to the source IP is searched. Extracted Request-ID; If the corresponding Request-ID is not found in the transaction number queue, step S505 is performed: learning the extracted Request-ID to the transaction number queue corresponding to the source IP, and setting the aging timing of the information item Device.

In the embodiment, when the length of the address queue and the transaction number queue is limited, when the learning is performed in step S505, it is determined that the number of different source IPs included in the stored information item is equal to the first set number, such as 5, The learning process of the information item will be skipped and the subsequent processing will be directly performed. That is, after the number of learned IP addresses exceeds the length of the address queue, the new IP address can be learned only after the number of queues corresponding to the IP address of the longer time is aged and the number of IP addresses is less than the length of the address queue. When learning is performed in step S505, different information items including the acquired source IP are determined. When the number is equal to the second set number, the information item including the acquired source IP having the longest storage time is deleted. That is, after the maximum number of Request-ID queues corresponding to the source IP is reached, the oldest learned Request-ID in the transaction number queue corresponding to the source IP is deleted, and the newly learned Request-ID is added.

Further, each time the oldest learned Request-ID in the transaction number queue is deleted, the corresponding timer is first destroyed, and then the Request-ID is deleted.

The execution flow of the aging timer being triggered and destroyed in this embodiment is: 1) setting the aging timer of the information item when setting the specific Request-ID entry of the information item in the transaction number queue; 2) the aging The timer expires, and the information item entry corresponding to the aging timer is deleted. 3) The aging timer of the information item is destroyed.

Further, after the aging timer of the information item in the 2) expires, the corresponding Request-ID entry in the column of the transaction number pair is deleted, and the process is also called the aging of the transaction number queue entry, or The aging of the Request-ID; check whether the transaction number queue of the same IP address after deleting the Request-ID entry is empty; if the column is empty, delete the corresponding IP address entry in the address queue. This process is called network management IP. Aging.

In addition, in this embodiment, the default time of the aging of the Request-ID corresponding to the IP address is 30 seconds, and the time passes the time. The machine interface can be flexibly configured according to the needs of the system.

According to another embodiment of the present invention, an SNMP request message processing apparatus is provided. As shown in FIG. 6, the apparatus includes: an SNMP management control block 601 configured to store an information item, where the information item includes previous reception. The source IP address and the Request-ID in the SNMP request message; the identifier information extracting unit 602 is configured to obtain the source IP and the Request-ID in the currently received SNMP request message, where different SNMP request reports are received from the same source IP address. The message is uniquely identified by using a different Request-ID; the identifier information searching unit 603 is configured to perform the search in the SNMP management control block with the currently obtained source IP and Request-ID as indexes; the message discarding unit 604 is set to When the information item including the current source IP address and the Request-ID is found, the currently received SNMP request packet is discarded.

Preferably, the apparatus further includes: an identification information learning unit 605 configured to use the currently obtained source IP and Request-ID as new information when the information item including the currently acquired source IP and Request-ID is not found. The item is stored in the SNMP management control block; the message processing unit 606 is configured to: when the information item including the currently acquired source IP and Request-ID is not found, The current received SNMP request message. The timer setting unit 607 is configured to set an aging timer corresponding to the information item in the SNMP management control block, and the identifier information aging unit 608 is configured to delete the aging timer when the aging timer reaches the timing time. The information item corresponding to the aging timer implements aging of the information items stored in the SNMP management control block 601.

In order to save space for storing information items of the device, the number of different source IPs included in the information item in the SNMP management control block is not greater than the first set number, and the number of different information items including the same source IP is not greater than the second set number. The identifier information learning unit 605 is further configured to: when determining that the stored number of different information items including the currently acquired source IP is equal to the second set number, deleting the information item including the currently acquired source IP that has the longest storage time And determining to store the new information item when the number of different source IPs included in the stored information item is equal to the first set number.

In a specific implementation, the SNMP management control block is composed of an IP address queue and a transaction number queue corresponding to an entry in the IP address queue, where different entries in the IP address queue store different source IPs in the information item, the same The Request-ID in the information item of the source IP is stored in the same transaction number queue. The source IP and the Request-ID corresponding to the IP address are learned in the form of a data structure.

One of ordinary skill in the art will appreciate that all or a portion of the steps above may be accomplished by a program to instruct the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Industrial applicability

The method and device for processing the SNMP request packet provided by the present invention can solve the problem of the repeated SNMP request message from the perspective of the network element device, and can effectively avoid the network management device when the flooding and routing loopback exist in the network. Impact on the NE device when sending an SNMP request packet to the NE device.

Claims

Claim

A method for processing a simple network management protocol (SNMP) request message, the method comprising: obtaining a source IP and a request identifier (Request-ID) in a currently received SNMP request, wherein different received from the same source IP The SNMP request packet is uniquely identified by using a different Request-ID; the current management source IP address and the Request-ID are used as an index to be searched in the SNMP management control block, where the SNMP management control block is used to store information items, and the information items include The source IP and Request-ID in the previously received SNMP request 4;

2. The method of claim 1 further comprising:

3. The method of claim 2, the method further comprising:

And setting an aging timer corresponding to the information item stored in the SNMP management control block, and deleting an information item corresponding to the aging timer when the aging timer reaches a timing time.

The method of claim 3, wherein the number of different source IPs included in the information item in the SNMP management control block is not greater than the first set number, and the number of different information items of the same source IP is not greater than Two sets the number.

The method according to claim 4, wherein before storing the currently acquired source IP and Request-ID as new information items in the SNMP management control block, the method further comprises: determining the stored When the number of different information items including the currently obtained source IP is equal to the second set number, the information item including the currently acquired source IP having the longest storage time is deleted.

6. The method according to claim 4, wherein before storing the currently acquired source IP and Request-ID as new information items in the SNMP management control block, the method further comprises: determining the stored When the number of different source IPs included in the information item is equal to the first set number, the storage of the new information item is skipped.

7. A Simple Network Management Protocol (SNMP) request message processing device, the device comprising:

An SNMP management control block, configured to store an information item, where the information item includes a previously received SNMP request, a source IP address, and a request identifier (Request-ID);

An identifier information searching unit configured to perform searching in the SNMP management control block by using the currently obtained source IP and Request-ID as indexes;

8. The apparatus of claim 7, the apparatus further comprising:

And an identifier information learning unit configured to store the currently acquired source IP and Request-ID as new information items to the SNMP management control block when the information item including the currently acquired source IP and Request-ID is not found. Medium; and

9. The device of claim 8, the device further comprising:

The device of claim 8, wherein the number of different source IPs included in the information item in the SNMP management control block is not greater than the first set number, and the number of different information items of the same source IP is not greater than Second, set the number,

The identifier information learning unit is further configured to: when it is determined that the stored number of different information items including the currently obtained source IP is equal to the second set number, delete the information item including the currently acquired source IP that has the longest storage time; When the stored information item includes the number of different source IPs equal to the first set number, the storage of the new information item is skipped.

The device according to any one of claims 7 to 10, wherein the SNMP management control block is composed of an IP address queue and a transaction number queue corresponding to an entry in an IP address queue, where the IP address queue is Different entries store different source IPs in the information item, and the Request-ID in the information item of the same source IP is stored in the same transaction number queue.