CN101076028A - Method for interacting telecommunication system and message by SNMP protocol - Google Patents
Method for interacting telecommunication system and message by SNMP protocol Download PDFInfo
- Publication number
- CN101076028A CN101076028A CNA2007101267607A CN200710126760A CN101076028A CN 101076028 A CN101076028 A CN 101076028A CN A2007101267607 A CNA2007101267607 A CN A2007101267607A CN 200710126760 A CN200710126760 A CN 200710126760A CN 101076028 A CN101076028 A CN 101076028A
- Authority
- CN
- China
- Prior art keywords
- message
- snmp
- variable
- managed device
- management station
- 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
Landscapes
- Computer And Data Communications (AREA)
Abstract
The method comprises: S502) defining a interface and its message number and variable between SNMP management station and at least one managed device; S504) SNMP management station sends message to at least one managed device through a SNMP agent, and sequentially bindings the message body of said message in the data binding list according to a preset sequence; taking the last variable in the data field binding list as the message; S506) according to the message number, the managed device makes process and takes out the message body form the variable binding list according to a preset sequence.
Description
Technical field
The present invention relates to the communications field, relate in particular to the communication system and the method for message interaction that adopt snmp protocol.
Background technology
Simple Network Management Protocol SNMP is that specialized designs is used for a kind of standard agreement at network managing network node (server, work station, router, switch etc.), and it is a kind of application layer protocol.SNMP makes that the network manager can supervising the network usefulness, finds and solve the growth of problem in the network (Trap or the INFORM message that report by the SNMP receiving equipment) and planning network.
The network of snmp management has three main parts: the equipment of being managed, agency (Agent) and network management system (nms).Managed devices is a network node (server, work station, router, a switch etc.), comprises SNMP agency and is among the supervising the network, and it mainly is to collect and management information.By SNMP, network management system NMS can obtain these information.Agency (Agent) is a network management software module on the managed devices.The SNMP agency has local related administrative information, and they are converted to the form compatible mutually with SNMP.
SNMP V1 has defined 5 kinds of messages:
The Get-Request operation: managing process extracts the value of one or more parameters from agent process.
The Get-Next-Request operation: managing process extracts the value of the next parameter of one or more parameters from agent process.
The Set-Request operation: managing process is provided with one or more parameter values of agent process.
The Get-Response operation: one or more parameter values that agent process returns, it is the operation response of the 3 kinds of operations in front.
The Trap operation: the message that agent process initiatively sends, the notice managing process has thing that (redefining the V2-Trap into SNMP in V2) takes place.
Increased by 2 kinds of messages among the SNMP V2:
The Get-Bulk-Request operation: managing process extracts the value of a plurality of parameters in one or more parameters back from agent process.
Inform-Request operation: be actually the SNMP V2-Trap (trap) that replys.
Introduce the message format (is reference with SNMPV2) that SNMP is packaged into the operation of UDP datagram below, as Fig. 1, a SNMP message is by a version identifier (versionidentifier), and a SNMP community identifier (community name) and a data field (PDU) are formed.Version identifier is used to distinguish the SNMP version, and 0 is SNMPV1, and 1 is SNMP V2.Community represents to accord with the character string password that is actually managing process and agent process use.PDU then is through the coded data field.
PDU form such as Fig. 2 that SNMP V2 is basic, the GetRequest of SNMPv1, GetNextRequest, GetResponse and SetRequest have the form identical with V2, just the Trap of SNMPv1 has different forms with them, and the Trap of SNMPv1 is also different with the SNMPv2-Trap form of SNMPv2.The PDU type field is used for distinguishing concrete action type, and request identifier (Request-ID) is one 32 a integer.Request-ID value in a Response-PDU is got the Request-ID value of that request PDU that it responds.Error condition (Error Status) and error indexes (Error Index): in a response message Response-PDU, extra incident has taken place the error condition of non-zero (Error Status) value representation makes and can not finish requested operation.At this moment, the nonzero value of error indexes (Error Index) has represented to cause the information of that variable binding in the variable binding table of this additional events.Comprise many variable bindings { name, value}, the variable of representative operation in the variable binding table.
Need to follow unified interface between management station and the managed device, the data that can be used on the managed device are just known by management station like this, and such interface defines with mib file.MIB refers to management information bank, specifically is meant what agent process comprised, and the set of the process that can be inquired about and be provided with by managing process.The define method of interface is with unified grammer (structure of management information SMI), and to file (mib file), management server and proxy server are resolved file according to the grammer of regulation with information description, thus the information of obtaining.
Operation all is to be initiated by network management system basically in the snmp protocol, agent side is passive accepts operations such as GET that network management system initiates and SET, and agent side has only can notify by Trap (trap) or INFORM (notice) self some major events generations.At first, this is a very simple interaction models, and is inapplicable under the application scenarios of comparatively complicated interacting message.Such as, network management system is wished by own given parameter, and obtain the data want from agent side, not all right by the GET operation, because can't go to be provided with parameter, change strategy, before the GET operation, give agent side parameters needed SET earlier, the result also is infeasible, when because network management system does not know that agent side can be needed DSR, having had only DSR can go to obtain by the GET operation, the 3rd strategy can allow agent side be ready to data, coming GET with Trap or INFORM informing network management system, perhaps directly variable is bundled in the list of bindings of Trap or INFORM to upload, the 3rd strategy is feasible, if but such operation is cumbersome.Secondly, in the existing interaction models, it is bigger that network management system gets pressure ratio, because the data of a lot of agent sides all will be removed poll by network management system.
If can realize interacting message on the basis of the agreement of SNMP, the problems referred to above just have been readily solved.
Summary of the invention
At above one or more problems, the invention provides the communication system and the method for message interaction that adopt snmp protocol, solved comparatively simple question of present SNMP interaction models, and only the setting by a variable just can allow the NMS agent side of unifying make multiple response, has realized the interacting message mechanism in the conventional system.
Communication system according to employing snmp protocol of the present invention comprises: the snmp management station is used for and the pre-defined interface of at least one managed device, and resolves from the message of at least one managed device and carry out corresponding operating according to interface; The SNMP agency is used to transmit the message from snmp management station or at least one managed device; And at least one managed device, be used for resolving from the message at snmp management station and carrying out corresponding operating according to predefined interface.
Wherein, the message that the snmp management station is sent at least one managed device is by being provided with request msg field SET-REQUEST PDU carrying, and last variable that will be provided with in the variable Bindings list in the request msg field is bound message number.
Message number is set to the SNMP agency is provided with variable according to the order of variable Bindings list when reception is provided with the request msg field value.
At least one managed device is sent to the message at snmp management station by SNMP v2Trap or the carrying of Inform data field, and second variable in its variable Bindings list bound what be used to identify SNMP v2 Trap (trap) or the carrying of Inform (notice) data field is the information of message, and last variable in the variable Bindings list is bound message number.
Method for message interaction according to portion's employing snmp protocol of the present invention may further comprise the steps: step S502, defining interface and message number and variable between snmp management station and at least one managed device; Step S504, the snmp management station sends message by at least one SNMP agency at least one managed device, the message body order by appointment of message is bundled in the data field list of bindings, and last variable in the list of bindings of data field is bound message number; And step S506, managed device is handled according to message number, and by appointment order takes out message body from variable Bindings list.
The snmp management station is sent to the message of at least one managed device by request msg field SET-REQUEST PDU carrying is set.
Method for message interaction according to employing snmp protocol of the present invention may further comprise the steps: step S512, defining interface and message number and variable between snmp management station and at least one managed device; Step S514, managed device sends message by at least one SNMP agency to the snmp management station, the message body order by appointment of message is bundled in the data field list of bindings, and last variable in the list of bindings of data field is bound message number; And step S516, handle according to message number at the snmp management station, and by appointment order takes out message body from variable Bindings list.
At least one managed device is sent to the message at snmp management station by SNMP v2Trap or the carrying of Inform data field, and second variable in its variable Bindings list bound what be used to identify SNMP v2Trap or the carrying of Inform data field is the information of message, and last variable in the variable Bindings list is bound message number.
The invention solves comparatively simple question of present SNMP interaction models, and only the setting by a variable just can allow the NMS agent side of unifying make multiple response, has realized the interacting message mechanism in the conventional system.Interacting message has been arranged, effectively reduced the burden of network management system, network traffics have been offered on can the active with agent side in the operation of a lot of polls alternative, also effectively less.Expanded the application scenarios of snmp protocol, can be applied to network management easily but have in the environment of interacting message.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram of SNMP message format;
Fig. 2 is the schematic diagram of the basic PDU form of SNMP V2;
Fig. 3 is the schematic diagram according to interface example between management station of the present invention and the managed device;
Fig. 4 is the block diagram according to the communication system of employing snmp protocol of the present invention;
Fig. 5 A and Fig. 5 B are the flow charts according to the method for message interaction of employing SNMP of the present invention;
Fig. 6 is the flow chart that managed devices according to the present invention is accepted management station's message; And
Fig. 7 is the flow chart that management station according to the present invention accepts managed devices message.
Embodiment
Below with reference to accompanying drawing, describe the specific embodiment of the present invention in detail.
Purpose of the present invention is exactly to solve the existing more limited problem of SNMP interaction models function ratio, realizes the function of interacting message in snmp protocol with existing technology.
Fig. 4 is the block diagram according to the communication system of employing snmp protocol of the present invention.As shown in Figure 4, comprise according to the communication system of employing snmp protocol of the present invention: snmp management station 402 is used for and the pre-defined interface of at least one managed device, and resolves from the message of at least one managed device and carry out corresponding operating according to interface; SNMP agency 404 is used to transmit the message from snmp management station or at least one managed device; And at least one managed device 406, be used for resolving from the message at snmp management station and carrying out corresponding operating according to predefined interface.
Message can be sent out to the SNMP agency in the snmp management station, again by acting on behalf of managed device, managed device is resolved message according to snmp management station and the predefined interface of managed device, carry out corresponding operation again, managed device also can be sent out message to the snmp management station by the SNMP agency, message also can be resolved by itself and the predefined interface of managed device in the snmp management station, and carries out corresponding action.
The snmp management station is carried by Set-Request PDU to the message of managed device, last variable in its variable Bindings list is bound message number, should be SNMP agency and be the order value that variable is set one by one according to its variable Bindings list when accepting Set-Request PDU, like this when managed device is received message number, whole message body is accepted fully, then can carry out respective handling according to message number this moment.
In above-mentioned SNMP communication system, managed device is carried by SNMP v2 Trap or Inform PDU to the message at snmp management station, second variable in its variable Bindings list bound and self-definingly is used for identifying that this SNMP v2 Trap or Inform PDU carried is the trap OID of message rather than trap, it (is not essential that last variable in its variable Bindings list is bound message number herein, only for unified to the message of managed device) with the snmp management station, after whole PDU is accepted by management station, management station can go to look into the value of second variable binding in its variable Bindings list and determine that this PDU is common Trap or INFORM or a piece of news, be that message is then taken out message number in the variable of last from variable Bindings list, carry out respective handling according to message number then.
Fig. 5 A and Fig. 5 B are the flow charts according to the method for message interaction of employing SNMP of the present invention.
Fig. 5 A is that the method for message interaction from the snmp management station at least one managed device may further comprise the steps: step S502, defining interface and message number and variable between snmp management station and at least one managed device; Step S504, the snmp management station sends message by at least one SNMP agency at least one managed device, the message body order by appointment of message is bundled in the data field list of bindings, and last variable in the list of bindings of data field is bound message number; And step S506, managed device is handled according to message number, and by appointment order takes out message body from variable Bindings list.
The snmp management station is sent to the message of at least one managed device by request msg field SET-REQUEST PDU carrying is set.
Shown in Fig. 5 B, at least one managed device may further comprise the steps to the method for message interaction at snmp management station: step S512, defining interface and message number and variable between snmp management station and at least one managed device; Step S514, managed device sends message by at least one SNMP agency to the snmp management station, the message body order by appointment of message is bundled in the data field list of bindings, and last variable in the list of bindings of data field is bound message number; And step S516, handle according to message number at the snmp management station, and by appointment order takes out message body from variable Bindings list.
At least one managed device is sent to the message at snmp management station by SNMP v2Trap or the carrying of Inform data field, and second variable in its variable Bindings list bound what be used to identify SNMP v2 Trap or the carrying of Inform data field is the information of message, and last variable in the variable Bindings list is bound message number.
The method for message interaction that this method proposes specifically comprises following key step:
Step 1, the interface (mib file) between definition management station and the managed device.
A, definition message number leaf node in the Mib file, the value of message number represents that with a signless integer OID of this leaf node is exactly the OID of message number.
B defines special trap OID, represents that this Trap or Inform PDU are message.
C defines other variable according to message body.
Step 2, management station sends message to managed device, sees Fig. 6.
Management station generates Set-Request PDU according to the message that will send, the order of the message body of this message by agreement is bundled in the list of bindings of PDU, the value of the OID of message number and message number is bound last variable of PDU, and send to authorized agency (S602).
The agency receives Set-Request PDU, and according to its variable Bindings list the value (S604) of variable is set, if last variable is not a message number, then handles (S610) as common Set-Request PDU.When the OID of last variable of finding to be provided with was the OID (S606) of message number, after then the value setting of this variable being finished, message call was handled entrance function (S608).Judge message number whether legal (S612), if message number is legal, in the Message Processing routine, handle function (this function is generally provided by managed device) (S616) according to the message number message call, if have, then by appointment order takes out message body from the variable Bindings list of PDU, if do not have corresponding message number then carry out fault processing.If illegal, then carry out abnormality processing (S616).
Step 3, managed device sends message to management station, sees Fig. 7.
Managed device generates Trap or Inform PDU according to message, second variable of this PDU variable Bindings list is set to step 1) middle S602) defined special trap OID, then the order of the message body of this message by agreement is bundled in the list of bindings of PDU, at last the OID of message number and value are bound last variable of this PDU list of bindings, and send to management station by the agency.
Trap or Inform PDU (S702) receive in management station, check second variable of its variable Bindings list, if not step 1) in S602) whether defined second variable be special trap OID (S704), as figure be not, then this PDU is handled (S706) as common Trap or Inform, otherwise retrieve last variable (S708) of this PDU variable Bindings list, if when finding that the OID of last variable is not the OID of message number, carry out fault processing (S712), otherwise message call is handled entrance function (S714).In the Message Processing routine, handle function, if do not have corresponding message number then carry out fault processing according to the message number message call.If have, then by appointment order takes out message body (S716) from the variable Bindings list of PDU.
For purpose of the present invention, technical scheme and beneficial effect are described better, adopt snmp protocol to realize that interacting message is described in detail (wherein on the master control veneer management station is arranged, on the RDM radio frequency check-out console proxy module is arranged) below between master control veneer in the base station of WCDMA and the RDM radio frequency check-out console:
One, the interface (mib file) between definition management station and the managed device is seen Fig. 4.Defining message header is msgHeadDef, and wherein comprising message number is msgId, and OID is 1.3.6.1.4.1.1943.1.4.2, and the message sequence number is sequenceNo.
The trap OID that defines sign Trap or Inform PDU and be message is 1.3.6.1.4.1.1943.1.0.1, and name is called rdmInformMsgHead.
According to other variable of message definition, that uses here has a request of 1.3.6.1.4.1.1943.1.5.1cmFrequencyResponse initial configuration, reprovision is receiveed the response 1.3.6.1.4.1.1943.1.5.2cmFrequencyResponse because be null message all, institute is not in the hope of hanging leaf node down, 1.3.6.1.4.1.1943.1.6.1cmFrequencyCfgHead (reprovision request) responded in the initial configuration request, having defined message body below, is a structure that comprises a table (aTwrdmFreqInfoTable).
Two, RDM radio frequency check-out console is sent out power on prompting and initial configuration request to master control veneer.
Peripheral single board powers on successfully, sends cold start-up Trap to master control veneer.
The message of peripheral single board structure initial configuration request sends to the proxy module of RDM radio frequency check-out console, and proxy module sends this message transformation for SNMP PDU.
Master control veneer is received this PDU, check second variable of its variable Bindings list, if not 1.3.6.1.4.1.1943.1.0.1rdmInformMsgHead, then this PDU is handled as common Trap, otherwise retrieve last variable of this PDU variable Bindings list, if when finding that the OID of last variable is not the MsgId1.3.6.1.4.1.1943.1.4.2 of message number, carry out fault processing, otherwise message call is handled entrance function.
In the Message Processing routine, handle function: if the initial configuration request message is then constructed initial configuration and receiveed the response, and sends to peripheral single board by SNMP according to the message number message call.If the processing function of this message does not then enter fault processing.
Three, master control veneer is responded the initial configuration request.
The agency receives Set-Request PDU, and have more the value that its variable Bindings list is provided with variable, when the OID of last variable of finding to be provided with is the OIDMsgId 1.3.6.1.4.1.1943.1.4.2 of message number, after then the value setting of this variable being finished, message call is handled entrance function, otherwise does not handle.
Handle function according to the message number message call in the Message Processing routine: if initial configuration receives the response, then the data of carrying in the initial configuration echo message are fitted in the module of RDM radio frequency check-out console and go, RDM radio frequency check-out console enters normal operating conditions.If this message processing function does not then enter fault processing.
From above performance, the technical scheme that the present invention proposes can realize interacting message on the basis of snmp protocol.
Adopt the inventive method, compared with prior art, mainly contain following advantage:
(1) solved comparatively simple question of present SNMP interaction models, and only the setting by a variable just can allow the NMS agent side of unifying make multiple response, has realized the interacting message mechanism in the conventional system.
(2) interacting message has been arranged, effectively reduced the burden of network management system, network traffics have been offered on can the active with agent side in the operation of a lot of polls alternative, also effectively less.
(3) expanded the application scenarios of snmp protocol, can be applied to network management easily but have in the environment of interacting message.
(4) this method can coexist with original snmp protocol, and it is the expansion of doing on the basis of snmp protocol.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1. communication system that adopts snmp protocol is characterized in that comprising:
The snmp management station is used for and the pre-defined interface of at least one managed device, and resolves from the message of described at least one managed device and carry out corresponding operating according to described interface;
The SNMP agency is used to transmit the message from described snmp management station or described at least one managed device; And
Described at least one managed device is used for resolving from the message at described snmp management station and carrying out corresponding operating according to predefined interface.
2. communication system according to claim 1, it is characterized in that, the message that described snmp management station is sent to described at least one managed device is by being provided with the carrying of request msg field, and last variable in the described variable Bindings list that is provided with in the request msg field is bound message number.
3. communication system according to claim 2 is characterized in that, described message number is set to described SNMP agency and is receiving the described value that variable is set according to the order of described variable Bindings list when the request msg field is set.
4. communication system according to claim 1, it is characterized in that, described at least one managed device is sent to the message at described snmp management station by SNMP v2 Trap or the carrying of Inform data field, and second variable in its variable Bindings list bound what be used to identify described SNMP v2 trap or the carrying of notification data field is the information of message, and last variable in the described variable Bindings list is bound message number.
5. a method for message interaction that adopts snmp protocol is characterized in that, may further comprise the steps:
Step S502, defining interface and message number and variable between snmp management station and at least one managed device;
Step S504, described snmp management station sends message by at least one SNMP agency to described at least one managed device, the message body order by appointment of described message is bundled in the data field list of bindings, and last variable in the list of bindings of described data field is bound message number; And
Step S506, described managed device is handled according to described message number, and by appointment order takes out message body from described variable Bindings list.
6. method for message interaction according to claim 5 is characterized in that, described snmp management station is sent to the message of described at least one managed device by the carrying of request msg field is set.
7. a method for message interaction that adopts snmp protocol is characterized in that, may further comprise the steps:
Step S512, defining interface and message number and variable between snmp management station and at least one managed device;
Step S514, described managed device sends message by at least one SNMP agency to described snmp management station, the message body order by appointment of described message is bundled in the data field list of bindings, and last variable in the list of bindings of described data field is bound message number; And
Step S516, handle according to described message number at described snmp management station, and by appointment order takes out message body from described variable Bindings list.
8. method for message interaction according to claim 7, it is characterized in that, described at least one managed device is sent to the message at described snmp management station by SNMP v2 trap or the carrying of notification data field, and second variable in its variable Bindings list bound what be used to identify described SNMP v2 trap or the carrying of notification data field is the information of message, and last variable in the described variable Bindings list is bound message number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101267607A CN101076028B (en) | 2007-06-21 | 2007-06-21 | Method for interacting telecommunication system and message by SNMP protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101267607A CN101076028B (en) | 2007-06-21 | 2007-06-21 | Method for interacting telecommunication system and message by SNMP protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101076028A true CN101076028A (en) | 2007-11-21 |
| CN101076028B CN101076028B (en) | 2011-08-10 |
Family
ID=38976846
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101267607A Expired - Fee Related CN101076028B (en) | 2007-06-21 | 2007-06-21 | Method for interacting telecommunication system and message by SNMP protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101076028B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217403B (en) * | 2008-01-16 | 2010-09-29 | 中兴通讯股份有限公司 | A realization method of alarming based on SNMP |
| CN101729286B (en) * | 2008-10-21 | 2012-09-05 | 大唐移动通信设备有限公司 | Method, device and system for modifying variables in management information base of agent terminal |
| CN102833091A (en) * | 2011-12-13 | 2012-12-19 | 上海艾泰科技有限公司 | Remote management method for switchboards |
| CN103812690A (en) * | 2013-08-06 | 2014-05-21 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN107528723A (en) * | 2017-07-07 | 2017-12-29 | 中国南方电网有限责任公司 | A kind of communication means suitable for power system interchanger |
| WO2020042413A1 (en) * | 2018-08-28 | 2020-03-05 | 烽火通信科技股份有限公司 | Method and system for implementing state machine in configuration editing process |
| CN111865639A (en) * | 2019-04-30 | 2020-10-30 | 深信服科技股份有限公司 | Method and device for collecting information of snmp service equipment and electronic equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1298137C (en) * | 2003-05-07 | 2007-01-31 | 中兴通讯股份有限公司 | Proxy network management realizing method based on SNMP protocol |
| CN100488122C (en) * | 2006-08-23 | 2009-05-13 | 华为技术有限公司 | System and method for network management |
-
2007
- 2007-06-21 CN CN2007101267607A patent/CN101076028B/en not_active Expired - Fee Related
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217403B (en) * | 2008-01-16 | 2010-09-29 | 中兴通讯股份有限公司 | A realization method of alarming based on SNMP |
| CN101729286B (en) * | 2008-10-21 | 2012-09-05 | 大唐移动通信设备有限公司 | Method, device and system for modifying variables in management information base of agent terminal |
| CN102833091A (en) * | 2011-12-13 | 2012-12-19 | 上海艾泰科技有限公司 | Remote management method for switchboards |
| CN103812690A (en) * | 2013-08-06 | 2014-05-21 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN103812690B (en) * | 2013-08-06 | 2017-02-22 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN107528723A (en) * | 2017-07-07 | 2017-12-29 | 中国南方电网有限责任公司 | A kind of communication means suitable for power system interchanger |
| WO2020042413A1 (en) * | 2018-08-28 | 2020-03-05 | 烽火通信科技股份有限公司 | Method and system for implementing state machine in configuration editing process |
| CN111865639A (en) * | 2019-04-30 | 2020-10-30 | 深信服科技股份有限公司 | Method and device for collecting information of snmp service equipment and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101076028B (en) | 2011-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101076028A (en) | Method for interacting telecommunication system and message by SNMP protocol | |
| EP1729444B1 (en) | A snmp-based asynchronous communication mechanism process method | |
| US6286040B1 (en) | User-friendly interface for setting expressions on an SNMP agent | |
| CN1298137C (en) | Proxy network management realizing method based on SNMP protocol | |
| CN102480759B (en) | Network-management realizing method and system on basis of fit wireless access point architecture | |
| EP2680490B1 (en) | Filtering within device management protocol queries | |
| CN1309211C (en) | Distributed central management method for special shaped network equipment in distributing network environment | |
| CN101030980A (en) | Wide-band terminal identifier based on Ethernet and its identifying method | |
| CN1190042C (en) | Network equipment management method based on ethernet technology | |
| CN1885858A (en) | Method for carrying out cluster management on network equipment based on SNMP protocol | |
| CN1921492A (en) | Method and device for configuration management | |
| CN100499502C (en) | Trap analyzing and preprocessing system and method thereof | |
| CN1437833A (en) | Update of producer-specific hardware information on the producer-independent OMC-NMC interface in a mobile radio network | |
| CN1533115A (en) | Method and device for supporting error reason of simple network management protocol | |
| CN1309208C (en) | Network safety system of computer network and controlling method thereof | |
| CN1581795A (en) | Network management safety authentication method | |
| CN101267335A (en) | A method for guaranteeing successful alarm receiving/transmission in simple network management protocol | |
| CN1801739A (en) | Information service hierarchy inheritance relation realizing method in network management interface | |
| CN1783808A (en) | Method for obtaining network key property indication and key property indication module | |
| CN1705306A (en) | A protocol automatic adapting method and apparatus | |
| CN101035026A (en) | Network management system and its communication method | |
| CN1725701A (en) | Method for implementing terminal management in network equipment | |
| CN1218534C (en) | Method for verifying the authentication of a manager application in a telecommunications management network operating system by means of a network element and network element suitable therefor | |
| CN1574836A (en) | Method for setting up a generic protocol relationship between network elements in a telecom network | |
| CN1523851A (en) | Security method for operator access control of 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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110810 Termination date: 20160621 |