CN111966661A - Dynamic expanding method for snmp tree management information base - Google Patents
Dynamic expanding method for snmp tree management information base Download PDFInfo
- Publication number
- CN111966661A CN111966661A CN202010741596.6A CN202010741596A CN111966661A CN 111966661 A CN111966661 A CN 111966661A CN 202010741596 A CN202010741596 A CN 202010741596A CN 111966661 A CN111966661 A CN 111966661A
- Authority
- CN
- China
- Prior art keywords
- object identifier
- identifiers
- subordinate
- calling module
- management information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 238000013507 mapping Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 36
- 239000003795 chemical substances by application Substances 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 238000001816 cooling Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 241000282326 Felis catus Species 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2246—Trees, e.g. B+trees
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method for dynamically expanding a snmp tree management information base, which comprises S100, establishing a method base associated with an object identifier; constructing a calling module associated with the equipment model; s200, acquiring the model of the equipment; s300, loading a corresponding calling module according to the equipment model; s400, the calling module calls a method in a method library associated with the object identifier to acquire object identifier information; s500, the calling module transmits the information to the proxy module, and the proxy module adds the object identifier dependency relationship and the object identifier information to the tree management information base. The invention discloses a method for dynamically expanding a snmp tree management information base, which enables a managed device to automatically transmit information required to be managed by the tree management information base to the tree management information base through an agent module, realizes the automatic dynamic expansion of the tree management information base, does not need managers to participate in the setting, and is convenient and simple.
Description
Technical Field
The invention relates to the field of network equipment management methods, in particular to a method for dynamically expanding a snmp tree management information base.
Background
In large-scale network management, it is necessary to know the operation status of network devices that are not nearby in real time. In an actual network, a method for automatically helping an administrator to collect network operation conditions by using a Simple Network Management Protocol (SNMP) is most widely used. By this method, the network administrator can exchange management information between SNMP Agent and network management system conveniently. Therefore, the network management personnel can be helped to know the network performance more conveniently, discover and solve network problems and plan the future development of the network.
The SNMP Agent manages the network device by using the management information base database, the management information base database is a tree-shaped database, the managed objects are located at the end nodes of the tree, and each end node has a unique position and a unique name. The IETF specifies that the Object Identifier (Object Identifier) of the management information base is uniquely specified, and the naming rule thereof is that the name of the parent node is prefixed to the name of the child node. The management information base collects and stores management information and enables the network management system to obtain the information through the SNMP Agent. For proprietary management information base node equipment of manufacturers, specific parameter information is often required to be collected and stored, and therefore in the prior art, management personnel often check the parameter information required by the equipment according to the model of the equipment and manually store the information in a management information base database, and the mode of manually expanding the management information base database is relatively troublesome to operate and prone to errors.
Disclosure of Invention
The invention provides a method for dynamically expanding a snmp tree management information base, and aims to solve the problems that the operation is troublesome and errors are easy to occur in the conventional method for manually expanding a management information base database.
In order to achieve the above object, the present invention provides a method for dynamically expanding a snmp tree management information base, comprising,
s100, establishing a method library associated with the object identifier; constructing a calling module associated with the equipment model;
s200, acquiring the model of the equipment;
s300, loading a corresponding calling module according to the equipment model;
s400, the calling module calls a method in a method library associated with the object identifier to acquire object identifier information;
s500, the calling module transmits the object identifier information to the proxy module, and the proxy module adds the object identifier information to the tree management information base according to a snmp format.
Furthermore, the calling module is arranged in the first file, the calling module defines the mapping relation between the object identifiers and the device models, and defines the dependency relation between the object identifiers.
Still further, the object identifiers include a top-level object identifier that maps device model numbers, a subordinate intermediate object identifier or a bottom-level object identifier under the top-level object identifier, a subordinate intermediate object identifier or a bottom-level object identifier under the intermediate object identifier, a bottom-level object identifier subordinate to the unique intermediate object identifier or to the unique top-level object identifier, an intermediate object identifier subordinate to the unique intermediate object identifier or to the unique top-level object identifier.
Further, the object identifier method library includes a first method defining an underlying object identifier and a first instruction for obtaining an underlying object identifier attribute.
Furthermore, the calling module defines a second method for processing the first method, and the second method comprises the steps of storing the first instruction in a corresponding storage address and establishing a relation between the storage address and an underlying object identifier corresponding to the first instruction;
the calling module defines a third method, the third method acquires the equipment model and reads the equipment model information in the first file, the third method judges whether the acquired equipment model is matched with the equipment model information read from the first file, and if the matching is finished, the calling module is loaded.
Furthermore, the content in the second file is read to obtain the device model, the device model is sent to all the calling modules, and the third method is executed after all the calling modules receive the device model.
Furthermore, the agent module traverses the subordinate intermediate object identifier and the bottom object identifier under the top object identifier in the first file, traverses the subordinate intermediate object identifier and the bottom object identifier under the intermediate object identifier, and calls all the bottom object identifiers under the top object identifier step by step to finally obtain the attributes of the bottom object identifier, and the agent module calls the first instruction in the storage address according to the relation between the bottom object identifier and the storage address to obtain the attributes of the bottom object identifier.
Still further, the object identifiers further include parent node identifiers and higher level object identifiers to which the parent node identifiers depend, the top level object identifiers being subordinate to unique parent node identifiers, the parent node identifiers being subordinate to unique higher level object identifiers, forming a tree-like subordinate structure.
The method for dynamically expanding the snmp tree management information base provided by the application has the following beneficial effects:
the method for dynamically expanding the snmp tree management information base comprises the steps that a method base associated with an object identifier is established on a managed device; constructing a calling module associated with the equipment model; acquiring the model of own equipment through a program, loading a corresponding calling module according to an equipment signal, calling the method in the method library by the calling module to acquire the information of the bottom layer object identifier, and defining the dependency relationship between the object identifiers by the calling module; the calling module transmits the information of the bottom layer object identifier and the affiliation between the object identifiers to the proxy module, and the proxy module sends the information to the tree management information base according to the snmp format, so that the dynamic automatic expansion of the tree management information base is realized, managers do not need to participate in setting, and the method is convenient and simple.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
FIG. 1 is a schematic diagram of a dynamic expanding method of a snmp tree management information base in an embodiment of the present invention;
FIG. 2 is a diagram illustrating object identifier classification and dependency relationships in an embodiment of the present invention;
FIG. 3 is a schematic diagram of invoking a calling module according to a device model in an embodiment of the present invention;
FIG. 4 is a schematic diagram of an agent module adding data to a tree management information base according to an embodiment of the present invention.
The objects, features and advantages of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The agent module refers to a network management module that operates in a managed device, and manages information of a local machine (managed device) and transmits the information in a format compatible with snmp. The second file is configured in a storage structure of the managed device, and the second file records the device model of the managed device; for the device model, the type of the device can be judged through some positions of the device model, and the manufacturer can be judged through some positions of the device model.
As shown in fig. 1, the present invention provides a method for dynamically expanding a snmp tree management information base, including,
s100, establishing a method library associated with object identifiers in the managed equipment, wherein the method library defines the relationship between the object identifiers and the objects in the managed equipment, and the object identifiers comprise top-level object identifiers, middle object identifiers and bottom-level object identifiers; the object identifier method library comprises a first method, the first method defines a bottom layer object identifier, and a first instruction for acquiring the object attribute corresponding to the bottom layer object identifier.
The example is illustrated using a python implementation under a managed device deploying a sonic system. Creating a file base _ device.py, which corresponds to the method library, creating a class base device in the base _ device.py file, and defining all methods required by acquiring all the bottom layer object identifier attributes in the management information library under the base device class, for example: defining a method for acquiring the utilization rate of the cpu, and defining a reading instruction for reading a register address for storing the utilization rate information of the cpu, wherein the method for acquiring the utilization rate of the cpu corresponds to an object identifier named cpu _ util; defining a method for acquiring the utilization rate of the memory, and defining a reading instruction for reading a register address for storing the utilization rate information of the memory, wherein the method for acquiring the utilization rate of the memory corresponds to an object identifier named as mem _ util; defining a method for acquiring the rotating speed of the cooling fan, and defining a reading instruction for reading a register address for storing the rotating speed information of the cooling fan, wherein the method for acquiring the rotating speed of the cooling fan corresponds to an object identifier named fan _ speed; defining a method for acquiring port state, defining a reading instruction for reading a register address of port state information, defining a method for acquiring port transmission speed, defining a reading instruction for reading a register address of port transmission speed information, corresponding to an object identifier named port _ state, and acquiring the port transmission speed, corresponding to the object identifier named port _ speed, both the method for acquiring port transmission speed and the method for acquiring port state are associated with the object identifier named port _ data. The reading instruction of the register address for reading and storing the cpu utilization rate information, the reading instruction of the register address for reading and storing the memory utilization rate information, the reading instruction of the register address for reading and storing the cooling fan rotating speed information, the reading instruction of the register address for reading the port state information and the reading instruction of the register address for reading the port transmission speed information all belong to the first instruction. cpu _ util, mem _ util, fan _ speed, port _ speed, and port _ state all belong to the underlying object identifier, and port _ data belongs to the intermediate object identifier.
Referring to fig. 2, a calling module associated with a device model is built in a managed device, the calling module is arranged in a first file, the calling module defines a mapping relation between object identifiers and device models, and defines an affiliation relation between the object identifiers; the top level object identifier maps the device model number as shown in fig. 2, directly subordinate intermediate object identifier 1, bottom level object identifier 1 and bottom level object identifier 2 under top level object identifier 1, subordinate bottom level object identifier 3 and intermediate object identifier 2 under intermediate object identifier 1, subordinate bottom level object identifier 4 and bottom level object identifier 5 under intermediate object identifier 2. The bottom level object identifier is subordinate to a unique intermediate object identifier or to a unique top level object identifier, the intermediate object identifier being subordinate to a unique intermediate object identifier or to a unique top level object identifier, such that the top level identifier, the intermediate identifier, and the bottom level identifier establish a tree-like dependency, the root of the tree being the top level identifier and the crown of the tree being the bottom level identifier. Specifically, for example, the device models SC5630EL, SC5630EL of the managed devices are mapped to the top-level object identifier named SC5630EL, the top-level object identifier SC5630EL directly subordinate to the intermediate object identifier port _ data, the bottom-level object identifiers cpu _ util, mem _ util, and fan _ speed, and the intermediate object identifiers port _ data subordinate to the bottom-level object identifiers port _ speed and port _ state.
The calling module also defines a second method for processing the first method, wherein the second method comprises the steps of storing the first instruction in a corresponding storage address, establishing a relation between the storage address and a bottom layer object identifier corresponding to the first instruction, pointing to the storage address through the bottom layer object identifier, and storing the corresponding first instruction in the storage address. Taking a managed device for deploying the sonic system and using python implementation as an example for illustration, the second method calls the information of the object identifier to be obtained by taking a keyword which is the same as the object identifier as an instruction, and the code is as follows:
cpu_util＝device.get_cpu_util
mem_util＝device.get_mem_util
fan_speed＝device.get_fan_speed
port_data_port_speed＝def get_port_data_port_speed
port_data_port_state＝def get_port_data_port_state
……
register_oid("1.3.6.1.4.1.37945.1.1",cpu_util)#cpu util
register_oid("1.3.6.1.4.1.37945.1.2",mem_util)#mem util
register_oid("1.3.6.1.4.1.37945.1.3",fan_speed)#fan speed
register_oid("1.3.6.1.4.1.37945.1.4",port_data_port_speed)
#port_data_port_speed
register_oid("1.3.6.1.4.1.37945.1.5",port_data_port_state)
#port_data_port_state
……
s200, reading the second file by the operation instruction of the managed equipment to acquire the equipment model of the managed equipment; taking a managed device for deploying the sonic system and using python implementation as an example, the second file is saved in a cat/etc/platform directory, a method get _ hwsku for reading the content of the second file is defined, the cat/etc/platform content is read, the device model hwsku is SC5630EL is obtained, and the following codes are returned:
def get_hwsku():
return os.popen("cat/etc/platform").readline().strip()
s300, the agent module loads a corresponding calling module according to the equipment model; taking a managed device for deploying a sonic system and using python implementation as an example, acquiring a device model hwsku as SC5630EL, defining a get _ device _ class by defget _ device _ class (), dynamically loading contents subordinate to an SC5630EL top-level object identifier in a first file by using importlib, and returning a function to a class object sc5630el.device, wherein the codes are as follows:
"return import _ module (" mibs. vector. name. devices. {0} ". format (h wsku). Device"), loads the contents of the second file for SC5630EL under the SC5630EL instance. Acquiring the content of the SC5630EL in the second file requires that the calling module defines a third method, where the third method acquires the device model, specifically, reads the content in the second file to acquire the device model, sends the device model to all calling modules through an instruction, and executes the third method after all calling modules receive the device model. The third method looks for the top-level identifier named SC5630EL in the first file, and if the third method retrieves the top-level identifier named SC5630EL from the first file, it loads the content under SC5630EL to the SC5630EL instance, and if not, it feeds back the non-execution hint.
S400, the calling module calls a method in a method library associated with the object identifier to acquire object identifier information; traversing the subordinate intermediate object identifiers and the subordinate bottom object identifiers under the top-level object identifiers in the first file, traversing the subordinate intermediate object identifiers and the subordinate bottom object identifiers under the intermediate object identifiers, calling all the bottom-level object identifiers under the top-level object identifiers step by step to finally obtain, and calling a first instruction in the storage address according to the relation between the bottom-level object identifiers and the storage address to obtain the attributes of the bottom-level object identifiers.
The SC5630EL instance obtains information of corresponding underlying object identifiers by executing instructions cpu _ util, mem _ util, fan _ speed, port _ data _ port _ speed, and port _ data _ port _ state … …, respectively.
S500, the SC5630EL instance transfers the object identifier dependency and the object identifier information in the first file to the proxy module, the specific SC5630EL instance saves the object identifier dependency and the object identifier information in the first file in a third file, the proxy module reads the content in the third file, and the proxy module adds the information to the tree management information base in snmp format.
Other managed devices load different first file contents according to the device model
The method for dynamically expanding the snmp tree management information base comprises the steps that a method base associated with an object identifier is established on a managed device; constructing a calling module associated with the equipment model; acquiring the model of own equipment through a program, loading a corresponding calling module according to an equipment signal, calling the method in the method library by the calling module to acquire the information of the bottom layer object identifier, and defining the dependency relationship between the object identifiers by the calling module; the calling module transmits the information of the bottom layer object identifier and the affiliation between the object identifiers to the proxy module, and the proxy module sends the information to the tree management information base according to the snmp format, so that the dynamic automatic expansion of the tree management information base is realized, managers do not need to participate in setting, and the method is convenient and simple.
Finally, it should be noted that, as one of ordinary skill in the art can appreciate that all or part of the processes of the methods of the above embodiments can be implemented by a computer program to instruct related hardware, and the program of the method for automatically configuring the server and the switch can be stored in a computer readable storage medium, and when executed, the program can include the processes of the embodiments of the methods described above. The storage medium of the program may be a magnetic disk, an optical disk, a Read Only Memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described method embodiments.
Further, the snmp refers to a simple network management protocol.
Furthermore, the methods disclosed according to embodiments of the present invention may also be implemented as a computer program executed by a processor, which may be stored in a computer-readable storage medium. Which when executed by a processor performs the above-described functions defined in the methods disclosed in embodiments of the invention.
Further, the above method steps and system elements may also be implemented using a controller and a computer readable storage medium for storing a computer program for causing the controller to implement the functions of the above steps or elements.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in a variety of forms such as synchronous RAM (DRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk, blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (8)
1. A method for dynamically expanding a snmp tree management information base is characterized in that the method comprises the following steps,
s100, establishing a method library associated with the object identifier; constructing a calling module associated with the equipment model;
s200, acquiring the model of the equipment;
s300, loading a corresponding calling module according to the equipment model;
s400, the calling module calls a method in a method library associated with the object identifier to acquire object identifier information;
s500, the calling module transmits the object identifier information to the proxy module, and the proxy module adds the object identifier information to the tree management information base according to a snmp format.
2. The method according to claim 1, wherein the calling module is disposed in the first file, the calling module defines a mapping relationship between the object identifier and the device model, and defines an affiliation relationship between the object identifiers.
3. The snmp tree-like management information base dynamic expansion method according to claim 2, wherein the object identifier comprises a top-level object identifier, an intermediate object identifier and a bottom-level object identifier, the top-level object identifier maps a device model number, a subordinate intermediate object identifier or a bottom-level object identifier under the top-level object identifier, a subordinate intermediate object identifier or a bottom-level object identifier under the intermediate object identifier, a bottom-level object identifier is subordinate to a unique intermediate object identifier or a subordinate unique top-level object identifier, and an intermediate object identifier is subordinate to a unique intermediate object identifier or a subordinate unique top-level object identifier.
4. The method of claim 3, wherein the object identifier method library comprises a first method, the first method defines an underlying object identifier, and defines a first instruction for obtaining an underlying object identifier attribute.
5. The method according to claim 4, wherein the calling module defines a second method for processing the first method, the second method comprises storing the first instruction in a corresponding storage address, and associating the storage address with an underlying object identifier corresponding to the first instruction;
and the calling module defines a third method, wherein the third method comprises the steps of acquiring the equipment model and the equipment model information in the first file, judging whether the acquired equipment model is matched with the equipment model information in the first file, and if the acquired equipment model is not matched with the equipment model information in the first file, loading the calling module.
6. The method according to claim 5, wherein the content in the second file is read to obtain the device model, the device model is sent to all calling modules, and all calling modules execute the third method after receiving the device model.
7. The method according to claim 5, wherein the proxy module traverses the subordinate intermediate object identifiers and bottom object identifiers under the top object identifier in the first file, traverses the subordinate intermediate object identifiers and bottom object identifiers under the intermediate object identifier, and calls all bottom object identifiers under the top object identifier step by step to finally obtain the attributes of the bottom object identifier, and the proxy module calls the first instruction in the storage address according to the relation between the bottom object identifier and the storage address to obtain the attributes of the bottom object identifier.
8. The method of claim 7, wherein the object identifiers further comprise parent node identifiers and higher level object identifiers to which the parent node identifiers belong, the top level object identifiers are subordinate to unique parent node identifiers, and the parent node identifiers are subordinate to unique higher level object identifiers, so as to form a tree-like subordinate structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741596.6A CN111966661B (en) | 2020-07-28 | 2020-07-28 | Dynamic expanding method for snmp tree management information base |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741596.6A CN111966661B (en) | 2020-07-28 | 2020-07-28 | Dynamic expanding method for snmp tree management information base |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111966661A true CN111966661A (en) | 2020-11-20 |
| CN111966661B CN111966661B (en) | 2023-01-06 |
Family
ID=73363314
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010741596.6A Active CN111966661B (en) | 2020-07-28 | 2020-07-28 | Dynamic expanding method for snmp tree management information base |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111966661B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1777123A (en) * | 2005-12-19 | 2006-05-24 | 北京交通大学 | SNMP-based IPv6 sensor network node management method |
| US20150324465A1 (en) * | 2014-05-07 | 2015-11-12 | Labtech Llc | Systems and methods for discovering and monitoring devices using search patterns for object identifiers and values |
| CN110933608A (en) * | 2018-09-18 | 2020-03-27 | 深圳市鸿合创新信息技术有限责任公司 | Equipment registration terminal and method and electronic equipment |
-
2020
- 2020-07-28 CN CN202010741596.6A patent/CN111966661B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1777123A (en) * | 2005-12-19 | 2006-05-24 | 北京交通大学 | SNMP-based IPv6 sensor network node management method |
| US20150324465A1 (en) * | 2014-05-07 | 2015-11-12 | Labtech Llc | Systems and methods for discovering and monitoring devices using search patterns for object identifiers and values |
| CN110933608A (en) * | 2018-09-18 | 2020-03-27 | 深圳市鸿合创新信息技术有限责任公司 | Equipment registration terminal and method and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111966661B (en) | 2023-01-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1910854B (en) | Automatic update system and method for using a meta mib | |
| US20030074436A1 (en) | Management information base object model | |
| US20040255010A1 (en) | Method, a controller, an arrangement and a computer program for managing a configuration of clustered computers | |
| Wu et al. | OneM2M-based IoT protocol integration | |
| CN112685709B (en) | Authorization token management method and device, storage medium and electronic equipment | |
| CN110781356A (en) | Hardware query method, equipment and storage medium based on management platform | |
| CN111817905B (en) | Network configuration method, related device and storage medium | |
| CN112436964A (en) | Equipment adaptation method and network management device | |
| CN111966661B (en) | Dynamic expanding method for snmp tree management information base | |
| Cavalieri et al. | Realising interoperability between opc ua and ocf | |
| CN111198677A (en) | Equipment object generation method, device and equipment | |
| CN113037571A (en) | Large-scale micro-service architecture and management method thereof | |
| CN114553706A (en) | Network topology discovery method and device and electronic equipment | |
| CN111857963A (en) | Container arrangement implementation method, device, equipment and medium for Proxmox VE | |
| WO2017054530A1 (en) | Resource access method, device and system | |
| CN112953770A (en) | Method, system and medium for configuration-free access of edge cloud gateway and cloud management system | |
| CN115827703B (en) | Enumeration data query method and device | |
| CN115918116A (en) | Information processing method, device and storage medium | |
| CN113742372A (en) | Method, device and system for accessing data in edge node | |
| KR100624477B1 (en) | Configuration management system and method using representative object instances | |
| CN111586203B (en) | Method, device and equipment for storing IP configuration and readable medium | |
| WO2023050815A1 (en) | Slice service configuration method, network device, network system, and storage medium | |
| CN115118569A (en) | Request processing method and device, network management equipment and readable storage medium | |
| CN113542034B (en) | Network element information processing system, network element management method and device | |
| WO2024001569A1 (en) | Network configuration method and apparatus, storage medium and electronic apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |