Network management method and communication device

Abstract

The invention provides a network management method and a communication device, and is applied to the technical field of network communication. The network management method is applied to a management device, and the management device determines a dumb device in a target network and generates virtual configuration information of the dumb device according to configuration information of neighbor devices of the dumb device in the target network. Wherein the dummy device is a network device which does not support the management device to analyze the configuration information in the target network. Based on the scheme, for the dummy equipment which does not support configuration information analysis in the target network, the management device can generate the virtual configuration information of the dummy equipment according to the configuration information of the neighbor equipment of the dummy equipment, so that the management device can correctly manage network equipment and links in the target network.

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a network management method and a communication device. Background Art

[0002] Network management technology is a technology that automatically manages the target network through a network management device. The network management device can collect information about the devices in the target network it manages, and then implement management functions such as network operation status monitoring, network communication performance analysis, network route publishing, and network path restoration based on the collected information.

[0003] However, the premise for realizing the above management function of the target network is that the network management device successfully parses the information collected from the devices in the target network. In actual scenarios, since the types, manufacturers, and configuration protocols of the devices in the network may be diverse, the network management device may not be able to parse the information of some devices, which in turn causes the network management device to be unable to correctly realize the management function of the target network. Summary of the invention

[0004] The present application provides a network management method and a communication device, which can generate virtual configuration information of a dumb device in a target network that does not support parsing configuration information by a management device, so that the management device can correctly manage the target network based on the virtual configuration information of the dumb device.

[0005] In a first aspect, a network management method is provided, which can be executed by a management device, or by a component of the management device, such as a processor, a chip, or a chip system of the management device, or by a logic module or software that can implement all or part of the functions of the management device. The method may include: determining a dumb device in a target network, and generating virtual configuration information of the dumb device based on configuration information of a neighboring device of the dumb device in the target network. The dumb device is a network device in the target network that does not support parsing of configuration information by the management device.

[0006] Based on this solution, for dumb devices in the target network that do not support parsing configuration information, the management device can generate virtual configuration information for the dumb devices based on the configuration information of their neighbor devices, so that the management device can correctly manage network devices and links in the target network.

[0007] In combination with the above-mentioned first aspect, as a possible implementation method, the configuration information of the neighbor device includes multiple first physical interfaces connected between the neighbor device and the dumb device and multiple first logical interfaces bound to the multiple first physical interfaces. Determining the virtual configuration information of the dumb device based on the configuration information of the neighbor device of the dumb device may include: determining multiple second physical interfaces of the dumb device based on the multiple first physical interfaces, and the multiple second physical interfaces are connected to the multiple first physical interfaces in a one-to-one correspondence. And, determining the second logical interface bound to the second physical interface connected to any first physical interface based on the first logical interface bound to any first physical interface among the multiple first physical interfaces. The second logical interface bound to the second physical interface connected to any first physical interface corresponds to the same VLAN as the first logical interface bound to any first physical interface. The virtual configuration information of the dumb device includes multiple second physical interfaces and multiple second logical interfaces bound to the multiple second physical interfaces.

[0008] Based on this solution, the management device can generate a physical interface connecting the dumb device to the neighboring device and a logical interface bound to the physical interface, so that the virtual configuration information of the dumb device can reflect the connection relationship between the dumb device and the neighboring device.

[0009] In combination with the first aspect above, as a possible implementation method, determining the virtual configuration information of the dumb device according to the configuration information of the neighbor device of the dumb device may also include: determining the virtual forwarding instance of the dumb device when any two first logical interfaces among multiple first logical interfaces are interconnected. The virtual forwarding instance of the dumb device has an inter-access relationship with the virtual forwarding instance bound to any two first logical interfaces, the virtual forwarding instance of the dumb device is bound to two second logical interfaces corresponding to any two first logical interfaces, and the two second physical interfaces bound to the two second logical interfaces are connected to the two first physical interfaces bound to any two first logical interfaces. The virtual configuration information of the dumb device includes the virtual forwarding instance of the dumb device.

[0010] Based on this solution, the management device can also generate a virtual forwarding instance of the dumb device and bind the virtual forwarding instance to the interface of the dumb device. Thus, the virtual configuration information of the dumb device can reflect the intercommunication relationship between the interfaces of the dumb device and the neighboring devices.

[0011] In combination with the first aspect above, as a possible implementation, the configuration information of the neighbor device also includes IP addresses of multiple first logical interfaces. The method also includes: if the IP addresses of any two first logical interfaces belong to the same network segment, determining that any two first logical interfaces are interconnected at layer 2.

[0012] In combination with the above-mentioned first aspect, as a possible implementation method, the configuration information of the neighboring device also includes Internet Protocol IP addresses of multiple first logical interfaces. The routing information of the neighboring device includes multiple routing entries, each routing entry includes a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface. The method also includes: if the IP addresses of any two first logical interfaces belong to different network segments, one of the any two first logical interfaces is the routing output interface of the first routing entry in the multiple routing entries, the network segment identified by the routing prefix of the second routing entry in the multiple routing entries includes the network segment identified by the routing prefix of the first routing entry, and another first logical interface is bound to the virtual forwarding instance of the second routing entry, then it is determined that any two first logical interfaces are interconnected at Layer 3.

[0013] In combination with the above-mentioned first aspect, as a possible implementation method, the method may also include: generating a network entity relationship diagram based on the virtual configuration information and the configuration information of at least one neighbor device, the network entity relationship diagram including the identifier of the dumb device in the virtual configuration information, the virtual forwarding instance of the dumb device, the association relationship between multiple second physical interfaces and multiple second logical interfaces, and the identifier of at least one neighbor device in the configuration information of at least one neighbor device, multiple first physical interfaces, multiple first logical interfaces and the association relationship between the virtual forwarding instances bound to the multiple first logical interfaces, as well as the association relationship between the interfaces connected to the dumb device and the neighbor device.

[0014] In combination with the above-mentioned first aspect, as a possible implementation method, the method may also include: obtaining the source IP address and the destination IP address of the network path to be restored. Using the source IP address as the starting point, search for the network path to the destination IP address, and search for the first neighbor device to the dumb device. There is a routing prefix matching the destination IP address in the routing information of the first neighbor device, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is a dumb device. Search the network entity relationship diagram starting from the first neighbor device to determine the forwarding path from the first neighbor device to the second neighbor device. There is a routing prefix matching the destination IP address in the routing information of the second neighbor device, and the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not a dumb device. The dumb device is a relay device on the forwarding path from the first neighbor device to the second neighbor device. Determine the network path to be restored based on the forwarding path from the first neighbor device to the second neighbor device.

[0015] Based on this solution, the management device can restore the forwarding path through the dumb device based on the network entity relationship diagram generated by the virtual configuration information of the dumb device, thereby enabling the routing restoration function of the management device to be correctly implemented.

[0016] In combination with the first aspect above, as a possible implementation, determining a dumb device in a target network may include: obtaining first device information, where the first device information is information about a network device included in the target network. Obtaining second device information, where the second device information is information about a network device that supports parsing configuration information by a management device. Based on the first network device information and the second network device information, determining a network device in the target network that does not support parsing configuration information by a management device as a dumb device in the target network.

[0017] In a second aspect, an embodiment of the present application provides a communication device, which can implement the functions performed by a management device in any possible design of the first aspect above, and the functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the device may include: a processing module. Among them, the processing module is used to determine a dumb device in a target network, and generate virtual configuration information of the dumb device based on the configuration information of a neighbor device of the dumb device in the target network. A dumb device is a network device in the target network that does not support the management device to parse the configuration information.

[0018] In combination with the above-mentioned second aspect, as a possible implementation method, the configuration information of the neighbor device includes multiple first physical interfaces connecting the neighbor device to the dumb device and multiple first logical interfaces bound to the multiple first physical interfaces. The processing module is used to determine multiple second physical interfaces of the dumb device based on the multiple first physical interfaces, and determine the second logical interface bound to the second physical interface connected to any first physical interface based on the first logical interface bound to any first physical interface among the multiple first physical interfaces. The virtual configuration information of the dumb device includes multiple second physical interfaces and multiple second logical interfaces bound to the multiple second physical interfaces. Among them, the multiple second physical interfaces are connected to the multiple first physical interfaces in a one-to-one correspondence. The second logical interface bound to the second physical interface connected to any first physical interface corresponds to the same VLAN as the first logical interface bound to any first physical interface.

[0019] In combination with the above-mentioned second aspect, as a possible implementation method, the processing module is also used to determine the virtual forwarding instance of the dumb device when any two first logical interfaces among multiple first logical interfaces are interconnected. The virtual configuration information of the dumb device includes the virtual forwarding instance of the dumb device. Among them, the virtual forwarding instance of the dumb device has an inter-access relationship with the virtual forwarding instance bound to any two first logical interfaces, the virtual forwarding instance of the dumb device is bound to two second logical interfaces corresponding to any two first logical interfaces, and the two second physical interfaces bound to the two second logical interfaces are connected to the two first physical interfaces bound to any two first logical interfaces.

[0020] In conjunction with the above second aspect, as a possible implementation, the configuration information of the neighbor device also includes the IP addresses of multiple first logical interfaces. The processing module is also used to determine that any two first logical interfaces are interconnected at layer 2 when the IP addresses of any two first logical interfaces belong to the same network segment.

[0021] In combination with the above-mentioned second aspect, as a possible implementation method, the configuration information of the neighboring device also includes Internet Protocol IP addresses of multiple first logical interfaces. The routing information of the neighboring device includes multiple routing entries, each routing entry includes a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface. The processing module is also used to determine that any two first logical interfaces are interconnected at the third layer when the IP addresses of any two first logical interfaces belong to different network segments, one of the first logical interfaces of any two first logical interfaces is the routing output interface of the first routing entry in the multiple routing entries, the network segment identified by the routing prefix of the second routing entry in the multiple routing entries includes the network segment identified by the routing prefix of the first routing entry, and the other first logical interface is bound to the virtual forwarding instance of the second routing entry.

[0022] In combination with the above-mentioned second aspect, as a possible implementation method, the processing module is also used to generate a network entity relationship diagram based on the virtual configuration information and the configuration information of at least one neighbor device, the network entity relationship diagram including the identifier of the dumb device in the virtual configuration information, the virtual forwarding instance of the dumb device, the association relationship between multiple second physical interfaces and multiple second logical interfaces, and the identifier of at least one neighbor device in the configuration information of at least one neighbor device, multiple first physical interfaces, multiple first logical interfaces and the association relationship between the virtual forwarding instances bound to the multiple first logical interfaces, as well as the association relationship between the interfaces connected to the dumb device and the neighbor device.

[0023] In combination with the above-mentioned second aspect, as a possible implementation method, the communication device also includes a transceiver module. The transceiver module is used to obtain the source IP address and the destination IP address of the network path to be restored. The processing module is also used to find the network path to the destination IP address with the source IP address as the starting point, and find the first neighbor device to the dumb device. In addition, the processing module is also used to search the network entity relationship diagram with the first neighbor device as the starting point to determine the forwarding path from the first neighbor device to the second neighbor device. Furthermore, the processing module is also used to determine the network path to be restored based on the forwarding path from the first neighbor device to the second neighbor device. Among them, there is a routing prefix matching the destination IP address in the routing information of the first neighbor device, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is a dumb device. There is a routing prefix matching the destination IP address in the routing information of the second neighbor device, and the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not a dumb device. The dumb device is a relay device on the forwarding path from the first neighbor device to the second neighbor device.

[0024] In conjunction with the above second aspect, as a possible implementation, the communication device further includes a transceiver module. The transceiver module is used to obtain first device information and second device information, the first device information being information about network devices included in the target network, and the second device information being information about network devices that support the management device to parse configuration information. The processing module is also used to determine, based on the first network device information and the second network device information, network devices in the target network that do not support the management device to parse configuration information as dumb devices in the target network.

[0025] In a third aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to enable the device to perform a network management method as described in any one of the first aspects above.

[0026] In conjunction with the third aspect, in a possible implementation, the device further includes a communication interface; the communication interface is used for the device to communicate with other devices. Exemplarily, the communication interface can be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.

[0027] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is executed on a computer, the computer can execute the network management method described in any one of the first aspects.

[0028] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the network management method described in any one of the first aspects.

[0029] Among them, the technical effects brought about by any design method in the second to fifth aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic diagram of the structure of a communication network provided in an embodiment of the present application;

[0031] Figure 2 A schematic diagram of the structure of another communication network provided in an embodiment of the present application;

[0032] Figure 3 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0033] Figure 4 A flowchart of a network management method provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of the structure of a network entity relationship diagram provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of the structure of another network entity relationship diagram provided in an embodiment of the present application;

[0036] Figure 7 A schematic diagram of the structure of another network entity relationship diagram provided in an embodiment of the present application;

[0037] Figure 8 A schematic diagram of the structure of another network entity relationship diagram provided in an embodiment of the present application;

[0038] Fig. 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0039] Fig.10 A schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with basically the same functions and effects. It can be understood by those skilled in the art that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit them to be necessarily different. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way for easy understanding. In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It can be known to those of ordinary skill in the art that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0041] The management device can collect the configuration information and routing information of the network devices in the communication network it manages, and then implement the management function of the communication network based on the configuration information and routing information. If there are network devices in the communication network that are incompatible with the management device, and the management device cannot parse the information of the incompatible network device, then the management device will not be able to correctly implement the management function of the communication network. Network management includes, for example, network path restoration, network operation status monitoring, network performance analysis, etc. The following is an illustrative explanation using network management as an example of network path restoration. Network path restoration is an important technology in intelligent network operation and maintenance. This technology can intuitively present information such as network devices and interfaces that data flows pass through in the network to users, thereby improving user experience.

[0042] Below first Figure 1 and Figure 2 The two communication networks shown are used as examples to illustrate the problems in the current implementation of the network path restoration function.

[0043] Figure 1 A schematic diagram of the structure of a communication network is shown in FIG. Figure 1 As shown, the communication network may include: leaf switches {leaf 1, leaf 2, leaf 3, leaf 4}, spine switch {spine 1}, border leaf switch {border leaf 1}, intrusion prevention system (IPS) device {IPS-1}, and firewall (FW) device {FW-1}. Among them, leaf 1, leaf 2, leaf 3 and leaf 4 are all connected to spine 1, spine 1 is connected to border leaf 1, border leaf 1 is connected to IPS-1, border leaf 1 is also connected to FW-1, and IPS-1 is connected to FW-1.

[0044] Among them, spine switches, leaf switches, and border leaf switches are switches with different roles in the leaf-spine architecture. The spine-leaf architecture is widely used in communication networks due to its high scalability, high reliability, and high performance. The leaf-spine architecture includes the spine layer and the leaf layer. The spine layer includes spine switches for routing and forwarding, and the leaf layer includes leaf switches for connecting servers and storage devices. Each leaf switch needs to be connected to the spine switch. The border leaf switch is a special leaf switch that is used to connect to external routers and provide external traffic access functions.

[0045] for Figure 1For the communication network shown, assuming that the management device is incompatible with IPS-1 (or in other words, IPS-1 does not support management), and the management device cannot parse the information collected from IPS-1 (for example, configuration information), then the network path for the data flow between FW-1 and boundary leaf 1 may not be restored or restored incorrectly. For example, the actual network path for the data flow from boundary leaf 1 to FW-1 may be: boundary leaf 1→IPS-1→FW-1. When the network management device performs network path restoration, it cannot restore the actual network path for the data flow from boundary leaf 1 to FW-1 because it cannot parse the configuration information of IPS-1. If the network management device performs shortest path restoration based on the topology structure, the restored network path for the data flow from boundary leaf 1 to FW-1 is: boundary leaf 1→FW1, and the restored path is not the actual network path from boundary leaf 1 to FW-1.

[0046] Figure 2 is a schematic diagram of the structure of another communication network, such as Figure 2 As shown, the communication network may include: leaf switches {leaf 1, leaf 2, leaf 3, leaf 4}, spine switch {spine 1}, border leaf switch {border leaf 1}, firewall device {FW-1}, and core network (core) device {core 1}. Among them, leaf 1, leaf 2, leaf 3 and leaf 4 are all connected to spine 1, spine 1 is also connected to border leaf 1, border leaf 1 is also connected to core 1, and border leaf 1 is also connected to FW-1.

[0047] for Figure 2 In the communication network shown, assuming that the network management device is incompatible with FW-1 (or, FW-1 does not support management), and the management device cannot parse the information collected from FW-1 (for example, configuration information), then the network path for the data flow to be transmitted between core 1 and border leaf 1 may not be restored or restored incorrectly. For example, the real network path for the data flow to be transmitted from border leaf 1 to core 1 can be: border leaf 1→FW-1→border leaf 1→core 1. In other words, border leaf 1 can first send the data flow to FW-1, and then receive the filtered data flow from FW-1, and then border leaf 1 forwards the filtered data flow from FW-1 to core 1. When the network management device performs network path restoration, it cannot parse the configuration information of FW-1, so it cannot restore the real network path for the data flow to be transmitted from border leaf 1 to core 1. If the network management device performs the shortest path restoration based on the topology structure, the restored network path for the data flow from border leaf 1 to core 1 is: border leaf 1→core 1, and the restored path is not the real network path from border leaf 1 to core 1.

[0048] In one implementation, the network management device can reduce the occurrence of devices that do not support management by expanding the adaptation to various vendors and various types of network devices. However, the vendors and types of network devices in the communication network managed by the network management device are unpredictable, and it is inevitable that there will be network devices in the communication network that do not support management by the network management device.

[0049] Another implementation method is to allow the network management device to correctly perform the corresponding functions by having technicians manually input information about network devices that do not support management. However, this method is labor-intensive and difficult to implement. In addition, the timeliness of manually importing network device information is poor and cannot cope with dynamic changes in the network.

[0050] In view of this, an embodiment of the present application provides a network management method, which can obtain virtual configuration information of a dumb device based on the configuration information of a neighbor device of a device that does not support management (hereinafter referred to as a dumb device), so that a network management device can normally perform network management functions. Taking the network path restoration function as an example, the virtual configuration information of the dumb device can correctly reflect the intercommunication relationship between the neighbor device and the dumb device, so that the network management device can correctly perform network path restoration based on the virtual configuration information of the dumb device.

[0051] Before introducing the network management method provided in the embodiment of the present application, the communication system / business scenario to which the network management method of the present application is applied is first introduced.

[0052] Figure 3 A schematic diagram of the structure of a communication system provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the management device can be connected to the target network, and the management device can obtain the information reported by the network devices in the target network. For the network devices in the target network that do not support the management device to parse the configuration information (hereinafter referred to as dumb devices), the management device can generate virtual configuration information of the dumb devices based on the configuration information of the neighboring devices of the dumb devices. For the specific implementation, please refer to the network management method below, which will not be described in detail here.

[0053] Alternatively, if Figure 3 As shown, the management device can also connect to the user device to obtain the source and destination information input by the user device, and then restore the network path from the source to the destination in the target network. The specific implementation can refer to the network management method below, which will not be described in detail here. In addition, the management device can also feed back the restored network path to the user device.

[0054] Optionally, Figure 3 The network devices in the target network may be switches, routers, firewalls, load balancing devices, etc., which are not limited in this application. For example, Figure 3The target network in can be Figure 1 or Figure 2 The communication network shown.

[0055] Optionally, Figure 3 The information reported by the device in the target network may include device information, link information, logical interface configuration information, routing information, etc., which is not limited in this application.

[0056] It should be understood that the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0057] The following will be combined Figure 3 The communication system shown describes the network management method provided by the embodiment of the present application. The actions, terms, etc. involved in the various embodiments of the present application can refer to each other without limitation. The message name or parameter name in the message in the embodiment of the present application is only an example, and other names can also be used in the specific implementation without limitation.

[0058] Figure 4 A flow chart of a network management method provided in an embodiment of the present application is as follows: Figure 4 As shown, the method may include the following steps:

[0059] Step 401: The management device determines a dumb device in a target network. The dumb device is a network device in the target network that does not support the management device to parse configuration information.

[0060] Optionally, step 401 may specifically include:

[0061] Step 4011: The management device obtains first device information, where the first device information is device information of a network device included in the target network.

[0062] As an implementation manner, the device information of each network device in the first device information may include information such as a device identification, a device type, and a device manufacturer of each network device.

[0063] For example, the target network is Figure 1 Taking the communication network shown in FIG. 1 as an example, the first device information acquired by the management device may be as shown in Table 1:

[0064] Table 1

[0065] Equipment identification Device Type Equipment Manufacturer FW-1 Firewall devices Manufacturer A IPS-1 IPS Devices Manufacturer B Border Leaves 1 Border leaf switch Manufacturer C Ridge 1 Spine Switches Manufacturer C Leaf 1 Leaf switch Manufacturer C Leaf 2 Leaf switch Manufacturer C Leaf 3 Leaf switch Manufacturer C Leaf 4 Leaf switch Manufacturer C

[0066] For example, the management device manages Figure 2 Taking the communication network shown in FIG. 1 as an example, the first device information acquired by the management device may be as shown in Table 2:

[0067] Table 2

[0068] Equipment identification Device Type Equipment Manufacturer Core 1 Core network equipment Manufacturer A FW-1 Firewall devices Manufacturer B Border Leaves 1 Border leaf switch Manufacturer C Ridge 1 Spine Switches Manufacturer C Leaf 1 Leaf switch Manufacturer C Leaf 2 Leaf switch Manufacturer C Leaf 3 Leaf switch Manufacturer C Leaf 4 Leaf switch Manufacturer C

[0069] Step 4012: The management device obtains second device information, where the second device information is device information of a network device that supports the management device in parsing configuration information.

[0070] As a possible implementation, the second device information may include the device type that supports the management device to parse the configuration information and the device manufacturer corresponding to the device type. For example, the second device information may include "firewall device + manufacturer A", indicating that the firewall device produced by manufacturer A supports the management device to parse the configuration information.

[0071] Step 4013: The management device determines, based on the first device information and the second device information, a network device in the target network that does not support parsing of configuration information by the management device as a dumb device in the target network.

[0072] As a possible implementation, if the device type of the first network device in the target network included in the first device information does not exist in the second device information, the management device may determine the first network device in the target network as a dumb device. Figure 1 For example, assume that the first device information is the device information shown in Table 1, and the second device information includes {firewall device + manufacturer A, border leaf device + manufacturer C, spine device + manufacturer C, leaf device + manufacturer C}. In this example, the first network device can be IPS-1, and the device type of IPS-1 is IPS device. Since the second device information does not include the device type of IPS device, the management device can determine Figure 1 IPS-1 in the example is a dumb device.

[0073] As a possible implementation, if the device type of the first network device in the target network included in the first device information exists in the second device information, but the second device information does not include the device manufacturer of the first network device, then the management device can determine the first network device in the target network as a dumb device. Figure 1Take the communication network in as an example, assuming that the first device information is the device information shown in Table 1, and the second device information includes {firewall device + manufacturer A, IPS device + manufacturer A, boundary leaf device + manufacturer C, spine device + manufacturer C, leaf device + manufacturer C}. In this example, the first network device can be IPS-1, the device type of IPS-1 is IPS device, and the device manufacturer of IPS-1 is manufacturer B. Although the second device information includes the device type of IPS device, the device manufacturer corresponding to the IPS device in the second device information is manufacturer A, which is different from the device manufacturer B of IPS-1. Therefore, the management device can determine Figure 1 IPS-1 in the example is a dumb device.

[0074] Step 402: The management device generates virtual configuration information of the dumb device according to the configuration information of the neighboring devices of the dumb device in the target network.

[0075] In the embodiment of the present application, the management device can collect and analyze the configuration information of the neighboring devices of the dumb device. For the convenience of description, the neighboring devices of the dumb device can be simply described as neighboring devices, which are described uniformly here.

[0076] Optionally, the configuration information of the neighbor device may include link information, and the link information of the neighbor device may include a physical interface of the neighbor device and a peer device connected to the physical interface.

[0077] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example. The neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. At least part of the link information of border leaf 1 can be shown in Table 3, and at least part of the link information of FW-1 can be shown in Table 4.

[0078] Table 3

[0079] Local device Physical Interface Peer device Border Leaves 1 a1 IPS-1 Border Leaves 1 a2 FW-1 Border Leaves 1 a3 Ridge 1

[0080] Table 4

[0081] Local device Physical Interface Peer device FW-1 b1 IPS-1 FW-1 b2 Border Leaves 1

[0082] For example, the target network is Figure 2 In the communication network shown, the dumb device is FW-1 as an example. The neighboring devices of the dumb device FW-1 include the border leaf 1, and at least part of the link information of the border leaf 1 can be as shown in Table 5.

[0083] Table 5

[0084] Local device Physical Interface Peer device Border Leaves 1 x1 FW-1 Border Leaves 1 x2 FW-1 Border Leaves 1 x3 Core 1 Border Leaves 1 x4 Ridge 1

[0085] Optionally, the multiple physical interfaces of the neighbor device may include a first physical interface connecting the neighbor device and the dumb device.

[0086] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example, and the neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. As shown in Table 3, the first physical interface among the multiple physical interfaces of border leaf 1 is a1. As shown in Table 4, the first physical interface among the multiple physical interfaces of FW-1 is b1.

[0087] As another example, take the target network as Figure 2 In the communication network shown, the dumb device is FW-1 as an example, and the neighboring devices of the dumb device FW-1 include border leaf 1. As shown in Table 5, the first physical interface of the border leaf 1 includes x1 and x2.

[0088] Optionally, the management device determines the virtual configuration information of the dumb device based on the configuration information of the neighbor device of the dumb device, which may include: the management device determines the multiple second physical interfaces of the dumb device based on the multiple first physical interfaces connected between the neighbor device and the dumb device, the multiple second physical interfaces of the dumb device are connected to the multiple first physical interfaces of the neighbor device in a one-to-one correspondence, and the virtual configuration information of the dumb device includes the multiple second physical interfaces of the dumb device.

[0089] For example, the target network is Figure 1 In the communication network shown, taking IPS-1 as an example, the neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. Table 3 shows that the first physical interface of border leaf 1 is a1, and the management device can generate the second physical interface of IPS-1 as c1, and the second physical interface c1 of IPS-1 is correspondingly connected to the first physical interface a1 of border leaf 1. Table 4 shows that the first physical interface of FW-1 is b1, and the management device can generate the second physical interface of IPS-1 as c2, and the second physical interface c2 of IPS-1 is correspondingly connected to the first physical interface b1 of FW-1.

[0090] As another example, take the target network as Figure 2 In the communication network shown, the dumb device is FW-1 as an example, and the neighbor devices of the dumb device FW-1 include the border leaf 1. Table 5 shows that the first physical interface of the border leaf 1 includes x1 and x2, and the management device can generate the second physical interface of the dumb device FW-1 includes y1 and y2, the second physical interface y1 of FW-1 and the first physical interface x1 of the border leaf 1 are correspondingly connected, and the second physical interface y2 of FW-1 and the first physical interface x2 of the border leaf 1 are correspondingly connected.

[0091] Optionally, the configuration information of the neighbor device may also include logical interface configuration information, and the logical interface configuration information of the neighbor device may include the physical interface of the neighbor device, the logical interface bound to the physical interface, the virtual forwarding instance bound to the logical interface, at least one Internet Protocol (IP) address of the logical interface and the corresponding subnet mask. As a possible implementation, the virtual forwarding instance in the configuration information of the neighbor device may be a virtual routing and forwarding (VRF) instance.

[0092] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example. The neighboring devices of the dumb device IPS-1 include the boundary leaf 1 and FW-1. At least part of the logical interface configuration information of the boundary leaf 1 can be as shown in Table 6, and at least part of the logical interface configuration information of FW-1 can be as shown in Table 7.

[0093] Table 6

[0094] equipment Physical Interface Logical interface Virtual forwarding instance Logical interface IP address and corresponding subnet mask Border Leaves 1 a1 VLANIF4001 VPN1 10.100.4.12 / 28 Border Leaves 1 a2 VLANIF4002 VPN2 10.100.4.28 / 28

[0095] Table 7

[0096] equipment Physical Interface Logical interface Virtual forwarding instance Logical interface IP address and corresponding subnet mask FW-1 b1 VLANIF4001 VSYS1 10.100.4.1 / 28 FW-1 b2 VLANIF4002 VSYS1 10.100.4.17 / 28

[0097] For example, the target network is Figure 2 In the communication network shown, the dumb device is FW-1 as an example. The neighboring devices of the dumb device FW-1 include the border leaf 1, and at least part of the logical interface configuration information of the border leaf 1 can be as shown in Table 8.

[0098] Table 8

[0099] equipment Physical Interface Logical interface Virtual forwarding instance IP address and subnet mask of the logical interface Border Leaves 1 x1 VLANIF4001 VPN1 10.100.4.12 / 28 Border Leaves 1 x2 VLANIF4002 VPN2 10.100.4.28 / 28

[0100] It should be noted that the " / 28" in Table 6, Table 7 and Table 8 above is a representation of a subnet mask. " / 28" means that the first 28 bits of the subnet mask are 1, and the subnet mask corresponding to " / 28" is: 255.255.255.240. An IP address is composed of a network address and a host address. The subnet mask is used to mask a part of the IP address to distinguish the network address and the host address of the IP address.

[0101] It should be understood that since the physical interface of the neighboring device includes a first physical interface connected to the dumb device, the logical configuration information of the neighboring device may include the first logical interface bound to the first physical interface, the virtual forwarding instance bound to the first logical interface, the IP address of the first logical interface and the corresponding subnet mask and other information.

[0102] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example, and the neighbor devices of the dumb device IPS-1 include border leaf 1 and FW-1. The physical interface a1 in Table 6 is the first physical interface of border leaf 1, and accordingly, the first logical interface bound to the first physical interface is virtual local area network interface (virtual local area network interface, VLANIF) 4001, the virtual forwarding instance bound to the first logical interface VLANIF4001 is virtual private network (virtual private network, VPN) 1, and the IP address of the first logical interface VLANIF4001 includes 10.100.4.12. The physical interface b1 in Table 7 is the first physical interface of FW-1, and accordingly, the first logical interface bound to the first physical interface b1 is VLANIF4001, the virtual forwarding instance bound to the first logical interface VLANIF4001 is virtual system (virtualsystem, VSYS) 1, and the IP address of the first logical interface VLANIF4001 includes 10.100.4.1.

[0103] As another example, take the target network as Figure 2 In the communication network shown, taking FW-1 as an example, the neighbor devices of the dumb device FW-1 include border leaf 1. x1 and x2 in Table 8 are both the first physical interfaces of border leaf 1. Accordingly, the first logical interface bound to the first physical interface x1 is VLANIF4001, the virtual forwarding instance bound to the first logical interface VLANIF4001 is VPN1, and the IP address of the first logical interface VLANIF4001 includes 10.100.4.12. The first logical interface bound to the first physical interface x2 is VLANIF4002, the virtual forwarding instance bound to the first logical interface VLANIF4002 is VPN2, and the IP address of the first logical interface VLANIF4002 includes 10.100.4.28.

[0104] Optionally, the management device determines the virtual configuration information of the dumb device according to the configuration information of the neighbor device of the dumb device, which may include: the management device determines the second logical interface bound to the second physical interface connected to any first physical interface according to the first logical interface bound to any first physical interface among the multiple first physical interfaces of the neighbor device. The second logical interface bound to the second physical interface connected to any first physical interface corresponds to the same virtual local area network (VLAN) as the first logical interface bound to any first physical interface. The virtual configuration information of the dumb device may include multiple second logical interfaces bound to the multiple second physical interfaces of the dumb device, and the multiple second logical interfaces are all determined in the above manner.

[0105] It should be understood that any first physical interface of the neighbor device and the second physical interface of the dumb device connected to the first physical interface will join the same VLAN, thereby ensuring that the communication between the two interfaces can be carried out correctly. Therefore, the first logical interface bound to any first physical interface of the neighbor device and the second logical interface bound to the second physical interface of the dumb device connected to the first physical interface correspond to the same VLAN.

[0106] As a possible implementation method, the management device can first determine the VLAN identifier corresponding to the first logical interface bound to any first physical interface of the neighboring device, and then generate the identifier of the second logical interface bound to the second physical interface connected to the dumb device and any first physical interface based on the determined VLAN identifier.

[0107] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example, and the neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. According to the above example, the first physical interface of border leaf 1 can be a1, the first logical interface bound to the first physical interface a1 can be VLANIF4001, and the first physical interface a1 can be connected to the second physical interface c1 of the dumb device IPS-1. The first physical interface of FW-1 can be b1, the first logical interface bound to the first physical interface b1 can be VLANIF4001, and the first physical interface b1 can be connected to the second physical interface c2 of the dumb device IPS-1. Based on this, the management device can first determine the identifier of the VLAN corresponding to the first logical interface VLANIF4001 bound to the first physical interface a1, for example, it can be VLAN4001. Then, the management device generates the second logical interface bound to the second physical interface c1 connected to the first physical interface a1 according to VLAN4001, for example, it can be VLANIF4001c1. Similarly, the management device can first determine the identifier of the VLAN corresponding to the first logical interface VLANIF4001 bound to the first physical interface b1, for example, it can be VLAN4001. Then, the management device generates a second logical interface bound to the second physical interface c2 connected to the first physical interface b1 according to VLAN 4001, which may be, for example, VLANIF 4001c2.

[0108] As another example, take the target network as Figure 2In the communication network shown, the dumb device is FW-1 as an example, and the neighbor devices of the dumb device FW-1 include border leaf 1. According to the above example, the multiple first physical interfaces of border leaf 1 may include x1 and x2, the first logical interface bound to the first physical interface x1 is VLANIF4001, the first logical interface bound to the first physical interface x2 is VLANIF4002, the first physical interface x1 can be connected to the second physical interface y1 of the dumb device FW-1, and the first physical interface x2 can be connected to the second physical interface y2 of the dumb device FW-1. Based on this, the management device can first determine the identifier of the VLAN corresponding to the first logical interface VLANIF4001 bound to the first physical interface x1, for example, it can be VLAN4001. Then, the management device generates the second logical interface bound to the second physical interface y1 connected to the first physical interface x1 according to VLAN4001, for example, it can be VLANIF4001y1. Similarly, the management device can first determine the identifier of the VLAN corresponding to the first logical interface VLANIF4002 bound to the first physical interface x2, for example, it can be VLAN4002. Then, the management device generates a second logical interface bound to the second physical interface y2 connected to the first physical interface x2 according to VLAN 4002, which may be, for example, VLANIF 4002y2.

[0109] It should be noted that the above embodiment takes the VLANIF interface and the VLAN as an example using the same numbering representation, for example, the VLAN corresponding to VLANIF4001 is VLAN4001, and both are numbered 4001. Optionally, the numbers used by the VLANIF interface and the VLAN may be different, and this application does not limit this. When the numbers used by the VLANIF interface and the VLAN are different, the management device may also parse the configuration information of the neighboring device to obtain the VLAN number of the logical interface bound to the physical interface of the neighboring device.

[0110] Optionally, determining the virtual configuration information of the dumb device according to the configuration information of the neighbor device of the dumb device may also include: determining the virtual forwarding instance of the dumb device when any two first logical interfaces among the multiple first logical interfaces are interconnected. Among them, the virtual forwarding instance of the dumb device has an inter-access relationship with the virtual forwarding instance bound to the two interconnected first logical interfaces, and the virtual forwarding instance of the dumb device is bound to the two second logical interfaces corresponding to the two interconnected first logical interfaces. The two first physical interfaces bound to the two interconnected first logical interfaces are connected to the two second physical interfaces bound to the two second logical interfaces corresponding to the two interconnected first logical interfaces.

[0111] It should be understood that the first logical interface is a logical interface bound to the first physical interface connecting the neighbor device and the dumb device. If two first logical interfaces are interconnected, it can be considered that the two first logical interfaces are interconnected through the dumb device relay. Therefore, there is an inter-access relationship between the virtual forwarding instance of the dumb device and the virtual forwarding instances bound to the two first logical interfaces.

[0112] It should be noted that the identifier of the virtual forwarding instance of the dumb device can be generated by the management device and any identification method can be used, which is not limited in this application.

[0113] For example, the target network is Figure 1 In the communication network shown, taking IPS-1 as an example, the neighbor devices of the dumb device IPS-1 include border leaf 1 and FW-1. The first physical interface, the first logical interface and the virtual forwarding instance of the border leaf 1 and FW-1 can refer to the previous example. Assuming that the first logical interface VLANIF4001 of the border leaf 1 is intercommunication with the first logical interface VLANIF4001 of FW-1, the management device can determine that the virtual forwarding instance VPN1 bound to the first logical interface VLANIF4001 of the border leaf 1 and the virtual forwarding instance of the dumb device IPS-1 have a mutual visit relationship, and determine that the virtual forwarding instance VSYS1 bound to the first logical interface VLANIF4001 of FW-1 and the virtual forwarding instance of the dumb device IPS-1 have a mutual visit relationship.

[0114] As another example, take the target network as Figure 2 In the communication network shown, taking FW-1 as an example, the neighbor devices of the dumb device FW-1 include border leaf 1. The first physical interface, the first logical interface and the virtual forwarding instance of border leaf 1 can refer to the previous example. Assuming that the first logical interface VLANIF4001 of border leaf 1 is intercommunication with the first logical interface VLANIF4002 of border leaf 1, the management device can determine that the virtual forwarding instance VPN1 bound to the first logical interface VLANIF4001 of border leaf 1 and the virtual forwarding instance of the dumb device FW-1 have a mutual visit relationship, and determine that the virtual forwarding instance VPN2 bound to the first logical interface VLANIF4002 of border leaf 1 and the virtual forwarding instance of the dumb device FW-1 have a mutual visit relationship.

[0115] Optionally, when the IP addresses of the two first logical interfaces of the neighboring device belong to the same network segment, the management device may determine that the two first logical interfaces are interconnected at Layer 2.

[0116] It should be understood that according to the layer 2 forwarding principle, when the source IP address and the destination IP address belong to the same network segment, only layer 2 forwarding is required from the source IP address to the destination IP address. In other words, the source IP address and the destination IP address belonging to the same network segment can be interconnected at the layer 2. Based on this principle, in the embodiment of the present application, if the two first logical interface IP addresses belong to the same network segment, then it can be considered that the two first logical interfaces are interconnected at the layer 2.

[0117] For example, the target network is Figure 1 In the communication network shown, taking IPS-1 as an example, the neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. According to Table 3 and Table 6, the first physical interface of border leaf 1 is a1, the first logical interface bound to the first physical interface a1 is VLANIF4001, and the IP address of the first logical interface VLANIF4001 includes 10.100.4.12. According to Table 4 and Table 7, the first physical interface of FW-1 is b1, the first logical interface bound to the first physical interface b1 is VLANIF4001, and the IP address of the first logical interface VLANIF4001 includes 10.100.4.1. Among them, the subnet mask lengths corresponding to IP address 10.100.4.12 and IP address 10.100.4.1 are both 28. According to the calculation of IP address and subnet mask, it can be determined that the network addresses of IP address 10.100.4.12 and IP address 10.100.4.1 are both 10.100.4.0, so IP address 10.100.4.12 and IP address 10.100.4.1 belong to the same network segment: 10.100.4.0 / 28. Based on this, the management device can consider that the first logical interface VLANIF4001 of boundary leaf 1 and the first logical interface VLANIF4001 in FW-1 are interconnected.

[0118] As a possible implementation manner, when the IP addresses of the two first logical interfaces of the neighbor device belong to the same network segment, the management device may use the same network segment to which the IP addresses of the two first logical interfaces belong to represent the virtual forwarding instance of the dumb device.

[0119] For example, the target network is Figure 1 In the communication network shown, the dumb device is IPS-1 as an example, and the neighbor devices of the dumb device IPS-1 include boundary leaf 1 and FW-1. The first physical interface, the first logical interface and the virtual forwarding instance of boundary leaf 1 and FW-1 can refer to the examples in the previous text. The virtual configuration information of the dumb device generated by the management device can be shown in Table 9.

[0120] Table 9

[0121] Identification of dumb devices Second physical interface Second logical interface Virtual forwarding instance IPS-1 c1 VLANIF4001c1 10.100.4.0 / 28 IPS-1 c2 VLANIF4001c2 10.100.4.0 / 28

[0122] Optionally, when the IP addresses of the two first logical interfaces belong to different network segments, the management device may further determine whether the two first logical interfaces are interoperable based on the routing information of at least one neighbor device of the dumb device. The routing information of at least one neighbor device may include multiple routing entries, each routing entry including a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface.

[0123] Optionally, in the case where the IP addresses of the two first logical interfaces belong to different network segments, if one first logical interface is a route outbound interface in a first routing entry of a neighboring device, and the network segment identified by the routing prefix in the second routing entry includes the network segment identified by the routing prefix of the first routing entry, and the route outbound interface in the second routing entry does not belong to multiple first logical interfaces, and another first logical interface is bound to a virtual forwarding instance in the second routing entry, then the management device can determine that the two first logical interfaces are interconnected at Layer 3. The first routing entry and the second routing entry are routing entries in the routing information of at least one neighboring device.

[0124] It should be understood that the routing outbound interface in the first routing entry is a first logical interface of the neighboring device, which means that this first logical interface can forward IP packets that match the routing prefix in the first routing entry to the dumb device. The network segment identified by the routing prefix in the second routing entry includes the network segment identified by the routing prefix in the first routing entry, and the virtual forwarding instance in the second routing entry is bound to another first logical interface of the neighboring device, which means that the IP packet sent by the first logical interface in the first routing entry to the dumb device can be received by the first logical interface in the second routing entry from the dumb device. Based on this, the management device can assume that the two first logical interfaces are interconnected through Layer 3, and the dumb device acts as a relay device for Layer 3 forwarding.

[0125] For example, the target network is Figure 2In the communication network shown, the dumb device is FW-1 as an example, and the neighbor devices of the dumb device FW-1 include border leaf 1. According to Table 5 and Table 8, the first physical interface of border leaf 1 includes x1 and x2, the first logical interface bound to the first physical interface x1 is VLANIF4001, the first logical interface bound to the first physical interface x2 is VLANIF4002, the IP address of the first logical interface VLANIF4001 includes 10.100.4.12, and the IP address of the first logical interface VLANIF4002 includes 10.100.4.28. Among them, the subnet mask lengths corresponding to the IP address 10.100.4.12 and the IP address 10.100.4.28 are both 28. According to the calculation of the IP address and the subnet mask, it can be determined that the network address of the IP address 10.100.4.12 is 10.100.4.0, and the network address of the IP address 10.100.4.28 is 10.100.4.16. The network address of IP address 10.100.4.12 is different from the network address of IP address 10.100.4.1, so IP address 10.100.4.12 and IP address 10.100.4.1 are not in the same subnet segment. Based on this, the management device also needs to determine whether the first logical interface VLANIF4001 and the first logical interface VLANIF4002 are interoperable in combination with the routing information.

[0126] For example, the routing information of border leaf 1 may be as shown in Table 10.

[0127] Table 10

[0128] equipment Virtual forwarding instance Route Prefix Routing Protocols Routing outbound interface Border Leaves 1 VPN1 10.200.20.0 / 24 Static VLANIF4001 Border Leaves 1 VPN1 10.100.0.0 / 16 Border Gateway Protocol XXX Border Leaves 1 VPN2 10.200.0.0 / 16 Border Gateway Protocol XXX Border Leaves 1 VPN2 10.100.10.0 / 24 Static VLANIF4002

[0129] Referring to the routing information shown in Table 10, the routing outbound interface in the first row of routing entries is the first logical interface VLANIF4001, the network segment 10.200.0.0 / 16 identified by the routing prefix in the third row of routing entries includes the network segment 10.200.20.0 / 24 identified by the routing prefix in the first row of routing entries, and the virtual forwarding instance VPN2 in the third row of routing entries is bound to the first logical interface VLANIF4002. Based on this, the management device can consider that the route from the first logical interface VLANIF4001 to the first logical interface VLANIF4002 is reachable.

[0130] Continuing to refer to the routing information shown in Table 10, the routing outbound interface in the fourth row of routing entries is the first logical interface VLANIF4002, the network segment 10.100.0.0 / 16 identified by the routing prefix in the second row of routing entries includes the network segment 10.100.10.0 / 24 identified by the routing prefix in the fourth row of routing entries, and the virtual forwarding instance VPN1 in the second row of routing entries is bound to the first logical interface VLANIF4001. Based on this, the management device can consider that the route from the first logical interface VLANIF4002 to the first logical interface VLANIF4001 is reachable.

[0131] Thus, the management device can determine that the first logical interface VLANIF4001 and the first logical interface VLANIF4002 are interconnected.

[0132] As a possible implementation manner, when the IP addresses of the two first logical interfaces of the neighboring device belong to different network segments, the management device may use the VPN identifier or the VSYS identifier as the identifier of the virtual forwarding instance.

[0133] For example, the target network is Figure 2 In the communication network shown, the dumb device is FW-1 as an example, and the neighbor devices of the dumb device FW-1 include border leaf 1. The first physical interface, the first logical interface and the virtual forwarding instance of the border leaf 1 can refer to the example in the previous text. The virtual configuration information of the dumb device generated by the management device can be shown in Table 11.

[0134] Table 11

[0135] Identification of dumb devices Second physical interface Second logical interface Virtual forwarding instance FW-1 y1 VLANIF4001y1 VSYS1 FW-1 y2 VLANIF4002y2 VSYS1

[0136] Optionally, the virtual configuration information of the dummy device is used to perform network management on the target network. The following is an exemplary description using an example in which the management device restores the network path passing through the dummy device based on the restored virtual configuration information of the dummy device.

[0137] Optionally, a network entity relationship diagram is generated based on the virtual configuration information of the dumb device and the configuration information of at least one neighbor device. The network entity relationship diagram may include the association relationship between the identifier of the dumb device, the virtual forwarding instance, multiple second physical interfaces, and multiple second logical interfaces in the virtual configuration information, the association relationship between the identifier of at least one neighbor device, multiple first physical interfaces, multiple first logical interfaces, and the virtual forwarding instances bound to the multiple first logical interfaces in the configuration information of at least one neighbor device, and the association relationship between the interfaces connected to the dumb device and the neighbor device.

[0138] As a possible implementation method, the management device can take the identifier of the dumb device, the virtual forwarding instance, multiple second physical interfaces and multiple second logical interfaces in the virtual configuration information of the dumb device as network entities, and take the identifier of at least one neighbor device, multiple first physical interfaces, multiple first logical interfaces and multiple virtual forwarding instances bound to the multiple first logical interfaces in the configuration information of at least one neighbor device as network entities, and establish an association relationship between the various network entities to obtain a network entity relationship diagram. In the network entity relationship diagram, the device identifier of the dumb device is associated with the virtual forwarding instance of the dumb device, the device identifier of the dumb device is respectively associated with multiple second physical input interfaces and multiple physical output interfaces, the virtual forwarding instance of the dumb device is respectively associated with multiple logical input interfaces and multiple logical output interfaces, multiple logical input interfaces are associated with multiple physical input interfaces, multiple logical output interfaces are associated with multiple physical output interfaces, the device identifier of each neighboring device is associated with the virtual forwarding instance in the neighboring device, the device identifier of each neighboring device is associated with multiple first physical interfaces of the neighboring device, the device identifier of each neighboring device is associated with multiple first logical interfaces of the neighboring device, the multiple first logical interfaces of each neighboring device are respectively associated with multiple first physical interfaces, and each first physical interface is associated with a physical input interface or a physical output interface connected to the opposite end.

[0139] For example, the target network is Figure 1 In the communication network shown in FIG. 1 , the dumb device is IPS-1 as an example. The multiple neighboring devices of the dumb device IPS-1 include border leaf 1 and FW-1. The configuration information of border leaf 1 and FW-1 can be shown in Table 6 and Table 7. The virtual configuration information of IPS-1 is shown in Table 9. Based on this, the network entity relationship diagram generated by the management device can be as shown in FIG. Figure 5 shown. Figure 5 Each oval in the figure represents a network entity, and the line between the ovals represents the establishment of an association relationship between the two network entities. Figure 5 As shown, the device identifier "Border Leaf 1" of the border leaf 1, the first physical interface "a1" of the border leaf 1, the first logical interface "VLANIF4001" bound to the first physical interface a1 of the border leaf 1, and the virtual forwarding instance "VPN1" bound to the first logical interface VLANIF4001 of the border leaf 1 are used as Figure 5 The device identifier "FW-1" of FW-1, the first physical interface "b1" of FW-1, the first logical interface "VLANIF4001" bound to the first physical interface b1 of FW-1, and the virtual forwarding instance "VSYS1" bound to the first logical interface VLANIF4001 of FW-1, as Figure 5The identifier of IPS-1 "IPS-1", the second physical interface "c1 and c2" of IPS-1, the second logical interface "VLANIF4001c1" bound to the second physical interface c1 of IPS-1, the second logical interface "VLANIF4001c2" bound to the second physical interface c2 of IPS-1, and the virtual forwarding instance "10.100.4.0 / 28" of IPS-1 are used as Figure 5 The network entities in the network. Among them, "Border Leaf 1" is connected to "a1" and "VPN1" respectively, "VPN1" is also connected to "VLANIF4001", and "VLANIF4001" is also connected to "a1". "FW-1" is connected to "b1" and "VSYS1" respectively, "VSYS1" is also connected to "VLANIF4001", and "VLANIF4001" is also connected to "b1". "IPS-1" is connected to "c1", "c2" and "10.100.4.0 / 28" respectively, "c1" is also connected to "VLANIF4001c1", "c2" is also connected to "VLANIF4001c2", and "10.100.4.0 / 28" is also connected to "VLANIF4001c1" and "VLANIF4001c2". In addition, "c1" is connected to "a1", and "c2" is connected to "b1".

[0140] It should be understood that the network entities in the network entity relationship diagram can be connected based on the association relationship between the parameters represented by the network entities. For example, a1 is the physical interface on the device boundary leaf 1, so Figure 5 In the example, "a1" can connect to "Border Leaf 1". VPN1 is a virtual forwarding instance in device Border Leaf 1, so Figure 5 VPN1 can be connected to Border Leaf 1. VLANIF4001 in Border Leaf 1 is the logical interface bound to VPN1. Figure 5 In the example, VPN1 can be connected to VLANIF4001. The logical interface bound to physical interface a1 in border leaf 1 is VLANIF4001, so Figure 5 "VLANIF4001" can be connected to "a1". The association relationship between the various entities of FW-1 can be referred to the above description, so it will not be repeated here. c1 and c2 are the physical interfaces of device IPS-1, so Figure 5 In the example, IPS-1 can be connected to c1 and c2. The logical interface bound to the physical interface c1 in IPS-1 is VLANIF4001c1. Figure 5 The logical interface bound to the physical interface c2 in IPS-1 is VLANIF4001c2, so Figure 5 VLANIF4001c2 can be connected to c2. 10.100.4.0 / 28 is the virtual forwarding instance of IPS-1. Figure 5 The virtual forwarding instance bound to logical interface VLANIF4001c1 and logical interface VLANIF4001c2 is 10.100.4.0 / 28. Figure 5 In the example, "10.100.4.0 / 28" can be connected to "VLANIF4001c1" and "VLANIF4001c2". In addition, since the physical interface c1 of the dumb device is a physical interface generated by the management device and connected to the physical interface a1 of the border leaf 1, and the physical interface c2 of the dumb device is a physical interface generated by the management device and connected to the physical interface b1 of FW-1, Figure 5 In this example, "c1" is connected to "a1", and "c2" is connected to "b1".

[0141] For example, the target network is Figure 2 In the communication network shown in FIG. 1 , the dumb device is FW-1 as an example. The neighboring devices of the dumb device FW-1 include the border leaf 1. The configuration information of the border leaf 1 can be shown in Table 8. The virtual configuration information of the dumb device FW-1 can be shown in Table 11. Based on this, the network entity relationship diagram generated by the management device can be as shown in FIG. Figure 6 shown. Figure 6 Each oval in the figure represents a network entity, and the line between the ovals represents the establishment of an association relationship between the two network entities. Figure 6 As shown, the device identifier of border leaf 1 "Border Leaf 1", the first physical interfaces "x1" and "x2" of border leaf 1, the first logical interface "VLANIF4001" bound to the first physical interface x1 of border leaf 1, the virtual forwarding instance "VPN1" bound to the first logical interface VLANIF4001 of border leaf 1, the first logical interface "VLANIF4002" bound to the first physical interface x2 of border leaf 1, and the virtual forwarding instance "VPN2" bound to the first logical interface VLANIF4002 of border leaf 1 are used as Figure 6 The identifier of FW-1 "FW-1", the second physical interface of FW-1 "y1 and y2", the second logical interface "VLANIF4001y1" bound to the second physical interface y1 of FW-1, the second logical interface "VLANIF4001y2" bound to the second physical interface y2 of FW-1, and the virtual forwarding instance "VSYS1" of FW-1 are used as Figure 6The network entities in the network. Among them, "Border Leaf 1" is connected to "x1", "x2", "VPN1" and "VPN2" respectively, "VPN1" is also connected to "VLANIF4001", "VPN2" is also connected to "VLANIF4002", "VLANIF4001" is also connected to "x1", and "VLANIF4002" is also connected to "x2". "FW-1" is connected to "y1", "y2" and "VSYS1" respectively, "y1" is also connected to "VLANIF4001y1", "y2" is also connected to "VLANIF4001y2", and "VSYS1" is also connected to "VLANIF4001y1" and "VLANIF4001y2". In addition, "y1" is connected to "x1" and "y2" is connected to "x2".

[0142] It should be understood that for the sake of clarity of illustration, Figure 6 There are two network entities representing the device identifier "Border Leaf 1" in the figure. These two network entities representing the device identifier "Border Leaf 1" are actually the same and are explained here uniformly.

[0143] It should be understood that the network entities in the network entity relationship diagram can be connected based on the association relationship between the parameters represented by the network entities. For example, since x1 and x2 are physical interfaces on the device boundary leaf 1, Figure 6 In the example, "x1" and "x2" can be connected to "Border Leaf 1". Since VPN1 and VPN2 are virtual forwarding instances in device Border Leaf 1, Figure 6 VPN1 and VPN2 can be connected to Border Leaf 1. Since VLANIF4001 in Border Leaf 1 is a logical interface bound to VPN1, Figure 6 VPN1 can be connected to VLANIF4001. Since VLANIF4002 of border leaf 1 is a logical interface bound to VPN2, Figure 6 VPN2 can be connected to VLANIF4002. Since the logical interface bound to the physical interface x1 of the border leaf 1 is VLANIF4001, Figure 6 In the example, VLANIF4001 can be connected to x1. Since the logical interface bound to physical interface x2 in border leaf 1 is VLANIF4002, Figure 6 In the example, VLANIF4002 can be connected to x2. Since y1 and y2 are physical interfaces on FW-1, Figure 6 The device identifier "FW-1" can be connected to "y1" and "y2" respectively. Since VSYS1 is the virtual forwarding instance of FW-1, Figure 6The device identifier "FW-1" can be connected to "VSYS1". Since VLANIF4001y1 and VLANIF4002y2 are logical interfaces bound to the virtual forwarding instance VSYS1, Figure 6 In the example, VSYS1 can be connected to VLANIF4001y1 and VLANIF4002y2. Since the logical interface bound to the physical interface y1 of FW-1 is VLANIF4001y1, Figure 6 In the example, VLANIF4001y1 can be connected to y1. Since the logical interface bound to the physical interface y2 of FW-1 is VLANIF4002y2, Figure 6 In the example, VLANIF4002y2 can be connected to y2. Since the physical interface x1 of border leaf 1 is connected to the physical interface y1 of FW-1, Figure 6 In the example, "x1" is also connected to "y1". Since the physical interface x2 of the boundary leaf 1 is connected to the physical interface y2 of FW-2, Figure 6 In the example, "x2" is also connected to "y2".

[0144] Optionally, the management device can obtain the source IP address and destination IP address of the network path to be restored in the target network, and search for the network path to the destination IP address starting from the source IP address. The management device can search for the first neighbor device among multiple neighbor devices of the dumb device. Among them, there is a routing prefix matching the destination IP address in the routing information of the first neighbor device, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is a dumb device. Afterwards, the management device can search the network entity relationship diagram starting from the first neighbor device to determine the forwarding path from the first neighbor device to the second neighbor device. Among them, there is a routing prefix matching the destination IP address in the routing information of the second neighbor device, and the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not a dumb device. Finally, the management device can determine the network path to be restored based on the forwarding path from the first neighbor device to the second neighbor device.

[0145] For example, the target network is Figure 1 In the communication network shown in the figure, the dumb device is IPS-1 as an example. Multiple neighbor devices of dumb device IPS-1 include border leaf 1 and FW-1. The configuration information of border leaf 1 and FW-1 can be shown in Table 6 and Table 7. The virtual configuration information of IPS-1 is shown in Table 9. The first network entity relationship is shown in Table 9. Figure 5 The routing information of the border leaf 1 may include the table items shown in Table 12, and the routing information of FW-1 may include the table items shown in Table 13.

[0146] Table 12

[0147] equipment Virtual forwarding instance Route Prefix Routing Protocols Routing outbound interface Border Leaves 1 VPN1 10.200.0.0 / 16 Static VLANIF4001 Border Leaves 1 VPN1 10.100.0.0 / 16 Border Gateway Protocol XXX

[0148] Table 13

[0149] equipment Virtual forwarding instance Route Prefix Routing Protocols Routing outbound interface FW-1 VSYS1 10.200.0.0 / 16 Static VLANIF4002 FW-1 VSYS1 10.100.0.0 / 16 Static VLANIF4001

[0150] Based on the above example, assuming that the source IP of the network path to be restored obtained by the management device is the IP address of leaf 1, and the destination IP address is 10.200.20.2, then the management device can restore the path starting from leaf 1. First, for the nodes between leaf 1 and border leaf 1, the management device can query the routing information to restore the network path. The management device can query border leaf 1 based on the routing information, and the destination IP address 10.200.20.2 can match the first row of routing entries in the routing information of border leaf 1 shown in Table 12. Among them, the routing prefix 10.200.0.0 / 16 and the destination IP address 10.200.20.2 in the first row of routing entries in Table 12 meet the prefix matching rule, and the physical interface bound to the routing output interface VLANIF4001 in the first row of routing entries in Table 12 is a1, which is connected to the dumb device IPS-1 (that is, the next hop of the route is the dumb device IPS-1). Since the management device does not have the routing information of the dumb device IPS-1, the management device can determine that according to Figure 5 The network entity relationship diagram shown in FIG. 1 restores the network path through the dumb device IPS-1. Since the virtual forwarding instance in the first row of the routing entry in Table 12 is VPN1, the management device can Figure 5 The virtual forwarding instance "VPN1" of the middle border leaf 1 is used as the starting point to search for Figure 5 The management device manages the network paths of other virtual forwarding instances in Figure 5 The network path searched for in the virtual forwarding instance to other neighbor devices may include: VPN1→VLANIF4001→a1→c1→VLANIF4001c1→10.100.4.0 / 28→VLANIF4001c2→c2→b1→VLANIF4001→VSYS1. Figure 5VSYS1 in the table is the virtual forwarding instance of the neighbor device FW-1. The management device can query the routing information in FW-1 according to the destination IP address "10.200.20.2" and the virtual forwarding instance VSYS1, and can match the first row of routing entries in Table 13. Among them, the virtual forwarding instance in the first row of routing entries in Table 13 is VSYS1, and the routing prefix 10.200.0.0 / 16 and the destination IP address 10.200.20.2 in the first row of routing entries in Table 13 meet the prefix matching rule. Since the physical interface a2 bound to the routing output interface VLANIF4002 in the first row of routing entries in Table 13 is not the physical interface connected to the dumb device IPS-1 (that is, the next hop of the route is not the dumb device IPS-1), the management device can determine that the network path searched above is the correct routing forwarding path, which is a part of the network path from leaf 1 to the destination IP address 10.200.20.2.

[0151] As another example, take the target network as Figure 2 In the communication network shown, take FW-1 as an example of a dumb device. The neighbor devices of dumb device FW-1 include border leaf 1. The configuration information of border leaf 1 can be as shown in Table 8, the routing information of border leaf 1 can be as shown in Table 10, and the virtual configuration information of dumb device FW-1 can be as shown in Table 11. Assuming that the source end of the network path to be restored obtained by the management device is leaf 1, and the destination IP address is 10.200.20.2, the management device can restore the path from leaf 1 as the starting point. First, for the nodes between leaf 1 and border leaf 1, the management device can query the routing information to restore the network path. The management device can query border leaf 1 according to the routing information, and the destination IP address 10.200.20.2 can match the first row of routing entries in the routing information of border leaf 1 shown in Table 10. Among them, the routing prefix 10.200.20.0 / 24 and the destination IP address 10.200.20.2 in the first row of routing entries in Table 10 meet the prefix matching rule, and the physical interface bound to the routing output interface VLANIF4001 in the first row of routing entries in Table 10 is x1, which is connected to the dumb device FW-1 (that is, the next hop of the route is the dumb device FW-1). Since the management device does not have the routing information of the dumb device FW-1, the management device can determine that according to Figure 6 The second network entity relationship diagram shown in FIG. 1 restores the network path through the dumb device FW-1. Since the virtual forwarding instance in the first row of the routing entry in Table 10 is VPN1, the management device can Figure 6 The virtual forwarding instance "VPN1" of the middle border leaf 1 is used as the starting point to search for Figure 6 The management device manages the network paths of other virtual forwarding instances in Figure 6The network path searched in the virtual forwarding instance to other neighbor devices may include: VPN1→VLANIF4001→x1→y1→VLANIF4001y1→VSYS1→VLANIF4002y2→y2→x2→VLANIF4002→VPN2. Figure 6 VPN2 in the figure is another virtual forwarding instance of the neighboring device border leaf 1. The management device can continue to query the routing information in the border leaf 1 according to the destination IP address 10.200.20.2 and the virtual forwarding instance VPN2, and can match the third row of routing entries in the routing information of the border leaf 1 shown in Table 10. Among them, the virtual forwarding instance in the third row of routing entries in Table 10 is VPN2, and the routing prefix 10.200.0.0 / 16 in the third row of routing entries in Table 10 meets the prefix matching rule with the destination IP address 10.200.20.2. Since the physical interface bound to the routing output interface VLANIF4002 corresponding to the third row of routing entries in Table 10 is not the physical interface connected to the dumb device FW-1 (that is, the next hop of the route is not the dumb device FW-1), the management device can determine that the forwarding path searched above is correct, and the forwarding path is part of the network path from leaf 1 to the destination IP address 10.200.20.2.

[0152] Based on the above scheme, when the management device performs network path restoration, even if the network path to be restored includes dumb devices and the management device does not have the routing information of the dumb devices, the management device can still generate a network entity relationship diagram based on the virtual configuration of the dumb devices, and then search for the forwarding path passing through the dumb devices based on the network entity relationship diagram, thereby correctly implementing network path restoration.

[0153] Optionally, the embodiment of the present application may further convert the above-mentioned network entity relationship diagram, and then the management device may determine the forwarding path from the first neighbor device to the second neighbor device based on the converted network entity relationship diagram.

[0154] As a possible implementation method, the network entity representing the virtual forwarding instance in the network entity relationship diagram can be retained, and the path corresponding to the network entity connected between any two network entities representing the virtual forwarding instances can be used as the network path information between the network entities corresponding to the two virtual forwarding instances.

[0155] For example, Figure 5 Take the network entity relationship diagram shown as an example. Figure 5 The network entities representing the virtual forwarding instances may include "VPN1", "VSYS1" and "10.100.4.0 / 28". These three network entities can be retained. Figure 5 After conversion, we can get Figure 7The network entity relationship diagram shown in Figure 1. Figure 5 The paths corresponding to VLANIF4001, a1, c1, and VLANIF4001c1 connected between VPN1 and 10.100.4.0 / 28 in As Figure 7 The path information of the connection between VPN1 and 10.100.4.0 / 28. Figure 5 The paths corresponding to VLANIF4001c2, c2, b1, and VLANIF4001 connected between 10.100.4.0 / 28 and VSYS1 As Figure 7 The path information of the connection between 10.100.4.0 / 28 and VSYS1.

[0156] As another example, Figure 6 Take the network entity relationship diagram shown as an example. Figure 6 The network entities representing the virtual forwarding instances may include "VPN1", "VPN2" and "VSYS1". These three network entities can be retained. Figure 6 After conversion, we can get Figure 8 The network entity relationship diagram shown in Figure 1. Figure 6 The paths corresponding to VLANIF4001, x1, y1, and VLANIF4001y1 that connect VPN1 and VSYS1 As Figure 8 The path information of the connection between VPN1 and VSYS1. Figure 6 The paths corresponding to VLANIF4002y2, y2, x2, and VLANIF4002 that connect VPN2 and VSYS1 As Figure 8 The path information of the connection between VPN2 and VSYS1.

[0157] Optionally, the above-mentioned network management method in the embodiment of the present application can be performed by a communication device, which can be a management device in the above-mentioned method embodiment, or a device including the above-mentioned management device, or a component that can be used for a management device. In order to realize the above-mentioned functions, the communication device includes a hardware structure and / or software module corresponding to each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0158] Fig. 9 A schematic diagram of the structure of a communication device is shown, and the communication device 90 includes a processing module 901. The processing module 901 is used to determine a dumb device in a target network, and generate virtual configuration information of the dumb device according to the configuration information of a neighbor device of the dumb device in the target network. The dumb device is a network device in the target network that does not support the management device to parse the configuration information.

[0159] Optionally, the configuration information of the neighbor device includes multiple first physical interfaces connected to the neighbor device and multiple first logical interfaces bound to the multiple first physical interfaces. The processing module 901 can be used to determine multiple second physical interfaces of the dumb device based on the multiple first physical interfaces, and determine the second logical interface bound to the second physical interface connected to any first physical interface based on the first logical interface bound to any first physical interface among the multiple first physical interfaces. The virtual configuration information of the dumb device may include multiple second physical interfaces and multiple second logical interfaces bound to the multiple second physical interfaces. Among them, the multiple second physical interfaces are connected to the multiple first physical interfaces in a one-to-one correspondence. The second logical interface bound to the second physical interface connected to any first physical interface corresponds to the same VLAN as the first logical interface bound to any first physical interface. .

[0160] Optionally, the processing module 901 can be used to determine the virtual forwarding instance of the dumb device when any two first logical interfaces among multiple first logical interfaces are interconnected. The virtual configuration information of the dumb device includes the virtual forwarding instance of the dumb device. Among them, the virtual forwarding instance of the dumb device has an inter-access relationship with the virtual forwarding instance bound to any two first logical interfaces, the virtual forwarding instance of the dumb device is bound to two second logical interfaces corresponding to any two first logical interfaces, and the two second physical interfaces bound to the two second logical interfaces are connected to the two first physical interfaces bound to any two first logical interfaces.

[0161] Optionally, the configuration information of the neighbor device further includes IP addresses of multiple first logical interfaces. The processing module 901 is further configured to determine that any two first logical interfaces are interconnected at layer 2 when the IP addresses of any two first logical interfaces belong to the same network segment.

[0162] Optionally, the configuration information of the neighbor device also includes Internet Protocol IP addresses of multiple first logical interfaces. The routing information of the neighbor device includes multiple routing entries, each routing entry includes a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface. The processing module 901 is also used to determine the three-layer interconnection between any two first logical interfaces when the IP addresses of any two first logical interfaces belong to different network segments, one of the any two first logical interfaces is the routing output interface of the first routing entry in the multiple routing entries, the network segment identified by the routing prefix of the second routing entry in the multiple routing entries includes the network segment identified by the routing prefix of the first routing entry, and the other first logical interface is bound to the virtual forwarding instance of the second routing entry.

[0163] Optionally, the processing module 901 is further used to generate a network entity relationship diagram according to the virtual configuration information and the configuration information of at least one neighbor device. The network entity relationship diagram includes the identifier of the dumb device in the virtual configuration information, the virtual forwarding instance of the dumb device, the association relationship between multiple second physical interfaces and multiple second logical interfaces, and the identifier of at least one neighbor device in the configuration information of at least one neighbor device, the association relationship between multiple first physical interfaces, multiple first logical interfaces and the virtual forwarding instances bound to the multiple first logical interfaces, and the association relationship between the interfaces connected to the dumb device and the neighbor device.

[0164] Optionally, the communication device may further include a transceiver module 902. The transceiver module 902 is used to obtain the source IP address and the destination IP address of the network path to be restored. The processing module 901 is also used to search the network path to the destination IP address with the source IP address as the starting point, and find the first neighbor device to the dumb device. In addition, the processing module 901 is also used to search the network entity relationship diagram with the first neighbor device as the starting point, and determine the forwarding path from the first neighbor device to the second neighbor device. Furthermore, the processing module 901 is also used to determine the network path to be restored based on the forwarding path from the first neighbor device to the second neighbor device. Among them, there is a routing prefix matching the destination IP address in the routing information of the first neighbor device, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is a dumb device. There is a routing prefix matching the destination IP address in the routing information of the second neighbor device, and the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not a dumb device, and the dumb device is a relay device on the forwarding path from the first neighbor device to the second neighbor device.

[0165] Optionally, the communication device further includes a transceiver module 902. The transceiver module 902 is used to obtain first device information and second device information, where the first device information is information about network devices included in the target network, and the second device information is information about network devices that support the management device to parse configuration information. The processing module 901 is also used to determine, based on the first network device information and the second network device information, network devices in the target network that do not support the management device to parse configuration information as dumb devices in the target network.

[0166] All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. Since the communication device 90 provided in this embodiment can execute the above network management method, the technical effects that can be obtained can refer to the above method embodiment, which will not be repeated here.

[0167] The embodiment of the present application can divide the communication device into functional modules according to the different method behaviors in the above method embodiments. For example, Fig. 9 The processing modules in the embodiment may include a dumb device determination module 901a, a virtual configuration information generation module 901b and a path restoration module 901c. The dumb device determination module 901a is used to execute related actions of determining the dumb device, the virtual configuration information generation module 901b is used to execute related actions of generating virtual configuration information of the dumb device, and the path restoration module 901c is used to execute related actions of network path restoration.

[0168] It should be understood that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. For example, two or more functions may be integrated into one processing module. In addition, the above-mentioned integrated modules may be implemented in the form of hardware or in the form of software function modules, and the present application does not limit this.

[0169] In this embodiment, the communication device 90 is presented in the form of various functional modules divided in an integrated manner. The "module" here may refer to a specific ASIC, a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 90 can be used Fig.10 The form of the communication device 100 is shown.

[0170] Fig.10 A schematic diagram of the structure of another communication device provided in an embodiment of the present application, such as Fig.10 As shown, the communication device 100 includes one or more processors 1001, a communication line 1002, and at least one communication interface ( Fig.10The communication interface 1003 and a processor 1001 are merely exemplary. Optionally, a memory 1004 may also be included. The processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. The communication line 1002 may include a passage for communication between different components. The communication interface 1003 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module may be a device such as a transceiver or a transceiver. Optionally, the communication interface 1003 may also be a transceiver circuit located in the processor 1001, which is used to realize the signal input and signal output of the processor. The memory 1004 may be a device with a storage function. For example, it can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. The memory can be independent and connected to the processor through a communication line 1002. The memory can also be integrated with the processor. Among them, the memory 1004 is used to store computer execution instructions for executing the solution of the present application, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the computer execution instructions stored in the memory 1004, so as to implement the network management method provided in the embodiment of the present application. Alternatively, the processor 1001 in the embodiment of the present application performs the processing-related functions in the network management method provided in the following embodiment of the present application, and the communication interface 1003 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.The computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application. As an embodiment, the processor 1001 may include one or more CPUs, for example. Fig.10 CPU0 and CPU1 in.

[0171] As an embodiment, the communication device 100 may include multiple processors, such as Fig.10 The processor 1001 and the processor 1007 in the embodiment of the present invention are shown in FIG. 1 . Each of these processors may be a single-core processor or a multi-core processor. The processors here may include but are not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0172] As an embodiment, the communication device 100 may further include an output device 1005 and an input device 1006. The output device 1005 communicates with the processor 1001 and may display information in a variety of ways. For example, the output device 1005 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1006 communicates with the processor 1001 and may receive user input in a variety of ways. For example, the input device 1006 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0173] The communication device 100 may also be referred to as a communication device, which may be a general device or a dedicated device. For example, the communication device 100 may be a controller in a network or a device having Fig.10 The embodiment of the present application does not limit the type of the communication device 100.

[0174] Fig.10The processor 1001 in the communication device 100 shown can enable the communication device 100 to execute the network management method in the above method embodiment by calling the computer-executable instructions stored in the memory 1004. Since the communication device 100 provided in this embodiment can execute the above network management method, the technical effects that can be obtained can refer to the above method embodiment, which will not be repeated here.

[0175] In various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. It can be appreciated by those of ordinary skill in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application. It can be clearly understood by those of ordinary skill in the art that for the convenience and simplicity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0176] As used in this application, the terms "component", "module", "system", etc. are intended to refer to a computer-related entity, which can be hardware, firmware, a combination of hardware and software, software, or software in operation. For example, a component can be, but is not limited to: a process running on a processor, a processor, an object, an executable file, a thread in execution, a program, and / or a computer. As an example, an application running on a computing device and the computing device can both be components. One or more components can exist in a process and / or thread in execution, and a component can be located in a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures thereon. These components can communicate in a local and / or remote process manner, such as according to a signal having one or more data packets (for example, data from a component, which interacts with another component in a local system, a distributed system, and / or interacts with other systems in a signal manner through a network such as the Internet). This application presents various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. discussed in connection with the figures. Furthermore, combinations of these aspects may also be used.

[0177] In addition, in the embodiments of the present application, the word "exemplary" is used to indicate an example, illustration or explanation. Any embodiment or design described as "example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present concepts in a specific way. In the embodiments of the present application, information, signal, message, and channel can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, the meanings to be expressed are consistent. "Of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, the meanings to be expressed are consistent. "System" and "network" can sometimes be used interchangeably. When the distinction is not emphasized, the meanings to be expressed are consistent. For example, "communication network" also refers to "communication system". The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0178] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A network management method, characterized in that: Applied to a management device, the method comprises: Determine a dumb device in the target network, where the dumb device is a network device in the target network that does not support the management device to parse configuration information; The virtual configuration information of the dumb device is determined according to the configuration information of the neighboring device of the dumb device.

2. The method according to claim 1, characterized in that The configuration information of the neighbor device includes a plurality of first physical interfaces connecting the neighbor device and the dumb device and a plurality of first logical interfaces bound to the plurality of first physical interfaces; The determining the virtual configuration information of the dumb device according to the configuration information of the neighboring device of the dumb device includes: Determine a plurality of second physical interfaces of the dumb device according to the plurality of first physical interfaces, wherein the plurality of second physical interfaces are connected to the plurality of first physical interfaces in a one-to-one correspondence; According to the first logical interface bound to any one of the multiple first physical interfaces, determine the second logical interface bound to the second physical interface connected to any one of the first physical interfaces; the second logical interface bound to the second physical interface connected to any one of the first physical interfaces corresponds to the same virtual local area network VLAN as the first logical interface bound to any one of the first physical interfaces; The virtual configuration information of the dumb device includes the multiple second physical interfaces and the multiple second logical interfaces bound to the multiple second physical interfaces.

3. The method according to claim 2, characterized in that The determining the virtual configuration information of the dumb device according to the configuration information of the neighboring device of the dumb device also includes: In the case where any two of the multiple first logical interfaces are interconnected, a virtual forwarding instance of the dumb device is determined; a mutual access relationship exists between the virtual forwarding instance of the dumb device and the virtual forwarding instance bound to the any two first logical interfaces, the virtual forwarding instance of the dumb device is bound to two second logical interfaces corresponding to the any two first logical interfaces, and two second physical interfaces bound to the two second logical interfaces are connected to two first physical interfaces bound to the any two first logical interfaces; the virtual configuration information of the dumb device includes the virtual forwarding instance of the dumb device.

4. The method according to claim 3, characterized in that The configuration information of the neighbor device also includes Internet Protocol IP addresses of the multiple first logical interfaces; the method also includes: If the IP addresses of any two first logical interfaces belong to the same network segment, it is determined that the two first logical interfaces are interconnected at layer 2.

5. The method according to claim 3, characterized in that: The configuration information of the neighbor device also includes Internet Protocol IP addresses of the multiple first logical interfaces; the routing information of the neighbor device includes multiple routing entries, each routing entry includes a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface; The method further comprises: If the IP addresses of any two first logical interfaces belong to different network segments, one of the any two first logical interfaces is the routing outbound interface of the first routing entry in the multiple routing entries, the network segment identified by the routing prefix of the second routing entry in the multiple routing entries includes the network segment identified by the routing prefix of the first routing entry, and the other first logical interface is bound to the virtual forwarding instance of the second routing entry, then it is determined that the any two first logical interfaces are interconnected at three layers.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: A network entity relationship diagram is generated based on the virtual configuration information and the configuration information of at least one neighbor device, wherein the network entity relationship diagram includes an identifier of the dumb device in the virtual configuration information, a virtual forwarding instance of the dumb device, an association relationship between the multiple second physical interfaces and the multiple second logical interfaces, an identifier of the at least one neighbor device in the configuration information of the at least one neighbor device, multiple first physical interfaces, multiple first logical interfaces and an association relationship between the virtual forwarding instances bound to the multiple first logical interfaces, and an association relationship between the interfaces connected to the dumb device and the neighbor device.

7. The method according to claim 6, characterized in that The method further comprises: Obtain the source IP address and destination IP address of the network path to be restored; Searching for a network path to the destination IP address with the source IP address as the starting point, and searching for a first neighbor device to the dumb device; a routing prefix matching the destination IP address exists in the routing information of the first neighbor device, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is the dumb device; The network entity relationship diagram is searched with the first neighbor device as the starting point to determine a forwarding path from the first neighbor device to the second neighbor device; there is a routing prefix matching the destination IP address in the routing information of the second neighbor device, the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not the dumb device, and the dumb device is a relay device on the forwarding path from the first neighbor device to the second neighbor device; The network path to be restored is determined according to the forwarding path from the first neighbor device to the second neighbor device.

8. The method according to any one of claims 1 to 7, characterized in that: The step of determining a dumb device in the target network includes: Acquire first device information and second device information, wherein the first device information is information about network devices included in the target network, and the second device information is information about network devices that support the management device to parse configuration information; According to the first network device information and the second network device information, a network device in the target network that does not support the management device parsing configuration information is determined as a dumb device in the target network.

9. A communication device, characterized in that: Applied to a management device, the communication device comprises a processing module; The processing module is used to determine a dumb device in the target network, where the dumb device is a network device in the target network that does not support the management device to parse configuration information; The processing module is further configured to determine virtual configuration information of the dumb device according to configuration information of a neighboring device of the dumb device.

10. The communication device according to claim 9, characterized in that: The configuration information of the neighbor device includes a plurality of first physical interfaces connecting the neighbor device and the dumb device and a plurality of first logical interfaces bound to the plurality of first physical interfaces; The processing module is further used to determine a plurality of second physical interfaces of the dumb device according to the plurality of first physical interfaces, wherein the plurality of second physical interfaces are connected to the plurality of first physical interfaces in a one-to-one correspondence; The processing module is also used to determine, according to the first logical interface bound to any one of the multiple first physical interfaces, a second logical interface bound to a second physical interface connected to any one of the first physical interfaces; the second logical interface bound to the second physical interface connected to any one of the first physical interfaces corresponds to the same virtual local area network VLAN as the first logical interface bound to any one of the first physical interfaces; The virtual configuration information of the dumb device includes the multiple second physical interfaces and the multiple second logical interfaces bound to the multiple second physical interfaces.

11. The communication device according to claim 10, characterized in that: The processing module is further configured to determine a virtual forwarding instance of the dumb device when any two of the plurality of first logical interfaces are interconnected; Among them, the virtual forwarding instance of the dumb device has an inter-access relationship with the virtual forwarding instance bound to the any two first logical interfaces, the virtual forwarding instance of the dumb device is bound to the two second logical interfaces corresponding to the any two first logical interfaces, and the two second physical interfaces bound to the two second logical interfaces are connected to the two first physical interfaces bound to the any two first logical interfaces; the virtual configuration information of the dumb device includes the virtual forwarding instance of the dumb device.

12. The communication device according to claim 11, characterized in that: The configuration information of the neighbor device also includes Internet Protocol IP addresses of the multiple first logical interfaces; The processing module is further configured to determine that the two first logical interfaces are interconnected at layer 2 when the IP addresses of the two first logical interfaces belong to the same network segment.

13. The communication device according to claim 11, characterized in that: The configuration information of the neighbor device also includes Internet Protocol IP addresses of the multiple first logical interfaces; the routing information of the neighbor device includes multiple routing entries, each routing entry includes a routing prefix, a routing output interface corresponding to the routing prefix, and a virtual forwarding instance corresponding to the routing output interface; The processing module is also used to determine that the any two first logical interfaces are interconnected at three layers when the IP addresses of the any two first logical interfaces belong to different network segments, one of the any two first logical interfaces is the routing output interface of the first routing entry among the multiple routing entries, the network segment identified by the routing prefix of the second routing entry among the multiple routing entries includes the network segment identified by the routing prefix of the first routing entry, and the other first logical interface is bound to the virtual forwarding instance of the second routing entry.

14. The communication device according to any one of claims 9 to 13, characterized in that: The processing module is also used to generate a network entity relationship diagram based on the virtual configuration information and the configuration information of at least one neighboring device, the network entity relationship diagram including the identifier of the dumb device in the virtual configuration information, the virtual forwarding instance of the dumb device, the association relationship between the multiple second physical interfaces and the multiple second logical interfaces, the identifier of at least one neighboring device in the configuration information of the at least one neighboring device, the multiple first physical interfaces, the multiple first logical interfaces and the virtual forwarding instances bound to the multiple first logical interfaces, and the association relationship between the interfaces connected to the dumb device and the neighboring device.

15. The communication device according to claim 14, characterized in that: The communication device also includes a transceiver module; The transceiver module is used to obtain the source IP address and the destination IP address of the network path to be restored; The processing module is also used to find a network path to the destination IP address with the source IP address as the starting point, and find a first neighbor device to the dumb device; The routing information of the first neighbor device contains a routing prefix that matches the destination IP address, and the next hop corresponding to the destination IP address in the routing information of the first neighbor device is the dumb device; The processing module is further used to search the network entity relationship diagram with the first neighbor device as the starting point to determine a forwarding path from the first neighbor device to the second neighbor device; The routing information of the second neighbor device contains a routing prefix that matches the destination IP address, the next hop corresponding to the destination IP address in the routing information of the second neighbor device is not the dumb device, and the dumb device is a relay device on the forwarding path from the first neighbor device to the second neighbor device; The processing module is further configured to determine the network path to be restored according to the forwarding path from the first neighbor device to the second neighbor device.

16. The communication device according to any one of claims 9 to 15, characterized in that: The communication device also includes a transceiver module; The transceiver module is used to obtain first device information and second device information, wherein the first device information is information about network devices included in the target network, and the second device information is information about network devices that support the management device to parse configuration information; The processing module is further configured to determine, based on the first network device information and the second network device information, a network device in the target network that does not support parsing configuration information by the management device as a dumb device in the target network.

17. A communication device, characterized in that: The communication device comprises: a processor and a memory; The memory is used to store computer-executable instructions. When the processor executes the computer-executable instructions, the communication device executes the network management method according to any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that: The method comprises instructions which, when executed on a computer, enable the computer to execute the network management method according to any one of claims 1 to 8.

Images