A configuration backup method, device, apparatus and system

Abstract

The application provides a configuration backup method, device, equipment and system, the method comprises the following steps: receiving a version update request sent by an internal device, the internal device comprises a plurality of service modules, the version update request comprises a device identifier of the internal device and version information of each service module; updating the device identifier and the version information of each service module in a version information table; when receiving a configuration update request sent by a network management device, determining a target service module based on first version information and second version information corresponding to the device identifier; wherein the corresponding version information of the target service module in the first version information and the second version information is different; sending a configuration update response to the network management device, the configuration update response comprising the device identifier and the service identifier of the target service module, so that the network management device obtains a configuration file corresponding to the service identifier from the internal device corresponding to the device identifier. Through the application, network bandwidth can be saved, backup efficiency can be improved, and management complexity can be reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a configuration backup method, apparatus, device and system. Background Technology

[0002] In large-scale network environments, the number of devices is large and the network structure is complex. To ensure stable network operation and fault recovery, regular backup of device configurations is crucial. For example, the network management device can send configuration backup requests to each device. After receiving the configuration backup request, each device sends its configuration to the network management device, which then receives and backs up the configurations of each device.

[0003] However, since network management equipment needs to perform full backups of the configurations of each device regularly, there are problems such as high network overhead, low backup efficiency, and high management complexity during the configuration backup process.

[0004] Regarding the issue of high network overhead: When the network management device regularly backs up the configuration of each device, it needs to communicate with each device individually. For example, for a network with thousands of devices, the network management device needs to establish a connection with each device and transmit data. This not only consumes a lot of network bandwidth, but also consumes a lot of resources of the network management device, resulting in a decline in network performance, affecting normal business operations, and causing high network overhead.

[0005] Regarding the issue of low backup efficiency: network management devices need to communicate with a large number of devices one by one to obtain device configurations, making the backup process time-consuming. As the network scale continues to expand, backup time may extend from several hours to several days, severely affecting the timeliness of backup tasks and resulting in low backup efficiency. Moreover, if a device fails during backup, the network management device may not be able to obtain the latest configuration in time to restore the device.

[0006] Addressing the issue of high management complexity: Due to the diverse types and complex configurations of devices, tracking configuration changes for each device and ensuring backup accuracy becomes difficult. Once configuration errors or data loss occur, locating and repairing the problem is costly, making configuration backup management for a large number of devices challenging and complex. Summary of the Invention

[0007] This application provides a configuration backup method applied to export equipment, the method comprising:

[0008] The system receives version update requests from internal devices, which include multiple service modules. The version update request includes the device identifier of the internal device and the version information of each service module. The version update request is sent by the internal device when its configuration changes, resulting in an update of the version information.

[0009] Update the device identifier and the version information of each service module in the version information table;

[0010] Upon receiving a configuration update request from a network management device, the target service module is determined based on the first version information and the second version information corresponding to the device identifier; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different;

[0011] A configuration update response is sent to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0012] This application provides a configuration backup device for use in export equipment, the device comprising:

[0013] A receiving unit is configured to receive a version update request sent by an internal device, the internal device including multiple service modules, the version update request including the device identifier of the internal device and the version information of each service module; the version update request is sent when the configuration of the internal device changes, resulting in an update of the version information; the device identifier and the version information of each service module are updated in the version information table;

[0014] The determining unit is configured to, upon receiving a configuration update request sent by a network management device, determine a target service module based on first version information and second version information corresponding to the device identifier; wherein, the first version information includes version information of each service module recorded in the version information table, and the second version information includes version information of each service module at the time the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different;

[0015] The sending unit is configured to send a configuration update response to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0016] This application provides an electronic device, including: a processor and a machine-readable storage medium, wherein the machine-readable storage medium stores machine-executable instructions that can be executed by the processor; the processor is used to execute the machine-executable instructions to implement the configuration backup method of the above example of this application.

[0017] This application provides a configuration backup system, the system comprising:

[0018] An internal device is used to send a version update request to an egress device when the configuration of the internal device changes, resulting in an update and change in the version information; wherein the internal device includes multiple service modules, and the version update request includes the device identifier of the internal device and the version information of each service module;

[0019] The export device is used to receive the version update request and update the device identifier and the version information of each business module in the version information table based on the version update request;

[0020] The network management device is used to send a configuration update request to the egress device when the scheduled backup time of the entire network arrives. The scheduled backup time of the entire network refers to the time when the configuration of all internal devices is backed up.

[0021] An export device is used to receive the configuration update request, determine the target service module based on the first version information and the second version information corresponding to the device identifier, and send a configuration update response to the network management device; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; the version information corresponding to the target service module is different in the first version information and the second version information; the configuration update response includes the device identifier and the service identifier of the target service module;

[0022] The network management device is used to obtain the device identifier and the service identifier from the configuration update response, and to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0023] This application provides a computer program product, which includes a computer program that, when executed by a processor, implements the configuration backup method described in the above example of this application.

[0024] This application provides a machine-readable storage medium storing machine-executable instructions that can be executed by a processor; wherein the processor is configured to execute the machine-executable instructions to implement the configuration backup method of the above example of this application when the machine-executable instructions are executed.

[0025] As can be seen from the above technical solutions, in this embodiment, when the configuration of an internal device changes, resulting in an update and change in version information, the egress device updates the device identifier of the internal device and the version information of each service module in the version information table. That is, the egress device maintains the version information of each service module of each internal device. Thus, when receiving a configuration update request from the network management device, the egress device can identify the target service module whose version information has changed and send the service identifier of the target service module to the network management device. The network management device then obtains the configuration file corresponding to the target service module. In other words, the network management device only needs to obtain the configuration file corresponding to the target service module whose version information has changed; it does not need to obtain the configuration files corresponding to service modules whose version information has not changed, nor does it need to obtain the configuration files of all devices. During device configuration backup, network overhead is low, backup efficiency is high, and management complexity is low.

[0026] The above-mentioned equipment configuration backup method can meet the network's requirements for efficient and stable operation. By avoiding communication between the network management device and a large number of unchanged devices and service modules, it greatly reduces network bandwidth usage and backup time, thereby saving network bandwidth, significantly reducing the communication overhead of regular backup configuration in large network topologies, improving backup efficiency, and reducing management complexity.

[0027] To significantly reduce communication overhead, i.e., minimize network overhead: By dividing devices into egress devices and internal devices, during regular network-wide configuration backups, the network management device only needs to communicate with the egress device once to obtain configuration change information. This allows the network management device to communicate with devices whose configurations have changed only as needed. For example, in a large network with 2000 devices, if only 100 devices experience configuration changes, the network management device only needs to perform 1+100 communications instead of 2000 communications with all 2000 devices, greatly reducing the number of communication connections and lowering network bandwidth usage and system resource consumption.

[0028] To improve backup efficiency, i.e. shorten backup time: By reducing communication between network management devices and a large number of unchanged devices, it is not necessary to communicate with each device individually to obtain configuration information. Therefore, the time required for the backup process is significantly shortened, greatly compressing the backup time and eliminating the need for backups to take several hours or even longer.

[0029] To reduce management complexity, i.e., simplify the management process: Configuration version information is centrally managed through the egress device. The network management device does not need to track configuration changes for each individual device; it only needs to interact with the egress device to grasp the overall network configuration changes. This simplifies the configuration backup management process, reduces the difficulty of configuration backup management, and minimizes configuration errors or backup omissions caused by management complexity. It improves the accuracy and reliability of network configuration management and simplifies the management process.

[0030] It can enhance network stability and reduce network interference. Because the communication overhead of the backup process is reduced, it minimizes interference with normal network traffic, lowers the risk of network congestion, ensures network stability, and enables the network to continuously and stably provide services to users, guaranteeing the normal transmission of business data. Attached Figure Description

[0031] Figure 1 This is a flowchart illustrating a configuration backup method according to one embodiment of this application;

[0032] Figure 2 This is a schematic diagram of the configuration backup method in one embodiment of this application;

[0033] Figure 3 This is a schematic diagram of the version information synchronization process in one embodiment of this application;

[0034] Figure 4 This is a schematic diagram of a network-wide periodic backup and optimization process in one embodiment of this application;

[0035] Figure 5 This is a schematic diagram of the configuration backup device in one embodiment of this application;

[0036] Figure 6 This is a hardware structure diagram of an electronic device according to one embodiment of this application. Detailed Implementation

[0037] This application provides a configuration backup method, which can be applied to export equipment. See [link to relevant documentation]. Figure 1 The diagram shown illustrates the process of this configuration backup method, which may include:

[0038] Step 101: Receive a version update request sent by an internal device. The internal device may include multiple business modules. The version update request includes the device identifier of the internal device and the version information of each business module. The version update request is sent by the internal device when the configuration changes, causing the version information to be updated and changed. When the version information of any business module of the internal device changes, the configuration of the internal device changes, and the configuration change causes the version information to be updated and changed.

[0039] Step 102: Update the device identifier and version information of each business module in the version information table.

[0040] Step 103: Upon receiving a configuration update request from the network management device, determine the target service module based on the first version information and the second version information corresponding to the device identifier; wherein, the first version information may include the version information of each service module recorded in the version information table, and the second version information may include the version information of each service module when the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different.

[0041] Step 104: Send a configuration update response to the network management device. The configuration update response may include the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0042] In one example, for each business module, the version information of that business module can include the version number of each business sub-module within that module. Each business module can include at least one business sub-module, and different sub-modules are used to implement different functions. When the configuration file corresponding to a business module changes, the configuration file is analyzed to identify the business sub-module whose configuration information has changed, and the version number of that sub-module is incremented (e.g., by 1). The configuration file corresponding to that business module can include the configuration information of each business sub-module.

[0043] In one example, updating the device identifier and version information of each business module in the version information table may include, but is not limited to: determining whether a data entry corresponding to the device identifier exists in the version information table; if no data entry corresponding to the device identifier exists, inserting a new data entry into the version information table, which includes the device identifier and version information of each business module; or, if a data entry corresponding to the device identifier already exists, updating the version information of each business module in the data entry corresponding to the device identifier.

[0044] In one example, a configuration update request might be sent by the network management device when the scheduled network backup time arrives. This scheduled backup time can represent the time when the network management device backs up the configurations of all internal devices. All devices managed by the network management device can be categorized as egress devices and internal devices. Devices connected to the external network can be designated as egress devices, and devices located within the network can be designated as internal devices. For each device, if its uplink port is connected to a border router and its IP address belongs to an internal network segment, then the device is considered an internal device.

[0045] As can be seen from the above technical solutions, in this embodiment, when the configuration of an internal device changes, resulting in an update and change in version information, the egress device updates the device identifier of the internal device and the version information of each service module in the version information table. That is, the egress device maintains the version information of each service module of each internal device. Thus, when receiving a configuration update request from the network management device, the egress device can identify the target service module whose version information has changed and send the service identifier of the target service module to the network management device. The network management device then obtains the configuration file corresponding to the target service module. In other words, the network management device only needs to obtain the configuration file corresponding to the target service module whose version information has changed; it does not need to obtain the configuration files corresponding to service modules whose version information has not changed, nor does it need to obtain the configuration files of all devices. During device configuration backup, network overhead is low, backup efficiency is high, and management complexity is low.

[0046] The above-mentioned equipment configuration backup method can meet the network's requirements for efficient and stable operation. By avoiding communication between the network management device and a large number of unchanged devices and service modules, it greatly reduces network bandwidth usage and backup time, thereby saving network bandwidth, significantly reducing the communication overhead of regular backup configuration in large network topologies, improving backup efficiency, and reducing management complexity.

[0047] To significantly reduce communication overhead, i.e., minimize network overhead: By dividing devices into egress devices and internal devices, during regular network-wide configuration backups, the network management device only needs to communicate with the egress device once to obtain configuration change information. This allows the network management device to communicate with devices whose configurations have changed only as needed. For example, in a large network with 2000 devices, if only 100 devices experience configuration changes, the network management device only needs to perform 1+100 communications instead of 2000 communications with all 2000 devices, greatly reducing the number of communication connections and lowering network bandwidth usage and system resource consumption.

[0048] To improve backup efficiency, i.e. shorten backup time: By reducing communication between network management devices and a large number of unchanged devices, it is not necessary to communicate with each device individually to obtain configuration information. Therefore, the time required for the backup process is significantly shortened, greatly compressing the backup time and eliminating the need for backups to take several hours or even longer.

[0049] To reduce management complexity, i.e., simplify the management process: Configuration version information is centrally managed through the egress device. The network management device does not need to track configuration changes for each individual device; it only needs to interact with the egress device to grasp the overall network configuration changes. This simplifies the configuration backup management process, reduces the difficulty of configuration backup management, and minimizes configuration errors or backup omissions caused by management complexity. It improves the accuracy and reliability of network configuration management and simplifies the management process.

[0050] It can enhance network stability and reduce network interference. Because the communication overhead of the backup process is reduced, it minimizes interference with normal network traffic, lowers the risk of network congestion, ensures network stability, and enables the network to continuously and stably provide services to users, guaranteeing the normal transmission of business data.

[0051] The technical solutions described above in the embodiments of this application will be explained below in conjunction with specific application scenarios.

[0052] In large-scale network environments, the number of devices is numerous and the network structure is complex. To ensure stable network operation and fault recovery, regular backups of device configurations are crucial. For example, network management devices can periodically perform full backups of each device's configuration. This involves the network management device periodically sending configuration backup requests to each device, and each device, upon receiving the request, sending its configuration back to the network management device, which then receives and backs up the configurations of each device. However, periodically performing full backups of all device configurations presents challenges such as high network overhead, low backup efficiency, and high management complexity.

[0053] In response to the above findings, this application proposes a configuration backup method, which is an efficient configuration backup method for large-scale network deployments. It can meet the network's requirements for efficient and stable operation. This configuration backup method can save network bandwidth, improve backup efficiency, and reduce management complexity.

[0054] This application proposes a configuration backup method, see [link to relevant documentation]. Figure 2 The diagram shown illustrates the framework of this configuration backup method, which may involve processes such as device role allocation, version number definition and management, version information synchronization, and regular network-wide backup optimization. The following sections explain these processes.

[0055] First, regarding device role classification. In the process of device role classification, all devices managed by the network management device can be divided into egress devices and internal devices. Egress devices are also called network egress devices. For example, devices that connect to external networks are egress devices, and devices located inside the network are internal devices.

[0056] In one example, devices in a large network (i.e., all devices managed by the network management device) can be divided into two roles: egress devices and internal devices. This involves defining roles and categorizing them as egress devices and internal devices. Egress devices act as the hub connecting the entire network to external networks and also handle configuration version information aggregation. Internal devices are those that perform various business functions within the network.

[0057] In one example, a device's role can be determined based on its function and location. For instance, a device that connects to an external network is designated as an egress device; such as a border router or firewall connecting to an external network. In this way, the egress device acts as the hub connecting the entire network to the external network.

[0058] Internal devices are devices located within the network that provide services to users or perform internal data forwarding. For example, devices providing services to users, such as servers, can be considered internal devices. Similarly, devices performing internal data forwarding, such as switches and routers, can be considered internal devices. Thus, internal devices are those that perform various business functions within the network.

[0059] In one example, in some complex networks, there may be multiple egress devices. Based on the network topology and management needs, the areas or groups of devices each egress device is responsible for can be rationally allocated. For instance, egress device 1 is responsible for area a1, and all internal devices within area a1 communicate with egress device 1; egress device 2 is responsible for area a2, and all internal devices within area a2 communicate with egress device 2, and so on.

[0060] In one example, during network deployment, the network administrator can specify device roles, that is, designate which devices are egress devices and which are internal devices. For instance, for egress devices, the network administrator can set specific role identifiers in the device configuration interface or network management system platform, such as setting the role identifier of the border router to "egress device," thus enabling the border router to act as an egress device. For internal devices, the network administrator can set specific role identifiers in the device configuration interface or network management system platform, such as setting the role identifier of the server (router, switch) to "internal device," thus enabling the server to act as an internal device.

[0061] In one example, during network deployment, each device can decide whether it is an egress or internal device through an election process. For instance, each device broadcasts a message carrying its IP address. Each device can then compare its IP address with those of other devices. If its IP address is the smallest, it becomes the egress device; otherwise, it becomes an internal device. Alternatively, if its IP address is the smallest, it becomes an internal device; otherwise, it becomes the egress device. Of course, this is just an example; a policy can be pre-configured on each device, allowing each device to decide whether to become an egress or internal device based on that policy.

[0062] In one example, during network deployment, for each device, if its uplink port is connected to an external network, then the device is considered an external network-connected device and is automatically classified as an egress device, undergoing egress device processing procedures. Conversely, if each device's uplink port is connected to a border router and its IP address belongs to an internal network segment, then the device is considered an internal network device performing various service functions and is automatically classified as an internal device, undergoing internal device processing procedures.

[0063] In summary, in highly automated networks, scripts can be written to automatically identify and assign roles based on information such as device IP address ranges and port connections. For example, if a device's uplink port is connected to a border router and its IP address belongs to the internal network segment, the script will automatically classify the device as an internal device and mark it accordingly.

[0064] Second, regarding version number definition and management.

[0065] In the process of defining and managing version numbers, version information of internal devices can be defined. Internal devices include multiple business modules, and the version information of internal devices is the version information of each business module of the internal device.

[0066] In one example, a business module can also be called an application module or a functional module. A business module is a module used to implement a certain business function, or a business module is a module used to implement a certain application function, or a business module is a module used to implement a certain function. For example, a routing business module is a business module used to implement routing functions, and a security business module is a business module used to implement security functions; there are no restrictions on this.

[0067] For each business module, the business module includes at least one business sub-module, and different business sub-modules are used to implement different functions (or different applications, or different businesses) supported by the business module. For example, the business module can support multiple functions (or, in other words, the business module is used to support multiple sub-functions under the same function), so each business sub-module is used to implement one function.

[0068] For example, the routing service module includes service sub-module X and service sub-module Y. The routing service module supports routing functions, including routing policy functions and routing table update functions. Thus, service sub-module X is used to implement the routing policy function, and service sub-module Y is used to implement the routing table update function.

[0069] For example, if the routing policy changes, such as adding a new routing policy, the business submodule X can add a new routing policy. Similarly, if the routing table update policy changes, such as adjusting the routing table update frequency, the business submodule Y can adjust the routing table update frequency.

[0070] In one example, for each business module, the version information can include the version number of each business sub-module. For instance, the version information of the business module might use the format "abc," where 'a' represents the version number of the first business sub-module, 'b' represents the version number of the second business sub-module, 'c' represents the version number of the third business sub-module, and so on. Assuming there are a total of M business sub-modules, then the version information would contain M version numbers.

[0071] Taking three business sub-modules as an example, the initial version information of the business module is 0.0.0 (or 1.1.1). Based on this, if the configuration information corresponding to the first business sub-module changes, the version number of the first business sub-module is incremented (e.g., the version number is incremented by 1), and the version information of the business module becomes 1.0.0. If the configuration information corresponding to the third business sub-module changes, the version number of the third business sub-module is incremented, and the version information of the business module becomes 1.0.1. If the configuration information corresponding to the first business sub-module changes, the version number of the first business sub-module is incremented, and the version information of the business module becomes 2.0.1, and so on.

[0072] Obviously, when the configuration information corresponding to each business sub-module changes, the version number of that business sub-module can be incremented, so that the version information of that business module will be updated synchronously.

[0073] For example, taking the routing service module as an example, assuming the routing service module includes service submodule X and service submodule Y, the version information of the routing service module adopts the format ab, where 'a' represents the version number of service submodule X and 'b' represents the version number of service submodule Y, that is, defining an independent version number for each service submodule. Assuming the current version of the routing service module is 1.3, based on this:

[0074] If the routing policy configuration changes, such as adding a new routing policy, that is, the configuration information corresponding to business submodule X changes, the version number of business submodule X in the version information of the routing business module will change. For example, if the version number changes from 1 to 2, the version information of the routing business module will be 2.3.

[0075] If the routing table update policy configuration changes, such as adjusting the routing table update frequency, i.e., the configuration information corresponding to service submodule Y changes, then the version number of service submodule Y in the version information of the routing service module will change. For example, if the version number changes from 3 to 4, the version information of the routing service module will be 2.4.

[0076] In summary, when the configuration information corresponding to business submodule X changes, the version number of business submodule X is incremented (e.g., by 1). When the configuration information corresponding to business submodule Y changes, the version number of business submodule Y is incremented (e.g., by 1), thereby updating the version information of the routing business module.

[0077] In one example, the internal device can include a version structure (also called a version number structure) corresponding to each business module. This version structure can include the business identifier of the business module (i.e., a unique identifier for the business module, which can be the name of the business module or any other identifier that uniquely represents the business module) and the version number of each business submodule of that business module. Thus, when accumulating the version numbers of business submodules, the version number of that business submodule can be modified within this version structure.

[0078] For example, assuming the internal device includes business module m1 and business module m2, the internal device also includes version structure n1 and version structure n2. The internal device needs to be divided into two memory areas: the first memory area is used to store version structure n1, and the second memory area is used to store version structure n2.

[0079] Based on this, the internal device can allocate specific memory areas for each business module to store version numbers, that is, use a version structure to store version numbers. The version structure can be in the form of an array, and the version structure includes a business identifier field and a version number field. The business identifier field is used to record the business identifier of the business module, and the version number field is used to record the version number of each business sub-module of the business module.

[0080] For example, version structure n1 is used to store the service identifier of service module m1 and the version number of each service submodule of service module m1. In addition, version structure n2 is used to store the service identifier of service module m2 and the version number of each service submodule of service module m2.

[0081] For example, taking the routing service module as an example, the version structure (i.e., the array of structures) can be represented as: {routing_module, 1.3}. `routing_module` represents the service identifier of the routing service module, and 1.3 represents the version number of each service submodule of the routing service module. When the configuration information corresponding to service submodule X changes, the version structure is updated to {routing_module, 2.3}. When the configuration information corresponding to service submodule Y changes, the version structure is updated to {routing_module, 2.4}, and so on.

[0082] During version number definition and management, version information for export devices can be defined. Each export device comprises multiple business modules, and its version information is the version information of each of these business modules. For each business module, the version information can include the version number of each of its sub-modules. The export device can include a version structure corresponding to each business module, and this structure can include the business identifier of the business module and the version number of each of its sub-modules.

[0083] Third, regarding version information synchronization. During version information synchronization, internal devices can send their device identifiers and version information of each business module to the egress device. The egress device then records the internal device identifiers and version information of each business module in its version information table. See also... Figure 3 The diagram shown illustrates the version information synchronization process, which may include:

[0084] Step 301: The internal device checks at fixed intervals whether the configuration file corresponding to the business module has changed. If yes, proceed to step 302 and subsequent steps. After the fixed interval, the internal device continues to check whether the configuration file corresponding to the business module has changed. If no, the process ends, and after the fixed interval, the internal device continues to check whether the configuration file corresponding to the business module has changed.

[0085] For example, an internal device may include multiple business modules, each corresponding to a configuration file. At fixed intervals (e.g., 5 minutes), the internal device calculates the first hash value of the configuration file corresponding to that business module and compares it with the previously recorded second hash value (i.e., the hash value of the configuration file corresponding to that business module during the previous check). If the first hash value and the second hash value are the same, it means that the configuration file corresponding to that business module has not changed. If the first hash value and the second hash value are different, it means that the configuration file corresponding to that business module has changed.

[0086] For example, internal devices can be configured with monitoring programs to calculate the first hash value of the configuration file corresponding to the business module and compare it with the second hash value recorded last time.

[0087] Step 302: If the configuration file corresponding to a business module changes, the internal device analyzes the configuration file to determine the business sub-module whose configuration information has changed, and increments the version number of that business sub-module. For example, the internal device can increment the version number of that business sub-module by 1.

[0088] For example, the configuration file corresponding to this business module includes the configuration information of each business sub-module. When this configuration file changes, the configuration information of each business sub-module can be analyzed. For each business sub-module, analyze whether the configuration information of that business sub-module has changed (i.e., whether it has changed compared to the configuration information corresponding to that business sub-module at the time of the last detection).

[0089] If the configuration information of this business submodule changes, the version number of this business submodule is incremented by 1. If the configuration information of this business submodule does not change, the version number of this business submodule remains unchanged.

[0090] Clearly, if the configuration file corresponding to a business module changes, the version number of at least one business sub-module will change (i.e., the version number will increment by 1). Considering that the version information of a business module includes the version numbers of each business sub-module of that business module, the version information of the business module will change.

[0091] Step 303: The internal device sends a version update request to the external device. The version update request may include the device identifier of the internal device and the version information of each business module of the internal device.

[0092] In one example, when the version information of any business module changes (i.e., the version numbers of its sub-modules are incremented), the internal device can send a version update request to the egress device. For instance, the internal device includes business module m1 and business module m2. If the version information of business module m1 changes, the internal device sends a version update request to the egress device. This version update request includes the internal device's device identifier, the version information of business module m1, and the version information of business module m2 (even if the version information of business module m2 has not changed, it still carries the version information of business module m2).

[0093] In one example, an internal device can encapsulate the device identifier and version information of each business module into a version update request in a specific format. For example, the message format of the version update request can be: [Device identifier, version information of business module 1, version information of business module 2, ..., version information of business module n].

[0094] For the device identifier, this identifier can be a unique identifier for the internal device, as long as it is unique. For the version information of the business module, this version information includes the version number of each business sub-module of the business module, such as 1.2.3, indicating that the version numbers of the three business sub-modules are 1, 2, and 3 respectively.

[0095] For the version information of business modules in the version update request, this version information needs to correspond to the business identifier of the business module. This means that the version information corresponds to the business identifier; that is, the version update request also includes the business identifier of the business module. For example, business module 1, business module 2, ..., business module n represent the business identifier. The business identifier of a business module is a unique identifier for that business module, such as the name of the business module.

[0096] Based on this, the version update request includes the device identifier of the internal device, the service identifier of each service module, and the version information of each service module. For example, the version update request may include the device identifier of the internal device, the service identifier of service module 1, the version information of service module 1, the service identifier of service module 2, the version information of service module 2, and so on.

[0097] In one example, when the version information of any business module changes, the internal device can send a version update request to the egress device. Alternatively, the internal device can adjust the sending frequency based on network load. When the network load is below a threshold, it can send version update requests promptly, ensuring timely updates whenever the version information of any business module changes. Or, when the network load is not below the threshold, it can appropriately cache and batch-send version update requests. This way, whenever the version information of a business module changes, a version update request can be generated and cached. When multiple version update requests are cached, the internal device can send all of them together to the egress device.

[0098] Step 304: The export device receives the version update request sent by the internal device.

[0099] Step 305: The export device obtains the device identifier of the internal device and the version information of each business module from the version update request, and updates the device identifier and the version information of each business module in the version information table.

[0100] In one example, the export device can maintain a version information table to record the version information of each business module of the internal device. This version information table can include multiple data entries, each recording the version information of each business module of an internal device. For example, the version information table can be a hash table, and the data entries within the hash table can be called key-value pairs. For instance, the export device sets up a dedicated data structure (such as a hash table) to store the version information of the internal device, with the device identifier as the key and the corresponding values ​​being an array containing the version information of each business module.

[0101] See Table 1 for an example of a version information table. This version information table may include multiple data entries, each of which records the device identifier and version information of each business module.

[0102] Table 1

[0103] AAA [2.4，3.1.1，1.1] BBB [4.4，2.1.1，2.2] … …

[0104] For example, AAA's internal equipment includes three business modules. The first business module includes two business sub-modules with version numbers 2 and 4. The second business module includes three business sub-modules with version numbers 3, 1, and 1. The third business module includes two business sub-modules with version numbers 1 and 1.

[0105] In one example, after the outgoing device obtains the device identifier of the internal device and the version information of each business module from the version update request, it determines whether a data entry corresponding to the device identifier exists in the version information table. If no data entry exists, a new data entry is inserted into the version information table, which includes the device identifier and the version information of each business module. If a data entry already exists, the version information of each business module is updated in the data entry corresponding to the device identifier.

[0106] For example, if the version update request includes the device identifier "CCC" and version information [3.4, 3.1.1, 3.1], then there is no data table entry corresponding to this device identifier. Instead, a new data table entry is inserted into the version information table, as shown in Table 2. If the version update request includes the device identifier "AAA" and version information [2.4, 3.2.1, 1.1], then there is a data table entry corresponding to this device identifier. The version information of each business module is updated in the data table entry corresponding to this device identifier, that is, replaced with the version information in the version update request, as shown in Table 3.

[0107] Table 2

[0108] AAA [2.4，3.1.1，1.1] BBB [4.4，2.1.1，2.2] CCC [3.4，3.1.1，3.1] … …

[0109] Table 3

[0110] AAA [2.4，3.2.1，1.1] BBB [4.4，2.1.1，2.2] … …

[0111] In one example, since version information corresponds to the business identifier of a business module, and version update requests include the business identifier of the business module, the correspondence between the device identifier of the internal device, the business identifier of the business module, and the version information of the business module can be recorded in the version information table. For example, see Table 4, which is an example of a version information table and corresponds to Table 3.

[0112] Table 4

[0113]

[0114] In one example, the exporting device periodically (e.g., hourly) organizes and verifies the information in the version information table to ensure its accuracy and completeness. This might include deleting invalid device identifiers and version information, and checking the format of the version information. Alternatively, after receiving K version update requests, the exporting device organizes and verifies the information in the version information table to ensure its accuracy and completeness. Or, after receiving P version update requests from internal devices, the exporting device organizes and verifies the information in the version information table to ensure its accuracy and completeness.

[0115] In one example, the version information table could also include the device identifier of the exported equipment and the version information of each business module of the exported equipment. This way, when the version information of any business module of the exported equipment changes, the device identifier of the exported equipment and the version information of each business module are directly recorded in the version information table.

[0116] Fourth, regular network-wide backup and optimization. During regular network-wide backup and optimization, the egress device can send the device identifier of the internal device and the service identifier of the target service module to the network management device. The network management device then retrieves the configuration file corresponding to the service identifier from the internal device corresponding to that device identifier. See also... Figure 4 The diagram shown illustrates the network-wide periodic backup and optimization process, which may include:

[0117] Step 401: The network management device sends a configuration update request to the egress device. For example, when the scheduled backup time for the entire network arrives, the network management device sends a configuration update request to the egress device. This scheduled backup time can represent the time when the network management device backs up the configurations of all internal devices.

[0118] For example, network management devices (network management systems) can periodically back up the configurations of all devices (such as internal and egress devices), such as every 6 hours or under certain conditions (such as nighttime backups). This time point for backing up the configurations of all devices can be called the network-wide periodic backup time point, and the network management device sends a configuration update request to the egress device at this time. During a network-wide periodic backup, the network management device only needs to communicate with the egress device once to request information on all devices whose configurations have changed, thus centrally obtaining change information.

[0119] Step 402: The outgoing device receives the configuration update request sent by the network management device.

[0120] In one example, when the outgoing device receives the configuration update request, it backs up the current version information table and records this backup version information table as the backup information table. When the outgoing device receives the configuration update request again, it can determine the target business module based on this backup information table.

[0121] Step 403: For each device identifier in the version information table, the egress device determines the first version information and the second version information corresponding to that device identifier. The first version information includes the version information of each service module recorded in the version information table (i.e., the current version information table), and the second version information includes the version information of each service module when the configuration update request was last received; that is, the version information of each service module recorded in the backup information table when the egress device last received the configuration update request.

[0122] For example, for the device identifier "AAA", the first version information can include the version information of business module m11 and business module m12 recorded in the current version information table. The second version information can include the version information of business module m11 and business module m12 recorded in the backup information table (i.e., the version information table when the egress device last received a configuration update request).

[0123] Step 404: The export equipment determines the target business module based on the first version information and the second version information; wherein, the version information corresponding to the target business module is different in the first version information and the second version information.

[0124] For example, regarding the device identifier "AAA", if the version information of business module m11 in the first version information differs from the version information of business module m11 in the second version information, then business module m11 is selected as the target business module. If the version information of business module m11 in the first version information is the same as the version information of business module m11 in the second version information, then business module m11 is not the target business module. Similarly, it can be determined whether business module m12 is the target business module.

[0125] If the target service module exists among all the service modules corresponding to device identifier "AAA", it indicates that the configuration file of the internal device corresponding to device identifier "AAA" has changed, and the network management device needs to be triggered to retrieve the changed configuration file from this internal device. If the target service module does not exist among all the service modules corresponding to device identifier "AAA", it indicates that the configuration file of the internal device corresponding to device identifier "AAA" has not changed, and the network management device does not need to be triggered to retrieve the changed configuration file from this internal device.

[0126] Step 405: The egress device sends a configuration update response (i.e., a response message to the configuration update request) to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module.

[0127] For example, if the target business module exists among all the business modules corresponding to device identifier "AAA", such as business module m11, then the configuration update response includes device identifier "AAA" and the business identifier of business module m11, but does not include the business identifier of business module m12. Furthermore, if the target business module does not exist among all the business modules corresponding to device identifier "BBB", then the configuration update response does not include device identifier "BBB" or the business identifier of the business module corresponding to device identifier "BBB".

[0128] In summary, after receiving a configuration update request, the outgoing device iterates through the version information table, comparing the version information of each business module of each internal device with the version information of the last backup record. If a difference is found in the version information of a certain business module, that is, if this business module is the target business module, then the device identifier of the internal device and the business identifier of the target business module are recorded.

[0129] After iterating through the version information table, the internal devices whose configuration files have changed and the target business modules whose configuration files have changed can be found. That is, it is determined which internal devices and which business modules have changed configuration files. Then, the egress device will organize the device identifiers of the internal devices that have changed and the business identifiers of the target business modules and return them to the network management device to realize the acquisition of changed configurations on demand.

[0130] For example, when the configuration file corresponding to the egress device changes, the configuration update response can also include the device identifier of the egress device and the service identifier of the target service module of the egress device. In this way, the network management device obtains the configuration file corresponding to the service identifier from the egress device corresponding to the device identifier.

[0131] Step 406: The network management device receives the configuration update response, obtains the device identifier and service identifier from the configuration update response, and obtains the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0132] For example, if the configuration update response includes device identifier "AAA" and the service identifier of service module m11, the network management device obtains the configuration file corresponding to service module m11 from the internal device corresponding to device identifier "AAA". Alternatively, the network management device might send a configuration retrieval request to the internal device corresponding to device identifier "AAA," including the service identifier of service module m11. In this case, the internal device needs to send the configuration file corresponding to service module m11 to the network management device. This internal device does not need to send the configuration files corresponding to other service modules (such as service module m12) to the network management device.

[0133] In one example, if the configuration update response includes multiple device identifiers, the network management device needs to establish a connection with the internal device corresponding to each device identifier; that is, it needs to establish a connection with each internal device whose configuration has changed in turn. After establishing a connection with an internal device, the network management device can obtain the configuration file corresponding to the target service module (i.e., the target service module of the internal device) from that internal device.

[0134] When establishing a connection between a network management device and an internal device, the connection method can be selected based on the device type and appropriate protocol. For example, for internal devices supporting SNMP (Simple Network Management Protocol), the network management device establishes an SNMP-based connection, and uses an SNMP GET request to retrieve the configuration file (i.e., the configuration information of the target service module) corresponding to the internal device. For internal devices supporting SSH (Secure Shell), the network management device establishes an SSH-based connection, logs into the internal device via SSH, and executes the corresponding command to retrieve the configuration file corresponding to the target service module. For example, the network management device logs into the internal device via SSH and executes the "show running-config" command to retrieve the configuration file.

[0135] In one example, after obtaining the configuration file corresponding to the target service module from internal devices, the network management device compares the configuration in the configuration file with the last backup configuration stored locally. It extracts only the changed configuration parts and stores them locally, thus completing the configuration backup. After obtaining the configuration information of all changed service modules from all devices, the network management device integrates and stores this configuration information, completing the backup and update of the entire network.

[0136] In the above method, the network management device only communicates with the devices whose configurations have changed to obtain the configuration information of the changed service modules, and realizes the operation of obtaining changed configurations on demand. This avoids the network management device communicating with a large number of unchanged devices and service modules, which greatly reduces network bandwidth usage and backup time.

[0137] As can be seen from the above technical solutions, in this embodiment, the network management device only needs to obtain the configuration file corresponding to the target service module whose version information has changed. During the device configuration backup process, network overhead is small, backup efficiency is high, and management complexity is low. It can meet the network's requirements for efficient and stable operation. By avoiding communication between the network management device and a large number of unchanged devices and service modules, it greatly reduces network bandwidth usage and backup time, thereby saving network bandwidth and significantly reducing the communication overhead of periodically backing up configurations in large network deployments. This improves backup efficiency and reduces management complexity. Devices in large network deployments are divided into egress devices and internal devices, clearly defining the functions of each role to achieve efficient backup. Version number rules are defined for each service module of the device, and version numbers are effectively stored and updated to accurately determine configuration changes. Internal devices synchronize version information to egress devices. The egress device's management of information and its strategy of obtaining changed configurations on demand during network-wide backup optimize the backup process.

[0138] Based on the same application concept as the above method, this application proposes a configuration backup device for use in export equipment. See [link to relevant documentation]. Figure 5 The diagram shown is a structural schematic of the device, which includes:

[0139] The receiving unit 51 is configured to receive a version update request sent by an internal device. The internal device includes multiple service modules. The version update request includes the device identifier of the internal device and the version information of each service module. The version update request is sent when the configuration of the internal device changes, causing the version information to be updated and changed. The device identifier and the version information of each service module are updated in the version information table.

[0140] The determining unit 52 is configured to determine the target service module based on the first version information and the second version information corresponding to the device identifier when receiving a configuration update request sent by the network management device; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different.

[0141] The sending unit 53 is used to send a configuration update response to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0142] In one example, for each business module, the version information of the business module includes the version number of each business sub-module of the business module; wherein, the business module includes at least one business sub-module, and different business sub-modules are used to implement different functions; wherein, when the configuration file corresponding to the business module changes, the business sub-module whose configuration information has changed is determined by analyzing the configuration file, and the version number of the business sub-module is accumulated; the configuration file corresponding to the business module includes the configuration information of each business sub-module; the configuration update request is sent by the network management device when the network-wide periodic backup time point arrives; wherein, the network-wide periodic backup time point represents the time point at which the network management device backs up the configuration of all internal devices; wherein, all devices managed by the network management device are divided into egress devices and internal devices, devices connected to the external network are egress devices, and devices located inside the network are internal devices;

[0143] Specifically, for each device, if its uplink port is connected to the border router and its IP address belongs to the internal network segment, then the device is identified as an internal device.

[0144] In one example, when the receiving unit 51 updates the device identifier and the version information of each service module in the version information table, it is specifically used to: determine whether there is a data table entry corresponding to the device identifier in the version information table; if there is no data table entry corresponding to the device identifier, insert a new data table entry in the version information table, the data table entry including the device identifier and the version information of each service module; or, if there is already a data table entry corresponding to the device identifier, update the version information of each service module in the data table entry corresponding to the device identifier.

[0145] Based on the same application concept as the above method, this application proposes a configuration backup system, the system comprising: an internal device, configured to send a version update request to an egress device when the configuration of the internal device changes, resulting in version information updates; wherein the internal device includes multiple service modules, and the version update request includes the device identifier of the internal device and version information of each service module; and an egress device, configured to receive the version update request and update the device identifier and the version information of each service module in a version information table based on the version update request.

[0146] The network management device is used to send a configuration update request to the egress device when the scheduled backup time of the entire network arrives. The scheduled backup time of the entire network refers to the time when the configuration of all internal devices is backed up.

[0147] An export device is used to receive the configuration update request, determine the target service module based on the first version information and the second version information corresponding to the device identifier, and send a configuration update response to the network management device; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; the version information corresponding to the target service module is different in the first version information and the second version information; the configuration update response includes the device identifier and the service identifier of the target service module;

[0148] The network management device is used to obtain the device identifier and the service identifier from the configuration update response, and to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

[0149] In one example, an internal device is used to detect at fixed intervals whether the configuration file corresponding to a business module has changed. If the configuration file corresponding to the business module has changed, the device analyzes the configuration file to determine the business sub-module whose configuration information has changed, and increments the version number of the business sub-module. The business module includes at least one business sub-module, with different sub-modules implementing different functions. The version information of the business module includes the version number of each business sub-module. The internal device includes a version structure corresponding to the business module, which includes the business identifier of the business module and the version number of each business sub-module. When incrementing the version number of a business sub-module, the version number of that business sub-module is modified in the version structure.

[0150] Based on the same application concept as the above method, this application proposes an electronic device (such as the export device mentioned above), see [link to relevant documentation]. Figure 6 As shown, the electronic device includes a processor 61 and a machine-readable storage medium 62, the machine-readable storage medium 62 storing machine-executable instructions that can be executed by the processor 61; the processor 61 is used to execute the machine-executable instructions to implement the configuration backup method disclosed in the above example.

[0151] Based on the same concept as the above method, this application also provides a machine-readable storage medium storing a plurality of computer instructions, which, when executed by a processor, can implement the configuration backup method disclosed in the above examples of this application.

[0152] The aforementioned machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, machine-readable storage media can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0153] Based on the same concept as the methods described above, this application also provides a computer program product, which includes a computer program. When executed by a processor, the computer program implements the configuration backup method disclosed in the examples above.

[0154] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0155] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A configuration backup method, characterized in that, Applied to export equipment, wherein the export equipment is a device connected to an external network, the method includes: The system receives version update requests from internal devices, which include multiple service modules. The version update request includes the device identifier of the internal device and the version information of each service module. The version update request is sent by the internal device when its configuration changes, resulting in an update of the version information. The internal device is a device that provides services to users or forwards internal data. Update the device identifier and the version information of each service module in the version information table; Upon receiving a configuration update request from a network management device, the target service module is determined based on the first version information and the second version information corresponding to the device identifier; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different; A configuration update response is sent to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

2. The method according to claim 1, characterized in that, For each business module, the version information of the business module includes the version number of each business sub-module of the business module; wherein, the business module includes at least one business sub-module, and different business sub-modules are used to implement different functions; Specifically, when the configuration file corresponding to the business module changes, the business sub-module whose configuration information has changed is identified by analyzing the configuration file, and the version number of the business sub-module is incremented. The configuration file corresponding to this business module includes the configuration information for each business sub-module.

3. The method according to claim 1, characterized in that, The step of updating the device identifier and the version information of each service module in the version information table includes: Determine whether the version information table contains a data entry corresponding to the device identifier; If there is no data entry corresponding to the device identifier, a new data entry is inserted into the version information table. This data entry includes the device identifier and the version information of each business module. Alternatively, if a data table entry corresponding to the device identifier already exists, the version information of each business module is updated in the data table entry corresponding to the device identifier.

4. The method according to claim 1, characterized in that, The configuration update request is sent by the network management device when the scheduled backup time for the entire network arrives; wherein, the scheduled backup time for the entire network refers to the time when the network management device backs up the configuration of all internal devices; Among them, all devices managed by the network management device are divided into outgoing devices and internal devices. Devices connected to the external network are outgoing devices, and devices located inside the network are internal devices. Specifically, for each device, if its uplink port is connected to the border router and its IP address belongs to the internal network segment, then the device is identified as an internal device.

5. A configuration backup device, characterized in that, Applied to export equipment, which is a device connected to an external network, the device includes: A receiving unit is configured to receive version update requests sent by internal devices, wherein the internal devices include multiple service modules, and the internal devices are devices that provide services to users or perform internal data forwarding. The version update request includes the device identifier of the internal device and the version information of each service module. The version update request is sent when the configuration of the internal device changes, resulting in an update of the version information. The device identifier and the version information of each service module are updated in the version information table. The determining unit is configured to, upon receiving a configuration update request sent by a network management device, determine a target service module based on first version information and second version information corresponding to the device identifier; wherein, the first version information includes version information of each service module recorded in the version information table, and the second version information includes version information of each service module at the time the configuration update request was last received; wherein, the version information corresponding to the target service module in the first version information and the second version information are different; The sending unit is configured to send a configuration update response to the network management device. The configuration update response includes the device identifier and the service identifier of the target service module. The configuration update response is used to enable the network management device to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

6. The apparatus according to claim 5, characterized in that, For each business module, the version information of the business module includes the version number of each business sub-module of the business module; wherein, the business module includes at least one business sub-module, and different business sub-modules are used to implement different functions; wherein, when the configuration file corresponding to the business module changes, the business sub-module whose configuration information has changed is determined by analyzing the configuration file, and the version number of the business sub-module is incremented; the configuration file corresponding to the business module includes the configuration information of each business sub-module; The configuration update request is sent by the network management device when the scheduled backup time for the entire network arrives; wherein, the scheduled backup time for the entire network refers to the time when the network management device backs up the configuration of all internal devices; wherein, all devices managed by the network management device are divided into egress devices and internal devices, devices connected to the external network are egress devices, and devices located inside the network are internal devices; Specifically, for each device, if its uplink port is connected to the border router and its IP address belongs to the internal network segment, then the device is identified as an internal device.

7. The apparatus according to claim 5, characterized in that, When the receiving unit updates the device identifier and the version information of each service module in the version information table, it is specifically used for: Determine whether the version information table contains a data entry corresponding to the device identifier; If there is no data entry corresponding to the device identifier, a new data entry is inserted into the version information table. This data entry includes the device identifier and the version information of each business module. Alternatively, if a data table entry corresponding to the device identifier already exists, the version information of each business module is updated in the data table entry corresponding to the device identifier.

8. An electronic device, characterized in that, include: A processor and a machine-readable storage medium, the machine-readable storage medium storing machine-executable instructions that can be executed by the processor; The processor is configured to execute machine-executable instructions to implement the method of any one of claims 1-4.

9. A configuration backup system, characterized in that, The system includes: An internal device is used to send a version update request to an egress device when the configuration of the internal device changes, resulting in an update and change of version information; wherein, the internal device is a device that provides services to users or performs internal data forwarding, the egress device is a device that connects to an external network, the internal device includes multiple service modules, and the version update request includes the device identifier of the internal device and the version information of each service module; The export device is used to receive the version update request and update the device identifier and the version information of each business module in the version information table based on the version update request; The network management device is used to send a configuration update request to the egress device when the scheduled backup time of the entire network arrives. The scheduled backup time of the entire network refers to the time when the configuration of all internal devices is backed up. An export device is used to receive the configuration update request, determine the target service module based on the first version information and the second version information corresponding to the device identifier, and send a configuration update response to the network management device; wherein, the first version information includes the version information of each service module recorded in the version information table, and the second version information includes the version information of each service module when the configuration update request was last received; the version information corresponding to the target service module is different in the first version information and the second version information; the configuration update response includes the device identifier and the service identifier of the target service module; The network management device is used to obtain the device identifier and the service identifier from the configuration update response, and to obtain the configuration file corresponding to the service identifier from the internal device corresponding to the device identifier.

10. The system according to claim 9, characterized in that, An internal device is used to detect at fixed intervals whether the configuration file corresponding to the business module has changed. If the configuration file corresponding to the business module has changed, the configuration file is analyzed to determine the business sub-module whose configuration information has changed, and the version number of the business sub-module is incremented. The business module includes at least one business sub-module, and different business sub-modules are used to implement different functions. The version information of the business module includes the version number of each business sub-module of the business module. The internal device includes a version structure corresponding to the business module. The version structure includes the business identifier of the business module and the version number of each business sub-module of the business module. When accumulating the version number of a business sub-module, the version number of the business sub-module is modified in the version structure.

Images