CN112671569B - Network management method and system based on configuration classification - Google Patents
Network management method and system based on configuration classification Download PDFInfo
- Publication number
- CN112671569B CN112671569B CN202011486470.5A CN202011486470A CN112671569B CN 112671569 B CN112671569 B CN 112671569B CN 202011486470 A CN202011486470 A CN 202011486470A CN 112671569 B CN112671569 B CN 112671569B
- Authority
- CN
- China
- Prior art keywords
- configuration
- network element
- level
- network
- entry
- 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.)
- Active
Links
Images
Abstract
The invention provides a network management method and system based on configuration classification. The invention divides the network configuration into global, node and equipment configuration according to the hierarchical relation. The network element devices are grouped according to the network plan (physical location, logical relationship), each group being bound to a node. The global configuration takes effect for all network element devices of the specified type within the network. The configuration at the node level takes effect for a specified type of network element device within the node. The device-level configuration is only effected for the specified network element device. By the hierarchical configuration, the configuration efficiency can be effectively improved while the configuration flexibility is kept.
Description
Technical Field
The present invention relates to network management, and more particularly, to a method and system for network management based on configuration classification.
Background
With the development of networks, the network scale is gradually enlarged, and network systems also occupy more and more important positions. The network management system is a network device management system for short, and is used for performing data configuration, monitoring, maintenance and the like on network management devices in the whole network system. With the expansion of network scale, the number of managed network element devices is increasing, and how to effectively configure the managed devices becomes extremely important.
Generally, a network management system generates a configuration for each managed network element device, and the configuration is sent from the network management system to the network element device through a data synchronization channel. For different network element devices, even if the same configuration is performed, the configuration needs to be repeatedly generated and issued for each network element device, so that a great problem exists in the efficiency of configuration, and network resources are wasted.
Therefore, it is desirable to provide a solution that can solve the problem of inefficiency and repeatability in configuring the network management system for the network element device.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
One embodiment of the present invention provides a network management method based on configuration classification, including: receiving configuration information, wherein the configuration information at least comprises configuration settings for network element equipment in a network and a level to which the configuration settings are applied, and the level comprises a global level, a node level and an equipment level; generating a configuration item based on the received configuration information, and performing conflict detection based on the configuration item; searching the network element equipment needing to apply the configuration setting based on the level applied by the configuration setting indicated in the configuration entry; generating a configuration synchronization event; and sending the configuration synchronization event to the searched network element equipment needing to apply the configuration setting.
Another embodiment of the present invention provides a network management system based on configuration hierarchy, including: a network management platform; a plurality of network element devices in the network, the plurality of network element devices being physically or logically grouped and each group being bound to a node; wherein the network management platform further comprises: the network management front-end interface configuration module is configured to present a configuration interface and receive configuration information, wherein the configuration information at least comprises configuration setting of network element equipment and the level to which the configuration setting is applied, and the level comprises a global level, a node level and an equipment level; the network management back-end configuration service module is configured to generate configuration items based on the configuration information and perform conflict detection based on the configuration items; and the network management configuration synchronization module is configured to search the network element equipment needing to apply the configuration setting based on the level applied by the configuration setting indicated in the configuration item, generate a configuration synchronization event and send the configuration synchronization event to the searched network element equipment needing to apply the configuration setting.
These and other features and advantages will become apparent upon reading the following detailed description and upon reference to the accompanying drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of aspects as claimed.
Drawings
So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this invention and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
Fig. 1 shows a schematic diagram 100 of configuring a network element device in a network in the prior art;
FIG. 2 illustrates a hierarchical architecture of a network 200 according to one embodiment of the invention;
FIG. 3 shows a schematic diagram of a network management system 300 based on configuration hierarchy according to one embodiment of the present invention;
FIG. 4 shows schematic diagrams 401 and 402 of a configuration interface according to an embodiment of the invention;
FIG. 5 illustrates a flow diagram of a method 500 for network management based on configuration hierarchy according to one embodiment of the present invention; and
FIG. 6 shows a block diagram of an exemplary computing device, according to an embodiment of the invention.
Detailed Description
The present invention will be described in detail below with reference to the attached drawings, and the features of the present invention will be further apparent from the following detailed description.
The invention divides the network configuration into global, node and equipment configuration according to the hierarchical relation. The network element devices are grouped according to a network plan (physical location, logical relationship), each group being bound to a node. The global configuration is effected for all network element devices of the specified type within the network. The configuration at the node level takes effect for a specified type of network element device within the node. The device-level configuration is only effected for the specified network element device. By the hierarchical configuration, the configuration efficiency can be effectively improved while the configuration flexibility is kept.
Fig. 1 shows a prior art example of configuring a network element device in a networkThe intent is 100. Generally, the network management platform 101 is for each network element device 102 in the network 1 ，102 2 ……102 n And (6) managing. For example, when the user needs to target the network element device 102 1 When the configuration of (e.g., adding, modifying, deleting, etc.) is set, the user creates and generates a configuration item 1 through the network management platform 101, and issues (e.g., directly sends or transfers through other intermediary devices) the configuration item 1 to the network element device 102 1 Network element device 102 1 The configuration setting is performed based on the received configuration entry 1. However, if desired, to network element device 102 1 ……102 n For the same configuration setting, the user needs to create n configuration entries 1 … … configuration entries n through the network management 101, and the network management 101 needs to send the n configuration entries to the network element device 102 1 ……102 n Therefore, for a relatively large network, it is time-consuming and laborious for a user to configure the network element devices separately, and network resources are wasted for data transmission.
Fig. 2 shows a hierarchical architecture of a network 200 according to one embodiment of the invention. According to an embodiment of the invention, the network element equipment 202 1 ……202 n According to the network plan, each packet is bound to a node 201 1 ……201 n . For example, network element device 202 1 ……202 3 May be grouped by physical location (e.g., within a certain area, within a certain predetermined threshold of distance from each other) and bound to node 201 1 . Also for example, network element device 202 7 ……202 11 Can be divided into a group based on logical relations according to the needs of tasks to be executed and bound to the node 201 3 . Those skilled in the art will appreciate that in practice, the network element device 202 1 ……202 n May also be artificially divided into one or more groups and bound to one or more nodes 201 accordingly. It is fully understood by those skilled in the art that the number of nodes and the number of network element devices shown in fig. 2 are merely illustrative and may be fully adopted in practiceWith any number of nodes and network element devices.
According to another embodiment of the present invention, the present invention can be used in a Domain Name System (DNS) management network, whereby the network element device 202 1 ……202 n Caching devices, recursive devices, log collection devices, etc. in a DNS management network may be included.
Fig. 3 shows a schematic diagram of a network management system 300 based on configuration hierarchy according to an embodiment of the invention. Any component in the system 300 may communicate with any other component, but not all connections are shown for ease of illustration. The network management platform 301, the network management front-end interface configuration module 302, the network management back-end configuration service module 303, and the network management configuration synchronization module 304 may be implemented by software, hardware, or a combination thereof.
The network management platform 301 can be accessed when a user needs to configure a network element device in the network. The network management front-end interface configuration module 302 in the network management platform 301 presents a configuration interface to a user. FIG. 4 shows schematic diagrams 401 and 402 of a configuration interface according to an embodiment of the invention. As shown at 401 in fig. 4, a user adds a node through a configuration interface. And, as shown in diagram 402, the user may further configure through the configuration interface. For example, the diagram 402 illustrates a "domain name speed limit configuration interface". The domain name speed limit configuration is a functional configuration item of DNS safety protection, and speed limit processing is carried out on the access of some malicious domain names. It will be fully appreciated by those skilled in the art that the interface shown in fig. 4 is merely illustrative and that other ways of adding nodes and configuring the network are fully possible.
Further, the user can set (e.g., add, modify, delete, etc.) the configuration of the network element device through the configuration interface presented by the network management front-end interface configuration module 302. For example, the user may input or select the network element service configuration data through the configuration interface, and select the configuration scope. According to an embodiment of the present invention, the selectable configuration scope may be global, node, or single network element device. The configuration settings at the global level are valid for all network element devices of the specified type within the network. The configuration settings at the node level are effected for network element devices of the specified type within the node. The device-level configuration settings are only in effect for the specified network element devices.
According to one embodiment of the invention, within, for example, a DNS-managed network, typical traffic configuration data may include one or more of the following: safety protection configuration, domain name TTL configuration, domain name resource scheduling configuration, back-end server configuration, user black and white list configuration, cache strategy configuration and the like.
In an embodiment of the present invention, in a DNS management network, for example, typical network element device types include a caching device, a recursive device, a log collection device, and the like. For example, a cache device provides services to users, and a typical global configuration (applicable to all cache devices) for a cache device includes: safety protection configuration, domain name TTL configuration, domain name resource optimization scheduling configuration and the like. Typical node configurations include (applicable to all cache devices within a node): service IP configuration, back-end forwarding configuration, user black and white list configuration and the like. Typical device configurations include (applicable to a single cache device): service IP configuration, service opening configuration, etc. It will be appreciated by those skilled in the art that the above configurations are merely illustrative and that different configurations exist for different types of devices.
According to one embodiment of the invention, in the global level of configuration, the user may choose to apply configuration settings to specified network element devices within the network (e.g., network element devices within the network that conform to the specified type or all network element devices within the network). In node-level configuration, a user may choose to apply configuration settings to one or more nodes and further choose to apply configuration settings to specified network element devices in the one or more nodes (e.g., network element devices in the one or more nodes that conform to the specified type or all network element devices in the one or more nodes). According to another embodiment of the invention, in device-level configuration, a user may choose to apply configuration settings to a specific network element device specified (e.g., by a serial number of the specific network element device, etc.).
After the user sets the configuration and the configuration range, the network management backend configuration service module 303 may generate a configuration entry based on the configuration and the configuration range set by the user. The configuration entry may include one or more fields indicating the configuration setting specific information. According to one embodiment of the invention, the one or more fields indicating the configuration specific information may comprise one or more of: a field indicating a configuration scope (e.g., global, node, device), a field indicating a configuration type (e.g., to identify whether a security protection configuration or a TTL configuration), a field indicating configuration content (e.g., specific information/values of a configuration selected by a user), a field indicating an operation type (e.g., add, modify, delete), and a field indicating a delivery status (e.g., an initial status is "to be delivered," and possible values include "to be delivered," "execution success," "execution failure"). Of course, the fields shown above are merely exemplary, and other types of fields for indicating configuration specific information are within the scope of the present invention.
For each configuration entry, one or more of the one or more fields it comprises may be combined to form a unique key for that configuration entry. Through the unique key, the network management backend configuration service module 303 may detect whether the configuration entry conflicts with an existing configuration entry (e.g., stored in the network management platform 301). That is, if there is a configuration entry whose unique key is the same as the unique key, it can be judged that the same configuration for the same network element device already exists. According to one embodiment of the present invention, the unique key is generally composed of one or more fields in the configuration entry, and is used for uniformly judging the conflict problem of the configuration in the selected configuration range. For example, if the user sets the domain name TTL configuration (the configuration is set to global scope), the configuration entry for it will include fields such as "domain type", "domain name", "maximum TTL", "minimum TTL", etc., in which case the only key of the configuration entry consists of "domain type" + "domain name". If the TTL configuration of a domain name exists in the device, when the TTL configurations of the same domain name are configured globally, the generation of a conflict can be detected according to the unique key. It will be fully appreciated by those skilled in the art that the above examples of unique keys are merely illustrative, and that the unique keys may differ depending on the type of configuration, and that other ways of constructing the unique keys may be employed to identify potential collision risks for configuration settings within the configuration scope.
According to an embodiment of the present invention, after the user configures and sets the configuration range through the configuration interface presented by the network management front-end interface configuration module 302, the network management back-end configuration service module 303 may, when generating a configuration entry, find whether there is a configuration entry with the same unique key in the memory through the unique key of the configuration entry. If yes, the network management back-end configuration service module 303 performs conflict judgment.
If there are several different levels of configuration entries for a certain network element device, the priority of the configuration at the device level is the highest, the priority of the configuration at the node level is the next highest, and the priority of the configuration at the global level is the lowest. If there are several configuration entries of the same hierarchy for a certain network element device, it may be default that the configuration entry currently being set by the user may overwrite the previous configuration entry.
According to one embodiment of the invention, when one or more network element devices indicated in the configuration entry conflict with the existing configuration entry, the user can modify the configuration according to the prompt. For example, for the network element device a, when the user selects to apply the configuration at the global level, if it is determined by the unique key that the configuration entry at the node level for the network element device a already exists, a reminder may be issued to prompt the user that the configuration entry at the node level for which the priority is higher than the configuration range to be currently set already exists, so that the user may select the configuration at the device level for which the priority for the network element device a is higher than the configuration at the node level or select the configuration at the node level for which the priority for the network element device a is equal to the configuration at the node level according to the reminder. In this case, the network management backend configuration service module 303 may regenerate the configuration entry based on the modification of the user, and perform a new round of collision detection. If the newly generated configuration entry does not have a conflict, the configuration entry is stored in memory.
According to an embodiment of the present invention, when one or more network element devices indicated in the configuration entry have a conflict with an already existing configuration entry, the user may also choose to ignore the alert, i.e., not perform further configuration setting on the one or more conflicting network element devices. According to another embodiment of the present invention, after detecting the conflict, if only a part of the network element devices to which the configuration setting is to be applied are determined to be the network element devices in which the conflict occurs, no prompt may be given to the user. In these two cases, the network management back-end configuration service module 303 may directly modify the configuration entry, so that the configuration information of the conflicting network element device is consistent with the current configuration information of the network element device, and mark the conflicting network element device to indicate that the configuration setting is not applied to the conflicting network element device, that is, no configuration setting instruction is issued to the conflicting network element device. Further, the network management back-end configuration service module 303 stores the modified configuration entry.
According to another embodiment of the present invention, the configuration entry may also be prioritized according to the user's privilege level. For example, if user a has a higher authority level than user B, and user a sets a global level configuration 1 for network element device a, and user B sets a node level configuration 2 for network element device a, it can still be considered that configuration 1 has a higher priority than configuration 2. That is, the configuration set by the user a has a higher priority than the configuration set by the user B regardless of the configuration range. Of course, those skilled in the art can set different conflict determination rules according to practical requirements.
According to an embodiment of the present invention, the network management configuration synchronization module 304 searches for information of the relevant network element device that needs to apply the configuration setting based on the configuration entry generated by the network management backend configuration service module 303, generates a configuration synchronization event, and issues the generated configuration synchronization event to the relevant network element device. The network element device may perform the configuration update at the appropriate time based on the received synchronization event.
Fig. 5 shows a flow diagram of a method 500 for network management based on configuration hierarchy according to an embodiment of the present invention.
In step 501, configuration information is received. According to an embodiment of the present invention, the network management platform 301 receives configuration information of a network element device from a user. The configuration information includes at least a type of network device, configuration settings of the network element device, a level to which the configuration settings apply (e.g., global level, node level, or device level). Herein, "configuration settings" may refer to additions, modifications, or deletions to the network element device configuration.
At step 502, based on the received configuration information, a configuration entry is generated and collision detection is performed. According to one embodiment of the invention, the network management platform 301 processes (e.g., extracts, sorts, combines, etc.) the fields in the configuration information to generate the configuration entry based on the received configuration information. Further, the network management platform 301 performs conflict detection with the stored configuration entry according to the unique key of the configuration entry. If no conflict exists, the configuration entry is stored directly in memory. Optionally, if a conflict exists, the user may be alerted to make the configuration modification. If the user selects the modification, the conflict detection is performed again and the modified configuration entries without conflict are stored in the memory. If the user does not perform configuration setting for the network element equipment with conflict after being reminded of conflict, the configuration entry can be modified, so that the configuration information of the network element equipment with conflict is kept consistent with the current configuration information of the network element equipment, and the modified configuration entry is stored in the memory. In this way it can be ensured that the configurations of the network element devices in which the conflict occurs are not modified by configurations of lower priority.
According to an embodiment of the present invention, after detecting a conflict, if only a part of the network element devices to which the configuration setting is to be applied are determined to be the conflicting network element devices, no prompt may be sent to the user, and the network management platform 301 may directly modify the configuration entry, so that the configuration information of the conflicting network element devices is consistent with the current configuration information of the network element devices, and mark the conflicting network element devices to indicate that the configuration setting is not applied to the conflicting network element devices, that is, no configuration setting instruction is issued to the conflicting network element devices.
In step 503, based on the level to which the configuration setting indicated in the configuration entry is applied, the network element device that needs to apply the configuration setting is searched. According to an embodiment of the present invention, the network management platform 301 searches the corresponding network element device based on the configuration range indicated in the configuration entry. For example, if the configuration entry indicates a device-level configuration, then the network element device that conforms to the specification is looked up. If the configuration entry indicates a node-level configuration, then the network element devices included under the specified node that meet the specification are searched. And if the configuration entry indicates the configuration at the global level, searching for the network element equipment which is included in the network and conforms to the specification.
At step 504, a configuration synchronization event is generated. According to one embodiment of the invention, the network management platform 301 generates a configuration synchronization event based on the configuration entry. A configuration synchronization event is a notification of a pending synchronization data activity, which contains information that may be configuration information and/or operational information that sets (e.g., adds, deletes, modifies) a configuration.
In step 505, the configuration synchronization event is sent to the network element device that needs to apply the configuration setting and is found in step 503. According to an embodiment of the present invention, the network management platform 301 issues the configuration synchronization event to the network element devices to which the configuration setting is to be applied, so that each network element device performs configuration update, so that the configuration of each network element device is kept synchronous. According to an embodiment of the present invention, the network management platform 301 may issue the configuration synchronization event to each network element device at the same time, or issue the configuration synchronization event to each network element device asynchronously (e.g., due to network load, artificial rules, scheduling, etc.).
Optionally, after the configuration synchronization event is issued, the network management platform 301 may modify the field indicating the issuing status in the corresponding configuration entry from "pending issue" to "issued". After each network element device performs the configuration update, an indication of whether the configuration update was successfully performed may be returned to the network management platform 301. According to the received indication, the network management platform 301 may further modify the field indicating the delivery status from "delivered" to "successful execution" or "failed execution".
In conclusion, the invention can realize the batch setting of the network element equipment configuration by reasonably grading the network, and effectively improves the efficiency of the repeated utilization of the configuration and the configuration behavior.
FIG. 6 shows a block diagram of an exemplary computing device, which is one example of a hardware device that may be applied to aspects of the present invention, according to one embodiment of the present invention.
With reference to FIG. 6, a computing device 600, which is one example of a hardware device that may be employed in connection with aspects of the present invention, will now be described. For example, network management platform 301, a network element device, may be implemented as computing device 600. Computing device 600 may be any machine that may be configured to implement processing and/or computing, and may be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, personal digital processing, a smart phone, an in-vehicle computer, or any combination thereof. The various methods/apparatus/servers/client devices described above may be implemented in whole or at least in part by a computing device 600 or similar device or system.
The bus 602 may include, but is not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA (eisa) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Software components may be located in the working memory 614, including, but not limited to, an operating system 616, one or more application programs 618, drivers, and/or other data and code. Instructions for implementing the methods and steps described above may be included in the one or more applications 618, and the aforementioned modules/units/components of the various apparatus/server/client devices may be implemented by instructions that are read and executed by the processor 604 for the one or more applications 618.
It should also be appreciated that variations may be made according to particular needs. For example, customized hardware might also be used and/or particular components might be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. In addition, connections to other computing devices, such as network input/output devices and the like, may be employed. For example, some or all of the disclosed methods and apparatus can be implemented with logic and algorithms in accordance with the present invention through programming hardware (e.g., programmable logic circuitry including Field Programmable Gate Arrays (FPGAs) and/or Programmable Logic Arrays (PLAs)) having assembly language or hardware programming languages (e.g., VERILOG, VHDL, C + +).
Although the various aspects of the present invention have been described thus far with reference to the accompanying drawings, the above-described methods, systems, and apparatuses are merely examples, and the scope of the present invention is not limited to these aspects but only by the appended claims and equivalents thereof. Various components may be omitted or may be replaced with equivalent components. In addition, the steps may also be performed in a different order than described in the present invention. Further, the various components may be combined in various ways. It is also important that as technology develops that many of the described components can be replaced by equivalent components appearing later.
Claims (8)
1. A method of network management based on configuration hierarchy, comprising:
receiving configuration information, wherein the configuration information at least comprises configuration settings for network element equipment in a network and levels to which the configuration settings are applied, and the levels comprise a global level, a node level and an equipment level;
generating a configuration item based on the received configuration information, and performing conflict detection based on the configuration item;
searching network element equipment needing to apply the configuration setting based on the level to which the configuration setting indicated in the configuration entry is applied;
generating a configuration synchronization event; and
sending the configuration synchronization event to the searched network element equipment needing to apply the configuration setting;
wherein the content of the first and second substances,
if the level to which the configuration setting applies is a global level, the configuration information further includes a designation of a network element device type, so that the configuration setting is effective for all network element devices of the designated type within the network;
if the level to which the configuration setting applies is a node level, the configuration information further includes a designation of one or more nodes and a designation of a type of network element device, such that the configuration setting is effective for the network element device of the designated type within the designated one or more nodes;
if the level to which the configuration setting applies is a device level, the configuration information further includes a designation of a specific network element device, so that the configuration setting is effective only for the designated network element device.
2. The method of claim 1, wherein performing collision detection based on the configuration entry further comprises:
(1) generating a unique key for the configuration entry;
(2) comparing the unique key with the unique key of the existing configuration item;
(3) determining that a conflict exists if there is a matching configuration entry having a unique key that is the same as the unique key;
(4) if so, judging whether the priority of the matched configuration item is higher than the priority of the configuration item, wherein the priority of the configuration at the equipment level is the highest, the priority of the configuration at the node level is the second priority, and the priority of the configuration at the global level is the lowest;
(5) prompting if the priority of the matched configuration item is higher than that of the configuration item;
(6) receiving the modified configuration information and generating a modified configuration item, and repeatedly executing the steps (1) - (5);
(7) storing the modified configuration entry.
3. The method of claim 1, wherein performing collision detection based on the configuration entry further comprises:
(1) generating a unique key for the configuration entry;
(2) comparing the unique key with the unique key of the existing configuration item;
(3) determining that a conflict exists if there is a matching configuration entry having a unique key that is the same as the unique key;
(4) if so, judging whether the priority of the matched configuration item is higher than the priority of the configuration item, wherein the priority of the configuration at the equipment level is the highest, the priority of the configuration at the node level is the second priority, and the priority of the configuration at the global level is the lowest;
(5) if the priority of the matched configuration entry is higher than that of the configuration entry, judging whether all the network element equipment to which the configuration setting is applied in the configuration entry has conflict;
(6) if not, modifying the configuration entry, wherein in the modified configuration entry, the configuration information of the conflicting network element equipment is kept consistent with the current configuration information of the network element equipment, and the conflicting network element equipment is marked to indicate that a configuration setting instruction is not issued to the conflicting network element equipment application;
(7) storing the modified configuration entry.
4. A method according to claim 2 or 3, wherein the configuration entry is stored if there is no conflict.
5. The method of claim 1, wherein finding the network element device that needs to apply the configuration setting based on the level to which the configuration setting indicated in the configuration entry applies further comprises:
if the level applied by the configuration setting is the configuration of the equipment level, searching the appointed network element equipment;
if the level applied by the configuration setting is the node level configuration, searching specified network element equipment of specified types in one or more specified nodes;
and if the level applied by the configuration setting is the configuration of the global level, searching the network element equipment of the specified type in the network.
6. The method of claim 1, wherein the network is a Domain Name System (DNS) network, and the network element device comprises one or more of: a caching device, a recursive device or a log collection device.
7. A configuration hierarchy based network management system comprising:
a network management platform;
a plurality of network element devices in a network, the plurality of network element devices being grouped physically or logically and each group being bound to a node;
wherein the network management platform further comprises:
the network management front-end interface configuration module is configured to present a configuration interface and receive configuration information, wherein the configuration information at least comprises configuration settings for network element equipment and levels applied by the configuration settings, and the levels comprise a global level, a node level and an equipment level;
the network management back-end configuration service module is configured to generate configuration items based on the configuration information and perform conflict detection based on the configuration items;
a network management configuration synchronization module configured to search for a network element device that needs to apply the configuration setting based on the level to which the configuration setting indicated in the configuration entry is applied, generate a configuration synchronization event, and send the configuration synchronization event to the searched network element device that needs to apply the configuration setting;
wherein the content of the first and second substances,
if the level to which the configuration setting applies is a global level, the configuration information further includes a designation of a network element device type, so that the configuration setting is effective for all network element devices of the designated type within the network;
if the level to which the configuration setting applies is a node level, the configuration information further includes a designation of one or more nodes and a designation of a type of network element device, such that the configuration setting is effective for the network element device of the designated type within the designated one or more nodes;
if the level to which the configuration setting applies is a device level, the configuration information further includes a designation of a specific network element device, so that the configuration setting is effective only for the designated network element device.
8. The system of claim 7, wherein the network is a Domain Name System (DNS) network, and the network element device comprises one or more of: a caching device, a recursive device or a log collection device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011486470.5A CN112671569B (en) | 2020-12-16 | 2020-12-16 | Network management method and system based on configuration classification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011486470.5A CN112671569B (en) | 2020-12-16 | 2020-12-16 | Network management method and system based on configuration classification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671569A CN112671569A (en) | 2021-04-16 |
| CN112671569B true CN112671569B (en) | 2022-09-30 |
Family
ID=75405596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011486470.5A Active CN112671569B (en) | 2020-12-16 | 2020-12-16 | Network management method and system based on configuration classification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671569B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4961224A (en) * | 1989-03-06 | 1990-10-02 | Darby Yung | Controlling access to network resources |
| CN106844753A (en) * | 2017-02-16 | 2017-06-13 | 北京天元创新科技有限公司 | A kind of method and device for building network element tree component |
| US10187309B1 (en) * | 2012-08-20 | 2019-01-22 | Amazon Technologies, Inc. | Congestion mitigation in networks using flow-based hashing |
| CN110198241A (en) * | 2019-06-03 | 2019-09-03 | 北京盟力星科技有限公司 | A kind of security control apparatus based on Network Management System |
| CN110710160A (en) * | 2017-05-31 | 2020-01-17 | 思科技术公司 | Generating network-wide logical models for network policy analysis |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10841221B2 (en) * | 2018-11-20 | 2020-11-17 | Arm Limited | Stage one cache lookup for network node of mesh network |
-
2020
- 2020-12-16 CN CN202011486470.5A patent/CN112671569B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4961224A (en) * | 1989-03-06 | 1990-10-02 | Darby Yung | Controlling access to network resources |
| US10187309B1 (en) * | 2012-08-20 | 2019-01-22 | Amazon Technologies, Inc. | Congestion mitigation in networks using flow-based hashing |
| CN106844753A (en) * | 2017-02-16 | 2017-06-13 | 北京天元创新科技有限公司 | A kind of method and device for building network element tree component |
| CN110710160A (en) * | 2017-05-31 | 2020-01-17 | 思科技术公司 | Generating network-wide logical models for network policy analysis |
| CN110198241A (en) * | 2019-06-03 | 2019-09-03 | 北京盟力星科技有限公司 | A kind of security control apparatus based on Network Management System |
Non-Patent Citations (2)
| Title |
|---|
| 基于网元的策略冲突解决方法;王峰;《计算机工程与应用》;20070101(第01期);全文 * |
| 建设电力通信网络管理系统;焦群;《电力系统自动化》;20000315(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671569A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2419854C2 (en) | Template based service management | |
| US11886609B2 (en) | Computer-implemented methods, systems comprising computer-readable media, and electronic devices for secure multi-datasource query job status notificaion | |
| US20220368706A1 (en) | Attack Behavior Detection Method and Apparatus, and Attack Detection Device | |
| EP2948875B1 (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| US11809397B1 (en) | Managing slot requests for query execution in hybrid cloud deployments | |
| US11411888B2 (en) | Distributed policy enforcement with optimizing policy transformations | |
| US20210152434A1 (en) | Internet of things device discovery and configuration | |
| GB2503546A (en) | Document suggestion by user action association and threshold comparison | |
| KR20210040321A (en) | Method and device for testing map service | |
| US11093617B2 (en) | Automated vulnerability grouping | |
| EP3881195A1 (en) | Approach for a controllable trade-off between cost and availability of indexed data in a cloud log aggregation solution such as splunk or sumo | |
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN112671569B (en) | Network management method and system based on configuration classification | |
| CN108733536B (en) | Monitoring management system and method | |
| CN112199624A (en) | Data access control method, device, electronic device and storage medium | |
| CN107733908B (en) | Data packet processing method and device, network equipment and readable storage medium | |
| CN116151631A (en) | Service decision processing system, service decision processing method and device | |
| US20200125431A1 (en) | Method for invoking component, and terminal | |
| KR101570980B1 (en) | Method for management common code of multi-tenane environment, server performing the same and storage media storing the same | |
| CN115840770B (en) | Local cache data processing method and related equipment based on distributed environment | |
| US11805002B2 (en) | Retrieving and provisioning entities based on inheritance | |
| CN114257598A (en) | Resource downloading method and device, storage medium and electronic equipment | |
| CN117633111A (en) | ClickHouse-based request processing method, device, equipment and medium | |
| CN114035939A (en) | Method, platform and storage medium for managing processes in container | |
| CN114063879A (en) | Method, electronic device and computer program product for processing operation commands |
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 | ||
| CB02 | Change of applicant information |
Address after: Room 401, building 1, No. 180, Yizhou Road, Xuhui District, Shanghai 200030 Applicant after: Yamu Technology Co.,Ltd. Address before: 200030 4th floor, building B3, Huaxin Huixiang City, 180 Yizhou Road, Xuhui District, Shanghai Applicant before: SHANGHAI YAMU COMMUNICATION TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |