CN100420206C - SNMP communication system and method - Google Patents
SNMP communication system and method Download PDFInfo
- Publication number
- CN100420206C CN100420206C CNB200610066397XA CN200610066397A CN100420206C CN 100420206 C CN100420206 C CN 100420206C CN B200610066397X A CNB200610066397X A CN B200610066397XA CN 200610066397 A CN200610066397 A CN 200610066397A CN 100420206 C CN100420206 C CN 100420206C
- Authority
- CN
- China
- Prior art keywords
- snmp
- management station
- query result
- inquiry
- agency
- 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.)
- Expired - Fee Related
Links
Abstract
The present invention provides an SNMP communication system and a method. The SNMP communication system comprises an SNMP management station, an SNMP agent and managed equipment, wherein the SNMP management station sends an inquiry condition or a setting condition to the SNMP agent; the SNMP agent operates to the corresponding managed equipment; the managed equipment resolves the inquiry condition or the setting condition according to the SNMP management station and an interface predetermined by the managed equipment, and executes corresponding inquiries or setting operation.
Description
Technical field
The present invention relates to a kind of SNMP (Simple Network Management Protocol) communication system and method, particularly a kind ofly can carry out data query in enormous quantities and specify complex conditions to carry out the SNMP communication system and the method for data processing.
Background technology
SNMP is the popular network management standard of present industry, for network management system provides the bottom-layer network management frame.The application of snmp protocol is very extensive, and the network equipment of many kinds, software and system all adopt this agreement to realize the network management management function.
The network management model of SNMP comprises following key element: snmp management station (SNMPManager), SNMP act on behalf of (SNMP Agent), management information bank (MIB) and managed devices (Managed Device).The snmp management station generally is a discrete equipment, is the interface between network manager and the network management system.The equipment of being managed is a node in the network, is called as network element sometimes, and the equipment of being managed can be router, switch, bridge, hub, main frame etc., is all moving a SNMP agency in the network equipment of each support SNMP; The SNMP agency is the network management software module that resides on the managed devices, is responsible for collecting and management information the various situations of the record network equipment.Management information bank is an information repository of being safeguarded by the SNMP agency, is a set with information of hierarchical nature, and it can be controlled by network management system.Defined various data objects in the management information bank, as the set of the management station's accessing points that is located at the Agency, management station can remove control, configuration or monitor network equipment by these data objects of direct control.
The work of managing is acted on behalf of by SNMP in the snmp management station, and one of major function of SNMP agency assists the snmp management station to finish whole Network Management work exactly.SNMP agency regularly collects the important information of managed devices, and the information of collecting is normal when will be used for determining the state of the independently network equipment, subnetwork or the whole network operation.The snmp management phase of standing firm is inquired about the information such as operating condition, configuration and performance that the SNMP agency collects relevant managed devices.
The protocol operation of operation comprises GetRequest, GetNextRequest, SetRequest, GetResponse between snmp management station and the SNMP agency, and their implication is as follows:
GetRequest: the request message that is used to obtain the value of specifying managed object;
GetNextRequest: the request message that is used for obtaining continuously the value of one group of managed object;
SetRequest: the message of value that is used to be provided with the managed object of appointment;
GetResponse: being used to be provided with the request message of the managed object of appointment, is returning of above-mentioned three protocol operations.
On traditional sense, the snmp management station sends requests such as GetRequest, GetNextRequest, SetRequest by network to the SNMP agency, the SNMP agency receives this request, according to the mib file among the MIB (management information bank) management object of managed devices is operated, and send GetResponse respond packet return result to the snmp management station.The object of each management here determines that all its implication and sign determine that by mib file each management object is all passed through unique OID (object identifier) sign.Each management object also is separate, does not also have relevance between mutually, and this is the characteristic of snmp protocol simple general-purpose just also.
The information of the several management objects of managed device its general processing procedure is described below: when need be inquired about in the snmp management station, in GetRequest, specify the OID of these several management objects, after the SNMP agency receives this request, from managed device, obtain corresponding information by internal interface, and return the information that the GetResponse respond packet is responded these several management objects.For example, the snmp management station is if want to inquire about the information of object sysDesc, the sysObjectID (node of the system that defines among the standard RFC1213 (system) group) of managed device, snmp management stands in the OID value 1.3.6.1.2.1.1.1.0 of appointment sysDesc in the GetRequest request package and the OID value 1.3.6.1.2.1.1.2.0 of sysObjectID, and the GetRequest request package is handed down to SNMP agency, the SNMP agency returns corresponding value in the GetResponse respond packet.
When the snmp management station need be provided with the several management objects of managed device, in SetRequest, specify the OID and the corresponding value of these several management objects, the SNMP agency will arrive managed device with the operation setting of these several management objects, and returns to the concrete operating result in snmp management station.For example, the snmp management station is if want to be provided with the object sysContcat and the sysName (node of the system group that defines among the standard RFC1213 of managed device, support read-write (read-write)) the concrete management object value that information, snmp management stand in the OID value 1.3.6.1.2.1.1.4.0 that specifies sysContact in the SetRequest request package and needs to be provided with; And the value of the OID value 1.3.6.1.2.1.1.5.0 of appointment sysName and the concrete management object that needs to be provided with, and the SetRequest request package is handed down to SNMP agency, the SNMP agency is set to managed device with the value of correspondence, and returns corresponding operating result in the GetResponse respond packet.
When the management object of managed device exists when a plurality of, usually it is defined as mibTable, and identifies corresponding management object by the index of table.Such as the ifTable port set that defines among the RFC1213, this moment, the snmp management station can travel through the data of whole table by the GetNextRequest request package, also can be by the object information of concrete certain index of GetRequest request package inquiry.
GetRequest, GetNextRequest and SetRequest request package corresponding response bag all are GetResponse.In the operation of top several modes, generally in GetRequest, GetNextRequest, SetRequest request package, in management object and the GetResponse respond packet to as if one to one.Under this pattern, when the user need be by being provided with simple querying condition, when inquiring about the information of managed device of some more complicated, just be difficult to realize by this traditional Get or Set operation.For example, the snmp management station wishes to specify a number segment to inquire about the user related information of this number segment, the surf time that comprises the user, operator's informaiton etc., perhaps wish to be provided with certain attribute information of certain number segment user, can't realize by this traditional Get or Set operation, the trouble even if operate also quite is (such as can be with user's number information, surf time, operator's informaitons etc. are defined as a mibTable, the index that number information is set to show, come this table of polling operation by assigned indexes), and when the user wants to change the condition of inquiry or setting, want to be provided with certain number segment at certain attribute information of certain surf time such as the user, also can't realize by table defined above.Can't embody the simple general-purpose of snmp protocol in such cases, strengthen the burden of Network Transmission on the contrary.
In addition, snmp protocol is fairly simple to the definition of error code, generally when Get or Set operation failure, determines concrete error message by return an error code in the GetResponse bag.But application scenario below, such as: a plurality of managed devices of SNMP proxy management, certain Get or Set action need SNMP agency obtain information from a plurality of managed devices simultaneously, perhaps operate a plurality of managed devices simultaneously, this moment may be on a plurality of managed devices operation failure, also may be on certain managed device operation failure, and the reason of failure is also different, just by a simple error code be can't be clearly concrete error message.
Summary of the invention
The object of the present invention is to provide a kind of SNMP communication system and method, make the snmp management station can querying condition be set very simply or complicated management object is inquired about or be provided with to the condition that is provided with.
According to SNMP communication system of the present invention, it comprises a snmp management station, SNMP agency, and managed device, and wherein, kind described managed device in described snmp management station has pre-determined an interface; The snmp management station is according to described interface setting querying condition or condition is set, and send querying condition or the condition that is provided with is acted on behalf of to SNMP, the SNMP agent operation is to corresponding managed device, managed device is according to snmp management station and the predetermined interface of managed device, resolve this querying condition or condition is set, carry out corresponding inquiry or setting operation according to analysis result.
In aforesaid SNMP communication system, when transmission querying condition in snmp management station was acted on behalf of with the execution query manipulation to SNMP, the SNMP agency was this inquiry distribution one transmission transaction ID, and sends it to the snmp management station.
In aforesaid SNMP communication system, described querying condition comprises the Record to return of expectation inquiry.
In aforesaid SNMP communication system, if successful inquiring, the SNMP agency is stored in the Query Result descriptor in the Query Result description list, concrete Query Information is stored in the Query Result record sheet, information acquisition request is passed through at the snmp management station, inquiry Query Result description list and Query Result record sheet obtain concrete Query Result.
In aforesaid SNMP communication system, if inquire about or be provided with failure, the SNMP agency is stored in concrete error message in the error message record sheet, and the snmp management station is by information acquisition request, and inquiry error information record sheet obtains concrete error message.
In aforesaid SNMP communication system, described querying condition comprises the parameter that Query Result is sorted, the SNMP agency Query Result is sorted, and the result after will sorting is stored in Query Result description list and the Query Result record sheet according to this parameter.
In aforesaid SNMP communication system, if the SNMP agency is checked through the snmp management station within the predetermined time not to operating with a certain Query Result, the result that then will inquire about removes.
In aforesaid SNMP communication system, corresponding transmission transaction ID can and be inquired about at one in the snmp management station, sends and asks bag to act on behalf of to SNMP clearly, asks the result who removes this inquiry clearly.
According to SNMP communication means of the present invention, it comprises: step a sets in advance the interface between snmp management station and the managed device; Step b, the snmp management station is according to described interface setting querying condition or condition is set, and sends querying condition or the condition that is provided with is acted on behalf of to SNMP, and the SMMP agent operation is to corresponding managed device; Step c, managed device is resolved this querying condition or condition is set according to the interface that step a is provided with, and carries out corresponding inquiry or setting operation according to analysis result.
In aforesaid SNMP communication means, in step b, when transmission querying condition in snmp management station was acted on behalf of with the execution query manipulation to SNMP, the SNMP agency was this inquiry distribution one transmission transaction ID, and sends it to the snmp management station.
In aforesaid SNMP communication means, described querying condition comprises the Record to return of expectation inquiry.
In aforesaid SNMP communication means, in step c, if successful inquiring, then the SNMP agency is stored in the Query Result descriptor in the Query Result description list, concrete Query Information is stored in the Query Result record sheet, the snmp management station is by information acquisition request, and inquiry Query Result description list and Query Result record sheet obtain concrete Query Result.
In aforesaid SNMP communication means, in step c, if inquire about or be provided with failure, the SNMP agency is stored in concrete error message in the error message record sheet, the snmp management station is by information acquisition request, and inquiry error information record sheet obtains concrete error message.
In aforesaid SNMP communication means, the querying condition that sends in step b comprises the parameter that Query Result is sorted, in step c, the SNMP agency is according to this parameter, Query Result is sorted, and the result after will sorting is stored in Query Result description list and the Query Result record sheet.
In aforesaid SNMP communication means, comprise that further SNMP agency checks the step whether operate a certain Query Result at the snmp management station within the predetermined time, if and when being checked through the snmp management station and this Query Result not operated, the step that Query Result is removed.
In aforesaid SNMP communication means, the snmp management station is at one and inquire about corresponding transmission transaction ID, sends request package and acts on behalf of to SNMP, and the step of this Query Result is removed in request.
According to the present invention,, inquire about some complicated management object information thereby make the snmp management station that querying condition can be set very simply by defining a MIB interface.
In addition, the SNMP agency distributes a transmission transaction ID for this inquiry, and sends it to the snmp management station, and concrete result need be inquired about according to this transmission transaction ID in the snmp management station.Thereby each snmp management station can only be inquired about and the corresponding Query Result of its querying condition that oneself sends, and can not inquire about the query manipulation that send at other snmp management station, has therefore strengthened the snmp protocol safety of data transmission.
In addition, when information a lot (data query in enormous quantities) counted in the record that satisfies querying condition, the snmp management station can be provided with the record number that expectation is returned, and with satisfied actual demand, thereby reduced the shared internal memory of SNMP agency.
In addition, at certain concrete operation, particularly during batch operation, when operation failure, can get access to complete failure information.
Description of drawings
Fig. 1 is the schematic diagram of the MIB interface of the present invention's definition;
Fig. 2 is according to snmp management of the present invention station, SNMP agency and managed device performed flow chart when carrying out query manipulation;
Fig. 3 is according to snmp management of the present invention station, SNMP agency and managed device performed flow chart when carrying out setting operation.
Embodiment
The invention provides a kind of technology that a kind of SNMP of expansion communication realizes, realize this MIB interface by defining general MIB interface with expansion SNMP agency (SNMP Agent) and snmp management station (SNMP Manager), data query in enormous quantities carries out data processing with the appointment complex conditions in the network management system to be implemented in.Said SNMP had made full use of the simple general-purpose of snmp protocol simultaneously in inquiry with some defectives when being provided with above this technology had solved, and by a general MIB interface, satisfies any given query in snmp management station or the operation of condition is set.
Below, the flow chart according to SNMP communication means of the present invention is described.
At first, in steps A: define a general MIB interface, can be at all inquiries or the operation of setting, this interface is that snmp management station and managed device are predetermined.According to this interface, managed device can be discerned the included command code of the MIB interface of this definition and concrete parameter or the like; This MIB interface comprises the condition setting district, results display area, and error message recording areas, and this will be described in detail with reference to Fig. 1 below.
Step B:SNMP management station is according to the set MIB interface of steps A, the condition of relevant inquiring or setting is set in the condition setting district, be handed down to the SNMP agency by SetRequest request, and set in advance a transmission transaction ID value, and the record number that returns of hope.The SNMP agency is converted to the form that managed device can be discerned with this request, and according to the information that this request comprised, operates corresponding managed device (that is, correspondingly being operated to a managed device or a plurality of managed device).Receive the managed device of this request,, resolve this querying condition or condition is set, inquire about and be provided with, and the result is sent to the SNMP agency according to the MIB interface of steps A definition.Then, the corresponding GetResponse of SNMP proxy response wraps, and returns the transmission transaction ID value and the respective record number of a reality;
Step C:SNMP Manage is somebody's turn to do inquiry corresponding object information by GetRequest or GetNextRequest operation poll according to transmission transaction ID value of returning and corresponding record number in results display area;
Step D: if SNMP acts on behalf of the return failure in step B, then the transmission transaction ID value of snmp management station by returning by GetRequest or GetNextRequest operation poll error message recording areas, obtained concrete error message record.
Wherein, for setting operation, step C can not need;
Wherein, for step B, if the snmp management station wishes to return all query note numbers, can specify and wish that the record number that returns is 0, the SNMP agency can return in respond packet inquiring about actual record number.
As shown in Figure 1, it has described the particular content of the defined MIB interface of the present invention, and it comprises condition setting district, results display area, and the error message recording areas.
In the condition setting district, comprise following several leaf node OID definition:
HwConfigcommandCode: concrete inquiry or condition is set, character string type.The condition that the snmp management station is provided with inquiry or is provided with by the value of specifying this node, condition is collaborative definite by management station's side and managed device side, comprise command code and concrete parameter, such as certain routing iinformation of inquiry is set, command code is Qry RouteInfo, concrete parameter is Route=***, concrete parameter can comprise multiple, as set the start-stop route segment, information such as time are set, as long as determined these relevant parameters with managed device, management station just can specify relevant querying condition arbitrarily;
HwConfigcommandTransID: at the transmission transaction ID of certain inquiry, integer type.Transmission transaction ID be between snmp management station and the SNMP agency at the unique identification of certain query manipulation, distribute by the SNMP agency.Snmp management stands in when querying condition is set, and the value of specifying this node is 0, and the SNMP agency distributes concrete value in the respond packet of returning;
HwConfigrowCount: the record number that expectation is returned, integer type.The record number that returns is wished at the snmp management station at certain query manipulation by the value setting of specifying this node, the SNMP agency can prepare corresponding data according to the record number that the snmp management station is provided with like this, do not need total data is all prepared, to save SNMP agency's internal memory.If all record numbers that satisfy querying condition are wished to return in the snmp management station, the value of then specifying this node is 0, and the SNMP agency returns the concrete record number of corresponding querying condition in the respond packet of returning.
HwConfigCleanTransID: notice SNMP agency removes the affairs ID of memory information, integer type behind certain poll-final.After snmp management stands in certain poll-final, the transmission transaction ID of the value of this node for corresponding inquiry is set, the SNMP agency receives this request back and removes the internal memory of corresponding inquiry.Whether the SNMP agency also can inquire about regular check snmp management station at certain query manipulation, if do not have, the SNMP agency also can remove corresponding internal memory voluntarily, to improve SNMP agency's performance.
Results display area comprises two general mibTable tables: hwConfigResultDescTable and hwConfigResultTable.These two tables hwConfigResultDescTable and hwConfigResultTable are stored among the SNMP agency, the SNMP agency is according to the result of each inquiry, corresponding information is inserted in these tables, the snmp management station utilizes corresponding index, can obtain relevant information, this will be described in detail later.
The hwConfigResultDescTable table comprises the descriptor at certain Query Result, as index, comprises following several node definition with transmission transaction ID:
HwConfigResultDescColumnIndex: the MIB side-play amount of designated result field, provide this field in hwConfigResultTable table last. the numerical value of back;
HwConfigResultDescColumnName: result field title;
HwConfigResultDescColumnType: result field type.
HwConfigResultTable table comprises the Query Result at certain inquiry, as index, comprises following several node definition with transmission transaction ID and recording mechanism:
HwConfigResultIntVal1～hwConfigResultIntVal10 is the value node definition of integer field at Query Result, is defined as 10 at present, can expand according to concrete applicable cases;
HwConfigResultStrVal1～hwConfigResultStrVal10 is the value node definition of character types field at Query Result, is defined as 10 at present, can expand according to concrete applicable cases;
HwConfigResultDateTime1～hwConfigResultDateTime10 is the value node definition of time type field at Query Result, is defined as 10 at present, can expand according to concrete applicable cases;
HwConfigResultIPAddr1～hwConfigResultIPAddr10 is the value node definition of IP address class type-word section at Query Result, is defined as 10 at present, can expand according to concrete applicable cases.
The error message recording areas mainly comprises the hwConfigErrRecordTable table, and this table is stored among the SNMP agency.When inquiring about or failure is set, the SNMP agency is stored in relevant error message in this table, the snmp management station can obtain concrete error message by this table, and it is mainly used at certain inquiry or setting operation, when SNMP agency need operate a plurality of managed device.This table is with hwConfigErrRecordTransID (the affairs ID that equipment side returns during at the failure of certain inquiry or setting operation, the error code that the corresponding device side is returned) and hwConfigErrRecordIndex (at certain this turkey recording of information number) as index, comprise following several node definition:
HwConfigErrRecordTime, the time that turkey takes place;
HwConfigErrRecordNodeName produces wrong corresponding managed device title when operating equipment;
HwConfigErrRecordIPAddress produces wrong managed device place host IP address when operating equipment;
HwConfigErrRecordObject, the object of concrete failure;
HwConfigErrRecordCauseID, the reason ID of failure.
The present invention relates to the snmp management station by query manipulation and the setting operation of SNMP agency to managed device, its operating process is different, is described respectively below.
Below, with reference to Fig. 2, query manipulation is carried out at snmp management station 11 by 12 couples of managed device 131-13n of SNMP agency flow process is described.
At first, snmp management station 11 is provided with querying condition, and following Several Parameters need be set: specifying command code and relevant parameters condition, these conditions in the hwConfigcommandCode node is that snmp management station 11 and managed device are consulted to determine; In the hwConfigcommandTransID node, specify affairs ID value (TransID) at this inquiry, this value is distributed by SNMP agency 12, be used for discerning each inquiry, it is 0 that snmp management station 11 is provided with this value earlier, and snmp management station 11 also can this value be set to other values certainly; Regularly hope the record number that SNMP agency 12 returns at this inquiry expectation at the hwConfigrowCount middle finger, return the record that all meet querying condition if wish SNMP agency 12, then this value is set is 0 at snmp management station 11.After specifying these nodes, snmp management station 11 assembling SetRequest request package are issued to SNMP agency 12 with querying condition.In this example, the TransID of setting is 0.
SNMP agency 12 may need to obtain data to managed device after receiving this request, therefore need to operate managed device by the internal interface of SNMP agency 12 and managed device again, and possible operation is to a plurality of managed devices; At this moment, SNMP agency 12 at first is converted to the form that managed device can be discerned with the request that snmp management station 11 sends, and then according to the information that this request comprised, operates corresponding managed device 131-13n.Receive the managed device 131-13n of this request,, resolve this querying condition, inquire about according to the content of set MIB interface.Then, managed device returns to SNMP agency 12 with operating result (Query Result).
SNMP agency 12 judges whether the operation of inquiry managed device is successful.If operate successfully, the record number that statistics is actual, and carry out respective handling according to the hwConfigrowCount value that snmp management station 11 is provided with in the SetRequest request package: if snmp management station 11 is provided with its value in request package is 0, and then SNMP agency 12 values that this node in the respond packet is set are actual record number; If this nodal value that snmp management station 11 is provided with in request package is less than the record number of reality, then SNMP agency 12 values that this node in the respond packet is set are the snmp management station 11 desired values of returning; If the value of this node that snmp management station 11 is provided with in request package is greater than the record number of reality, then SNMP agency 12 is provided with the record number of the value of this node in the respond packet for reality.SNMP agency 12 distributes a unique inquiry transaction ID at this inquiry simultaneously, and response GetResponse wraps to snmp management station 11, returns the record number and the transmission transaction ID of reality in this bag.If the query manipulation failure then responds GetResponse and wraps to snmp management station 11, and clear and definite corresponding error code.In addition, if successful inquiring, then SNMP agency 12 inserts corresponding information in the hwConfigResultDescTable table and hwConfigResultTable table that is stored among the SNMP agency 12; If the inquiry failure, then SNMP agency 12 inserts corresponding information in the hwConfigErrRecordTable table that is stored among the SNMP agency 12.
The GetResponse bag is resolved at snmp management station 11, if return failure, then obtain corresponding error code information, and with error code as index, call the hwConfigErrRecordTable table that the inquiry of GetRequest or GetNextRequest interface is stored among the SNMP agency 12 and obtain concrete failure information.
The GetResponse bag is resolved at snmp management station 11, if operate successfully, the 12 transmission transaction ID that return are acted on behalf of as index with SNMP earlier in snmp management station 11, call GetRequest or GetNextRequest interface and inquire about the descriptor that the hwConfigResultDescTable table that is stored among the SNMP agency 12 obtains Query Result, after getting access to result's descriptor, call the hwConfigResultTable table that the inquiry of GetRequest or GetNextRequest interface is stored among the SNMP agency 12 again and obtain concrete object information.
In the superincumbent operation, if snmp management station 11 wishes to specify certain attribute to carry out sorting operation, the attribute of corresponding ordering then is set in the querying condition that is handed down to SNMP agency 12, by SNMP agency 12 sorting operations of being correlated with, the record that obtains in the results display area is exactly the information after the ordering, like this, be exactly that snmp management station 11 does not also get access to all Query Results, can carry out the complete ordering of Query Result equally.
Act on behalf of 12 performances for promoting SNMP, whether SNMP agency 12 can be provided with one-period detection snmp management station 11 and Query Result be operated: SNMP agency 12 guarantees the integrality of data in this cycle, do not carry out any query manipulation if surpass this cycle snmp management station 11, then SNMP agency 12 can empty the query note of corresponding certain inquiry, to discharge internal memory, after this if query manipulation is carried out again at this Query Result in snmp management station 11, SNMP agency 12 returns a specific error code, and prompting snmp management station 11 needs inquiry that querying condition is set.Snmp management station 11 also can be the corresponding transmission transaction ID of certain inquiry by the value that the hwConfigCleanTransID node is set, and issues the SetRequest request package and requires SNMP agency 12 to discharge the internal memory of corresponding certain inquiry.
Below, with reference to Fig. 3, setting operation is carried out at snmp management station 11 by 12 couples of managed device 131-13n of SNMP agency flow process is described.
At first, snmp management station 11 is provided with condition, only need in the hwConfigcommandCode node command code be set and the relevant parameters condition get final product, and it is definite that these conditions are that snmp management station 11 and managed device are consulted equally.Snmp management station 11 assembling SetRequest request package will be provided with condition and be issued to SNMP agency 12.
SNMP agency 12 may need to obtain data to managed device after receiving this request, therefore need to operate managed device by the internal interface of SNMP agency 12 and managed device again, and possible operation is to a plurality of managed devices; At this moment, SNMP agency 12 at first is converted to the form that managed device can be discerned with the request that snmp management station 11 sends, and then according to the information that this request comprised, operates corresponding managed device 131-13n.Receive the managed device 131-13n of this request,, resolve this condition is set, be provided with according to the content of set MIB interface.Then, managed device returns to SNMP agency 12 with operating result (result is set).
Whether SNMP acts on behalf of 12 decision operation (setting) successful, and the GetResponse that sends response SetRequest request simultaneously wraps to snmp management station 11.If operation failure, then with error code as index, corresponding failure information is filled in the hwConfigErrRecordTable table, this hwConfigErrRecordTable table is stored among the SNMP agency 12.
Receive after the GetResponse bag at snmp management station 11, resolves this GetResponse bag.When determining operation failure, obtain corresponding error code information, and with error code as index, call the hwConfigErrRecordTable table that the inquiry of GetRequest or GetNextRequest interface is stored among the SNMP agency 12 and obtain concrete failure information.
According to the present invention,, make the snmp management station that querying condition can be set very simply and inquire about some complicated management object information by defining a MIB interface.In addition, at certain query manipulation, between snmp management station and SNMP agency, can come the fail safe of guarantee information by a unique transmission transaction ID sign.In addition, when information a lot (data query in enormous quantities) counted in the record that satisfies querying condition, the snmp management station can be provided with the record number that expectation is returned, and with satisfied actual demand, and reduced the shared internal memory of SNMP agency.In addition, when not getting access to all management object information fully, allow satisfying the complete ordering of all data of querying condition at the snmp management station.At certain concrete operation, particularly during batch operation, when operation failure, can get access to complete failure information.
Present embodiment is to the detailed description that the present invention carried out for those of ordinary skills are understood; but those of ordinary skills can expect; can also make other variation and modification in the scope that does not break away from claim of the present invention and contained, it is all in protection scope of the present invention.
Claims (16)
1. SNMP communication system, it comprises a snmp management station, SNMP agency, and managed device, wherein,
Described snmp management station and described managed device have pre-determined an interface;
The snmp management station is according to described interface setting querying condition or condition is set, and send querying condition or the condition that is provided with is acted on behalf of to SNMP, the SNMP agent operation is to corresponding managed device, managed device is according to snmp management station and the predetermined described interface of managed device, resolve this querying condition or condition is set, and carry out corresponding inquiry or setting operation according to analysis result.
2. SNMP communication system as claimed in claim 1, wherein,
When transmission querying condition in snmp management station was acted on behalf of with the execution query manipulation to SNMP, the SNMP agency was this inquiry distribution one transmission transaction ID, and sends it to the snmp management station.
3. SNMP communication system as claimed in claim 2, wherein,
Described querying condition comprises the Record to return of expectation inquiry.
4. SNMP communication system as claimed in claim 3, wherein,
If successful inquiring, the SNMP agency is stored in the Query Result descriptor in the Query Result description list, concrete Query Information is stored in the Query Result record sheet,
The snmp management station is by information acquisition request, and inquiry Query Result description list and Query Result record sheet obtain concrete Query Result.
5. SNMP communication system as claimed in claim 3, wherein,
If inquire about or be provided with failure, the SNMP agency is stored in concrete error message in the error message record sheet,
The snmp management station is by information acquisition request, and inquiry error information record sheet obtains concrete error message.
6. as each described SNMP communication system of claim 1-4, wherein,
Described querying condition comprises the parameter that Query Result is sorted, and SNMP acts on behalf of according to this parameter, Query Result is sorted, and the result after will sorting is stored in Query Result description list and the Query Result record sheet.
7. as each described SNMP communication system of claim 1-5, wherein,
If the SNMP agency is checked through the snmp management station within the predetermined time and a certain Query Result is not operated, then this Query Result is removed.
8. as each described SNMP communication system of claim 2-5, wherein,
The snmp management station is at one and inquire about corresponding transmission transaction ID, sends request package and acts on behalf of to SNMP, and the result of this inquiry is removed in request.
9. SNMP communication means, it comprises:
Step a sets in advance the interface between snmp management station and the managed device;
Step b, the snmp management station is according to the described interface setting querying condition that is provided with among the step a or condition is set, and sends querying condition or the condition that is provided with is acted on behalf of to SNMP, and the SNMP agent operation is to corresponding managed device;
Step c, managed device is resolved this querying condition or condition is set according to the described interface that step a is provided with, and carries out corresponding inquiry or setting operation according to analysis result.
10. SNMP communication means as claimed in claim 9, wherein,
In step b, when transmission querying condition in snmp management station was acted on behalf of with the execution query manipulation to SNMP, the SNMP agency was this inquiry distribution one transmission transaction ID, and sends it to the snmp management station.
11. SNMP communication means as claimed in claim 10, wherein,
Described querying condition comprises the Record to return of expectation inquiry.
12. SNMP communication means as claimed in claim 11, wherein,
In step c, if successful inquiring, then the SNMP agency is stored in the Query Result descriptor in the Query Result description list, concrete Query Information is stored in the Query Result record sheet,
The snmp management station is by information acquisition request, and inquiry Query Result description list and Query Result record sheet obtain concrete Query Result.
13. SNMP communication means as claimed in claim 11, wherein,
In step c, if inquire about or be provided with failure, the SNMP agency is stored in concrete error message in the error message record sheet,
The snmp management station is by information acquisition request, and inquiry error information record sheet obtains concrete error message.
14. as each described SNMP communication means of claim 9-12, wherein,
The querying condition that sends in step b comprises the parameter that Query Result is sorted,
In step c, SNMP acts on behalf of according to this parameter, Query Result is sorted, and the result after will sorting is stored in Query Result description list and the Query Result record sheet.
15. as each described SNMP communication means of claim 9-13, it further comprises:
SNMP agency checks the step whether operate a certain Query Result at the snmp management station within the predetermined time, and
If when being checked through the snmp management station and this Query Result not operated, the step that Query Result is removed.
16. as each described SNMP communication means of claim 10-13, it further comprises:
The snmp management station is at one and inquire about corresponding transmission transaction ID, sends request package and acts on behalf of to SNMP, and the result's of this inquiry step is removed in request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610066397XA CN100420206C (en) | 2006-04-05 | 2006-04-05 | SNMP communication system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610066397XA CN100420206C (en) | 2006-04-05 | 2006-04-05 | SNMP communication system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1859216A CN1859216A (en) | 2006-11-08 |
| CN100420206C true CN100420206C (en) | 2008-09-17 |
Family
ID=37298082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200610066397XA Expired - Fee Related CN100420206C (en) | 2006-04-05 | 2006-04-05 | SNMP communication system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100420206C (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101192994B (en) * | 2007-07-25 | 2010-06-02 | 中兴通讯股份有限公司 | A method for conditionally getting data in SNMP |
| CN101247272B (en) * | 2008-03-24 | 2011-05-11 | 中兴通讯股份有限公司 | Network management method and apparatus |
| CN101964726B (en) * | 2010-09-21 | 2012-07-25 | 电子科技大学 | SNMP-based reliable data transmission method |
| CN103001807B (en) * | 2012-12-20 | 2015-09-09 | 北京思特奇信息技术股份有限公司 | A kind of request-reply module corresponding with snmp protocol |
| CN103684884B (en) * | 2013-12-31 | 2016-08-31 | 京信通信系统（中国）有限公司 | The method and system of data communication is optimized based on SNMP |
| CN105512134A (en) * | 2014-09-25 | 2016-04-20 | 中兴通讯股份有限公司 | Method and system for querying data based on SNMP protocol |
| CN105790979A (en) * | 2014-12-22 | 2016-07-20 | 中兴通讯股份有限公司 | Network operation management method and device |
| CN107528723A (en) * | 2017-07-07 | 2017-12-29 | 中国南方电网有限责任公司 | A kind of communication means suitable for power system interchanger |
| CN109120443A (en) * | 2018-08-17 | 2019-01-01 | 郑州云海信息技术有限公司 | A kind of management method and device of network attached storage NAS device |
| CN110034949A (en) * | 2019-02-21 | 2019-07-19 | 国电南瑞科技股份有限公司 | A kind of Write-protection method based on snmp protocol |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6199109B1 (en) * | 1998-05-28 | 2001-03-06 | International Business Machines Corporation | Transparent proxying of event forwarding discriminators |
| US6219703B1 (en) * | 1996-10-31 | 2001-04-17 | Motorola, Inc. | Method and apparatus for constructing a device management information base in a network management station |
| CN1403916A (en) * | 2002-09-24 | 2003-03-19 | 浙江浙大网新科技股份有限公司 | SNMP monitoring method of browser content |
| WO2003032577A1 (en) * | 2001-10-05 | 2003-04-17 | Globespan Virata Incorporated | System and method for fully populating a snmp management information base by means of default values |
| US20030093426A1 (en) * | 2001-11-13 | 2003-05-15 | Gunther Peter | Method and system for network configuration discovery |
| CN1445671A (en) * | 2002-03-15 | 2003-10-01 | 联想(北京)有限公司 | Monitoring method for remote alarming information in real time and with accuracy position |
| CN1581795A (en) * | 2003-08-06 | 2005-02-16 | 华为技术有限公司 | Network management safety authentication method |
| CN1753402A (en) * | 2004-09-22 | 2006-03-29 | 中兴通讯股份有限公司 | Method of using simple network management protocol to act multirariant block inquiry |
-
2006
- 2006-04-05 CN CNB200610066397XA patent/CN100420206C/en not_active Expired - Fee Related
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6219703B1 (en) * | 1996-10-31 | 2001-04-17 | Motorola, Inc. | Method and apparatus for constructing a device management information base in a network management station |
| US6199109B1 (en) * | 1998-05-28 | 2001-03-06 | International Business Machines Corporation | Transparent proxying of event forwarding discriminators |
| WO2003032577A1 (en) * | 2001-10-05 | 2003-04-17 | Globespan Virata Incorporated | System and method for fully populating a snmp management information base by means of default values |
| US20030093426A1 (en) * | 2001-11-13 | 2003-05-15 | Gunther Peter | Method and system for network configuration discovery |
| CN1445671A (en) * | 2002-03-15 | 2003-10-01 | 联想(北京)有限公司 | Monitoring method for remote alarming information in real time and with accuracy position |
| CN1403916A (en) * | 2002-09-24 | 2003-03-19 | 浙江浙大网新科技股份有限公司 | SNMP monitoring method of browser content |
| CN1581795A (en) * | 2003-08-06 | 2005-02-16 | 华为技术有限公司 | Network management safety authentication method |
| CN1753402A (en) * | 2004-09-22 | 2006-03-29 | 中兴通讯股份有限公司 | Method of using simple network management protocol to act multirariant block inquiry |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1859216A (en) | 2006-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100420206C (en) | SNMP communication system and method | |
| CN100544282C (en) | A kind of trouble correlation analytic system and method | |
| US6330560B1 (en) | Multiple manager to multiple server IP locking mechanism in a directory-enabled network | |
| US5978845A (en) | Network management relay mechanism | |
| US6286040B1 (en) | User-friendly interface for setting expressions on an SNMP agent | |
| JP4132441B2 (en) | Data management device for managed objects | |
| US20040078457A1 (en) | System and method for managing network-device configurations | |
| WO2012041388A1 (en) | Generation of a query plan for accessing a database | |
| US6484160B1 (en) | Process for optimizing accesses to a database | |
| CN101099398B (en) | Method and devices for matching data between a manager and an agent in a management network | |
| US6502130B1 (en) | System and method for collecting connectivity data of an area network | |
| CN101247272B (en) | Network management method and apparatus | |
| CN101582881A (en) | Method and device for controlling access | |
| CN102684894B (en) | Method and device for realizing northboundbound interface | |
| US6694304B1 (en) | System and method for retrieving network management table entries | |
| EP1639492B1 (en) | Discovering and merging network information | |
| JP2000066978A (en) | Network management information collection system, network management device to be used for the system and node to be managed | |
| US7653709B1 (en) | Method for remote interrogation of SNMP agents | |
| Cisco | Glossary | |
| KR100358156B1 (en) | Converting Method of Managing Operation from service management system to Switching Command in a Integrated Network | |
| Cisco | Glossary | |
| Cisco | Glossary | |
| US20070022313A1 (en) | Notifications in a telecommunications network | |
| US6622146B1 (en) | System managing method and apparatus for decreasing a load applied to a common processing unit | |
| JP3533911B2 (en) | Integrated network management system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080917 Termination date: 20150405 |
|
| EXPY | Termination of patent right or utility model |