CN101795206A - Method and device for realizing SNMP agent on distributed equipment - Google Patents
Method and device for realizing SNMP agent on distributed equipment Download PDFInfo
- Publication number
- CN101795206A CN101795206A CN200910224847A CN200910224847A CN101795206A CN 101795206 A CN101795206 A CN 101795206A CN 200910224847 A CN200910224847 A CN 200910224847A CN 200910224847 A CN200910224847 A CN 200910224847A CN 101795206 A CN101795206 A CN 101795206A
- Authority
- CN
- China
- Prior art keywords
- snmp
- rpc
- request
- converted
- xdr
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a method and a device for realizing an SNMP agent on distributed equipment. The method comprises that when the SNMP agent receives a simple network management protocol (SNMP) message transmitted by a network management system (NMS), an operation request in the SNMP message is converted into a remote procedure call (RPC) request which is transmitted to an RPC client; the RPC client uses RPC communication to transmit the RPC request to an RPC server on a controlled board; the RPC server converts the RPC request into a function call to a local managed object, a module to be managed is called to complete management request operation, and the return value of the procedure call is transmitted to an RPC client on a master control board; the RPC client transmits the return value of the RPC call to the SNMP agent; and after the SNMP agent receives the return value, the SNMP agent explains the return value into SNMP operation results, and the SNMP operation results are encapsulated in an SNMP answer message and are returned to the NMS. By adopting the method and the device, the invention can solve the problems in the prior art that the complexity of SNMP multilevel agents is high and the workload is heavy.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to a kind of method and apparatus of on distributed constitution equipment, realizing the SNMP agency.
Background technology
A SNMP (Simple Network Management Protocol, the Simple Network Management Protocol) formation of system comprises following element usually as shown in Figure 1:
Several nodes, each node memory is acted on behalf of at a SNMP, and this entity has comprised response command and has produced the application program of announcement; Node with the whole SNMP of comprising agency in some technical documentations is called the SNMP agency, is meant then that in this article intra-node finishes the software module of SNMP agent functionality;
At least one manager NMS (Network Management Station), this entity have comprised the application program that produces order and/or receive announcement.
A management agreement, promptly snmp protocol is used for transmit management information between NMS and agency.In the SNMP system, managed object defines according to the requirement of SMI (Structure of Management Information, structure of management information) standard, and this message structure main feature can be summarized as follows:
Whole management object system is with classification, tree structure tissue, and managed object is the leaf node of tree structure, and managed object is retrieved and traveled through in the mode of dictionary preface.
The database that defines all kinds of managed objects is called MIB (Management Information Base, management information bank), and the file of depositing these information is called mib file.In mib file, managed object is divided into each module (MODULE) by its function of dominant, the module here is not meant software module, both do not have necessary relation, usually managed object possesses the equivalence value of an inside in software module, and the operation requests of managed object is converted to operation to its equivalence value in software module.
As shown in Figure 2, the building method of interface between SNMP agency and the managed object in the prior art, SNMP node processing NMS operation requests specifically comprises step:
In the above-mentioned steps, step (4) is finished by the module at managed object place, and other process is all finished by the SNMP proxy module.Because object distribution that SNMP managed is in each module of system, how the relation of treatment S NMP proxy module and these modules is technology emphasis that the SNMP agency designs, and concrete in the prior art implementation comprises:
The SNMP node of A, distributed formation;
As shown in Figure 3, the equipment of distributed formation generally includes with lower member:
A master control borad is responsible for the collaborative work of whole equipment, and management interface externally is provided, and for example, handles the order of man-machine interaction, the reception/transmission of the message in the SNMP mode;
A plurality of controlled board, each controlled board are comparatively independently computer subsystems, are responsible for the service part of equipment, and these business itself need externally provide management interface;
Possess management channels between master board and the controlled board, the control request of master board and response are by this management channels transmission.
In the equipment of distributed formation, owing to may be distributed on a plurality of controlled board by administration module, their address space is isolated, and can not adopt local function call to finish the operation requests of SNMP again, and the method for therefore above-mentioned mib compiling structure software can not directly be used again.
At above-mentioned situation, existing solution is normally acted on behalf of classification with SNMP: in master board, realize master agent, realize sub agent on the controlled board, the distribution of being responsible for snmp message by master agent with converge.For example, (RFC1227) (Agent Extensibility Protocol acts on behalf of Extended Protocol to standardized SMUX agreement, and what RFC2741) adopt all is this model with the AgentX agreement for SNMP multiplexing protocol, SNMP multiplex protocol.Below be the operation principle that example is introduced this model with SMUX:
As shown in Figure 4, mark off master agent and sub agent at intra-node, the step of SNMP node processing NMS operation requests comprises:
If comprised the operation requests that mails to a plurality of sub agents in the snmp message, then handle complicated more: master agent sends to corresponding sub agent after message need being disassembled by subtree, also the response of each sub agent will be synthesized one and reply;
This class is that based on multistage agency's distributed schemes major defect the complexity of scheme is higher, realizes that workload is bigger.If distributed apparatus is inner to be adopted multistagely when acting on behalf of scheme, following difficulty is arranged:
Master agent on the master control borad need be known the distribution of sub agent, resolves replying that the request mail to sub agent and sub agent beam back.When handle to need crossing over the operation requests of a plurality of sub agents, collaborative work is just complicated more, for example, and when having comprised the request to a plurality of sub agents in snmp message; And for example, when get-next operation when a subtree crosses another subtree, all need master agent further to handle according to the formation of MIB tree and the return results of sub agent;
Because master control borad this locality also has by administration module, master agent constitute two kinds of selections: the local sub agent of also being realized in the administration module, then master agent does not need directly with mutual by administration module; Perhaps master agent comprises tradition agency's function.Any method no matter all makes the SNMP function of master control borad realize complexity than the tradition agency undoubtedly.
On each controlled board, all need to realize the function of SNMP sub agent; It is redundant that master control borad and controlled board have partial function, as message parse, security control etc.;
Define the communication mode that adopts between master control borad and the controlled board, for example SNMP SMUX will use the TCP link.
Summary of the invention
The invention provides a kind of method and apparatus of on distributed constitution equipment, realizing the SNMP agency, be used for overcoming the multistage complexity height of acting on behalf of of prior art SNMP, realize the bigger problem of workload.
A kind of SNMP agent node of realizing on distributed constitution equipment comprises master control borad and controlled board, comprises SNMP agency and RPC client computer in the described master control borad; Comprise managed object and RPC server in the described controlled board, wherein,
The SNMP agency, the Simple Network Management Protocol snmp message that the person NMS that is used for the receiving management sends, and the operation requests in this snmp message is converted to invocation of procedure RPC request, this invocation of procedure RPC request is passed to the RPC client computer, and the return value that the RPC client computer is sent is interpreted as the SNMP operating result, and this SNMP operating result is packaged in sends back to described NMS in the SNMP response message;
The RPC client computer is used to use RPC communication that described RPC request is sent to the RPC server, and receives the return value of RPC request;
Described RPC server is used for RPC request is converted to function call to the local management object, sends function call request to described managed object, and described RPC client computer is returned in the return value transmission of described function call;
Managed object is used to provide the function call interface of the management request finished, and receives the call request that described RPC server sends, and will call the result and return to described RPC server.
A kind of method that realizes the SNMP agency on distributed constitution equipment is characterized in that, comprising:
When the agency of the SNMP in the master control borad receives the Simple Network Management Protocol snmp message of manager NMS transmission, described snmp message is converted to native data formats, and the operation requests in this snmp message is converted to invocation of procedure RPC request, pass to the RPC client computer that is provided with on this master control borad;
The RPC client computer uses RPC communication that the RPC request is sent to RPC server on the controlled board;
RPC server on the controlled board is converted to function call to the local management object with RPC request, and calls and describedly finished the management solicit operation by administration module, and master control borad is returned in the return value transmission of the invocation of procedure;
After described SNMP agency receives described return value, this return value is interpreted as the SNMP operating result, and this SNMP operating result is packaged in the SNMP response message returns to NMS.
The method and apparatus that the embodiment of the invention provided docks the SNMP system with ONC RPC system, utilize ONC RPC to transmit management operation request between master control borad and the controlled board.Shield the difference of remote procedure call and LPC by ONC RPC, make SNMP proxy module and constructed, avoid the multistage SNMP agency plant of complex structure by the mode that administration module can still call according to this locality.
Description of drawings
Fig. 1 is the formation structure chart of SNMP system in the prior art;
Fig. 2 is the flow chart of the building method of interface between SNMP agency and the managed object in the prior art;
Fig. 3 acts on behalf of the structure chart of the equipment of distributed formation for SNMP in the prior art;
Fig. 4 is for marking off the flow chart of the SNMP node processing NMS operation requests of master agent and sub agent at intra-node in the prior art;
Fig. 5 A is a RPC process of the program frame schematic diagram that rpcgen generates in the prior art;
Fig. 5 is a kind of structural representation of realizing SNMP agency's node on distributed constitution equipment of the embodiment of the invention;
Fig. 6 is a kind of flow chart of realizing SNMP agency's method on distributed constitution equipment of the embodiment of the invention.
Embodiment
A kind of node of realizing the SNMP agency on distributed constitution equipment of the embodiment of the invention comprises master control borad and controlled board, comprises SNMP agency and RPC client computer in the described master control borad; Comprise managed object and RPC server in the described controlled board, wherein, the SNMP agency, the Simple Network Management Protocol snmp message that the person NMS that is used for the receiving management sends, and the operation requests in this snmp message is converted to invocation of procedure RPC request, this invocation of procedure RPC request is passed to the RPC client computer, and the return value that the RPC client computer is sent is interpreted as the SNMP operating result, and this SNMP operating result is packaged in sends back to described NMS in the SNMP response message; The RPC client computer is used to use RPC communication that described RPC request is sent to the RPC server, and receives the return value of RPC request; Described RPC server is used for RPC request is converted to function call to the local management object, sends function call request to described managed object, and described RPC client computer is returned in the return value transmission of described function call; Managed object is used to provide the function call interface of the management request finished, and receives the call request that described RPC server sends, and will call the result and return to described RPC server.
For reaching the task of the SNMP proxy module of realizing distributed constitution equipment, the technical program is docked the SNMP system with ONC RPC system, utilizes ONC RPC to transmit management operation request between master control borad and the controlled board.Shield the difference of remote procedure call and LPC by ONC RPC, make SNMP proxy module and constructed, avoid the multistage SNMP agency plant of complex structure by the mode that administration module can still call according to this locality.
Wherein RPC (Remote procedure call, remote procedure call) is specially:
RPC is a kind of inter-process communication mechanisms, it makes a computer program can call the process that is positioned at another address space, and need not pay close attention to the details of this remote interaction, need not be concerned about again when it makes coding the process that need call be local, or on remote system (said here process is exactly a function for the C programming language).
RPC has multiple implementation, can adopt ONC RPC (Open NetworkComputing Remote Procedure Call, open network calculate RPC) in embodiments of the present invention, wherein ONC RPC framework mainly comprise following characteristics:
Process can only have a parameter, a return value; When needs transmit a plurality of numerical value, can take they are encapsulated as the method for a structure;
The transport layer independence does not need transmission service reliably;
Call semanteme, call semantical definition client computer to calling the hypothesis that the result can do.ONC RPC provides " once minimum " semanteme, promptly calls when returning when one, and it has been performed once at least;
Data representation, the data type of ONC RPC adopts XDR (External Data Representation, External Data Representation) expression, XDR is a kind of dtd standard, it has defined the expression way of transmission data between the computer system of different systems.
XDR is a kind of data type by implication definition, the information that does not comprise data type in the data that this mode defines, therefore require data producer and consumer that the explanation of data is reached an agreement by other means, as arranging to illustrate by additional document or interface.
A process is by tlv triple (program number, program version numbering, process numbering) sign
Program is meant the set of one group of correlated process, and each process wherein all has unique numbering.For example, NFS (Network File System, NFS) is exactly a program among the RPC, and its program number is 0x10_0002, and current version numbering is 3, and file operation such as read (reading), write (writing) etc. all are the processes among the NFS.
The uniqueness of numbering can adopt the whole bag of tricks to guarantee.This programme only relates to the numbering of device interior, and the scope that numbering is used is very little, so solution do not need very complicatedly, for example can take preallocated method.
Binding, which platform main frame is client computer need know service earlier on, then could the access services process.This problem can adopt several different methods to solve, for example, can solidify the corresponding relation of service processes and address, more method in common is a service processes with its service registry in a certain appointed position, the client when operation from the corresponding relation of the appointed position service of obtaining with the address.
ONC RPC adopts the client-server working model, and client computer refers to call the program (or software systems) of RPC process, and server is meant the program (or software systems) that realizes the RPC process.
ONC RPC realizes that needed program frame adopts RPC CompilerTools (RPCLanguage Compiler) rpcgen to construct usually.Rpcgen can be according to the remote process explanation in the RPC specification file (RPCspecification), generation is used to dock the program frame of client computer and server, makes the developer need not be concerned about that the RPC process finishes needed program module and reciprocal process.
The content of RPC specification file is to indicate client computer and server needs Sharing Information, generally includes the tabulation of program number/start context, process statement far away, comprises its parameter declaration, returned value specification and numbering:
For example, realize the process of a long-range integer summation, its RPC specification file is as follows:
The organization definition * of struct add_oper{/* procedure parameter/
int?oper1；
int?oper2；
}；
program?ADDPROG{
version?ADDVERS{
Int ADD (struct add_oper)=1; / * process numbering */
}=1; / * program version */
}=100; / * program number */
According to this file, rpcgen just can generate the framework of client computer and server program.
Shown in Fig. 5 A, in the program frame that rpcgen generates, be usually directed to 6 modules in the RPC process, comprise module, the client program 1 that calls RPC, module, server program 2 and two RPC protocol modules of realizing RPC:
Client computer RPC interface module is responsible for the RPC request is converted to the RPC protocol massages, and is received the return value from the invocation of procedure of server;
Server RPC interface module is responsible for the RPC message is converted to invocation of procedure request again, and the process in the caller 2 is come complete call, and will call the result and send it back client again;
The RPC protocol module is responsible for utilizing the transmission service of system that message is passed to the opposite end, or receives message from the opposite end, and this module all exists in client computer and service;
There is not direct correlation with " client program 1 " in the upper module and " server program 2 ", for " client program 1 ", do not know it calling a remote process, for " server program 2 ", it does not know that its caller is a long-range program.Other module generates by the RPC CompilerTools.
In embodiments of the present invention the SNMP proxy module with by administration module in different software systems, the SNMP proxy module is resolved the snmp message production process and is called, the invocation of procedure that obtains by the RPC framework pass on the controlled board by administration module, specific implementation comprises:
As shown in Figure 5, a kind of node of realizing the SNMP agency on distributed constitution equipment of the embodiment of the invention comprises master control borad and controlled board, and wherein said master control borad comprises SNMP agency 501 and RPC client computer 502; Described controlled board comprises RPC server 503 and managed object 504:
Described SNMP agency 501, the Simple Network Management Protocol snmp message that the person NMS that is used for the receiving management sends, and the operation requests in this snmp message is converted to invocation of procedure RPC request, this invocation of procedure RPC request is passed to RPC client computer 502, and the return value that RPC client computer 502 is sent is interpreted as the SNMP operating result, and this SNMP operating result is packaged in sends back to described NMS in the SNMP response message;
This SNMP agency 501 is used for that also the simple syntactic variable of self and applicational grammar variable are converted into external data XDR and represents.
In order to explain the improper value in the RPC invoked procedure, the mistake that this SNMP agency 501 also is used for RPC invoked procedure that the RPC request is returned transforms the error condition " noAccess " of SNMP.
For the correct managed object 504 that calls on the controlled board, this SNMP agency 501 also is used for the object identity of the managed object of snmp message is converted to the address of managed object.
Managed object 504 on the controlled board is used to provide the function call interface of finishing the management request, receives the call request that described RPC server sends, and finishes the SNMP operation requests, and the result is returned to caller.
Wherein, SNMP agency 501 will resolve snmp message, be converted to internal form, mib variable is mapped to local equivalence value, SNMP agency 501 can use distinct methods and realize, they but in fact all be that the SNMP operation requests is converted to by the function call of administration module, but the concrete form of function interface may be different.Because the information function interface corresponding with it in the snmp message exists fixing mapping relations usually, therefore, directly the function of information in the snmp message and RPC is contrasted analysis in the embodiment of the invention, this analysis conclusion is applicable to also whether analyze RPC is enough to carry by the converted function call of snmp message, in embodiments of the present invention snmp message is resolved, be converted to internal form, specifically comprise:
The XDR that ONC RPC uses in the embodiment of the invention can represent the data type of all objects among the SNMP, and transformation rule is as follows:
(A), three kinds of simple syntactic variables among the SNMP are converted into the XDR form:
Integer type INTEGER: directly corresponding to the Integer type among the XDR;
8 hyte character string OCTET STRING: because the type is a varying string, use the string of XDR to represent it, preceding 4 bytes in the inside of the string type of XDR are data lengths, because ASN.1 is the explicit data definition, the length that must comprise this character string when using OCTECT STRING is inserted this length taking-up in the length field of XDR string type when conversion.
Object identity OBJECT IDENTIFIER: i.e. the sign of managed object, this value is not used in function call, but when RPC calls, OBJECT IDENTIFIER will be converted to the address of the managed object in the RPC communication.
(B), 6 kinds of applicational grammar variablees among the SNMP are converted into the XDR form:
IPv4 address IpAddress, the Fixed-Length Array (fixed length array) of use XDR, length is 4;
32 digit counter Counter32, the Unsigned Integer type of use XDR;
32 signless integer Unsigned32, the Unsigned Integer type of use XDR;
The time answer TimeTicks that ticks uses the Unsigned Integer type of XDR;
Nontransparent type Opaque is identical with the conversion of OCTET STRING;
64 digit counter Counter64, the Unsigned Hyper Integer type of use XDR;
64 signless integer Unsigned46, the Unsigned Integer type of use XDR;
In addition, for the SNMP object of form types, adopt a structure that the variable of form is encapsulated and get final product, because the form types member is made of above-mentioned simple types, then can be considered as be conversion to member in the form in the conversion of form.
(C), the conversion of the improper value that returns of RPC call error value and SNMP operation requests:
The terminal error of the invocation of procedure has two kinds of possibilities, and the one, the mistake in the RPC invoked procedure is referred to as external error in embodiments of the present invention; Another kind of is internal error during the invocation of procedure realizes, and this moment, the RPC invoked procedure was successful, and type of error is referred to as internal error in embodiments of the present invention in the return value of the invocation of procedure;
In the RPC process issuable external error comprise that program does not exist, program does not match, process does not exist, parameter does not match, system mistake, authentication error and RPC version error.
More than except that " system mistake ", other wrong only possibility can be converted to all external error values the error condition " noAccess " of SNMP owing to design mistake occurs.Because the error condition of SNMP just is used for prompting usually, NMS no longer is further processed error condition, so the inaccuracy of error condition can not have influence on the management process of NMS.
Internal error is that the requirement according to SNMP when handling the management request of far-end process produces improper value, does not need to change again, and this moment, the return value of RPC process was success.
(D), the implicit type of XDR definition:
The implicit type definition that XDR adopts needs the producer of data and consumer that the explanation of data is reached an agreement in advance, and this problem solves by the process statement of RPC.Comprised parameter and return value type in the statement of RPC process, therefore statement when data are dealt on the server by client computer, can guarantee that both are consistent for the explanation of data with the program that is used for simultaneously on client computer and the server.
(E), the change of invocation of procedure semanteme:
ONC RPC does not guarantee that the invocation of procedure is necessarily reliable, and snmp protocol has also been supposed the unreliability of SNMP operation requests, so the SNMP agency can tolerate the unreliability of RPC;
(F), by the addressing of administration module:
For finishing SNMP agency to by the invocation of procedure of administration module, the OBJECT IDENTIFIER of managed object in the snmp message need be converted to by the address of administration module, by the addressing of administration module is not the scope of the described concern of the embodiment of the invention, and present embodiment can be selected to be determined by the address of administration module by the address table that presets.Owing to constituted the network of device interior between master control borad and the controlled board, in the system schema addressing method must be arranged, the addressing scheme of device interior is generally all fairly simple, for example: if device interior uses is the TCP/IP network, then can with TCP or udp port with by the just curing when the system design of the mapping relations between the administration module.
As shown in Figure 6, the embodiment of the invention also provides a kind of method that realizes the SNMP agency on distributed constitution equipment, specifically may further comprise the steps:
Step 605 after the SNMP agency on the master control borad receives described return value, is interpreted as the SNMP operating result with this return value, is packaged in the SNMP response message and returns to NMS.
Because the information function interface corresponding with it in the snmp message exists fixing mapping relations usually, therefore, the embodiment of the invention directly with snmp message in the function of information and RPC contrast analysis, this analysis conclusion is applicable to also whether analyze RPC is enough to carry by the converted function call of snmp message:
Then described step 601 is converted to invocation of procedure RPC request with described SNMP request, passes to the RPC client computer that is provided with on this master control borad, specifically comprises:
The XDR that ONC RPC uses in the embodiment of the invention can represent the data type of all objects among the SNMP, and transformation rule is as follows:
(A), three kinds of simple syntactic variables among the SNMP are converted into the XDR form:
INTEGER: directly corresponding to the Integer type among the XDR;
OCTET STRING: because the type is a varying string, use the string of XDR to represent it, preceding 4 bytes in the inside of the string type of XDR are data lengths, because ASN.1 is the explicit data definition, the length that must comprise this character string when using OCTECT STRING is inserted this length taking-up in the length field of XDR string type when conversion.
OBJECT IDENTIFIER: i.e. the sign of managed object, this value is not used in function call, but when RPC calls, OBJECT IDENTIFIER will be converted to the address of the managed object in the RPC communication.
(B), 6 kinds of applicational grammar variablees among the SNMP are converted into the XDR form:
IpAddress, the Fixed-Length Array (fixed length array) of use XDR, length is 4;
Counter32, the Unsigned Integer type of use XDR;
Unsigned32, the Unsigned Integer type of use XDR;
TimeTicks, the Unsigned Integer type of use XDR;
Opaque is identical with the conversion of OCTET STRING;
Counter64, the Unsigned Hyper Integer type of use XDR;
Unsigned32, the Unsigned Integer type of use XDR;
In addition, for the SNMP object of form types, adopt a structure that the variable of form is encapsulated and get final product, because the form types member is made of above-mentioned simple types, then can be considered as be conversion to member in the form in the conversion of form.
(C), the conversion of the improper value that returns of RPC call error value and SNMP operation requests:
The terminal error of the invocation of procedure has two kinds of possibilities, and the one, the mistake in the RPC invoked procedure is referred to as external error in embodiments of the present invention; Another kind of is internal error during the invocation of procedure realizes, and this moment, the RPC invoked procedure was successful, and type of error is referred to as internal error in embodiments of the present invention in the return value of the invocation of procedure;
In the RPC process issuable external error comprise that program does not exist, program does not match, process does not exist, parameter does not match, system mistake, authentication error and RPC version error.
More than except that " system mistake ", other wrong only possibility can be converted to all external error values the error condition " noAccess " of SNMP owing to design mistake occurs.Because the error condition of SNMP just is used for prompting usually, NMS no longer is further processed error condition, so the inaccuracy of error condition can not have influence on the management process of NMS.
Internal error is that the requirement according to SNMP when handling the management request of far-end process produces improper value, does not need to change again, and this moment, the return value of RPC process was success.
(D), the implicit type of XDR definition:
The implicit type definition that XDR adopts needs the producer of data and consumer that the explanation of data is reached an agreement in advance, and this problem solves by the process statement of RPC.Comprised parameter and return value type in the statement of RPC process, therefore statement when data are dealt on the server by client computer, can guarantee that both are consistent for the explanation of data with the program that is used for simultaneously on client computer and the server.
(E), the change of invocation of procedure semanteme:
ONC RPC does not guarantee that the invocation of procedure is necessarily reliable, and snmp protocol has also been supposed the unreliability of SNMP operation requests, so the SNMP agency can tolerate the unreliability of RPC;
(F), by the addressing of administration module:
For finishing SNMP agency to by the invocation of procedure of administration module, the OBJECT IDENTIFIER of managed object in the snmp message need be converted to by the address of administration module, by the addressing of administration module is not the scope of the described concern of the embodiment of the invention, and present embodiment can be selected to be determined by the address of administration module by the address table that presets.Owing to constituted the network of device interior between master control borad and the controlled board, in the system schema addressing method must be arranged, the addressing scheme of device interior is generally all fairly simple, for example: if device interior uses is the TCP/IP network, then can with TCP or udp port with by the just curing when the system design of the mapping relations between the administration module.
The method and apparatus that the embodiment of the invention provides docks the SNMP system with ONC RPC system, utilize ONC RPC to transmit management operation request between master control borad and the controlled board.Shield the difference of remote procedure call and LPC by ONC RPC, make SNMP proxy module and constructed, avoid the multistage SNMP agency plant of complex structure by the mode that administration module can still call according to this locality.
Method of the present invention is not limited to the embodiment described in the embodiment, and those skilled in the art's technical scheme according to the present invention draws other execution mode, belongs to technological innovation scope of the present invention equally.Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (10)
1. a node of realizing the SNMP agency on distributed constitution equipment comprises master control borad and controlled board, it is characterized in that, comprises SNMP agency and RPC client computer in the described master control borad; Comprise managed object and RPC server in the described controlled board, wherein,
The SNMP agency, the Simple Network Management Protocol snmp message that the person NMS that is used for the receiving management sends, and the operation requests in this snmp message is converted to invocation of procedure RPC request, this invocation of procedure RPC request is passed to the RPC client computer, and the return value that the RPC client computer is sent is interpreted as the SNMP operating result, and this SNMP operating result is packaged in sends back to described NMS in the SNMP response message;
The RPC client computer is used to use RPC communication that described RPC request is sent to the RPC server, and receives the return value of RPC request;
Described RPC server is used for RPC request is converted to function call to the local management object, sends function call request to described managed object, and described RPC client computer is returned in the return value transmission of described function call request;
Managed object is used to provide the function call interface of the management request finished, and receives the call request that described RPC server sends, and will call the result and return to described RPC server.
2. agent node as claimed in claim 1 is characterized in that, described SNMP agency is used for that also the simple syntactic variable of self and applicational grammar variable are converted into external data XDR and represents.
3. agent node as claimed in claim 1 is characterized in that, the mistake that described SNMP agency also is used for RPC invoked procedure that the RPC request is returned transforms the error condition " noAccess " of SNMP.
4. agent node as claimed in claim 1 is characterized in that, described SNMP agency also is used for the object identity of the managed object of snmp message is converted to the address of managed object.
5. a method that realizes the SNMP agency on distributed constitution equipment is characterized in that, comprising:
When the agency of the SNMP in the master control borad receives the Simple Network Management Protocol snmp message of manager NMS transmission, described snmp message is converted to native data formats, and the operation requests in this snmp message is converted to invocation of procedure RPC request, pass to the RPC client computer that is provided with on this master control borad;
The RPC client computer uses RPC communication that the RPC request is sent to RPC server on the controlled board;
RPC server on the controlled board is converted to function call to the local management object with RPC request, and calls and describedly finished the management solicit operation by administration module, and master control borad is returned in the return value transmission of the invocation of procedure;
After described SNMP agency receives described return value, this return value is interpreted as the SNMP operating result, and this SNMP operating result is packaged in the SNMP response message returns to NMS.
6. method as claimed in claim 5 is characterized in that, the operation requests in this snmp message is converted to invocation of procedure RPC request, comprising:
The simple syntactic variable of described SNMP request and applicational grammar variable are converted into external data XDR to be represented.
7. method as claimed in claim 6 is characterized in that, the simple syntactic variable of described SNMP request is converted into external data XDR to be represented, comprising:
Integer type Integer in the described SNMP request is directly corresponding to the Integer type among the XDR; Use the character string string of XDR to represent 8 hyte character string OCTET STRING; Object identity OBJECT IDENTIFIER will be converted to the address of the managed object in the RPC communication.
8. method as claimed in claim 6 is characterized in that, the applicational grammar variable of described SNMP request is converted into external data XDR represents, comprising:
The fixed length array Fixed-Length Array of use XDR represents the IPv4 address IpAddress in the SNMP request, and length is 4;
The signless integer Unsigned Integer type of use XDR is represented 32 digit counter Counter32 in the SNMP request;
The Unsigned Integer type of use XDR is represented 32 signless integer Unsigned32 in the SNMP request;
Use the Unsigned Integer type of XDR to represent time in SNMP request answer TimeTicks that ticks;
The character string string of use XDR represents the nontransparent type Opaque in the SNMP request;
The Unsigned Hyper Integer type of use XDR is represented 64 digit counter Counter64 in the SNMP request;
The Unsigned Integer type of use XDR is represented 64 signless integer Unsigned64 in the SNMP request;
If be the SNMP request of form types, adopt structure that the variable of form is encapsulated.
9. method as claimed in claim 6 is characterized in that, the operation requests in this snmp message is converted to invocation of procedure RPC request also comprises: the address that the object identity of the managed object in the described SNMP request is converted to managed object.
10. method as claimed in claim 5, it is characterized in that, if the SNMP on master control borad agency receives and goes described surely return value after the described return value is RPC call error value, then the mistake in the RPC invoked procedure that the RPC request is returned transforms the error condition " noAccess " of SNMP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102248477A CN101795206B (en) | 2009-11-26 | 2009-11-26 | Method and device for realizing SNMP agent on distributed equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102248477A CN101795206B (en) | 2009-11-26 | 2009-11-26 | Method and device for realizing SNMP agent on distributed equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101795206A true CN101795206A (en) | 2010-08-04 |
| CN101795206B CN101795206B (en) | 2012-08-15 |
Family
ID=42587639
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102248477A Active CN101795206B (en) | 2009-11-26 | 2009-11-26 | Method and device for realizing SNMP agent on distributed equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101795206B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102540911A (en) * | 2010-12-10 | 2012-07-04 | 北京北方微电子基地设备工艺研究中心有限责任公司 | Control device and control method for equipment |
| CN102739552A (en) * | 2012-07-19 | 2012-10-17 | 迈普通信技术股份有限公司 | Method and system for realizing multi-master-control remote procedure call (RPC) |
| CN103339910A (en) * | 2010-11-08 | 2013-10-02 | 谷歌公司 | Full-duplex bi-directional communication over a remote procedure call based communications protocol, and applications thereof |
| US8825825B2 (en) | 2012-03-06 | 2014-09-02 | International Business Machines Corporation | SNMP request processing within distributed device architecture |
| US10860440B2 (en) | 2013-06-26 | 2020-12-08 | EMC IP Holding Company LLC | Scheduled recovery in a data protection system |
| WO2021057802A1 (en) * | 2019-09-23 | 2021-04-01 | 三维通信股份有限公司 | Das system management method and device, electronic device, and storage medium |
| US11113252B2 (en) | 2013-06-26 | 2021-09-07 | EMC IP Holding Company LLC | User selectable data source for data recovery |
| US11113157B2 (en) | 2013-06-26 | 2021-09-07 | EMC IP Holding Company LLC | Pluggable recovery in a data protection system |
| US11240209B2 (en) | 2013-06-28 | 2022-02-01 | EMC IP Holding Company LLC | Data transfer in a data protection system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7451199B2 (en) * | 2002-05-10 | 2008-11-11 | International Business Machines Corporation | Network attached storage SNMP single system image |
| US7472186B2 (en) * | 2004-09-09 | 2008-12-30 | International Business Machines Corporation | Method for using SNMP as an RPC mechanism for exporting the data structures of a remote library |
| CN100484027C (en) * | 2005-09-14 | 2009-04-29 | 华为技术有限公司 | Network management system and method using simple network management protocol |
| CN101494561A (en) * | 2009-03-04 | 2009-07-29 | 中兴通讯股份有限公司 | Network management method and system based on simple network management protocol |
-
2009
- 2009-11-26 CN CN2009102248477A patent/CN101795206B/en active Active
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9258345B2 (en) | 2010-11-08 | 2016-02-09 | Google Inc. | Full-duplex bi-directional communication over a remote procedure call based communications protocol, and applications thereof |
| CN106878267A (en) * | 2010-11-08 | 2017-06-20 | 谷歌公司 | Set up the method and system of full-duplex bi-directional communication |
| CN103339910A (en) * | 2010-11-08 | 2013-10-02 | 谷歌公司 | Full-duplex bi-directional communication over a remote procedure call based communications protocol, and applications thereof |
| CN103339910B (en) * | 2010-11-08 | 2017-02-08 | 谷歌公司 | Full-duplex bi-directional communication over a remote procedure call based communications protocol, and applications thereof |
| CN102540911B (en) * | 2010-12-10 | 2014-08-27 | 北京北方微电子基地设备工艺研究中心有限责任公司 | Control device and control method for equipment |
| CN102540911A (en) * | 2010-12-10 | 2012-07-04 | 北京北方微电子基地设备工艺研究中心有限责任公司 | Control device and control method for equipment |
| US8825825B2 (en) | 2012-03-06 | 2014-09-02 | International Business Machines Corporation | SNMP request processing within distributed device architecture |
| US10659284B2 (en) | 2012-03-06 | 2020-05-19 | International Business Machines Corporation | SNMP request processing within distributed device architecture |
| CN102739552B (en) * | 2012-07-19 | 2015-09-23 | 迈普通信技术股份有限公司 | A kind of method and system realizing many master controls remote procedure call |
| CN102739552A (en) * | 2012-07-19 | 2012-10-17 | 迈普通信技术股份有限公司 | Method and system for realizing multi-master-control remote procedure call (RPC) |
| US10860440B2 (en) | 2013-06-26 | 2020-12-08 | EMC IP Holding Company LLC | Scheduled recovery in a data protection system |
| US11113252B2 (en) | 2013-06-26 | 2021-09-07 | EMC IP Holding Company LLC | User selectable data source for data recovery |
| US11113157B2 (en) | 2013-06-26 | 2021-09-07 | EMC IP Holding Company LLC | Pluggable recovery in a data protection system |
| US11240209B2 (en) | 2013-06-28 | 2022-02-01 | EMC IP Holding Company LLC | Data transfer in a data protection system |
| WO2021057802A1 (en) * | 2019-09-23 | 2021-04-01 | 三维通信股份有限公司 | Das system management method and device, electronic device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101795206B (en) | 2012-08-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101795206B (en) | Method and device for realizing SNMP agent on distributed equipment | |
| Medved et al. | Opendaylight: Towards a model-driven sdn controller architecture | |
| CN101202665B (en) | Method for generating graphical user interface | |
| US6757899B2 (en) | Dynamic CORBA gateway for CORBA and non-CORBA clients and services | |
| CN107454092B (en) | OPCUA and DDS protocol signal conversion device, communication system and communication method | |
| EP2561656B1 (en) | Servlet api and method for xmpp protocol | |
| CN102185716B (en) | Universal management method and system for communication equipment | |
| CN104883266B (en) | network configuration access method and device | |
| CN1968134B (en) | Middleware-based multimedia consolidation service realizing method and system | |
| CN106559251A (en) | A kind of Compilation Method and corresponding interface, component and system based on YANG models | |
| CN104615489B (en) | A kind of implementation method of multinode data interaction | |
| CN107450993A (en) | A kind of data interactive method of distributed IEC61850 communication components | |
| CN111552568A (en) | Cloud service calling method and device | |
| Leppinen et al. | Java-and CORBA-based network management | |
| CN109445384A (en) | A kind of more apparatus control systems | |
| WO2023125755A1 (en) | Service request processing method and apparatus based on large-scale cluster, and device and medium | |
| US20040243693A1 (en) | Inbound connector | |
| Miori et al. | Domotic technologies incompatibility becomes user transparent | |
| CN103475506A (en) | Multi-equipment management control method and multi-equipment management control system | |
| US6898792B1 (en) | Foreign object definition information repository | |
| CN106339307A (en) | Futures exchange transaction front-end system simulator | |
| Popić et al. | Efficient Usage of Resources in SDN by Modifying YANG Modules in Linux-based Embedded Systems | |
| Pavlou | The OSIMIS TMN Platform: Support for Multiple Technology Integrated Management Systems | |
| NL2029244B1 (en) | Method and system for calling, signing, and analyzing blockchain cross-chain contract, and storage medium | |
| AU740953B2 (en) | System and method relating to generic handling of 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 | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: BEIJING Z-GOOD TECHNOLOGY SERVICE CO., LTD. Free format text: FORMER OWNER: FUJIAN XINGWANGRUIJIE NETWORK CO., LTD. Effective date: 20140514 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 350002 FUZHOU, FUJIAN PROVINCE TO: 100085 HAIDIAN, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20140514 Address after: 100085 Beijing city Haidian District No. 33 Xiaoying Road 1 1F06 room Patentee after: BEIJING ZHIGU TECHNOLOGY SERVICES CO., LTD. Address before: Cangshan District of Fuzhou City, Fujian province 350002 Jinshan Road No. 618 Garden State Industrial Park building 19# Patentee before: Fujian Xingwangruijie Network Co., Ltd. |
|
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20100804 Assignee: Fujian Xingwangruijie Network Co., Ltd. Assignor: BEIJING ZHIGU TECHNOLOGY SERVICES CO., LTD. Contract record no.: 2014990000767 Denomination of invention: Method and device for realizing SNMP agent on distributed equipment Granted publication date: 20120815 License type: Common License Record date: 20140924 |
|
| LICC | Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model |