CN116708178A - Method, device, equipment, medium and product for backtracking change history of network equipment - Google Patents

Abstract

The disclosure provides a backtracking method, device, equipment, medium and product of network equipment change history, which relate to the technical field of science and technology operation and maintenance and can be applied to the technical field of finance and science, wherein the method comprises the following steps: and acquiring first configuration information and second configuration information of the network equipment, wherein the first configuration information represents the current configuration of the network equipment, and the second configuration information represents the historical configuration of the network equipment. And comparing the first configuration information with the second configuration information to obtain configuration difference information. And acquiring a plurality of pieces of change information from the historical configuration to the time period corresponding to the current configuration in the change management system. The configuration difference information is matched with a plurality of pieces of change information, and change information related to the configuration difference information is determined.

Description

Method, device, equipment, medium and product for tracing back the change history of network equipment

Technical Field

The present disclosure relates to the field of science and technology operation and maintenance technology, can be applied to the field of financial technology technology, and particularly to a method, device, equipment, medium and product for tracing back the change history of network equipment.

Background Art

In financial enterprises, especially banks, network systems need to maintain high stability at all times. Configuration changes of network equipment often need to go through a strict approval process. The reasons for the changes, operating steps, and configuration commands need to be uploaded to the change management system for approval and record. With the continuous update and iteration of business systems, business access requirements are constantly changing, and network changes (especially firewall policy changes) are often very frequent. Over time, the change system has accumulated a large amount of historical changes, making it very difficult to retrieve a certain change information from it. During internal and external audits, it is often necessary to trace back historical changes for a certain configuration. The existing backtracking method generally searches for related changes in the massive changes over the years, and checks them one by one by comparing the change implementation plans. It is very difficult to trace the source of network changes.

Summary of the invention

In view of this, the main purpose of the present disclosure is to provide a method, device, equipment, medium and product for tracing back the change history of network equipment, aiming to at least partially solve the technical problem of the difficulty of tracing the source of existing tracing methods.

To achieve the above-mentioned purpose, the first aspect of an embodiment of the present disclosure provides a method for tracing the change history of a network device, comprising: obtaining first configuration information and second configuration information of a network device, wherein the first configuration information represents the current configuration of the network device, and the second configuration information represents the historical configuration of the network device; comparing the first configuration information with the second configuration information to obtain configuration difference information; obtaining multiple change information within a time period corresponding to the historical configuration to the current configuration in a change management system; matching the configuration difference information with the multiple change information to determine the change information associated with the configuration difference information.

According to an embodiment of the present disclosure, the method of obtaining the first configuration information and the second configuration information of a network device includes: obtaining device information of a network device that needs to be monitored and configured, wherein the device information includes an IP address, a device name, and a configuration capture method; using the configuration capture method to capture the first configuration information and the second configuration information of the network device that needs to be monitored and configured; and storing the first configuration information and the second configuration information according to the capture time.

According to an embodiment of the present disclosure, the configuration capture method includes: logging into the network management system to download the first configuration information and the second configuration information of the network device; or logging into the network device and transmitting the first configuration information and the second configuration information through a file transfer protocol or a simple file transfer protocol; or; logging into the network device and entering a command to capture.

According to an embodiment of the present disclosure, the comparing the first configuration information and the second configuration information to obtain configuration difference information includes: obtaining device information of a network device that needs to be monitored and configured, wherein the device information includes an IP address, a device name, and a configuration coding format; parsing the first configuration information and the second configuration information line by line according to the configuration coding format; comparing the parsed first configuration information and the parsed second configuration information line by line, extracting the difference between the first configuration information and the second configuration information, and obtaining the configuration difference information; and storing the configuration difference information with the IP address, the device name, and the inspection time as indexes.

According to an embodiment of the present disclosure, the method also includes: inputting the configuration difference information into a web page rendering engine to generate a hypertext markup language file; adding a first tag, a second tag and a third tag in the hypertext markup language file, wherein the first tag is used to mark the currently newly added configuration, the second tag is used to mark the currently deleted configuration, and the third tag is used to mark the currently changed configuration.

According to an embodiment of the present disclosure, the method also includes: adding a first hyperlink to the first tag, adding a second hyperlink to the second tag, and adding a third hyperlink to the third tag, wherein the first hyperlink, the second hyperlink and the third hyperlink are respectively used to locate configuration information marked by corresponding tags.

According to an embodiment of the present disclosure, matching the configuration difference information with the multiple change information includes: extracting the change order number, change application user, change reason and implementation plan in each change information respectively; parsing each implementation plan one by one to determine whether each implementation plan is associated with the configuration difference information; in response to the implementation plan being associated with the configuration difference information, adding the change order number, change application user and change reason corresponding to the implementation plan to the configuration difference information.

According to an embodiment of the present disclosure, parsing each implementation scheme one by one to determine whether each implementation scheme is associated with the configuration difference information includes: using a natural language processing model to process the text content in each implementation scheme to extract the operation commands for the corresponding network device in each implementation scheme; performing vector matching on the configuration difference information and each operation command to calculate the similarity between the configuration difference information and each operation command; and determining that the implementation scheme corresponding to the similarity greater than a preset threshold is associated with the configuration difference information.

According to an embodiment of the present disclosure, the adopting of a natural language processing model to process the text content in each of the implementation schemes includes: selecting a corresponding parsing engine according to the file suffix of each implementation scheme to parse the implementation scheme.

According to an embodiment of the present disclosure, the method includes: in the case of determining that there is no change information matching the configuration difference information, sending reminder information to the terminal, wherein the reminder information is used to remind the user to manually fill in the change information.

A second aspect of an embodiment of the present disclosure provides a device for tracing the change history of a network device, comprising: a first acquisition module, used to acquire first configuration information and second configuration information of a network device, wherein the first configuration information represents a current configuration of the network device, and the second configuration information represents a historical configuration of the network device; a comparison module, used to compare the first configuration information and the second configuration information to obtain configuration difference information; a second acquisition module, used to acquire multiple change information within a time period corresponding to a historical configuration to a current configuration in a change management system; and a matching module, used to match the configuration difference information with the multiple change information to determine the change information associated with the configuration difference information.

A third aspect of an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute a backtracking method based on the above-mentioned network device change history.

A fourth aspect of an embodiment of the present disclosure provides a computer-readable storage medium, on which executable instructions are stored. When the instructions are executed by a processor, the processor executes a backtracking method based on the above-mentioned network device change history.

A fifth aspect of an embodiment of the present disclosure provides a computer program product, including a computer program, which, when executed by a processor, implements a backtracking method based on the above-mentioned network device change history.

The network device change history backtracking method, apparatus, device, medium and product provided by the embodiments of the present disclosure have at least the following beneficial effects:

By comparing the current configuration of the network device with the historical configuration to obtain configuration difference information, and then directly associating the configuration difference information with multiple change information within the corresponding time period, it is possible to quickly obtain change information of the current configuration, thereby improving the efficiency of network device change retrieval, facilitating management personnel to trace back the history of network changes, continuously improving the level of network change management, and enhancing the network stability of financial enterprises.

Based on the device information, the configuration information can be quickly obtained, thereby realizing efficient capture of the configuration information. By setting a variety of configuration information capture methods, the capture requirements in different scenarios can be met, thereby improving the flexibility of the backtracking method.

Based on the device information, the configuration encoding format of the configuration information can be quickly obtained, thereby realizing efficient parsing of the configuration information. Furthermore, the obtained configuration difference information is converted into a hypertext markup language file and different configuration difference information is marked with different tags, which can conveniently and intuitively compare the difference configurations. By setting a corresponding hyperlink for each tag, it is possible to jump to the corresponding configuration difference information by clicking the hyperlink, thereby realizing efficient query of the configuration difference information.

Since the change information is associated with the configuration difference information only by parsing the implementation plan in the change information, the amount of data involved in the association is small, thereby improving the efficiency of change history backtracking.

By calculating the similarity between the change information and the configuration difference information to determine whether the change information is associated with the configuration exception information, the configuration information associated with the configuration difference information can be accurately determined, thereby improving the accuracy of change history backtracking.

The text content in each of the implementation schemes is processed using a natural language processing model, which can be applied to implementation schemes in different formats, avoids setting different parsing templates for different modules, and improves the efficiency of historical change backtracking.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

FIG1 schematically shows a system architecture 100 of a method and apparatus for tracing back a network device change history according to an embodiment of the present disclosure;

FIG2 schematically shows a flow chart of a method for tracing back a network device change history according to an embodiment of the present disclosure;

FIG3 schematically shows a flow chart of obtaining first configuration information and second configuration information of a network device in operation S201 according to an embodiment of the present disclosure;

FIG4 schematically shows the process of three methods of capturing specific configuration information according to an embodiment of the present disclosure;

FIG5 schematically shows a flow chart of comparing the first configuration information with the second configuration information in operation S202 according to an embodiment of the present disclosure;

FIG6 schematically shows a flow chart of a method for tracing back a network device change history according to another embodiment of the present disclosure;

FIG7 schematically shows a flow chart of a method for tracing back a network device change history according to another embodiment of the present disclosure;

FIG8 schematically shows a flow chart of matching configuration difference information with multiple change information in operation S204 according to an embodiment of the present disclosure;

FIG9 schematically shows a flowchart of parsing each implementation scheme one by one to determine whether each implementation scheme is associated with configuration difference information in operation S802 according to an embodiment of the present disclosure;

FIG10 schematically shows a block diagram of a device for tracing back a change history of a network device according to an embodiment of the present disclosure;

FIG11 schematically shows a block diagram of a device for tracing back a change history of a network device according to another embodiment of the present disclosure;

FIG12 schematically shows a block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and/or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc.).

Some block diagrams and/or flow charts are shown in the accompanying drawings. It should be understood that some boxes or combinations thereof in the block diagrams and/or flow charts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data consistency repair device, so that these instructions can create a device for implementing the functions/operations described in these block diagrams and/or flow charts when executed by the processor. The technology of the present disclosure can be implemented in the form of hardware and/or software (including firmware, microcode, etc.). In addition, the technology of the present disclosure can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by an instruction execution system or used in combination with an instruction execution system.

In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision, disclosure and application of the information involved are in compliance with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and do not violate public order and good morals.

In the technical solution of the present disclosure, if it is necessary to obtain user personal information, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

In response to the technical problems existing in the related technologies, the embodiments of the present disclosure provide a method for tracing the change history of a network device, which is applied to a server, and includes: obtaining first configuration information and second configuration information of a network device, wherein the first configuration information represents the current configuration of the network device, and the second configuration information represents the historical configuration of the network device. Compare the first configuration information and the second configuration information to obtain configuration difference information. Obtain multiple change information within the time period corresponding to the historical configuration to the current configuration in the change management system. Match the configuration difference information with the multiple change information to determine the change information associated with the configuration difference information.

FIG1 schematically shows a system architecture 100 of a method and apparatus for tracing back the change history of a network device according to an embodiment of the present disclosure. It should be noted that FIG1 is only an example of a system architecture to which the embodiment of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiment of the present disclosure cannot be used in other devices, systems, environments or scenarios.

As shown in Fig. 1, the system architecture 100 according to this embodiment may include a terminal 101, a storage device 102, a network 103 and a server 104. The network 103 is used to provide a communication link between the terminal 101, the storage device 102 and the server 104.

The terminal 101 may be, for example, an electronic device with a touch screen, such as a mobile phone, a computer, or an intelligent cabinet. The user may initiate the change history tracing of the network device by clicking a corresponding function box on the touch screen or inputting a change history backtracking request. The terminal 101 may be configured with a result display unit to display the result information of the change history tracing.

The storage device 102 can be used to store various information in the change history tracing process. The storage device 102 may include, for example: a network device information storage unit, a configuration storage unit, and a configuration difference information storage unit. The network device information storage unit is used to store the network device information that needs to be monitored and configured, including the device type, IP address, device name, configuration capture method, and configuration encoding format. The configuration storage unit is used to store the configuration information of the network device. When storing, the corresponding directory can be established by date, and the daily configuration is stored in the directory corresponding to the date. The configuration difference information storage unit is used to record the configuration difference information of each network device, for example, it may include the device name, IP address, configuration difference part, inspection time, change order number, change reason, etc.

The network 103 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc. The wired mode may be, for example, a cable and any of the following interfaces: optical fiber channel, infrared interface, D-type data interface, serial interface, USB interface, USB Type-C interface or Dock interface, and the wireless mode may be, for example, a wireless communication mode, wherein the wireless communication may be, for example, any of multiple wireless technology standards such as Bluetooth, Wi-Fi, Infrared, ZigBee, etc.

The server 104 may be a server that provides various services, such as a background management server for tracing the change history of network devices (only as an example). The server 104 may, for example, be provided with a configuration capture unit, a configuration information analysis and comparison unit, a change retrieval unit, and a notification sending unit. The server 104 receives a request for tracing back the change history sent by the terminal 101 through the network 103, performs tracing back the change history of the network device according to the request for tracing back the change history, and sends the generated configuration difference information and the configuration difference information after adding the change information to the storage device 102 for storage through the network 103. In the process of executing the tracing back the change history of the network device, the configuration capture unit of the server 104 obtains the first configuration information and the second configuration information of the network device through the network 103, obtains multiple change information corresponding to the time period from the historical configuration to the current configuration in the change management system through the change retrieval unit, compares the first configuration information and the second configuration information based on the configuration information analysis and comparison unit, obtains the configuration difference information, matches the configuration difference information with the multiple change information, and determines the change information associated with the configuration difference information.

It should be noted that the method for tracing back the history of network device changes provided in the embodiment of the present disclosure can be executed by the server 104. Accordingly, the device for tracing back the history of network device changes provided in the embodiment of the present disclosure can be set in the server 104. Alternatively, the method for tracing back the history of network device changes provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 104 and can communicate with the terminal 101 and/or the server 104. Accordingly, the device for tracing back the history of network device changes provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 104 and can communicate with the terminal 101 and/or the transfer server 104. Alternatively, the method for tracing back the history of network device changes provided in the embodiment of the present disclosure can also be partially executed by the server 104 and partially executed by the terminal 101. Correspondingly, the device for tracing back the history of network device changes provided in the embodiment of the present disclosure can also be partially set in the server 104 and partially set in the terminal 101.

It should be understood that the number of terminals, storage devices, networks and servers in Figure 1 is only illustrative. Any number of terminals, storage devices, networks and servers may be provided according to implementation requirements.

The network device change history backtracking method provided by the embodiments of the present disclosure can be applied to the field of financial technology. For example, for a financial institution, a financial enterprise deploys two firewalls of a certain model as border firewalls. As the business system continues to change, network administrators need to frequently add or delete firewall policies, and all configuration adjustments are approved and recorded through the change management system. As time goes by, a large amount of firewall history changes will accumulate in the change system, and it will be very difficult to retrieve a certain change information from the change system. The network device change history backtracking method provided by the embodiments of the present disclosure improves the efficiency of network device change retrieval and facilitates administrators to quickly trace back the network change history.

It should be understood that the network device change history backtracking method provided by the embodiment of the present disclosure is not limited to the financial technology field, but can also be used in any field other than the financial field. The above description is only exemplary, and the network device change history backtracking method of the embodiment of the present disclosure can be applied to any field with network device configuration changes, such as e-commerce, product recommendation, logistics and other technical fields.

The following will describe a scenario of backtracking the change history of a network device based on FIG. 1 , and will describe in detail a method for backtracking the change history of a network device according to an embodiment of the present disclosure through FIGS. 2 to 8 .

FIG2 schematically shows a flow chart of a method for tracing back a change history of a network device according to an embodiment of the present disclosure.

As shown in FIG. 2 , the method for tracing back the change history of a network device may include, for example, operations S201 to S204 .

In operation S201, first configuration information and second configuration information of a network device are acquired.

In an embodiment of the present disclosure, the first configuration information represents the current configuration of the network device, for example, it may be the network device configuration of the day. The second configuration information represents the historical configuration of the network device, for example, it may be the network device configuration of the previous day. The first configuration information and the second configuration information may be a corresponding directory established in the configuration storage unit according to the date, and the daily configuration is stored in the directory corresponding to the date. Therefore, the first configuration information and the second configuration information may be directly obtained from the configuration storage unit. Robotic Process Automation (RPA) may be used to obtain the first configuration information and the second configuration information.

In operation S202, the first configuration information and the second configuration information are compared to obtain configuration difference information.

In an embodiment of the present disclosure, the configuration difference information may be text information, and may be stored based on the current comparison time. The configuration difference information may be understood, for example, as the routing information included in the first configuration information being inconsistent with the routing information included in the second configuration information, which is not specifically limited by the present disclosure, and the specific configuration needs to be operated according to actual application requirements.

In operation S203, a plurality of change information within a time period corresponding to the historical configuration to the current configuration in the change management system is obtained.

For example, if the current day is recorded as t, that is, the time corresponding to the current configuration is t, then the previous day can be recorded as (t-1), that is, the time corresponding to the historical configuration is (t-1). Therefore, you can log in to the change management system and retrieve the network change information from the inspection time (t-1) to the inspection time t. The method of retrieving change information is to log in to the change management system for retrieval.

In operation S204, the configuration difference information is matched with the plurality of change information to determine the change information associated with the configuration difference information.

In an embodiment of the present disclosure, among the multiple change information, there may be change information associated with the configuration difference information, or there may not be change information associated with the configuration difference information. In the case where there is change information associated with the configuration difference information, the configuration difference information and the associated change information can be stored. In the case where there is no change information associated with the configuration difference information, the matching process can be terminated.

According to the embodiments of the present disclosure, by comparing the current configuration of a network device with its historical configuration to obtain configuration difference information, and then directly associating the configuration difference information only with multiple change information within a corresponding time period, the amount of data calculation is greatly reduced. Therefore, the change information of the current configuration can be quickly obtained, thereby improving the efficiency of network device change retrieval, facilitating management personnel to trace back the history of network changes, continuously improving the level of network change management, and enhancing the network stability of financial enterprises.

FIG. 3 schematically shows a flowchart of acquiring first configuration information and second configuration information of a network device in operation S201 according to an embodiment of the present disclosure.

As shown in FIG. 3 , the acquisition of the first configuration information and the second configuration information of the network device in operation S201 may include, for example, operations S301 to S303 .

In operation S301, device information of a network device that needs to be monitored and configured is obtained.

In operation S302, a configuration capture method is used to capture first configuration information and second configuration information of a network device that needs to be monitored and configured.

In operation S303, the first configuration information and the second configuration information are stored according to the captured time.

In the embodiments of the present disclosure, the device information may include, for example, the device type, IP address, device name, configuration capture method, etc. Among them, the device type, IP address, and device name can be used to mark and distinguish network devices that need to be monitored and configured, and the configuration capture method is used to indicate the specific method of obtaining the configuration of the current network device.

Furthermore, the configuration capture method may include: logging into the network management system to download the first configuration information and the second configuration information of the network device. Alternatively, logging into the network device and transmitting the first configuration information and the second configuration information via a file transfer protocol or a simple file transfer protocol. Alternatively, logging into the network device and inputting a command to capture.

FIG. 4 schematically illustrates the processes of three specific configuration information capture methods according to an embodiment of the present disclosure.

As shown in Figure 4, for example, before grabbing the configuration, obtain the current time (such as date) and create a corresponding directory according to the date. During the grabbing process, determine whether the configuration information has been grabbed through the network management system. If the network management system has grabbed it, the first configuration information and the second configuration information can be downloaded directly from the network management system. Alternatively, send an instruction to log in to the network device, and transfer the configuration file containing the configuration information to the File Transfer Protocol (FTP) server or the Trivial File Transfer Protocol (TFTP) server to obtain the first configuration information and the second configuration information. Alternatively, send an instruction to log in to the network device and enter the show run/display current-configuration command to obtain the first configuration information and the second configuration information. After the grabbing is completed, save the grabbed first configuration information and the second configuration information to the directory created by the current date, so as to facilitate the subsequent query of the configuration information by date.

According to the embodiments of the present disclosure, based on the device information, the configuration information capture method can be quickly obtained, thereby achieving efficient capture of the configuration information. By setting a variety of configuration information capture methods, the capture requirements in different scenarios can be met, thereby improving the flexibility of the backtracking method.

FIG. 5 schematically shows a flow chart of comparing the first configuration information with the second configuration information in operation S202 according to an embodiment of the present disclosure.

As shown in FIG. 5 , comparing the first configuration information with the second configuration information in operation S202 may include operations S501 to S504 .

In operation S501, device information of a network device that needs to be monitored and configured is obtained, wherein the device information includes an IP address, a device name, and a configuration encoding format.

In operation S502, the first configuration information and the second configuration information are parsed line by line according to the configuration encoding format.

In operation S503, the parsed first configuration information and the parsed second configuration information are compared line by line, and the difference between the first configuration information and the second configuration information is extracted to obtain configuration difference information.

In operation S504, the configuration difference information is stored using the IP address, device name, and inspection time as indexes.

In the embodiment of the present disclosure, the configuration difference information obtained by comparison may be text information.

According to the embodiments of the present disclosure, the configuration encoding format of the configuration information can be quickly acquired based on the device information, thereby achieving efficient parsing of the configuration information.

FIG6 schematically shows a flow chart of a method for tracing back the change history of a network device according to another embodiment of the present disclosure.

As shown in FIG. 6 , the method for tracing back the network device change history may also include operations S601 to S602 .

In operation S601, the configuration difference information is input into a web page rendering engine to generate a hypertext markup language file.

In operation S602, a first tag, a second tag, and a third tag are added to a hypertext markup language file.

In an embodiment of the present disclosure, the first tag is used to mark the currently newly added configuration, the second tag is used to mark the currently deleted configuration, and the third tag is used to mark the currently changed configuration.

For example, the current configuration and the previous configuration are input into the web rendering engine to generate a Hypertext Markup Language (HTML) file that records the two configurations and the difference comparison. The configuration differences are marked with different colors in the HTML. The newly added configuration on the day is marked in green, the deleted configuration on the day is marked in red, and the changed configuration on the day is marked in yellow. The HTML file is also stored in the difference information recording unit.

FIG7 schematically shows a flow chart of a method for tracing back the change history of a network device according to yet another embodiment of the present disclosure.

As shown in FIG. 7 , the method for tracing back the change history of a network device may further include operation S701 , for example.

In operation S701, a first hyperlink is added to a first tag, a second hyperlink is added to a second tag, and a third hyperlink is added to a third tag.

In the embodiment of the present disclosure, the first hyperlink, the second hyperlink and the third hyperlink are respectively used to locate the configuration information marked by the corresponding tag. That is, the first hyperlink can be used to locate the currently added configuration, the second hyperlink can be used to locate the currently deleted configuration, and the third hyperlink can be used to locate the currently modified configuration.

The following uses the Python difflib module as an example to give a specific example:

Based on this example, the current check time is April 20, 2023, therefore, the first configuration information on April 20, 2023 and the second configuration information on April 19, 2023 are obtained for matching. It should be understood that this example is only a specific example and is not intended to limit the present disclosure.

According to the embodiments of the present disclosure, the acquired configuration difference information is converted into a hypertext markup language file and different configuration difference information is marked with different tags, so that the difference configurations can be easily and intuitively compared. By setting a corresponding hyperlink for each tag, it is possible to jump to the corresponding configuration difference information by clicking the hyperlink, thereby realizing efficient query of the configuration difference information.

FIG. 8 schematically shows a flow chart of matching configuration difference information with multiple change information in operation S204 according to an embodiment of the present disclosure.

As shown in FIG. 8 , matching the configuration difference information with the multiple change information in operation S204 may include operations S801 to S803 , for example.

In operation S801, the change order number, change application user, change reason and implementation plan in each change information are extracted respectively.

In operation S802, each implementation scheme is parsed one by one to determine whether each implementation scheme is associated with configuration difference information.

In operation S803, in response to the implementation plan being associated with the configuration difference information, the change order number, change application user, and change reason corresponding to the implementation plan are added to the configuration difference information.

In the embodiments of the present disclosure, a corresponding parsing engine can be selected according to the file suffix of each implementation scheme to parse the implementation scheme. The file suffix can be, for example, txt/doc/xls. Thus, the parsing method of the implementation scheme can be quickly determined based on the file suffix.

According to the embodiments of the present disclosure, since the change information is associated with the configuration difference information only by parsing the implementation scheme in the change information, the amount of data involved in the association is small, thereby improving the efficiency of change history backtracking.

FIG. 9 schematically shows a flowchart of parsing each implementation scheme one by one to determine whether each implementation scheme is associated with configuration difference information in operation S802 according to an embodiment of the present disclosure.

As shown in FIG. 9 , in operation S802 , parsing each implementation scheme one by one to determine whether each implementation scheme is associated with configuration difference information may include, for example, operations S901 to S903 .

In operation S901, a natural language processing model is used to process the text content in each implementation scheme to extract operation commands for corresponding network devices in each implementation scheme.

In operation S902, vector matching is performed between the configuration difference information and each operation command to calculate the similarity between the configuration difference information and each operation command.

In operation S903 , it is determined that the implementation scheme corresponding to the similarity greater than a preset threshold is associated with the configuration difference information.

In the embodiments of the present disclosure, since different implementation users write implementation plans in different formats, setting a corresponding parsing engine for each implementation plan format will make the operation complicated and reduce the efficiency of tracing back the history of network device changes. Therefore, a natural language processing model can be used to process the text content in the implementation plan to extract the operation commands for the network device in the implementation plan. For example, the format of a certain implementation plan is shown in Table 1:

Table 1

When parsing, it is only necessary to extract the contents contained in the section "VII. Change Implementation Steps". It should be understood that the arrangement format of the implementation plan in Table 1 is only exemplary and can be adjusted according to the actual application scenario, and this disclosure does not limit it.

Furthermore, the extracted configuration difference information and the operation command in the implementation scheme can both be in text form, and vector matching can be performed on the two texts to calculate the similarity of the two texts. For example, taking the python difflib module as an example, the vector matching process can be:

It should be understood that this example is only a specific example and is not intended to limit the present disclosure.

Since a change plan may involve the operation of multiple network devices, or multiple changes may be made to configure the same network device, it is possible to determine whether the configuration difference information is associated with the change information by setting a comparison threshold. For example, the comparison threshold can be set to 0.3 and 0.03. When the similarity x of the two texts is greater than or equal to 0.3, it can be considered that the change information is associated with the current network device configuration change; when the similarity x of the two texts is greater than or equal to 0.03 and less than 0.3, an inquiry message can be sent to the administrator to confirm whether the change information is associated with the current network device configuration change; when the similarity x of the two texts is less than 0.03, it is considered that the change information is not associated with the current network device configuration change.

According to an embodiment of the present disclosure, by calculating the similarity between the change information and the configuration difference information to determine whether the change information is associated with the configuration exception information, the configuration information associated with the configuration difference information can be accurately determined, thereby improving the accuracy of change history backtracking.

Furthermore, when it is determined that there is no change information matching the configuration difference information, a reminder message is sent to the terminal, wherein the reminder message is used to remind the user to manually fill in the change information.

For example, the reminder method may be an email, a text message, etc. Manually filling in the change information may include, for example, the change order number and the change reason.

Based on the above embodiment, the configuration difference information can also be displayed in a Web manner. The displayed content includes the device name, configuration difference information (text form), change order number, change reason, inspection time, and the management personnel can use the search function to quickly retrieve the relevant information of a certain configuration, including the configuration addition date, change order number, change reason, etc., and can jump to the corresponding HTML page by clicking a hyperlink. The configuration addition, modification and deletion are marked with different colors on the HTML page, which makes it easy to intuitively compare the difference configurations.

To sum up, the network device change history backtracking method provided by the present embodiment can improve the efficiency of network device change retrieval, facilitate management personnel to backtrack network change history, continuously improve the level of network change management, and enhance the network stability of financial enterprises.

Based on the network device change history backtracing method shown in Figures 2 to 9, the embodiment of the present disclosure also provides a network device change history backtracing device. The following will describe the network device change history backtracing device of the embodiment of the present disclosure through Figures 10 to 11 based on the scenario described in Figure 1.

FIG10 schematically shows a block diagram of a device for tracing back a change history of a network device according to an embodiment of the present disclosure.

As shown in FIG. 10 , the apparatus 1000 for tracing back the change history of a network device may include a first acquisition module 1010 , a comparison module 1020 , a second acquisition module 1030 , and a matching module 1040 .

The first acquisition module 1010 is used to acquire first configuration information and second configuration information of the network device, wherein the first configuration information represents the current configuration of the network device and the second configuration information represents the historical configuration of the network device. The first acquisition module 1010 can be used to perform the operation S201 described above, which will not be repeated here.

The comparison module 1020 is used to compare the first configuration information with the second configuration information to obtain configuration difference information. The comparison module 1020 can be used to perform the operation S202 described above, which will not be described in detail here.

The second acquisition module 1030 acquires multiple change information in the change management system within a time period corresponding to the historical configuration to the current configuration. The second acquisition module 1030 can be used to perform the operation S203 described above, which will not be described in detail here.

The matching module 1040 is used to match the configuration difference information with the multiple change information to determine the change information associated with the configuration difference information. The matching module 1040 can be used to perform the operation S204 described above, which will not be described in detail here.

FIG11 schematically shows a block diagram of a device for tracing back a change history of a network device according to another embodiment of the present disclosure.

As shown in FIG. 11 , the apparatus 1000 for tracing back the change history of a network device may further include, for example, a generating module 1050 , a first adding module 1060 , and a second adding module 1070 .

The generation module 1050 is used to input the configuration difference information into the web page rendering engine to generate a hypertext markup language file. The generation module 1050 can be used to perform the operation S601 described above, which will not be described in detail here.

The first adding module 1060 adds a first tag, a second tag, and a third tag to the hypertext markup language file. The first tag is used to mark the currently newly added configuration, the second tag is used to mark the currently deleted configuration, and the third tag is used to mark the currently changed configuration. The first adding module 1060 can be used to perform the operation S602 described above, which will not be repeated here.

The second adding module 1070 adds a first hyperlink to the first tag, adds a second hyperlink to the second tag, and adds a third hyperlink to the third tag. The first hyperlink, the second hyperlink, and the third hyperlink are respectively used to locate the configuration information marked by the corresponding tags. The second adding module 1070 can be used to perform the operation S701 described above, which will not be repeated here.

According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

For example, any multiple of the first acquisition module 1010, the comparison module 1020, the second acquisition module 1030, the matching module 1040, the generation module 1050, the first addition module 1060, and the second addition module 1070 can be combined in one module/unit/sub-unit for implementation, or any one of the modules/units/sub-units can be split into multiple modules/units/sub-units. Alternatively, at least part of the functions of one or more of these modules/units/sub-units can be combined with at least part of the functions of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the first acquisition module 1010, the comparison module 1020, the second acquisition module 1030, the matching module 1040, the generation module 1050, the first addition module 1060, and the second addition module 1070 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware, and firmware, or by a proper combination of any of them. Alternatively, at least one of the first acquisition module 1010, the comparison module 1020, the second acquisition module 1030, the matching module 1040, the generation module 1050, the first addition module 1060, and the second addition module 1070 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

It should be noted that the network device change history backtracking device part in the embodiment of the present disclosure corresponds to the network device change history backtracking method part in the embodiment of the present disclosure, and their specific implementation details and technical effects are also the same, which will not be repeated here.

Fig. 12 schematically shows a block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present disclosure. The electronic device shown in Fig. 12 is only an example and should not bring any limitation to the functions and scope of use of the embodiment of the present disclosure.

As shown in FIG12 , the electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage portion 1208 into a random access memory (RAM) 1203. The processor 1201 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and/or a related chipset and/or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), and the like. The processor 1201 may also include an onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

In RAM 1203, various programs and data required for the operation of electronic device 1200 are stored. Processor 1201, ROM 1202 and RAM 1203 are connected to each other through bus 1204. Processor 1201 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1202 and/or RAM 1203. It should be noted that the program can also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 1200 may further include an input/output (I/O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may further include one or more of the following components connected to the I/O interface 1205: an input portion 1206 including a keyboard, a mouse, etc.; an output portion 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1208 including a hard disk, etc.; and a communication portion 1209 including a network interface card such as a LAN card, a modem, etc. The communication portion 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed, so that a computer program read therefrom is installed into the storage portion 1208 as needed.

According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and/or installed from the removable medium 1211. When the computer program is executed by the processor 1201, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

The present disclosure also provides a computer-readable storage medium, which may be included in the device/apparatus/system described in the above embodiments; or may exist independently without being assembled into the device/apparatus/system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 1202 and/or the RAM 1203 described above and/or one or more memories other than the ROM 1202 and the RAM 1203 .

The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments and/or claims of the present disclosure can be combined and/or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teaching of the present disclosure, the features described in the various embodiments and/or claims of the present disclosure may be combined and/or combined in a variety of ways. All of these combinations and/or combinations fall within the scope of the present disclosure.

Claims (14)

1. A method for backtracking the change history of network equipment, applied to the server, including: Acquiring first configuration information and second configuration information of a network device, wherein the first configuration information represents a current configuration of the network device, and the second configuration information represents a historical configuration of the network device; Comparing the first configuration information with the second configuration information to obtain configuration difference information; Obtain multiple change information in the time period from the historical configuration to the current configuration in the change management system; Matching the configuration difference information with the plurality of change information to determine change information associated with the configuration difference information. 2. The retrospective method of network device change history according to claim 1, wherein said obtaining the first configuration information and the second configuration information of the network device comprises: Obtaining device information of a network device that needs to be monitored and configured, wherein the device information includes an IP address, a device name, and a configuration grabbing method; Grabbing the first configuration information and the second configuration information of the network device that needs to be monitored and configured by using the configuration grabbing method; The first configuration information and the second configuration information are stored according to the captured time. 3. The retrospective method of network device change history according to claim 2, wherein the configuration capture method comprises: Log in to a network management system to download the first configuration information and the second configuration information of the network device; or log into the network device, and transmit the first configuration information and the second configuration information through a file transfer protocol or a simple file transfer protocol; or; Log in to the network device and input commands to grab. 4. The retrospective method of network device change history according to claim 1, wherein said comparing said first configuration information with said second configuration information to obtain configuration difference information comprises: Obtaining device information of network devices that need to be monitored and configured, wherein the device information includes IP addresses, device names and configuration encoding formats; Analyzing the first configuration information and the second configuration information line by line according to the configuration encoding format; comparing the parsed first configuration information and the parsed second configuration information line by line, extracting the difference between the first configuration information and the second configuration information, and obtaining the configuration difference information ; The configuration difference information is stored using the IP address, the device name, and the checking time as indexes. 5. The retrospective method of the network equipment change history according to claim 4, said method further comprising: Inputting the configuration difference information into a web page rendering engine to generate a hypertext markup language file; Add a first tag, a second tag, and a third tag in the hypertext markup language file, wherein the first tag is used to mark the currently added configuration, and the second tag is used to mark the currently deleted configuration , the third label is used to mark the currently changed configuration. 6. The retrospective method of the network equipment change history according to claim 5, said method further comprising: Add a first hyperlink to the first label, add a second hyperlink to the second label, and add a third hyperlink to the third label, wherein the first hyperlink, the second hyperlink The link and the third hyperlink are respectively used to locate the configuration information marked by the corresponding label. 7. The retrospective method for network device change history according to claim 1, wherein said matching said configuration difference information with said plurality of change information comprises: Separately extract the change order number, change application user, change reason and implementation plan in each change information; Analyzing each implementation scheme one by one, and determining whether each implementation scheme is associated with the configuration difference information; In response to the association between the implementation solution and the configuration difference information, add the change order number, change application user, and change reason corresponding to the implementation solution to the configuration difference information. 8. The retrospective method of network device change history according to claim 7, wherein said parsing each implementation scheme one by one, and determining whether each implementation scheme is associated with the configuration difference information comprises: Using a natural language processing model to process the text content in each of the implementations, so as to extract the operation commands for the corresponding network devices in each of the implementations; performing vector matching on the configuration difference information and each of the operation commands to calculate the similarity between the configuration difference information and each of the operation commands; It is determined that implementations corresponding to a similarity greater than a preset threshold are associated with the configuration difference information. 9. The retrospective method of network device change history according to claim 8, wherein said respectively adopting a natural language processing model to process the text content in each of said embodiments comprises: According to the file suffix of each implementation, a corresponding analysis engine is selected to analyze the implementation. 10. The retrospective method of the network equipment change history according to claim 1, said method comprising: When it is determined that there is no change information matching the configuration difference information, a reminder message is sent to the terminal, wherein the reminder message is used to remind the user to manually fill in the change information. 11. A retrospective device for changing history of network equipment, comprising: A first acquiring module, configured to acquire first configuration information and second configuration information of a network device, wherein the first configuration information represents a current configuration of the network device, and the second configuration information represents a configuration of the network device historical configuration; A comparing module, configured to compare the first configuration information with the second configuration information to obtain configuration difference information; The second obtaining module is used to obtain a plurality of change information in the time period corresponding to the historical configuration to the current configuration in the change management system; A matching module, configured to match the configuration difference information with the plurality of change information, and determine change information associated with the configuration difference information. 12. An electronic device comprising: one or more processors; storage means for storing one or more programs, Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are made to execute the method according to any one of claims 1-10. 13. A computer-readable storage medium, wherein executable instructions are stored on the computer-readable storage medium, and when the instructions are executed by a processor, the processor executes the method according to any one of claims 1-10. 14. A computer program product comprising a computer program, the computer program implementing the method according to any one of claims 1-10 when executed by a processor.