CN102123051A - Method for extending simple network management protocol (SNMP) error feedback messages - Google Patents
Method for extending simple network management protocol (SNMP) error feedback messages Download PDFInfo
- Publication number
- CN102123051A CN102123051A CN2011100596069A CN201110059606A CN102123051A CN 102123051 A CN102123051 A CN 102123051A CN 2011100596069 A CN2011100596069 A CN 2011100596069A CN 201110059606 A CN201110059606 A CN 201110059606A CN 102123051 A CN102123051 A CN 102123051A
- Authority
- CN
- China
- Prior art keywords
- error
- snmp
- message
- nms
- information
- 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.)
- Pending
Links
Landscapes
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for extending simple network management protocol (SNMP) error feedback messages. A method for extending a new data type in VARIABLE BINGDINGS of Response messages of the SNMP is utilized to transmit detailed reason description of a managed device on operation failures. When error messages are fed back, an Error Status is returned by SNMP standard error codes, and the VARIABLE BINGDINGS is bound at the same time so as to display the detailed error prompt messages, thus helping a network administrator to analyze and quickly position the reasons of the operation failures. The method provided by the invention has the advantages that a network management station (NMS) can obtain the more detailed error messages, can avoid the case that the NMS of a third party manufacturer can not analyze the Error Status, can be compatible with current international standards and the like.
Description
Technical field
The present invention relates to a kind of method of the SNMP of expansion error feedback information, the method for the expansion SNMP error feedback information in especially a kind of network management system.
Background technology
Along with network condition is complicated day by day, scale is increasing, and various new network technologies are constantly used, and very difficult by manually implementing the diverse network business, network management is more and more important in the operation maintenance of network.Network management comprises fault, performance, configuration, safety and charging five functional.For the unified various heterogeneous networks and the different network equipments managed effectively, make network management standardization, IETF (Internet engineering duty group) has formulated SNMP (simple network management protocol) agreement at the Internet network management.SNMP is the application layer protocol that how to transmit management information between a kind of regulation network management workstation (NMS) and the agency (AGENT), target is to guarantee that management information transmits in any 2, is convenient to any node retrieving information of network manager on network, makes amendment, trouble-shooting.NMS sends various inquiries and message is set the network equipment, and receives response and trap (Trap) message from managed device.AGENT is a process that resides on the managed device, be responsible for accepting, handling request message (Request) from network management workstation, obtain (get, getNext) then on the slave unit in other protocol modules or the numerical value that (set) manages variable is set, form response message (Response), the anti-NMS that gives.At some in emergency circumstances, change, in the time of access success etc., initiatively send Trap message notifying NMS as Interface status.
SNMP has three versions, is respectively SNMPv1, SNMPv2c and SNMPv3.On basic principle, three versions are basic identical.SNMPv1 is the initial specification of snmp protocol, comprises get, getNext, set operation and Trap message.SNMPv2c supports more operation on the basis of having inherited SNMPv1, support the more data type, and the abundanter fault processing sign indicating number and the support of multiple transport protocols are provided.SNMPv3 has improved the defective of the secure context among the SNMPv1/v2c.This paper relates generally to the basic principle of SNMP, so to introduce in the literary composition all be to be example with the SNMPv1 version.
As shown in Figure 2, the snmp message form is made up of 3 major parts: version number, group's name and SNMP PDU (protocol data unit, protocol Data Unit).Wherein SNMP PDU is made up of following components again: (1) PDU type: comprise GetRequest-PDU, GetNextRequest-PDU, GetResponse-PDU, SetRequest-PDU and Trap-PDU; (2) REQUESTID: be used for corresponding requests and corresponding message between NMS and Agent; (3) ERROR STATUS: be used in reference to the reason that the contract quotation literary composition is made mistakes; (4) ERROR INDEX: mistake appears in which variable that is used to indicate variable binding centering; (5) VARIABLE BINGDINGS: be that several example value by OID and this OID are bound forming.The reason that Error Status field can make mistake according to message is inserted the corresponding error sign indicating number.SNMPv1 provides following 5 standard error sign indicating number: noError 0, and TooBig 1 ... genErr 5.SNMPv2c provides the more error code of horn of plenty, includes 18 standard error sign indicating numbers.
But in actual applications, professional relevant error reason is often arranged, not in the standard error sign indicating number that snmp protocol provides, that is to say that the error code that snmp protocol provides can't reflect professional relevant error reason.For example in the wireless traffic, when creating service moulding plate and being tied to port, need that the detection port security configuration is whether correct, whether the Radius configuration correct etc., this moment is because the restriction of snmp protocol, the network equipment can only return 3 (Bad Value) for Error Status, and NMS can't distinguish concrete error reason.In addition, when carrying out the multivariable bindings, if a part of variable is operated successfully, part variable operation failure, then because the restriction of snmp protocol, ERROR INDEX and ERROR STATUS can only fill in one (generally filling in the variable of first failure in the reality), and the standard error sign indicating number can't react real result.When the network equipment made a mistake in operation, the error code by standard returned, and NMS is translated as the character string that the keeper can discern with this error code, for example is translated as " authentication failed please check whether username and password is correct " to 16.In these cases, because the error code of standard very little, can not clearly express detailed error message.
In the prior art, part manufacturer may expand exclusive error code, for example the specific type of error of extended error sign indicating number 19 expressions on SNMP V2c.But, there are differences between the extended error sign indicating number of different vendor, the error code of expansion is easy to cause incompatible between the manufacturer again.For example NotWritable (17) both can represent that the destination node of Set did not exist, and can represent that also destination node do not support Set, distinguished if expand extra error code, can cause between the manufacturer equipment incompatible.
Summary of the invention
The present invention is the weak point that exists in the above-mentioned prior art for avoiding, and a kind of method of the SNMP of expansion error feedback information is provided, so that NMS obtains more detailed error message, and can avoid the NMS of third party manufacturer can not resolve Error Status.
The present invention at first provides a kind of method of the SNMP of expansion error feedback information.
A kind of method of expanding SNMP error feedback information is characterized in, in the VARIABLE BINGDINGS of the Response of SNMP message, expands a kind of data type SNMP_ERROR_DETAIL and represents detailed error message; After makeing mistakes in the device processes, in the process of NMS feedback error information, for the access request that makes a mistake, the data type of corresponding node is revised as SNMP_ERROR_DETAIL in VARIABLE BINGDINGS, and writes detailed error message with the form of character string.
The method of described expansion SNMP error feedback information wherein, may further comprise the steps to the process of NMS feedback error information:
A.NMS sends request message to managed device, and the process AGENT on the managed device accepts and handle the request message that .NMS sends;
If the success of the process AGENT processing request message b1. on the managed device will be assembled the corresponding message of SNMP and return to NMS then according to the request message return data;
If the process AGENT processing request message b2. on the managed device is unsuccessful, will return standard error information with the form of returning SNMP standard error sign indicating number according to RFC (Request ForComments, Request for Comment); Simultaneously, at the node that makes a mistake, the character string of binding SNMP_ERROR_DETAIL type as detailed error message, is assembled the corresponding message of SNMP then and is returned to NMS.
Compared with the prior art, beneficial effect of the present invention is embodied in:
In the method for expansion SNMP error feedback information of the present invention, when error message is fed back, when returning Error Status by SNMP standard error sign indicating number, by the detailed miscue information of binding among the VARIABLE BINGDINGS, help the keeper to understand detailed error message better, can make NMS obtain more detailed error message, be used to point out that the keeper is easier rights the wrong, and can avoid the NMS of third party manufacturer can not resolve Error Status, can be better and third party manufacturer compatibility.
Description of drawings
Fig. 1 is to the flow chart of NMS feedback error information in the method for expansion of the present invention SNMP error feedback information.
Fig. 2 is the composition structure diagram of snmp message form.
Below pass through embodiment, and the invention will be further described in conjunction with the accompanying drawings.
Embodiment
As shown in Figure 1, a kind of method of expanding SNMP error feedback information in the VARIABLE BINGDINGS of the Response of SNMP message, is expanded a kind of data type SNMP_ERROR_DETAIL and is represented detailed error message; After makeing mistakes in the device processes, in the process of NMS feedback error information, for the access request that makes a mistake, the data type of corresponding node is revised as SNMP_ERROR_DETAIL in VARIABLE BINGDINGS, and writes detailed error message with the form of character string.Described detailed error message, be for the standard error sign indicating number that snmp protocol provides, described detailed error message can have been explained wrong related content in more detail, transmitting managed devices describes for the detailed reason of operation failure, be a kind of information that can make the technical staff know concrete error reason, to help the reason that the network manager analyzes and rapid positioning operation is failed.And the standard error sign indicating number that snmp protocol provides can only provide the most basic error message, and can't make the technical staff obtain further information about mistake, thereby can not help the network manager to analyze reason with the rapid positioning operation failure.
In the method for the present invention, may further comprise the steps to the process of NMS feedback error information
A.NMS sends request message to managed device, and the process AGENT on the managed device accepts and handle the request message that .NMS sends;
If the success of the process AGENT processing request message b1. on the managed device will be assembled the corresponding message of SNMP and return to NMS then according to the request message return data;
If the process AGENT processing request message b2. on the managed device is unsuccessful, will return standard error information with the form of returning SNMP standard error sign indicating number according to RFC (Request ForComments, Request for Comment); Simultaneously, at the node that makes a mistake, the character string of binding SNMP_ERROR_DETAIL type as detailed error message, is assembled the corresponding message of SNMP then and is returned to NMS.
This programme is represented detailed error message by a kind of data type of expansion in the VARIABLE BINGDINGS of the Response of SNMP message:
Suppose that new data type SNMP_ERROR_DETAIL value is 0x83 (concrete numerical value can be decided, and conflicting only otherwise with existing standard gets final product) when specific implementation.
When submitting request to, do not adopt equipment this new data type at NMS, still use MIB (Management Information Base, management information bank) the defined form of file, in device processes, make mistakes, need be when the NMS reporting errors, for the access request that makes a mistake, the data type of corresponding node is revised as SNMP_ERROR_DETAIL in VARIABLE BINGDINGS, and writes detailed error message with the form of character string.
Suppose that NMS need be to the following MIB node of equipment disposition
| NAME | VALUE |
| vacmAccessNotifyViewName.4.116.101.115.116.1.45.3.1 | test |
If configuration successful, then equipment is to theing contents are as follows that webmaster returns:
The code description configuration successful of returning.
When disposing following two nodes simultaneously, because first node do not exist, so whole configuration can be failed.
| NAME | VALUE |
| vacmAccessEntry.99.4.116.101.115.116.1.45.3.1 | test |
| vacmAccessNotifyViewName.4.116.101.115.116.1.45.3.1 | test |
If do not adopt the solution of the present invention, for the situation of this configuration failure, standard SNMP return information is as follows:
Returned SNMP standard error sign indicating number NOT WRITABLE (17).At this moment, the snmp protocol of standard can not clearly be expressed concrete error reason.
And after the employing the solution of the present invention, returning Error Status simultaneously, by the detailed miscue information of binding among the VARIABLE BINGDINGS, help the better orientation problem of keeper.For the mistake of above-mentioned configuration failure, this moment, the SNMP return information was as follows:
When returning SNMP standard error sign indicating number NOT WRITABLE (17), include detailed miscue information among Object identifier 1 that returns and the Value:Error Detail; Content among the described Value:Error Detail promptly described " error message in detail ".
For third party NMS,, be NotWritable (17) so NMS still can correctly resolve the error code of its message because this programme is not revised the error code information (being the Error Status field in the SNMP return information) in the standard SNMP back message using.
The method of expansion SNMP error feedback information of the present invention, by expanding a kind of data type, the detailed error message of statement can make NMS obtain more detailed error message, and can avoid the NMS of third party manufacturer can not resolve Error Status in Response; The error message that this scheme does not need to revise standard SNMP represents, can be better and third party manufacturer compatibility.
Claims (2)
1. a method of expanding SNMP error feedback information is characterized in that, in the VARIABLE BINGDINGS of the Response of SNMP message, expands a kind of data type SNMP_ERROR_DETAIL and represents detailed error message; After makeing mistakes in the device processes, in the process of NMS feedback error information, for the access request that makes a mistake, the data type of corresponding node is revised as SNMP_ERROR_DETAIL in VARIABLE BINGDINGS, and writes detailed error message with the form of character string.
2. a kind of method of expanding SNMP error feedback information according to claim 1 is characterized in that, described process to NMS feedback error information may further comprise the steps:
A.NMS sends request message to managed device, and the process AGENT on the managed device accepts and handle the request message that .NMS sends;
If the success of the process AGENT processing request message b1. on the managed device will be assembled the corresponding message of SNMP and return to NMS then according to the request message return data;
If the process AGENT processing request message b2. on the managed device is unsuccessful, will return standard error information with the form of returning SNMP standard error sign indicating number according to RFC; Simultaneously, at the node that makes a mistake, the character string of binding SNMP_ERROR_DETAIL type as detailed error message, is assembled the corresponding message of SNMP then and is returned to NMS.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100596069A CN102123051A (en) | 2011-03-13 | 2011-03-13 | Method for extending simple network management protocol (SNMP) error feedback messages |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100596069A CN102123051A (en) | 2011-03-13 | 2011-03-13 | Method for extending simple network management protocol (SNMP) error feedback messages |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102123051A true CN102123051A (en) | 2011-07-13 |
Family
ID=44251512
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011100596069A Pending CN102123051A (en) | 2011-03-13 | 2011-03-13 | Method for extending simple network management protocol (SNMP) error feedback messages |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102123051A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516530A (en) * | 2012-06-20 | 2014-01-15 | 中兴通讯股份有限公司 | Method and device for obtaining extension error information from agent end |
| CN110602331A (en) * | 2019-08-12 | 2019-12-20 | 深圳震有科技股份有限公司 | Error code expansion-based cause positioning method, intelligent terminal and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533115A (en) * | 2003-02-14 | 2004-09-29 | ���ǵ�����ʽ���� | Method and device for supporting error reason of simple network management protocol |
| CN101741596A (en) * | 2008-11-25 | 2010-06-16 | 中兴通讯股份有限公司 | Method, system and management node for feeding back error message of simple network management protocol |
-
2011
- 2011-03-13 CN CN2011100596069A patent/CN102123051A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1533115A (en) * | 2003-02-14 | 2004-09-29 | ���ǵ�����ʽ���� | Method and device for supporting error reason of simple network management protocol |
| CN101741596A (en) * | 2008-11-25 | 2010-06-16 | 中兴通讯股份有限公司 | Method, system and management node for feeding back error message of simple network management protocol |
Non-Patent Citations (1)
| Title |
|---|
| XU GUANGHUI ETC.: "An Improved Error Handling Method in SNMPv2 Protocol Operations", 《JOURNAL OF COMPUTER SCIENCE AND TECHNOLOGY》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516530A (en) * | 2012-06-20 | 2014-01-15 | 中兴通讯股份有限公司 | Method and device for obtaining extension error information from agent end |
| CN110602331A (en) * | 2019-08-12 | 2019-12-20 | 深圳震有科技股份有限公司 | Error code expansion-based cause positioning method, intelligent terminal and storage medium |
| CN110602331B (en) * | 2019-08-12 | 2021-06-18 | 深圳震有科技股份有限公司 | Error code expansion-based cause positioning method, intelligent terminal and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6085237A (en) | User-friendly interface for setting expressions on an SNMP agent | |
| CN101110822A (en) | Event notice sending method, system and equipment based on network configuration protocol | |
| CN103460203A (en) | Cluster unique identifier | |
| US8935388B2 (en) | Systems and methods of automated event processing | |
| US10187272B2 (en) | Interface management service entity, function service entity, and element management method | |
| JP2010507298A (en) | Method for logical deployment, undeployment, and monitoring of a target IP network | |
| US20140108490A1 (en) | Device Management Method, Apparatus and System | |
| CN106886410A (en) | A kind of software version management system | |
| CN101616022A (en) | A kind of intelligent device management method and system based on snmp protocol | |
| KR100489689B1 (en) | Method for supporting error cause of SNMP and apparatus thereof | |
| CN101202751A (en) | System and method for providing SNMP data for virtual networking devices | |
| CN101848107A (en) | SNMP (Simple Network Management Protocol) network element and communication method of SNMP network element and proprietary protocol network element | |
| CN110971438A (en) | Method and device for configuring data | |
| CN115623000B (en) | Method and device for efficiently distributing data on digital networking | |
| CN101217403A (en) | A realization method of alarming based on SNMP | |
| US20140181289A1 (en) | Verifying information stored on a managed network device | |
| CN102123051A (en) | Method for extending simple network management protocol (SNMP) error feedback messages | |
| CN113992504A (en) | Network transmission equipment management method based on industrial internet identification analysis | |
| CN101710862A (en) | Method and device for processing network management operation error message | |
| CN103902429A (en) | Early warning method, sever and system in automated test | |
| US7836358B2 (en) | Method and network element for improving error management in managed networks, and computer program product therefor | |
| CN101212346A (en) | Software version management method and device for network element management system | |
| EP2566103B1 (en) | Apparatus and method for correlating faults in an information carrying network | |
| US20170286560A1 (en) | Method, device and system for device troubleshooting service of the internet of things | |
| CN102868559A (en) | Method and system for generating weblog data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110713 |