CN105187244A - Access management system of digital communication equipment supporting multiple management modes - Google Patents
Access management system of digital communication equipment supporting multiple management modes Download PDFInfo
- Publication number
- CN105187244A CN105187244A CN201510516678.XA CN201510516678A CN105187244A CN 105187244 A CN105187244 A CN 105187244A CN 201510516678 A CN201510516678 A CN 201510516678A CN 105187244 A CN105187244 A CN 105187244A
- Authority
- CN
- China
- Prior art keywords
- access
- snmp
- management
- module
- function
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
Abstract
The invention provides an access management system of digital communication equipment supporting multiple management modes. The access management system comprises an SNMP (Simple Network Management Protocol) module with a virtual SNMP access processing logic unit and a proxy core unit, a target service module with an MIB (Management Information Base) tree and a management program module. According to the invention, the SNMP module is directly used as a universal management module; a uniform management program is unnecessary to abstract additionally; SNMP application only relates to three operations including GET, GET-NEXT and SET; and the access management system is very succinct and easy to implement.
Description
Technical field
The invention belongs to digital communicating field, refer more particularly to a kind of digital communication equipment access information management supporting multiple management mode.
Background technology
Current network communication apparatus, in order to the diversity requirement of satisfied different client, supports multiple way to manage---order line, SNMP, WEB etc. usually.The usual network equipment is in order to support these way to manages simultaneously, need independently to do functional development by these different service logics, even if same function, also multipass to be developed for different way to manage, rate of code reuse is low, research and development exploitation and safeguard that input cost is high, the consistency that function externally presents is poor, also add the software vulnerability possibility of equipment.
Fig. 1 is the software layer aggregated(particle) structure of current multiple way to manage the network equipment deposited, the network equipment such as, exists the logical business function module of the number such as network device interface, VLAN, equipment, in order to support snmp management, just needs to remove the configuration management function of development interface module, the configuration management function etc. of VLAN module by SNMP function logic; Same equipment also needs to support order line management, just needs the configuration management function etc. of the configuration management function by order line function logic development interface module, VLAN module; Similar, often newly increase a kind of way to manage on network devices, such as WEB way to manage, just again for it develops the configuration management function of all business function module.If there is N kind way to manage, and equipment has M kind business module need configuration management, developer will be input N the exploitation that M kind business module repeats, and concerning each business function module, independent maintenance between the code developed for this N time, once certain business function module changes, the code that the N number of way to manage before developed is relevant all needs amendment.
If different way to manage uses different developers on human resource development drops into, also probably occur that a kind of exploitation of developer to another kind of way to manage of way to manage is indifferent to, to user under different way to manage, the same business function of final products presents that there is some difference.
Summary of the invention
For solving the problem, the invention provides a kind of digital communication equipment access information management supporting multiple management mode, comprise the SNMP module with virtual SNMP access process logical block and Broker Core unit, target service module, the management program module with MIB tree.
Described virtual SNMP access process logical block is for providing the access SNMP access API of module;
Matching inquiry is carried out during the MIB of input parameter in target service module that described Broker Core unit is used for putting according to access API sets;
Management program module, for providing the management function of non-SNMP form, reaches management objectives by access API Access MIB.
Further, access API comprises GETAPI, GET-NEXTAPI, SETAPI, and wherein, GETAPI, GET-NEXTAPI are used for running status and/or the configuring condition of query facility, and SNMPSETAPI is for realizing the setting to equipment.
Further, the input parameter of GETAPI, GET-NEXTAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, and the input parameter of SETAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, the value of object to be configured.
The access method of the above-mentioned digital communication equipment access information management based on SNMP, comprises the steps:
Step one: management program module inputs MIB access request by access API;
Step 2: input parameter is delivered to Broker Core unit by virtual SNMP access process logical block;
Step 3: Broker Core unit carries out matching inquiry according to the MIBOID of access on MIB tree, finds the function point auxiliary code that this MIB is corresponding; Described auxiliary code is be registered to the call back function on MIB tree;
Step 4: auxiliary code judges SNMP request type, adjusts back the execution function of this MIB registration according to request type; Described execution function is the configuration management API of the functional module of SNMP request correspondence;
Step 5: perform function according to SNMP request type executable operations;
Step 6: function returns step by step, access API returns execution result eventually to management program module.
Further, in step 5, if SNMP request type is GET or GET-NEXT, performs function and just take out corresponding value from the functional module that request is corresponding, if SNMP request type is SET, perform function just by functional module corresponding for the settings write request of equipment.
Beneficial effect of the present invention is:
1. the present invention directly uses SNMP module as " general module ", does not need additionally to take out one " unified management program " again.Abstract work itself acquires a certain degree of difficulty and can increase exploitation amount, and SNMP module itself is well suited for serving as this function: first it is the function that digital communication equipment must be supported, is basic module; Secondly the use of SNMP only relates to GET, GET-NEXT, SET tri-kinds operation, and very terse being easy to is implemented.
2. the present invention is efficient, reliable.Because the code of other way to manages is completed by SNMP virtual access API, do not relate to snmp protocol message, network protocol stack is not needed to participate in, message is not had to send the process of wait acknowledge, whole handling process is more brief, and more efficiently, and the execution of whole program only has calling step by step of function, do not have network processes process, reliability is high.
3. the present invention supports concurrent.Because other way to manages are realized by SNMP virtual access API, and the execution of these API itself allows concurrent, thus the different way to manages of whole equipment effect when concurrent utilization is fine.
Accompanying drawing explanation
Fig. 1 is the software layer hierarchical structure chart of current multiple way to manage the network equipment deposited.
Fig. 2 is based on the unified software layer aggregated(particle) structure of the various way to manages of SNMP;
Fig. 3 is SNMPAGENT software configuration traditional on the network equipment;
Fig. 4 is the SNMPAGENT software configuration of the network equipment after increasing the process of virtual SNMP access logic.
Embodiment
A kind of digital communication equipment access information management supporting multiple management mode of the present invention, comprises the SNMP module with virtual SNMP access process logical block and Broker Core unit, target service module, the management program module with MIB tree.
Described virtual SNMP access process logical block is for providing the access SNMP access API of module.Access API comprises GETAPI, GET-NEXTAPI, SETAPI.Wherein, GETAPI, GET-NEXTAPI are used for running status and/or the configuring condition of query facility, and SNMPSETAPI is for realizing the setting to equipment.GETAPI, GET-NEXTAPI, SETAPI to as if equipment on MIB, i.e. the various function modeling management information bank of refining.Further, the input parameter of GETAPI, GET-NEXTAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, and the input parameter of SETAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, the value of object to be configured.
Matching inquiry is carried out during the MIB of input parameter in target service module that described Broker Core unit is used for putting according to access API sets.The management information bank that MIB and various function modeling refine.
Management program module, for providing the management function of non-SNMP form, uses the mode that similar network management system manages network equipments configuration---and the MIB being accessed equipment by SNMPGET, GET-NEXT, SET is developed.As shown in Figure 2, if other administration modules such as order line, WEB receive user to the configuration of certain function on equipment or inquiry request, so this administration module is not that functional module directly with concrete is mutual, but similar network management system, API is accessed, the MIB that access equipment is current by virtual SNMP.The key point of this design is the support that virtual SNMP accesses.
Below the working method of said system is described.
Traditional equipment end SNMPAGENT software configuration as shown in Figure 3, equipment end is after the SNMP request receiving webmaster, first Message processing is carried out, after parsing message content, next enters the core processing of SNMP agency, here the mib information that equipment is registered will be searched, this SNMP is found to ask corresponding concrete function point, then the aid in treatment code of this function point is adjusted back, according to the different classes of (GET of request, GET-NEXT or SET), the MIB performing this function point implements code, by configuration distributing to specific functional modules or the parameter getting request from functional module, SNMP Broker Core will organize execution result afterwards, message processing module (MPM) will build SNMP message, finally message is fed back to network management system.
The support of virtual SNMP access, as long as on original structure, increases virtual SNMP and accesses API processing logic, bypass Message processing process, just can multiplexing most of SNMP handling process originally except Message processing and code.Fig. 4 is the software configuration schematic diagram after increasing virtual SNMP access process logic.Virtual SNMP access provides GET, GET-NEXT, SETAPI with snmp protocol equivalence, on the basis of multiplexing existing SNMP process code, concurrency conflict is not had with normal SNMP Message processing, also there is not concurrency conflict each other in virtual access API, good function call level SNMP can be provided to access and support.
The access method of the above-mentioned digital communication equipment access information management based on SNMP, can be summarized as following steps:
Step one: management program module inputs MIB access request by access API;
Step 2: input parameter is delivered to Broker Core unit by virtual SNMP access process logical block;
Step 3: Broker Core unit carries out matching inquiry according to the MIBOID of access on MIB tree, finds the function point auxiliary code that this MIB is corresponding; Described auxiliary code is be registered to the call back function on MIB tree;
Step 4: auxiliary code judges SNMP request type, adjusts back the execution function of this MIB registration according to request type; Described execution function is the configuration management API of the functional module of SNMP request correspondence;
Step 5: perform function according to SNMP request type executable operations;
If SNMP request type is GET or GET-NEXT, performs function and just take out corresponding value from the functional module that request is corresponding, if SNMP request type is SET, perform function just by functional module corresponding for the settings write request of equipment.
Step 6: function returns step by step, access API returns execution result eventually to management program module.
Beneficial effect of the present invention is:
1. directly use SNMP module as " general module ", do not need additionally to take out again one " unified management program ".Abstract work itself acquires a certain degree of difficulty and can increase exploitation amount, and SNMP module itself is well suited for serving as this function: first it is the function that digital communication equipment must be supported, is basic module; Secondly the use of SNMP only relates to GET, GET-NEXT, SET tri-kinds operation, and very terse being easy to is implemented.
2. efficient, reliable.Because the code of other way to manages is completed by SNMP virtual access API, do not relate to snmp protocol message, network protocol stack is not needed to participate in, message is not had to send the process of wait acknowledge, whole handling process is more brief, and more efficiently, and the execution of whole program only has calling step by step of function, do not have network processes process, reliability is high.
3. support concurrent.Because other way to manages are realized by SNMP virtual access API, and the execution of these API itself allows concurrent, thus the different way to manages of whole equipment effect when concurrent utilization is fine.
Claims (5)
1. support the digital communication equipment access information management of multiple management mode for one kind, it is characterized in that, described management system comprises the SNMP module with virtual SNMP access process logical block and Broker Core unit, target service module, the management program module with MIB tree;
Described virtual SNMP access process logical block is for providing the access SNMP access API of module;
Matching inquiry is carried out during the MIB of input parameter in target service module that described Broker Core unit is used for putting according to access API sets;
Management program module, for providing the management function of non-SNMP form, reaches management objectives by access API Access MIB.
2. as claimed in claim 1 based on the digital communication equipment access information management of SNMP, it is characterized in that, access API comprises GETAPI, GET-NEXTAPI, SETAPI, wherein, GETAPI, GET-NEXTAPI are used for running status and/or the configuring condition of query facility, and SNMPSETAPI is for realizing the setting to equipment.
3. as claimed in claim 2 based on the digital communication equipment access information management of SNMP, it is characterized in that, the input parameter of GETAPI, GET-NEXTAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, and the input parameter of SETAPI comprises SNMP request type, the MIBOID of access, the object indexing of access, the value of object to be configured.
4., as claimed in claim 3 based on the access method of the digital communication equipment access information management of SNMP, it is characterized in that, comprise the steps:
Step one: management program module inputs MIB access request by access API;
Step 2: input parameter is delivered to Broker Core unit by virtual SNMP access process logical block;
Step 3: Broker Core unit carries out matching inquiry according to the MIBOID of access on MIB tree, finds the function point auxiliary code that this MIB is corresponding; Described auxiliary code is be registered to the call back function on MIB tree;
Step 4: auxiliary code judges SNMP request type, adjusts back the execution function of this MIB registration according to request type; Described execution function is the configuration management API of the functional module of SNMP request correspondence;
Step 5: perform function according to SNMP request type executable operations;
Step 6: function returns step by step, access API returns execution result eventually to management program module.
5. as claimed in claim 4 based on the access method of the digital communication equipment access information management of SNMP, it is characterized in that, in step 5, if SNMP request type is GET or GET-NEXT, perform function and just take out corresponding value from the functional module that request is corresponding, if SNMP request type is SET, perform function just by functional module corresponding for the settings write request of equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510516678.XA CN105187244B (en) | 2015-08-21 | 2015-08-21 | A kind of digital communication equipment access information management and its working method for supporting a variety of management modes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510516678.XA CN105187244B (en) | 2015-08-21 | 2015-08-21 | A kind of digital communication equipment access information management and its working method for supporting a variety of management modes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105187244A true CN105187244A (en) | 2015-12-23 |
| CN105187244B CN105187244B (en) | 2018-10-30 |
Family
ID=54909098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510516678.XA Expired - Fee Related CN105187244B (en) | 2015-08-21 | 2015-08-21 | A kind of digital communication equipment access information management and its working method for supporting a variety of management modes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105187244B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634800A (en) * | 2015-12-25 | 2016-06-01 | 北京时代民芯科技有限公司 | Data storage maintenance method based on SNMP and SQLite |
| CN109039701A (en) * | 2018-06-25 | 2018-12-18 | 烽火通信科技股份有限公司 | The method and system of a variety of way to manages of the network equipment based on MIB database |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1558603A (en) * | 2004-01-17 | 2004-12-29 | 港湾网络有限公司 | Integrated net element management system and handling method thereof |
| CN1610309A (en) * | 2003-10-22 | 2005-04-27 | 华为技术有限公司 | Development method of management agent for supporting simple network management protocol |
| CN101572624A (en) * | 2009-01-04 | 2009-11-04 | 四川川大智胜软件股份有限公司 | Cross-platform cross-method SNMP extension MIB realization method |
| CN102281152A (en) * | 2011-06-08 | 2011-12-14 | 烽火通信科技股份有限公司 | Distributed communication system, implementation method, marshalling and unmarshalling method of remote API (Application Program Interface) |
| US20120030327A1 (en) * | 2010-07-30 | 2012-02-02 | Jeff Conrad | Identification of management information base object identifiers supported by a managed device |
| CN104620539A (en) * | 2012-06-15 | 2015-05-13 | 思杰系统有限公司 | Systems and methods for supporting a SNMP request over a cluster |
-
2015
- 2015-08-21 CN CN201510516678.XA patent/CN105187244B/en not_active Expired - Fee Related
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1610309A (en) * | 2003-10-22 | 2005-04-27 | 华为技术有限公司 | Development method of management agent for supporting simple network management protocol |
| CN1558603A (en) * | 2004-01-17 | 2004-12-29 | 港湾网络有限公司 | Integrated net element management system and handling method thereof |
| CN101572624A (en) * | 2009-01-04 | 2009-11-04 | 四川川大智胜软件股份有限公司 | Cross-platform cross-method SNMP extension MIB realization method |
| US20120030327A1 (en) * | 2010-07-30 | 2012-02-02 | Jeff Conrad | Identification of management information base object identifiers supported by a managed device |
| CN102281152A (en) * | 2011-06-08 | 2011-12-14 | 烽火通信科技股份有限公司 | Distributed communication system, implementation method, marshalling and unmarshalling method of remote API (Application Program Interface) |
| CN104620539A (en) * | 2012-06-15 | 2015-05-13 | 思杰系统有限公司 | Systems and methods for supporting a SNMP request over a cluster |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634800A (en) * | 2015-12-25 | 2016-06-01 | 北京时代民芯科技有限公司 | Data storage maintenance method based on SNMP and SQLite |
| CN105634800B (en) * | 2015-12-25 | 2018-09-11 | 北京时代民芯科技有限公司 | A kind of data storage system maintenance method based on SNMP and SQLite |
| CN109039701A (en) * | 2018-06-25 | 2018-12-18 | 烽火通信科技股份有限公司 | The method and system of a variety of way to manages of the network equipment based on MIB database |
| CN109039701B (en) * | 2018-06-25 | 2021-08-24 | 烽火通信科技股份有限公司 | Method and system for multiple management modes of network equipment based on MIB database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105187244B (en) | 2018-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108549580B (en) | Method for automatically deploying Kubernets slave nodes and terminal equipment | |
| CN107431651B (en) | Life cycle management method and equipment for network service | |
| CN111385114B (en) | VNF service instantiation method and device | |
| US10917294B2 (en) | Network function instance management method and related device | |
| RU2683630C2 (en) | Method for update of nsd network service descriptor and device | |
| US20170134520A1 (en) | Systems and methods for distributed network-aware service placement | |
| CN104199957A (en) | Redis universal agent implementation method | |
| CN103197952A (en) | Management system and method aiming at maintenance and deployment of application system based on cloud infrastructure | |
| CN101964763B (en) | Message handling method | |
| US20070115818A1 (en) | Triggered notification | |
| CN112416969B (en) | Parallel task scheduling system in distributed database | |
| CN103595801A (en) | Cloud computing system and real-time monitoring method for virtual machine in cloud computing system | |
| CN103685535A (en) | Interface design of cloud database system for large-scale distributed heterogeneous data treatment | |
| CN111797173B (en) | Alliance chain sharing system, method and device, electronic equipment and storage medium | |
| CN107682460A (en) | A kind of distributed storage trunked data communication method and system | |
| CN106547790B (en) | Relational database service system | |
| CN109189431A (en) | A kind of client side upgrading method, device, equipment and readable storage medium storing program for executing | |
| CN108259605B (en) | Data calling system and method based on multiple data centers | |
| CN110417876A (en) | Node server and main control device in session method, distributed system | |
| EP4258609A1 (en) | Container cluster management method and apparatus | |
| CN105187244A (en) | Access management system of digital communication equipment supporting multiple management modes | |
| CN103297514A (en) | Virtual machine management platform and virtual machine management method based on cloud infrastructure | |
| CN108965403A (en) | O&M monitors establishment of connection method and terminal device | |
| CN112073555A (en) | Method for configuring IP address, electronic device and computer readable storage medium | |
| CN109542841A (en) | The method and terminal device of data snapshot are created in cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200804 Address after: Floor 2, No.16, Gaopeng Avenue, high tech Zone, Chengdu, Sichuan 610000 Patentee after: Chengdu Guangda Hengji Communication Technology Co., Ltd Address before: 610041 building four, building two, Shiyang Industrial Park, five village, Shiyang village, fifty-five village, Chengdu hi tech Zone, Sichuan, Qingyun Patentee before: CHENGDU GUANGDA NEW NETWORK TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20181030 Termination date: 20200821 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |