CN116155676B - A coordination method and component of SNMP protocol and RESTful protocol - Google Patents

A coordination method and component of SNMP protocol and RESTful protocol Download PDF

Info

Publication number
CN116155676B
CN116155676B CN202310156231.0A CN202310156231A CN116155676B CN 116155676 B CN116155676 B CN 116155676B CN 202310156231 A CN202310156231 A CN 202310156231A CN 116155676 B CN116155676 B CN 116155676B
Authority
CN
China
Prior art keywords
snmp
protocol
restful
alarm
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202310156231.0A
Other languages
Chinese (zh)
Other versions
CN116155676A (en
Inventor
贺学文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Hollysys Automation Co Ltd
Original Assignee
Hangzhou Hollysys Automation Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Hollysys Automation Co Ltd filed Critical Hangzhou Hollysys Automation Co Ltd
Priority to CN202310156231.0A priority Critical patent/CN116155676B/en
Publication of CN116155676A publication Critical patent/CN116155676A/en
Application granted granted Critical
Publication of CN116155676B publication Critical patent/CN116155676B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Communication Control (AREA)

Abstract

The application discloses a coordination method and a coordination component of an SNMP protocol and a RESTful protocol, which relate to the technical field of communication protocols and comprise the steps of setting an on-line switch at an SMNP interface, shielding concurrent message storms of a plurality of SNMP devices by using the on-line switch, communicating with the SNMP devices through an SNMP agent module, determining corresponding target field operation of the RESTful protocol based on a preset field mapping relation and first field operation of the SNMP devices by the SNMP agent module, and determining corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and first alarm operation of the SNMP device by the SNMP agent module. The method can shield SNMP storm on line, so that the communication between SNMP and SNMP equipment is converted into the communication between the Restful and the SNMP equipment, and the request of interface mutual conversion between the SNMP and the Restful is realized.

Description

SNMP protocol and RESTful protocol coordination method and assembly
Technical Field
The invention relates to the technical field of communication protocols, in particular to a coordination method and a coordination component of an SNMP protocol and a RESTful protocol.
Background
SNMP (Simple Network Management Protocol ) is a standard protocol specifically designed for managing network nodes (servers, workstations, routers, switches, HUBS, etc.) in an IP network. The SNMP network management framework based on TCP/IP is the current standard in industry. RESTful (Representational STATE TRANSFER) is an emerging IT interface specification, while SNMP is a traditional network management communication interface specification, and there is a converged demand for RESTful and SNMP at IIot in the open today. SNMP is generally classified into multiple levels according to importance, and as with other network protocols, SNMP has the possibility of a message storm, and once multiple SNMP devices generate a concurrent storm, as a RESTful interface layer converged at a higher level, an exponential message storm may be generated to impact the stability of IIot systems. That is, there is both the interface inter-conversion requirements of SNMP and RESTful, and the underlying SNMP message storm screening requirements. Traditionally, these two requirements often fall into different software or hardware products.
In summary, how to realize on-line defending against message storm to ensure the stability of IIot systems and simultaneously realize the interface inter-conversion of SNMP and RESTful, and avoiding the use of different hardware or software is a technical problem to be solved in the field.
Disclosure of Invention
Therefore, the present invention aims to provide a method and a component for coordinating SNMP protocol and RESTful protocol, which can realize the on-line defense of message storm to ensure the stability of IIot systems, and simultaneously realize the interface conversion between SNMP and RESTful, and avoid using different hardware or software. The specific scheme is as follows:
in a first aspect, the present application discloses a coordination method of SNMP protocol and RESTful protocol, which is applied to a preset protocol coordination gateway, and includes:
setting an on-line switch at an SMNP interface so as to shield concurrent message storm of a plurality of SNMP devices by using the on-line switch;
Communicating with the SNMP equipment through an SNMP agent module, and determining a corresponding target field operation of the RESTful protocol based on a preset field mapping relation and a first field operation of the SNMP equipment by the SNMP agent module;
and determining the corresponding target alarm operation of the RESTful protocol for the first alarm operation of the SNMP equipment based on a preset alarm level mapping rule by the SNMP agent module.
Optionally, before the communication with the SNMP device through the SNMP agent module, the method further includes:
performing relation mapping on the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain a preset field mapping relation between the SNMP protocol and the RESTful protocol;
And performing relation mapping on the first alarm operation of the SNMP protocol and the second alarm field operation of the RESTful protocol to obtain preset alarm level mapping rules of the SNMP protocol and the RESTful protocol.
Optionally, the mapping the relationship between the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain a preset field mapping relationship between the SNMP protocol and the RESTful protocol includes:
the method comprises the steps of performing relation mapping on Get operation and GetNext operation of an SNMP protocol and Get operation of a RESTful protocol, performing relation mapping on Trap operation of the SNMP protocol and Put operation and Post operation of the RESTful protocol, and performing relation mapping on Set operation of the SNMP protocol and Post operation and Delete operation of the RESTful protocol to obtain a preset field mapping relation of the SNMP protocol and the RESTful protocol.
Optionally, in the SMNP interface setting on-line switching process, the method further includes:
and configuring a flow threshold and a synchronization threshold in the SMNP interface so as to discard the communication data exceeding the synchronization threshold when the acquired communication data quantity of the SNMP device is larger than the synchronization threshold.
Optionally, the determining, based on a preset alarm level mapping rule and the SNMP agent module, the corresponding target alarm operation of the RESTful protocol for the first alarm operation of the SNMP device includes:
And when the alarm flow of the SNMP equipment sent by the SNMP agent module is received to be larger than the flow threshold, generating REST alarm information for the alarm flow based on a preset alarm level mapping rule.
Optionally, after generating REST alarm information for the alarm traffic based on the preset alarm level mapping rule, the method further includes:
And screening out the target alarm flow with the highest alarm level from the alarm flow corresponding to the REST alarm information, and storing the target alarm flow in a RESTful push thread pool so that the RESTful push thread pool submits the target alarm flow to a RESTful server according to a preset sequence.
Optionally, the method for coordinating the SNMP protocol with the RESTful protocol further includes:
Setting a RESTful push thread pool for the RESTful protocol push and the decoupled SNMP protocol receiving in the preset protocol coordination gateway.
In a second aspect, the present application discloses a coordination device for SNMP protocol and RESTful protocol, which is applied to a preset protocol coordination gateway, and includes:
The storm shielding module is used for setting an on-line switch at the SMNP interface so as to shield the concurrent message storms of a plurality of SNMP devices by using the on-line switch;
The field operation determining module is used for communicating with the SNMP equipment through the SNMP agent module and determining the corresponding target field operation of the RESTful protocol on the basis of a preset field mapping relation and the first field operation of the SNMP equipment by the SNMP agent module;
and the alarm operation determining module is used for determining the corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and the first alarm operation of the SNMP agent module on the SNMP equipment.
In a third aspect, the present application discloses an electronic device, comprising:
A memory for storing a computer program;
a processor for executing the computer program to implement the steps of the disclosed SNMP protocol and RESTful protocol coordination method.
In a fourth aspect, the present application discloses a computer readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the steps of the previously disclosed SNMP protocol and RESTful protocol coordination method.
The application discloses a coordination method of an SNMP protocol and a RESTful protocol, which is applied to a preset protocol coordination gateway and comprises the steps of setting an on-line switch at an SMNP interface so as to shield concurrent message storms of a plurality of SNMP devices by using the on-line switch, communicating with the SNMP devices through an SNMP agent module, determining corresponding target field operation of the RESTful protocol based on a preset field mapping relation and first field operation of the SNMP devices by the SNMP agent module, and determining corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and first alarm operation of the SNMP devices by the SNMP agent module. Therefore, the on-line switch is arranged on the SNMP interface, so that the SNMP storm can be shielded on line, and then the communication between the SNMP and the SNMP equipment is converted into the communication between the Restful and the SNMP equipment through the mapping relations such as field mapping, alarm level mapping and the like between the SNMP protocol and the Restful protocol, namely, the request of the interface mutual conversion between the SNMP and the Restful is realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a coordination method of SNMP protocol and RESTful protocol disclosed in the present application;
FIG. 2 is a flow chart of a method for SNMP data acquisition disclosed in the present application;
FIG. 3 is a diagram of a SNMP message structure disclosed in the present application;
Fig. 4 is a flowchart of a gateway and a coordination method for coordinating SNMP and RESTful according to the present application;
Fig. 5 is a flowchart of a specific coordination method of SNMP protocol and RESTful protocol disclosed in the present application;
fig. 6 is a schematic structural diagram of a coordination device of SNMP protocol and RESTful protocol disclosed in the present application;
fig. 7 is a block diagram of an electronic device according to the present disclosure.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
SNMP is a standard protocol specifically designed for managing network nodes (servers, workstations, routers, switches, HUBS, etc.) in an IP network. The SNMP network management framework based on TCP/IP is the current standard in industry.
RESTful is an emerging IT interface specification, while SNMP is a traditional network management communication interface specification, and there is a converged demand for RESTful and SNMP at IIot in the past. SNMP is generally classified into multiple levels according to importance, and as with other network protocols, SNMP has the possibility of a message storm, and once multiple SNMP devices generate a concurrent storm, as a RESTful interface layer converged at a higher level, an exponential message storm may be generated to impact the stability of IIot systems. That is, there is both the interface inter-conversion requirements of SNMP and RESTful, and the underlying SNMP message storm screening requirements. Traditionally, these two requirements often fall into different software or hardware products.
Therefore, the application provides a coordination scheme of SNMP protocol and RESTful protocol, which can realize the on-line defense of message storm, ensure the stability of IIot system, realize the interface interconversion of SNMP and RESTful and avoid using different hardware or software.
Referring to fig. 1, the embodiment of the invention discloses a coordination method of SNMP protocol and RESTful protocol, which is applied to a preset protocol coordination gateway and comprises the following steps:
And S11, setting an on-line switch at an SMNP interface so as to shield concurrent message storms of a plurality of SNMP devices by using the on-line switch.
In this embodiment, by setting a corresponding on-line switch on the SNMP interface for on-line screening of SNMP message storms, it can be understood that, because there are multiple SNMP devices, there may be concurrent messages generated by multiple SNMP devices at the same time, and as an upper layer Restful interface layer, when receiving the concurrent messages of multiple SNMP devices, an exponential message storm may be generated, which impacts the stability of the IIOT system, so that in the SNMP interface between the SNMP device layer and the SNMP protocol, a corresponding on-line switch for screening SNMP message storms is set.
And step S12, communicating with the SNMP equipment through an SNMP agent module, and determining the corresponding target field operation of the RESTful protocol on the basis of a preset field mapping relation and the first field operation of the SNMP equipment by the SNMP agent module.
In this embodiment, the SNMP agent module communicates with the SNMP device, and it can be understood that in the SNMP protocol, the SNMP agent module is mainly composed of an SNMP management program and an SNMP agent module, and the SNMP agent module is running on each managed SNMP device, and is responsible for counting each item of information of the SNMP device, interacting with the SNMP management program, receiving and executing a command of the SNMP management program, and uploading various local network information. The SNMP management program and the SNMP agent module are loosely coupled, and communication between the two modules is completed through UDP protocol. In general, an SNMP manager sends various commands to an SNMP agent module through a UDP protocol, and when the SNMP agent module receives a command, the SNMP agent module returns parameters required by the SNMP manager. But when the SNMP agent module detects the abnormality of the network element, the SNMP agent module can actively send a message to the SNMP management program to announce the current abnormality. As shown in fig. 2, the SNMP data acquisition flow, that is, a process of communicating between the SNMP management program and the SNMP agent program through the UDP protocol, the SNMP management program issues a corresponding instruction to acquire communication data of the SNMP device. And determining the corresponding target field operation of the RESTful protocol on the basis of a preset field mapping relation and the first field operation of the SNMP device by the SNMP agent module. It can be understood that when the SNMP agent module communicates with the SNMP device, in a specific embodiment, when the RESTful protocol issues certain field operation instructions to the SNMP device, the RESTful protocol needs to perform field conversion on the target field operation and based on a preset field mapping relationship, that is, obtain a first field operation, so that the SNMP agent module issues instructions to the SNMP device by using the first field operation. In another specific embodiment, if the SNMP agent module actively detects that the SNMP device has an abnormal condition, that is, actively reports abnormal data, the SNMP agent module still needs to convert the first field operation of the SNMP device into the second field operation of RESTful based on the preset field operation instruction. As shown in fig. 3, the message structure of the SNMP protocol specifically comprises an IP header and a UDP datagram, where the UDP datagram comprises a UDP header and an SNMP message, and in the SNMP message specifically comprises a version number, a community, a PDU type, a request identifier, an error state, an error index, and a variable name value pair, and in SNMPv1 specifically comprises a PDU type, a trap header, and a variable binding portion, where the trap header comprises an IP address of an enterprise or an agent, a trap type, a specific code, and a timestamp. The variable binding is then a variable name value pair.
In this embodiment, before the communication between the SNMP agent module and the SNMP device, the method further includes performing a relationship mapping between a first field operation of the SNMP protocol and a second field operation of the RESTful protocol to obtain a preset field mapping relationship between the SNMP protocol and the RESTful protocol, and performing a relationship mapping between a first alarm operation of the SNMP protocol and a second alarm field operation of the RESTful protocol to obtain a preset alarm level mapping rule between the SNMP protocol and the RESTful protocol. It can be understood that in order to realize the interface interchange between the SNMP protocol and the RESTful protocol, the field operation of the SNMP protocol and the field operation of the RESTful protocol need to be mapped and configured, and the alarm interface of the SNMP protocol and the alarm level of the RESTful protocol are mapped and configured, specifically, the SNMP protocol and the RESTful protocol mapping fields are configured one by one, and the combination of multiple mapping fields of the SNMP protocol and one field of the RESTful can also be realized. The field map represents, for example, the table 1:
TABLE 1
The alarm levels in SNMP, such as normal, slight, important, serious and RESTful alarm level mapping rules, are subjected to rule mapping configuration, and the relation mapping is carried out on the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain the preset field mapping relation between the SNMP protocol and the RESTful protocol, wherein the relation mapping is carried out on Get operation and GetNext operation of the SNMP protocol and Get operation of the RESTful protocol, the relation mapping is carried out on Trap operation of the SNMP protocol and Put operation and Post operation of the RESTful protocol, and the relation mapping is carried out on Set operation of the SNMP protocol and Post operation and Delete operation of the RESTful protocol to obtain the preset field mapping relation between the SNMP protocol and the RESTful protocol.
And step S13, determining a corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and a first alarm operation of the SNMP agent module on the SNMP equipment.
In this embodiment, when the SNMP agent module communicates with the SNMP device and the SNMP device uploads the flow data, the alarm operation of the SNMP interface on the current flow data needs to be converted into the target alarm operation of the RESTful protocol based on the preset alarm level mapping rule, that is, the target alarm operation is obtained, so that the corresponding processing is performed on the current flow data through the RESTful service module.
Referring to fig. 4, the interface of the RESTful protocol and the SNMP protocol is coordinated by a preset protocol coordination gateway, specifically, the preset protocol coordination gateway comprises a RESTful proxy, a RESTful message coding and decoding module, a RESTful/SNMP protocol conversion module, an SNMP message coding and decoding module and an SNMP proxy module, when various SNMP devices of an SNMP device layer communicate with the SNMP proxy module, in order to enable the RESTful interface layer to perform instruction control on the SNMP devices or process flow data sent by the SNMP, the SNMP device is subjected to coding and decoding by the SNMP message coding and decoding module in the SNMP/RESTful gateway, then the SNMP/RESTful message conversion is performed by the arrival protocol conversion module, then the RESTful proxy module is reached, and finally the RESTful service module communicates with the RESTful service module to realize the control on the SNMP devices.
The application discloses a coordination method of an SNMP protocol and a RESTful protocol, which is applied to a preset protocol coordination gateway and comprises the steps of setting an on-line switch at an SMNP interface so as to shield concurrent message storms of a plurality of SNMP devices by using the on-line switch, communicating with the SNMP devices through an SNMP agent module, determining corresponding target field operation of the RESTful protocol based on a preset field mapping relation and first field operation of the SNMP devices by the SNMP agent module, and determining corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and first alarm operation of the SNMP devices by the SNMP agent module. Therefore, the on-line switch is arranged on the SNMP interface, so that the SNMP storm can be shielded on line, and then the communication between the SNMP and the SNMP equipment is converted into the communication between the Restful and the SNMP equipment through the mapping relations such as field mapping, alarm level mapping and the like between the SNMP protocol and the Restful protocol, namely, the request of the interface mutual conversion between the SNMP and the Restful is realized.
Referring to fig. 5, an embodiment of the present invention discloses a specific coordination method of SNMP protocol and RESTful protocol, and compared with the previous embodiment, the present embodiment further describes and optimizes the technical solution. Specific:
And S21, configuring a flow threshold and a synchronization threshold in the SMNP interface so as to discard the communication data exceeding the synchronization threshold when the acquired communication data quantity of the SNMP device is larger than the synchronization threshold.
In this embodiment, two switches, namely a flow threshold a and a synchronization threshold B, are configured in each SNMP interface, and when communication data is synchronized, communication data exceeding the synchronization threshold B is discarded, and SNMP alarm information (such as trap information) is dynamically received, so as to detect whether the alarm flow reaches the flow threshold.
And S22, when the alarm flow of the SNMP equipment sent by the received SNMP agent module is larger than the flow threshold, generating REST alarm information for the alarm flow based on a preset alarm level mapping rule.
In this embodiment, if the alarm traffic exceeds the traffic threshold a, a REST alarm message is generated internally to prompt the SNMP traffic abnormality and provide a corresponding alarm traffic processing scheme for the SNMP interface, for example, discard all SNMP messages after which all alarm traffic exceeds the traffic threshold a.
And S23, screening out the target alarm flow with the highest alarm level from the alarm flows corresponding to the REST alarm information, and storing the target alarm flow in a RESTful push thread pool so that the RESTful push thread pool submits the target alarm flow to a RESTful server according to a preset sequence.
In this embodiment, only the alarm of the highest alarm level is screened out for all the information that the alarm flow exceeds the flow threshold A, and the screened alarm flow of the highest alarm level only accounts for less than 30% of the total alarm flows, and the target alarm flow of the screened highest alarm level does not exceed the flow threshold A, the REST alarm flows are discarded in situ, the screened alarm flow of the highest alarm level meeting the above conditions is put into a local REST buffer pool and submitted to REST SERVER end sequentially by the REST thread pool, and the SNMP alarm flow of the SNMP interface is continuously monitored, and the square is restored to normal only when the flow is lower than k.A, wherein k is 0.5, 1.
In this embodiment, a RESTful push thread pool for the RESTful protocol push and the SNMP protocol receive decoupling is set in the preset protocol coordination gateway. It can be understood that the preset protocol coordination gateway locally sets a RESTful push thread pool, realizes front and rear ends with SNMP, realizes REST push and SNMP receiving decoupling, configures SNMP alarm level dynamic screening at each SNMP interface, realizes dynamic REST conversion of different SNMP alarms, and does not need configuration modification.
Therefore, the SNMP and RESTful inter-conversion function provided by the gateway is coordinated through the preset protocol, and the nearest storm shielding function for the underlying SNMP message is also provided, so that the self-adaptive gateway is a self-adaptive gateway for the high-elasticity SNMP and the RESTful, is simple and easy to understand, does not need to rely on high-performance software and hardware, and can be suitable for any software/hardware platform.
Referring to fig. 6, the application also correspondingly discloses a coordination device of SNMP protocol and RESTful protocol, which is applied to a preset protocol coordination gateway, and comprises:
a storm shielding module 11, configured to set an on-line switch at an SMNP interface, so as to shield a concurrent message storm of a plurality of SNMP devices by using the on-line switch;
a field operation determining module 12, configured to communicate with the SNMP device through an SNMP agent module, and determine a corresponding target field operation of the RESTful protocol for a first field operation of the SNMP device based on a preset field mapping relationship and the SNMP agent module;
an alarm operation determining module 13, configured to determine a corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and a first alarm operation of the SNMP agent module on the SNMP device.
The application discloses an on-line switch arranged on an SMNP interface so as to shield a concurrent message storm of a plurality of SNMP devices by utilizing the on-line switch, the on-line switch is communicated with the SNMP devices through an SNMP agent module, a corresponding target field operation of the RESTful protocol is determined on the basis of a preset field mapping relation and a first field operation of the SNMP devices by the SNMP agent module, and a corresponding target alarm operation of the RESTful protocol is determined on the basis of a preset alarm level mapping rule and the first alarm operation of the SNMP devices by the SNMP agent module. Therefore, the on-line switch is arranged on the SNMP interface, so that the SNMP storm can be shielded on line, and then the communication between the SNMP and the SNMP equipment is converted into the communication between the Restful and the SNMP equipment through the mapping relations such as field mapping, alarm level mapping and the like between the SNMP protocol and the Restful protocol, namely, the request of the interface mutual conversion between the SNMP and the Restful is realized.
Further, the embodiment of the present application further discloses an electronic device, and fig. 7 is a block diagram of an electronic device 20 according to an exemplary embodiment, where the content of the figure is not to be considered as any limitation on the scope of use of the present application.
Fig. 7 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present application. The electronic device 20 may include, in particular, at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input-output interface 25, and a communication bus 26. The memory 22 is configured to store a computer program, which is loaded and executed by the processor 21 to implement relevant steps in the SNMP protocol and RESTful protocol coordination method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide working voltages for each hardware device on the electronic device 20, the communication interface 24 is capable of creating a data transmission channel with an external device for the electronic device 20, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein, and the input/output interface 25 is configured to obtain external input data or output data to the external device, and the specific interface type of the input/output interface may be selected according to the specific application needs and is not specifically limited herein.
Processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 may be implemented in at least one hardware form of DSP (DIGITAL SIGNAL Processing), FPGA (Field-Programmable gate array), PLA (Programmable Logic Array ). The processor 21 may also include a main processor, which is a processor for processing data in a wake-up state, also called a CPU (Central Processing Unit ), and a coprocessor, which is a low-power processor for processing data in a standby state. In some embodiments, the processor 21 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 21 may also include an AI (ARTIFICIAL INTELLIGENCE ) processor for processing computing operations related to machine learning.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon may include an operating system 221, a computer program 222, and the like, and the storage may be temporary storage or permanent storage.
The operating system 221 is used for managing and controlling various hardware devices on the electronic device 20 and the computer program 222, so as to implement the operation and processing of the processor 21 on the mass data 223 in the memory 22, which may be Windows Server, netware, unix, linux, etc. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the SNMP protocol and RESTful protocol coordination method performed by the electronic device 20 disclosed in any of the previous embodiments. The data 223 may include, in addition to data received by the electronic device and transmitted by the external device, data collected by the input/output interface 25 itself, and so on.
Furthermore, the application also discloses a computer readable storage medium for storing a computer program, wherein the computer program realizes the coordination method of the SNMP protocol and the RESTful protocol when being executed by a processor. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application. The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The above detailed description of the coordination method and the component of the SNMP protocol and the RESTful protocol provided by the present invention has been provided, and specific examples are used herein to illustrate the principles and implementations of the present invention, and the above description of the examples is only for aiding in understanding the method and the core concept of the present invention, and meanwhile, for those skilled in the art, according to the concept of the present invention, there are variations in the specific implementations and application ranges, so that the disclosure should not be interpreted as limiting the present invention.

Claims (8)

1.一种SNMP协议与RESTful协议协调方法，其特征在于，应用于预设协议协调网关，包括：1. A method for coordinating SNMP and RESTful protocols, characterized in that it is applied to a preset protocol coordination gateway, comprising: 在SMNP接口设置在线开关，以便利用所述在线开关屏蔽多个SNMP设备的并发消息风暴；其中，所述SMNP接口位于SNMP设备层与SNMP协议之间，所述SNMP协议包括SNMP管理程序和SNMP代理模块，所述SNMP代理模块运行在各个被管理的SNMP设备之上，所述SNMP代理模块与所述SNMP管理程序通过UDP协议进行通信交互，接收并执行所述SNMP管理程序的命令；An online switch is set at the SMNP interface so as to use the online switch to shield concurrent message storms of multiple SNMP devices; wherein the SMNP interface is located between the SNMP device layer and the SNMP protocol, the SNMP protocol includes an SNMP management program and an SNMP agent module, the SNMP agent module runs on each managed SNMP device, the SNMP agent module communicates and interacts with the SNMP management program through the UDP protocol, and receives and executes commands of the SNMP management program; 通过SNMP代理模块与所述SNMP设备进行通信，并基于预设字段映射关系以及所述SNMP代理模块对所述SNMP设备的第一字段操作确定对应的所述RESTful协议的目标字段操作；Communicate with the SNMP device through an SNMP agent module, and determine a corresponding target field operation of the RESTful protocol based on a preset field mapping relationship and a first field operation of the SNMP agent module on the SNMP device; 基于预设告警级别映射规则以及所述SNMP代理模块对所述SNMP设备的第一告警操作确定对应的所述RESTful协议的目标告警操作；Determine the corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and the first alarm operation of the SNMP agent module on the SNMP device; 所述通过SNMP代理模块与SNMP设备进行通信之前，还包括：Before communicating with the SNMP device through the SNMP agent module, the method further includes: 配置所述SNMP协议中告警级别的单个trap信息字段与所述RESTful告警级别的单个trap信息字段之间的第一映射关系，和配置所述SNMP协议中告警级别的多个trap信息字段与所述RESTful告警级别的单个trap信息字段之间的第二映射关系；其中，所述SNMP协议中告警级别包括：普通级别、轻微级别、重要级别、严重级别；Configure a first mapping relationship between a single trap information field of the alarm level in the SNMP protocol and a single trap information field of the RESTful alarm level, and configure a second mapping relationship between multiple trap information fields of the alarm level in the SNMP protocol and a single trap information field of the RESTful alarm level; wherein the alarm levels in the SNMP protocol include: normal level, minor level, important level, and severe level; 对所述SNMP协议的第一字段操作与所述RESTful协议的第二字段操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设字段映射关系；Performing relationship mapping between the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain a preset field mapping relationship between the SNMP protocol and the RESTful protocol; 对所述SNMP协议的第一告警操作与所述RESTful协议的第二告警字段操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设告警级别映射规则；Performing relationship mapping between the first alarm operation of the SNMP protocol and the second alarm field operation of the RESTful protocol to obtain a preset alarm level mapping rule between the SNMP protocol and the RESTful protocol; 所述在SMNP接口设置在线开关过程中，还包括：The process of setting the online switch in the SMNP interface also includes: 在所述SMNP接口中配置流量阈值和同步阈值，以便获取的所述SNMP设备的通信数据数量大于所述同步阈值时，对超出所述同步阈值部分的通信数据进行丢弃处理。A flow threshold and a synchronization threshold are configured in the SMNP interface so that when the amount of communication data of the SNMP device obtained is greater than the synchronization threshold, the communication data exceeding the synchronization threshold is discarded. 2.根据权利要求1所述的SNMP协议与RESTful协议协调方法，其特征在于，所述对所述SNMP协议的第一字段操作与所述RESTful协议的第二字段操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设字段映射关系，包括：2. The SNMP protocol and RESTful protocol coordination method according to claim 1, characterized in that the relationship mapping between the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain the preset field mapping relationship between the SNMP protocol and the RESTful protocol includes: 对所述SNMP协议的Get操作和GetNext操作与所述RESTful协议的Get操作进行关系映射；对所述SNMP协议的Trap操作与所述RESTful协议的Put操作和Post操作进行关系映射；对所述SNMP协议的Set操作与所述RESTful协议的Post操作和Delete操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设字段映射关系。Perform relationship mapping between the Get operation and the GetNext operation of the SNMP protocol and the Get operation of the RESTful protocol; perform relationship mapping between the Trap operation of the SNMP protocol and the Put operation and the Post operation of the RESTful protocol; perform relationship mapping between the Set operation of the SNMP protocol and the Post operation and the Delete operation of the RESTful protocol to obtain the preset field mapping relationship between the SNMP protocol and the RESTful protocol. 3.根据权利要求1所述的SNMP协议与RESTful协议协调方法，其特征在于，所述基于预设告警级别映射规则以及所述SNMP代理模块对所述SNMP设备的第一告警操作确定对应的所述RESTful协议的目标告警操作，包括：3. The SNMP protocol and RESTful protocol coordination method according to claim 1, characterized in that the step of determining the corresponding target alarm operation of the RESTful protocol based on the preset alarm level mapping rule and the first alarm operation of the SNMP agent module on the SNMP device comprises: 当接收所述SNMP代理模块发送的SNMP设备的告警流量大于所述流量阈值时，则基于预设告警级别映射规则针对所述告警流量生成REST告警信息。When the alarm flow of the SNMP device sent by the SNMP agent module is greater than the flow threshold, REST alarm information is generated for the alarm flow based on a preset alarm level mapping rule. 4.根据权利要求3所述的SNMP协议与RESTful协议协调方法，其特征在于，所述基于预设告警级别映射规则针对所述告警流量生成REST告警信息之后，还包括：4. The SNMP protocol and RESTful protocol coordination method according to claim 3, characterized in that after generating REST alarm information for the alarm traffic based on the preset alarm level mapping rule, it also includes: 从所述REST告警信息对应的告警流量中筛选出最高告警级别的目标告警流量，并将所述目标告警流量存储于RESTful推送线程池中，以便所述RESTful推送线程池按照预设顺序将所述目标告警流量提交至RESTful服务器。The target alarm flow with the highest alarm level is screened out from the alarm flow corresponding to the REST alarm information, and the target alarm flow is stored in the RESTful push thread pool, so that the RESTful push thread pool submits the target alarm flow to the RESTful server in a preset order. 5.根据权利要求1至4任一项所述的SNMP协议与RESTful协议协调方法，其特征在于，还包括：5. The SNMP protocol and RESTful protocol coordination method according to any one of claims 1 to 4, characterized in that it also includes: 设置用于所述RESTful协议推送和所述SNMP协议接收解耦的RESTful推送线程池于所述预设协议协调网关。A RESTful push thread pool for decoupling the RESTful protocol push and the SNMP protocol reception is set in the preset protocol coordination gateway. 6.一种SNMP协议与RESTful协议协调装置，其特征在于，应用于预设协议协调网关，包括：6. A SNMP protocol and RESTful protocol coordination device, characterized in that it is applied to a preset protocol coordination gateway, comprising: 风暴屏蔽模块，用于在SMNP接口设置在线开关，以便利用所述在线开关屏蔽多个SNMP设备的并发消息风暴；其中，所述SMNP接口位于SNMP设备层与SNMP协议之间，所述SNMP协议包括SNMP管理程序和SNMP代理模块，所述SNMP代理模块运行在各个被管理的SNMP设备之上，所述SNMP代理模块与所述SNMP管理程序通过UDP协议进行通信交互，接收并执行所述SNMP管理程序的命令；A storm shielding module, used to set an online switch on the SMNP interface so as to use the online switch to shield concurrent message storms of multiple SNMP devices; wherein the SMNP interface is located between the SNMP device layer and the SNMP protocol, the SNMP protocol includes an SNMP management program and an SNMP agent module, the SNMP agent module runs on each managed SNMP device, the SNMP agent module communicates and interacts with the SNMP management program through the UDP protocol, and receives and executes commands of the SNMP management program; 字段操作确定模块，用于通过SNMP代理模块与所述SNMP设备进行通信，并基于预设字段映射关系以及所述SNMP代理模块对所述SNMP设备的第一字段操作确定对应的所述RESTful协议的目标字段操作；A field operation determination module, configured to communicate with the SNMP device through an SNMP agent module, and determine a corresponding target field operation of the RESTful protocol based on a preset field mapping relationship and a first field operation of the SNMP agent module on the SNMP device; 告警操作确定模块，用于基于预设告警级别映射规则以及所述SNMP代理模块对所述SNMP设备的第一告警操作确定对应的所述RESTful协议的目标告警操作；An alarm operation determination module, configured to determine a corresponding target alarm operation of the RESTful protocol based on a preset alarm level mapping rule and a first alarm operation of the SNMP agent module on the SNMP device; 所述SNMP协议与RESTful协议协调装置，具体用于配置所述SNMP协议中告警级别的单个trap信息字段与所述RESTful告警级别的单个trap信息字段之间的第一映射关系，和配置所述SNMP协议中告警级别的多个trap信息字段与所述RESTful告警级别的单个trap信息字段之间的第二映射关系；其中，所述SNMP协议中告警级别包括：普通级别、轻微级别、重要级别、严重级别；对所述SNMP协议的第一字段操作与所述RESTful协议的第二字段操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设字段映射关系；对所述SNMP协议的第一告警操作与所述RESTful协议的第二告警字段操作进行关系映射，以获取所述SNMP协议与所述RESTful协议的预设告警级别映射规则；The SNMP protocol and RESTful protocol coordination device is specifically used to configure a first mapping relationship between a single trap information field of an alarm level in the SNMP protocol and a single trap information field of the RESTful alarm level, and to configure a second mapping relationship between multiple trap information fields of an alarm level in the SNMP protocol and a single trap information field of the RESTful alarm level; wherein the alarm levels in the SNMP protocol include: ordinary level, minor level, important level, and severe level; a relationship mapping is performed between the first field operation of the SNMP protocol and the second field operation of the RESTful protocol to obtain a preset field mapping relationship between the SNMP protocol and the RESTful protocol; a relationship mapping is performed between the first alarm operation of the SNMP protocol and the second alarm field operation of the RESTful protocol to obtain a preset alarm level mapping rule between the SNMP protocol and the RESTful protocol; 所述风暴屏蔽模块，具体用于在所述SMNP接口中配置流量阈值和同步阈值，以便获取的所述SNMP设备的通信数据数量大于所述同步阈值时，对超出所述同步阈值部分的通信数据进行丢弃处理。The storm shielding module is specifically used to configure the flow threshold and the synchronization threshold in the SMNP interface, so that when the amount of communication data of the SNMP device obtained is greater than the synchronization threshold, the communication data exceeding the synchronization threshold is discarded. 7.一种电子设备，其特征在于，包括：7. An electronic device, comprising: 存储器，用于保存计算机程序；Memory, used to store computer programs; 处理器，用于执行所述计算机程序，以实现如权利要求1至5任一项所述的SNMP和RESTful协调方法的步骤。A processor, configured to execute the computer program to implement the steps of the SNMP and RESTful coordination method according to any one of claims 1 to 5. 8.一种计算机可读存储介质，其特征在于，用于存储计算机程序；其中，所述计算机程序被处理器执行时实现如权利要求1至5任一项所述的SNMP和RESTful协调方法的步骤。8. A computer-readable storage medium, characterized in that it is used to store a computer program; wherein, when the computer program is executed by a processor, the steps of the SNMP and RESTful coordination method according to any one of claims 1 to 5 are implemented.
CN202310156231.0A 2023-02-20 2023-02-20 A coordination method and component of SNMP protocol and RESTful protocol Active CN116155676B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310156231.0A CN116155676B (en) 2023-02-20 2023-02-20 A coordination method and component of SNMP protocol and RESTful protocol

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310156231.0A CN116155676B (en) 2023-02-20 2023-02-20 A coordination method and component of SNMP protocol and RESTful protocol

Publications (2)

Publication Number Publication Date
CN116155676A CN116155676A (en) 2023-05-23
CN116155676B true CN116155676B (en) 2025-04-01

Family

ID=86340496

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310156231.0A Active CN116155676B (en) 2023-02-20 2023-02-20 A coordination method and component of SNMP protocol and RESTful protocol

Country Status (1)

Country Link
CN (1) CN116155676B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103684822A (en) * 2012-09-12 2014-03-26 中国移动通信集团公司 Method and equipment for managing network equipment
CN111726822A (en) * 2019-03-21 2020-09-29 大唐移动通信设备有限公司 Trap message processing method and data synchronization management device

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184003B (en) * 2007-12-03 2010-08-18 中兴通讯股份有限公司 Foreground and background alarm management system and management method based on network management protocol
CN101286996A (en) * 2008-05-30 2008-10-15 北京星网锐捷网络技术有限公司 Storm attack resisting method and apparatus
CN105530111A (en) * 2014-10-21 2016-04-27 中兴通讯股份有限公司 Alarm suppression method and system for the Internet of things
CN106506194A (en) * 2016-10-17 2017-03-15 武汉丰天鼎业信息网络有限公司 The method of dissimilar or model device alarm by snmp protocol automatic identification
US20190207801A1 (en) * 2017-12-29 2019-07-04 Dell Products, Lp System and Method for Rule-Based Simple Network Management Protocol Agent
CN111416733A (en) * 2020-02-27 2020-07-14 苏州浪潮智能科技有限公司 An alarm processing method, system and related device under high concurrency and large traffic

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103684822A (en) * 2012-09-12 2014-03-26 中国移动通信集团公司 Method and equipment for managing network equipment
CN111726822A (en) * 2019-03-21 2020-09-29 大唐移动通信设备有限公司 Trap message processing method and data synchronization management device

Also Published As

Publication number Publication date
CN116155676A (en) 2023-05-23

Similar Documents

Publication Publication Date Title
US12068938B2 (en) Network health data aggregation service
US20260106812A1 (en) Visualization of network health information
CN110890976B (en) Dynamic intention guarantee method and device in computer network and storage medium
JP7116759B2 (en) Centralized network configuration in distributed system
US8838830B2 (en) Optimizing distributed computer networks
CN110247784B (en) Method and device for determining network topology
US9886445B1 (en) Datacenter entity information system
US20130305091A1 (en) Drag and drop network topology editor for generating network test configurations
CN115499230A (en) Network attack detection method and device, equipment and storage medium
US10048994B2 (en) Identifying failed customer experience in distributed computer systems
CN108449350A (en) A kind of multi-protocols method of combination and device
US8554980B2 (en) Triggered notification
CN117082033A (en) Method, device, equipment and medium for establishing network connection between storage device and host
CN105207908A (en) Message processing method and system framework
CN116155676B (en) A coordination method and component of SNMP protocol and RESTful protocol
WO2025036112A1 (en) Data security protection selection method and apparatus, and storage medium
CN116095180B (en) A routing method, device and storage medium for log backhaul
CN117215781A (en) Equipment scheduling system and method
CN111818134A (en) Data transmission method and device based on fog computing in substation data center
CN114826939B (en) Network traffic analysis method of K8S cluster
US12445345B2 (en) Replay of analytics for a network management system
CN114221819B (en) A network scanning method and device based on game theory
US11563640B2 (en) Network data extraction parser-model in SDN
CN115174415B (en) A method, device and equipment for information publishing control of virtual tunnel endpoints
CN121396761A (en) Cloud computer access monitoring method and system based on dynamic optimization

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant