A management method and device of a network equipment, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a network device management method and device, electronic equipment and storage medium, the method comprising: obtaining intermediate system to intermediate system (IS-IS) topology information of an i-th core device in a target network area, the IS-IS topology information of the i-th core device comprising neighbor relationship information between the i-th core device and each first network device; determining a network device having a direct physical neighbor relationship with the i-th core device according to the neighbor relationship information between the i-th core device and each first network device; and determining a logical topology graph between network devices in the target network area according to the network devices having a direct physical neighbor relationship with N core devices.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a network device management method and device, electronic equipment and a storage medium. BACKGROUND

[0002] With the development of technology, the scale of network architecture gradually expands. In order to facilitate the management and maintenance of network devices in a region, a logical topology diagram between network devices in the region can be drawn. The network topology diagram presents complex network structures in a graphical manner, enabling network administrators to intuitively see the positions of various nodes (such as computers, servers, switches, routers, etc.) in the network and their connection relationships with each other. This graphical representation not only helps to understand the physical layout of the network, but also displays logical connections, thereby providing convenience for fault diagnosis, resource optimization, security protection, etc.

[0003] However, when drawing a logical topology diagram between network devices in a region, the relevant information of all devices in the region needs to be collected. When the number of network devices in the region is large, the data processing amount during the drawing of the logical topology diagram is further increased, thereby reducing the drawing speed. SUMMARY

[0004] The embodiments of the present application provide a network device management method and device, electronic equipment and a storage medium to solve the problem in the prior art that when drawing a logical topology diagram between network devices in a region, the relevant information of all devices in the region needs to be collected, thereby causing a large data processing amount and slow drawing speed.

[0005] In a first aspect, the embodiments of the present application provide a network device management method, which comprises:

[0006] Obtaining intermediate system to intermediate system (IS-IS) topology information of an i-th core device in a target network region, wherein the IS-IS topology information of the i-th core device comprises neighbor relationship information between the i-th core device and each first network device, the first network device comprises a network device in the target network region except the i-th core device, i takes each integer value from 1 to N, and N represents the number of core devices in the target network region;

[0007] According to the neighbor relationship information between the i-th core device and each first network device, determining a network device having a direct physical neighbor relationship with the i-th core device;

[0008] According to the obtained network devices having a direct physical neighbor relationship with the N core devices, a logical topology graph between the network devices in the target network area is determined.

[0009] Optionally, the neighbor relationship information of the ith core device and the jth first network device comprises: a first identifier corresponding to a kth path, a second identifier corresponding to the kth path, and a target interface corresponding to the kth path.

[0010] The kth path is a path with the ith core device as a starting point device and the jth first network device as a terminal device, k is an integer from 1 to L, and L represents the number of paths between the ith core device and the jth first network device.

[0011] The first identifier represents an identifier of the terminal device of the kth path.

[0012] The second identifier represents an identifier of a next-hop device of the starting point device on the kth path.

[0013] The target interface represents an interface of the starting point device connecting the device represented by the second identifier.

[0014] j is an integer from 1 to M, and M represents the number of first network devices.

[0015] The determining, according to the neighbor relationship information of the ith core device and each first network device, of network devices having a direct physical neighbor relationship with the ith core device comprises:

[0016] In a case where the first identifier and the second identifier are the same, it is determined that the network device having a direct physical neighbor relationship with the ith core device through the target interface comprises the jth first network device.

[0017] In a case where the first identifier and the second identifier are different, it is determined that the network device having an indirect physical neighbor relationship with the ith core device through the target interface comprises the jth first network device.

[0018] Optionally, the method further comprises:

[0019] Obtaining target information of each network device in the target network area;

[0020] Marking the target information in the logical topology graph;

[0021] The target information comprises at least one of the following:

[0022] Device identifier, IS-IS neighbor protocol state, interface logical number, link usage rate, link protocol state, interface cyclic redundancy check (CRC) error code, interface optical module optical attenuation value.

[0023] Optionally, the method further comprises:

[0024] generating an inspection report according to the target information;

[0025] The inspection report comprises at least one of the following:

[0026] The total number of interfaces, the number of abnormal interfaces, the ID of an abnormal interface, the ID of an interface with a CRC error code exceeding a first threshold, the number of CRC error codes, the ID of an interface with a link usage rate exceeding a second threshold, and the ID of an interface with an IS-IS neighbor state exception.

[0027] Optionally, the method further comprises:

[0028] pushing the inspection report to a predetermined communication address.

[0029] Optionally, the method further comprises:

[0030] prompting the interfaces indicated as abnormal in the inspection report in the logical topology diagram.

[0031] Optionally, the IS-IS topology information of the ithcore device in the target network area is acquired by:

[0032] acquiring the IS-IS topology information of the ithcore device in the target network area through a collection instruction recognizable by a network device in the target network area.

[0033] In a second aspect, an embodiment of the present application provides a network device management apparatus, the apparatus comprising:

[0034] a data collection module configured to acquire intermediate system to intermediate system (IS-IS) topology information of an ithcore device in a target network area, wherein the IS-IS topology information of the ithcore device comprises neighbor relationship information of the ithcore device and each first network device, the first network device comprising a network device in the target network area other than the ithcore device, i being an integer from 1 to N, N representing the number of core devices in the target network area;

[0035] an IS-IS network logical topology mapping module configured to:

[0036] determine a network device having a direct physical neighbor relationship with the ithcore device according to the neighbor relationship information of the ithcore device and each first network device.

[0037] According to the network devices having the direct physical neighbor relationship with the N core devices, a logical topology graph between the network devices in the target network area is determined.

[0038] In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a transceiver, and a processor:

[0039] The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the management method of the network device in the first aspect.

[0040] In a fourth aspect, an embodiment of the present application provides a readable storage medium, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the management method of the network device in the first aspect.

[0041] In the embodiment of the present application, the IS-IS topology information of the i th core device in the target network area can be acquired, wherein the IS-IS topology information of the i th core device includes the neighbor relationship information between the i th core device and each first network device, the first network device includes the network device in the target network area except the i th core device, i takes each integer from 1 to N, and N represents the number of core devices in the target network area; thus, the network device having the direct physical neighbor relationship with the i th core device can be determined according to the neighbor relationship information between the i th core device and each first network device; and then the logical topology graph between the network devices in the target network area can be determined according to the network devices having the direct physical neighbor relationship with the N core devices.

[0042] It can be seen that, in the embodiment of the present application, when the logical topology graph between the network devices in the target network area is determined, the related information of all network devices in the region does not need to be collected, only the IS-IS topology information of the core device in the region needs to be collected, and then the neighbor relationship between each network device in the region can be determined based on the IS-IS topology information of each core device, and the logical topology graph between the network devices in the region can be determined. Therefore, in the embodiment of the present application, when the logical topology graph between the network devices is determined, the data collection amount can be reduced, the data processing amount can be reduced, and then the determination speed of the logical topology graph can be accelerated. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of these drawings.

[0044] Figure 1 The flow chart of the management method of the network device provided in the embodiments of the present application is shown in the figure.

[0045] Figure 2 The first example of the logical topology graph of the target network area in the embodiments of the present application is shown in the figure.

[0046] Figure 3 The second example of the logical topology graph of the target network area in the embodiments of the present application is shown in the figure.

[0047] Figure 4 The third example of the logical topology graph of the target network area in the embodiments of the present application is shown in the figure.

[0048] Figure 5 The structural block diagram of the management device of the network device provided in the embodiments of the present application is shown in the figure.

[0049] Figure 6 The schematic diagram of the specific implementation of the management device of the network device provided in the embodiments of the present application is shown in the figure.

[0050] Figure 7 The structural block diagram of the electronic device provided in the embodiments of the present application is shown in the figure. DETAILED DESCRIPTION

[0051] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that there are three cases of A alone, A and B together, and B alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0052] In the embodiments of the present application, the term "a plurality of" means two or more, and other quantifiers are similar.

[0053] The technical solutions in the embodiments of the present application will be described clearly and completely in the following description of the embodiments of the present application in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0054] The embodiment of the present application provides a network device management method and device, electronic equipment and storage medium, to solve the problem that in the prior art, when a logical topology graph between network devices in a region is drawn, related information of all devices in the region needs to be collected, thereby causing large data processing amount and slow drawing speed.

[0055] The method and the device are based on the same application concept, and since the principles of the method and the device for solving problems are similar, the implementation of the device and the method can be referred to each other, and the repeated parts will not be described herein.

[0056] Figure 1 A flowchart of a network device management method provided by the embodiment of the present application is shown, and the method can include the following steps 101 to 103.

[0057] Step 101: Obtain intermediate system to intermediate system (IS-IS) topology information of an i th core device in a target network region.

[0058] It should be noted that the intermediate system to intermediate system (IS-IS) protocol is an interior gateway protocol (IGP) based on link state and using a shortest path first (SPF) algorithm for routing calculation. Each network device (for example, a router) running the IS-IS protocol generates a link state protocol data unit (LSPDU) containing link state information of all IS-IS protocol enabled interfaces of the network device, and through establishing an IS-IS adjacency relationship with adjacent devices, the local device link state database (LSDB) is updated, so that the LSDB can be synchronized with the LSDB of other devices in the entire IS-IS network. Based on the synchronization of the LSDB, each network device in the domain can obtain IS-IS topology information and update the link state protocol (LSP) in time.

[0059] In the embodiment of the present application, the IS-IS topology information of the i th core device includes neighbor relationship information of the i th core device and each first network device, the first network device includes a network device in the target network region except the i th core device, i is each integer in 1 to N, and N represents the number of core devices in the target network region.

[0060] In addition, in order to support a large-scale routing network, IS-IS adopts a hierarchical structure of two levels of backbone area and non-backbone area in an autonomous system. Generally, Level-1 network devices are deployed in a non-backbone area, Level-2 network devices and Level-1-2 network devices are deployed in a backbone area, and each non-backbone area is connected to the backbone area through a Level-1-2 network device. In order to ensure the continuity of the backbone area, the network devices of Level-2 in the routing domain must be physically continuous, and all network devices of Level-2 (i.e., forming a Level-2 neighbor relationship) form the backbone network of the routing domain.

[0061] Optionally, the target network area includes the backbone area, i.e., in the embodiment of the present application, a logical topology graph between the network devices in the backbone area can be drawn.

[0062] Step 102: determining the network devices having a direct physical neighbor relationship with the i-th core device according to the neighbor relationship information of each first network device and the i-th core device.

[0063] The neighbor relationship information of each first network device and the i-th core device can indicate which first network devices have a direct physical neighbor relationship with the i-th core device. After the network devices having a direct physical neighbor relationship with each core device in the target network area are determined, a logical topology graph of the target network area can be drawn based on this.

[0064] Step 103: determining a logical topology graph between the network devices in the target network area according to the obtained network devices having a direct physical neighbor relationship with the N core devices.

[0065] That is, according to the obtained network devices having a direct physical neighbor relationship with the N core devices, a logical topology graph between the network devices in the target network area can be drawn.

[0066] It should be noted that the target network area includes a plurality of network devices, and the core devices in the target network area have been set up between the network devices in the target network area. Therefore, the core devices in the target network area are predetermined.

[0067] The core devices relay data in the transmission process between the network devices. Therefore, the core devices and some other network devices can have a direct physical neighbor relationship. Thus, based on the network devices having a direct physical neighbor relationship with each core device, a logical topology graph of the target network area can be drawn.

[0068] For example Figure 2As shown in the first example, Router A and Router B are core devices, then based on Router B, Router C, Router D, Router E, Router F which have direct physical relationship with Router A, and Router A, Router C, Router D, Router E, Router F which have direct physical relationship with Router B, the logical topology diagram shown in the first example can be drawn.

[0069] For example Figure 3 As shown in the second example, Router A and Router B are core devices, then based on Router B, Router C, Router D which have direct physical relationship with Router A, and Router A, Router E, Router F which have direct physical relationship with Router B, the logical topology diagram shown in the second example can be drawn.

[0070] For example Figure 4 As shown in the third example, Router A, Router B, Router E are core devices, then based on Router B, Router C which have direct physical relationship with Router A, and Router A, Router D which have direct physical relationship with Router B, and Router C, Router D which have direct physical relationship with Router E, the logical topology diagram shown in the third example can be drawn.

[0071] It can be seen that in the embodiments of the present application, the related information of all network devices in the region does not need to be collected, and only the IS-IS topology information of the core devices in the region needs to be collected, so that the logical topology diagram between the network devices in the region can be drawn, the data collection amount is reduced, the data processing amount is reduced, and the drawing speed of the logical topology diagram is further accelerated.

[0072] From the above steps 101 to 103, in the embodiments of the present application, the IS-IS topology information of the i-th core device in the target network region can be obtained, wherein the IS-IS topology information of the i-th core device includes the neighbor relationship information of the i-th core device and each first network device, the first network device includes the network device in the target network region except the i-th core device, i takes each integer from 1 to N, and N represents the number of core devices in the target network region; then the network device having direct physical neighbor relationship with the i-th core device is determined according to the neighbor relationship information of the i-th core device and each first network device; and further the logical topology diagram between the network devices in the target network region is determined according to the obtained network devices having direct physical neighbor relationship with the N core devices.

[0073] It can be seen that, in the embodiment of the present application, when determining the logical topology graph between the network devices in the target network area, the related information of all network devices in the area does not need to be collected, and only the IS-IS topology information of the core devices in the area needs to be collected. Based on the IS-IS topology information of each core device, the neighbor relationship between each network device in the area can be determined, and then the logical topology graph between the network devices in the area can be determined. Therefore, when determining the logical topology graph between the network devices, the embodiment of the present application can reduce the amount of data collection, thereby reducing the amount of data processing, and then the determination speed of the logical topology graph can be accelerated.

[0074] In addition, in the prior art, a traditional network topology is generally drawn based on physical logical connection, while the embodiment of the present application is drawn based on the protocol of IS-IS, avoiding the scenario that the state of the physical link and the state of the system interface protocol are inconsistent after the long-distance physical link between devices passes through the transmission wave division system.

[0075] Optionally, the neighbor relationship information between the i-th core device and the j-th first network device includes: a first identifier corresponding to a k-th path, a second identifier corresponding to the k-th path, and a target interface corresponding to the k-th path.

[0076] The k-th path is a path with the i-th core device as a starting point device and the j-th first network device as a terminal device, k is an integer from 1 to L, and L represents the number of paths between the i-th core device and the j-th first network device.

[0077] The first identifier represents the identifier of the terminal device of the k-th path.

[0078] The second identifier represents the identifier of the next hop device of the starting point device on the k-th path.

[0079] The target interface represents the interface of the starting point device connected to the device represented by the second identifier.

[0080] The value of j is each integer from 1 to M, and M represents the number of first network devices.

[0081] In the step 102, the network device having a direct physical neighbor relationship with the i-th core device is determined according to the neighbor relationship information between the i-th core device and each first network device, including the following steps A-1 to A-2:

[0082] Step A-1: in the case that the first identifier is the same as the second identifier, determining that the network device having a direct physical neighbor relationship with the ith core device through the target interface comprises the jth first network device (i.e., if the first identifier is the same as the second identifier, it can be determined that the ith core device has a direct physical neighbor relationship with the jth first network device through the target interface).

[0083] Step A-2: in the case that the first identifier is different from the second identifier, determining that the network device having an indirect physical neighbor relationship with the ith core device through the target interface comprises the jth first network device (i.e., if the first identifier is different from the second identifier, it can be determined that the ith core device has an indirect physical neighbor relationship with the jth first network device through the target interface).

[0084] Wherein, the identifier of the device can be a system ID.

[0085] In order to facilitate the understanding of the above steps A-1 to A-2, the process of determining the network device having a direct physical neighbor relationship with each core device is introduced based on the example shown in Figures 2 to 4

[0086] For example Figure 2 The first example shown in Table 1, RouterA, RouterB is a core device, and the IS-IS topology information of RouterA collected and the conclusion obtained based on the topology information can be as shown in Table 1:

[0087] Table 1: IS-IS topology information and conclusion of RouterA

[0088]

[0089]

[0090]

[0091] It should be noted that each piece of data in Table 1 corresponds to a path.

[0092] Based on the conclusion in Table 1, it can be determined that RouterA has a direct physical neighbor relationship with RouterB through Interface-a, and RouterA has a direct physical neighbor relationship with RouterC, RouterD, RouterE and RouterF through Interface-x.

[0093] ​Similarly, based on the collected IS-IS topology information of Router B, we can find that Router B and Router A have a direct physical neighbor relationship through Interface-b, and Router B has a direct physical neighbor relationship with Router C, Router D, Router E, and Router F through Interface-y.

[0094] Thus, based on the above content, we can get Figure 2 The logical topology diagram of the first example is shown.

[0095] For example Figure 3 In the second example shown, RouterA and RouterB are core devices. The IS-IS topology information collected from RouterA and the conclusions obtained based on the topology information are shown in Table 2:

[0096] Table 2 IS-IS topology information and conclusions of RouterA

[0097]

[0098]

[0099] Based on the conclusions in Table 2, RouterA and RouterB are direct physical neighbors through Interface-a, and RouterA, RouterC, and RouterD are direct physical neighbors through Interface-x.

[0100] Similarly, based on the collected IS-IS topology information of RouterB, we can find that RouterB and RouterA have a direct physical neighbor relationship through Interface-b, and RouterB has a direct physical neighbor relationship with RouterE and RouterF through Interface-y.

[0101] Furthermore, as shown in Table 2, the data 2 in the neighbor relationship information between RouterA and RouterE indicates that RouterD is on the path between RouterA and RouterE. Therefore, RouterD and RouterE are connected. Similarly, the data 2 in the neighbor relationship information between RouterA and RouterF indicates that RouterC is on the path between RouterA and RouterF. Therefore, RouterC and RouterF are connected.

[0102] Thus, based on the above content, we can get Figure 3 The logical topology diagram of the second example is shown.

[0103] For example Figure 4 In the third example shown, RouterA, RouterB and RouterE are core devices, the collected IS-IS topology information of RouterA and the conclusions based on the topology information can be shown in Table 3:

[0104] Table 3 IS-IS topology information of RouterA and conclusions

[0105]

[0106]

[0107] Based on the conclusions in Table 3, it can be concluded that RouterA and RouterB have a direct physical neighbor relationship through Interface-a1, and RouterA and RouterC have a direct physical neighbor relationship through Interface-a2.

[0108] Similarly, according to the collected IS-IS topology information of RouterB, it can be concluded that RouterB and RouterA have a direct physical neighbor relationship through Interface-b1, and RouterB and RouterD have a direct physical neighbor relationship through Interface-b2.

[0109] Similarly, according to the collected IS-IS topology information of RouterE, it can be concluded that RouterE and RouterC have a direct physical neighbor relationship through Interface-e1, and RouterE and RouterF have a direct physical neighbor relationship through Interface-42.

[0110] In this way, based on the above content, the logical topology graph of the third example shown can be obtained. Figure 4

[0111] It should be noted that in addition, Figure 4 The above expression represents a physical continuous IS-IS protocol ring neighbor network topology scenario that may exist with 5 or more devices, which is extremely rare in real network topology planning. Large networks are generally built by planning Autonomous System (AS).

[0112] Optionally, the method further comprises:

[0113] Obtaining target information of each network device in the target network area;

[0114] Labeling the target information in the logical topology graph; ​

[0115] The target information includes at least one of the following:

[0116] Device identifier, IS-IS neighbor protocol status, interface logical number, link usage rate, link protocol status, interface cyclic redundancy check (CRC) error code, interface optical module optical attenuation value.

[0117] In addition, the IS-IS neighbor protocol status indicates whether the neighbor relationship between two network devices is normal. For example, the IS-IS neighbor protocol status is 1, indicating that the neighbor relationship between two network devices is normal, and the IS-IS neighbor protocol status is 0, indicating that the neighbor relationship between two network devices is disconnected or abnormal.

[0118] The interface logical number indicates the logical number of the interface of the network device that starts the IS-IS protocol.

[0119] The link usage rate can also be referred to as a broadband usage rate.

[0120] As described above, in the embodiments of the present application, the target information of each network device in the target network area can also be obtained, so that after the logical topology graph is drawn, the target information of each network device is marked in the logical topology graph. In this way, the target information of each network device can be directly viewed through the logical topology graph.

[0121] The target information of the network device can be marked in a region corresponding to the network device; or a touch switch can be set at (or near) the icon position of the network device in the logical topology graph. Clicking the touch switch can display the target information of the network device.

[0122] Optionally, the method further includes:

[0123] Generating an inspection report according to the target information;

[0124] The inspection report includes at least one of the following:

[0125] Total number of interfaces, number of abnormal interfaces, abnormal interface identifier (ID), interface ID whose CRC error code exceeds a first threshold value, number of CRC error codes, interface ID whose link usage rate exceeds a second threshold value, interface ID whose interface optical module optical attenuation value is not in a predetermined range, interface ID whose link protocol status is abnormal, interface ID whose IS-IS neighbor status is abnormal.

[0126] In addition, the total number of interfaces indicates a number of interfaces of all network devices in the target network area starting the IS-IS protocol; and the abnormal interface indicates an abnormal interface in the interfaces of all network devices in the target network area starting the IS-IS protocol, wherein the abnormal interface can be determined according to at least one of a link usage rate, a link protocol state, a CRC error code, and an interface optical module optical attenuation value, for example, an interface with a CRC error code exceeding a first threshold value, an interface with a link usage rate exceeding a second threshold value, an interface with an interface optical module optical attenuation value not in a predetermined range, an interface with an abnormal link protocol state, and an interface with an abnormal IS-IS neighbor state.

[0127] In addition, different types of abnormal interfaces (for example, an interface with a CRC error code exceeding a first threshold value, an interface with a link usage rate exceeding a second threshold value, an interface with an interface optical module optical attenuation value not in a predetermined range, an interface with an abnormal link protocol state, and an interface with an abnormal IS-IS neighbor state) in the abnormal interfaces can be classified and counted.

[0128] As can be seen from the above, in the embodiments of the present application, the target information of each network device in the target network area can be used to generate the inspection report, so that relevant personnel can view the relevant situation of the abnormal interface from the inspection report, so as to timely process the abnormal situation.

[0129] It can be understood that the target information of each network device in the logical topology diagram of the target network area can be periodically updated, so that the inspection report can be periodically updated; or the target information of each network device in the logical topology diagram of the target network area can also be manually triggered to update, so that the inspection report can be periodically updated.

[0130] Optionally, the method further comprises:

[0131] The inspection report is pushed to a predetermined communication address.

[0132] For example, the inspection report can be pushed to a communication address of a relevant user in an instant messaging application, so that relevant personnel can view the relevant situation of the abnormal interface from the inspection report in a timely manner, so as to timely process the abnormal situation.

[0133] Optionally, the method further comprises:

[0134] The interface indicated as abnormal in the inspection report is prompted in the logical topology diagram.

[0135] Among them, different ways can be adopted for prompting according to the abnormal type corresponding to the abnormal interface, for example, the interface of disconnection (Down) can be marked red, and the interface whose link utilization rate exceeds the second threshold can be marked yellow.

[0136] Therefore, the abnormal interface can be prompted in the logical topology diagram, so that the abnormal interface can be clearly and obviously viewed in the logical topology diagram, to facilitate the active inspection of the operation and maintenance personnel.

[0137] Optionally, the IS-IS topology information of the i-th core device in the target network area is acquired by:

[0138] The IS-IS topology information of the i-th core device in the target network area is acquired by a collection instruction recognizable by the network device in the target network area.

[0139] Exemplarily, a client of a network configuration protocol (NETCONF) or a client of a command-line interface (CLI) such as SecureCRT / Putty can be used to send a collection instruction in a manner of a remote connection tool (SSH) or a remote login system (Telnet), so as to acquire the IS-IS topology information through the collection quality. For example, the collection instruction can include at least one of the following:

[0140] 1. An instruction for collecting IS-IS topology information: show isis topology;

[0141] 2. An instruction for collecting IS-IS neighbor state: show isis adjacency;

[0142] 3. An instruction for collecting device interface information: show interface|include protocol|Description|BW|Intf|CRC;

[0143] 4. An instruction for collecting device interface module information: show intf-statistics utilizationphy-interface-only.

[0144] It should be noted that the above SecureCRT is a terminal emulation program supporting SSH; Putty is a free and open source terminal emulator, serial console and network file transfer application, which supports common connection protocols such as SSH, Telnet, etc.

[0145] In addition, in the prior art, when drawing a logical topology graph by collecting global network equipment and topology information through a conventional Simple Network Management Protocol (SNMP) or a Link Layer Discovery Protocol (LLDP), only a few collection instructions need to be executed at the core equipment side (generally two devices serving as a master and a backup) to complete the collection of IS-IS topology information (Ms millisecond level) in the embodiment of the application, and the topology can be quickly and agilely updated after the information comparison.

[0146] The above introduces the management method of the network equipment provided by the embodiment of the application, and the management device of the network equipment provided by the embodiment of the application will be introduced below in combination with the drawings.

[0147] Referring to Figure 5 The embodiment of the application further provides a management device of a network equipment, and the device comprises:

[0148] The data collection module 501 is configured to acquire intermediate system to intermediate system (IS-IS) topology information of an i-th core equipment in a target network area, wherein the IS-IS topology information of the i-th core equipment comprises neighbor relationship information between the i-th core equipment and each first network equipment, the first network equipment comprises network equipment in the target network area except the i-th core equipment, i is an integer from 1 to N, and N represents the number of core equipments in the target network area.

[0149] The IS-IS network logical topology drawing module 502 is configured to:

[0150] According to the neighbor relationship information between the i-th core equipment and each first network equipment, determine network equipment having a direct physical neighbor relationship with the i-th core equipment.

[0151] According to the obtained network equipment having a direct physical neighbor relationship with the N core equipments, determine a logical topology graph between the network equipment in the target network area.

[0152] Therefore, in the embodiment of the present application, the data collection module 501 can obtain the IS-IS topology information of the i th core device in the target network area, wherein the IS-IS topology information of the i th core device includes the neighbor relationship information between the i th core device and each first network device, the first network device includes the network device in the target network area except the i th core device, i is each integer in 1 to N, and N represents the number of core devices in the target network area; so that the IS-IS network logical topology drawing module 502 determines the network device having a direct physical neighbor relationship with the i th core device according to the neighbor relationship information between the i th core device and each first network device; and then determines the logical topology graph between the network devices in the target network area according to the obtained network devices having a direct physical neighbor relationship with the N core devices.

[0153] It can be seen that, in the embodiment of the present application, when determining the logical topology graph between the network devices in the target network area, the related information of all network devices in the region does not need to be collected, only the IS-IS topology information of the core device in the region needs to be collected, and then the neighbor relationship between each network device in the region can be determined based on the IS-IS topology information of each core device, and the logical topology graph between the network devices in the region can be determined. Therefore, in the embodiment of the present application, when determining the logical topology graph between the network devices, the data collection amount can be reduced, so that the data processing amount can be reduced, and then the drawing speed of the logical topology graph can be accelerated.

[0154] Optionally, the neighbor relationship information between the i th core device and the j th first network device includes: a first identifier corresponding to the k th path, a second identifier corresponding to the k th path, and a target interface corresponding to the k th path;

[0155] The k th path is a path taking the i th core device as a starting point device and taking the j th first network device as a terminal device, k is an integer from 1 to L, and L represents the number of paths between the i th core device and the j th first network device;

[0156] The first identifier represents the identifier of the terminal device of the k th path;

[0157] The second identifier represents the identifier of the next hop device of the starting point device on the k th path;

[0158] The target interface represents the interface of the starting point device connecting the device represented by the second identifier;

[0159] j is each integer in 1 to M, and M represents the number of first network devices;

[0160] The IS-IS network logical topology mapping module 502 determines, according to the neighbor relationship information of the i-th core device and each first network device, a network device having a direct physical neighbor relationship with the i-th core device, including:

[0161] In a case where the first identifier is the same as the second identifier, the network device having a direct physical neighbor relationship with the i-th core device through the target interface includes the j-th first network device.

[0162] In a case where the first identifier is different from the second identifier, the network device having an indirect physical neighbor relationship with the i-th core device through the target interface includes the j-th first network device.

[0163] Optionally, the data acquisition module 501 is further configured to:

[0164] acquire target information of each network device in the target network area;

[0165] label the target information in the logical topology graph;

[0166] The target information includes at least one of the following:

[0167] device identifier, IS-IS neighbor protocol state, interface logical number, link usage rate, link protocol state, interface cyclic redundancy check (CRC) error code, interface optical module optical attenuation value.

[0168] Optionally, the apparatus further includes:

[0169] a monitoring and alarming module configured to generate a patrol report according to the target information;

[0170] The patrol report includes at least one of the following:

[0171] total number of interfaces, number of abnormal interfaces, abnormal interface identifier (ID), interface ID whose CRC error code exceeds a first threshold, number of CRC error codes, interface ID whose link usage rate exceeds a second threshold, interface ID whose interface optical module optical attenuation value is not within a predetermined range, interface ID whose link protocol state is abnormal, interface ID whose IS-IS neighbor state is abnormal.

[0172] Optionally, the apparatus further includes:

[0173] a monitoring and alarming module configured to push the patrol report to a predetermined communication address.

[0174] Optionally, the apparatus further includes:

[0175] The monitoring alarm module is used to prompt the interface indicated as abnormal in the inspection report in the logical topology diagram.

[0176] Optionally, the data acquisition module 501 is specifically configured to:

[0177] The IS-IS topology information of the i-th core device in the target network area is obtained through a collection instruction recognizable by the network devices in the target network area.

[0178] In summary, the specific implementation of the network device management device of the embodiment of the present application can be described as follows:

[0179] like Figure 6 As shown, the management device of the network device includes the following modules:

[0180] The data collection module is responsible for collecting IS-IS topology information and target information of network devices (i.e., routing devices) from the target network area. The IS-IS topology information includes neighbor relationship information (i.e., the first identifier, second identifier, and target interface mentioned above). The target information includes device identifier, IS-IS neighbor protocol status, interface logical number, link utilization rate, link protocol status, interface CRC error code, and interface optical module optical attenuation value.

[0181] The data storage module uses a graph database to store IS-IS topology information of network devices and a time series database to store target information;

[0182] It should be noted that a graph database is a database that uses a graph structure for semantic queries. It uses vertices, edges, and properties to represent and store data. A vertex is an abstraction of an object, generally referring to an entity, such as the router in the embodiment of this application. An edge is a relationship between two vertices, either directed or undirected, such as the connection line between the routers in the embodiment of this application. A vertex's property is a specific description of an object. Depending on the type of vertex, each vertex can have different properties, such as the first identifier, second identifier, and target interface in the embodiment of this application.

[0183] A time series database (TSD) is a database that stores data sets recorded in chronological order. Time series data refers to data collected, recorded, or observed over a period of time at specific time intervals or timestamps. Time series data typically consists of two main components: a timestamp and the corresponding collected value. The timestamp represents the time point or time period of the data point and can be in the form of a date, time, or timestamp; the collected value is the numerical value or indicator measured or recorded at a given time point or time period.

[0184] The data collection module can provide two modes of timing collection (3-5 minutes) and immediate collection, and both collection actions will trigger the start of the IS-IS network logical topology mapping module to update the logical topology map in time. The network device generally provides two query display modes of detail and brief, and all collection instructions are executed in the brief mode for fast data collection (milliseconds, Ms). Among them, the collection instructions can be as described above, and will not be described here.

[0185] The IS-IS network logical topology mapping module is composed of a mapping submodule and a labeling submodule. The mapping submodule is responsible for calling data from the graph database and analyzing and mapping the logical topology map of the IS-IS protocol, and labeling device identifiers (such as system IDs) and interface (Interface) logical numbers. The labeling submodule is responsible for calling target data from the time series database and labeling each item of information included in the target information in the logical topology map drawn by the mapping submodule. In addition, when labeling each item of information included in the target information, the labeling submodule can set a numerical interval for color labeling for the same item of information, that is, different colors are used to label values in different numerical intervals.

[0186] It should be noted that the specific process of the mapping submodule for mapping the logical topology map based on the IS-IS topology information can be referred to as described above, and will not be described here.

[0187] The monitoring and alarming module is responsible for inspecting the target information in the logical topology map and generating and pushing an inspection report. The inspection report includes the total number of interfaces, the number of abnormal interfaces, the abnormal interface identifier ID, the interface ID whose CRC error code exceeds the first threshold value, the CRC error code number, the interface ID whose link usage rate exceeds the second threshold value (for example, 70%), the interface ID whose interface optical module optical attenuation value is not within the predetermined range, the interface ID whose link protocol state is abnormal, and the interface ID whose IS-IS neighbor state is abnormal. The pushing mode includes at least one of the following: instant messaging APP message, short message, email, and network management system. In addition, the monitoring and alarming module can also alarm the abnormal interface.

[0188] Optionally, the IS-IS network logical topology mapping module can use different ways to label according to the abnormal type of the abnormal interface, for example, the interface that is down can be labeled red, and the interface whose link usage rate exceeds the second threshold value can be labeled yellow.

[0189] Optionally, after the IS-IS network logical topology mapping module draws the logical topology map that standardizes the above-mentioned target information, the monitoring and alarming module is triggered to perform an inspection action, thereby triggering an alarm.

[0190] In addition, with the rapid development of business, the network quality requirement is also higher and higher under the impetus of the cloud change number transfer wave. At present, the network core equipment failure relies on the traditional log uploaded to the log server for analysis, cooperates with the SNMP information collection and pushes to the network management system, configures different processing priorities and alarm levels for different report contents to generate alarm work orders, and the alarm pushing process lasts too long (5-10 minutes for the highest level alarm), and there are hidden dangers such as log loss and slow processing due to the processing performance bottleneck of the log server (delay or not triggering the pushing). Therefore, in order to timely, accurately and intelligently grasp the health status of the core equipment and implement agile and automatic inspection, the management device of the network equipment is proposed.

[0191] In summary, compared with the prior art, the management device of the network equipment of the embodiment of the present application has the following beneficial effects:

[0192] (1) The IS-IS topology information is collected through the instructions recognizable by the network equipment, so as to analyze and draw the logical topology graph, and only a few instructions need to be executed on the core equipment side to complete the collection of the IS-IS topology information (millisecond level), and the topology can be quickly and agilely updated after the information comparison.

[0193] (2) On the basis of physical and logical connection, the protocol of IS-IS is drawn, which avoids the scene that the physical link state and system interface protocol state are inconsistent after the long-distance physical link between devices needs to pass through the transmission wave division system.

[0194] (3) The topology drawn in combination with the above target information (i.e. device identification, IS-IS neighbor protocol state, interface logical number, link usage rate, link protocol state, interface cyclic redundancy check (CRC) error code, and interface optical module optical attenuation value) can quickly and intuitively view the state information of each protocol interface, provides the prediction ability of fault occurrence, is beneficial to improve the fault handling efficiency and optimize the equipment maintenance plan, and can also facilitate the rapid inspection of the core network operation by the operation and maintenance personnel, and avoid the account authorization problem of the core equipment.

[0195] (4) The inspection result can be realized in real time visualization monitoring, and the inspection result can be automatically counted and generated into a report, and multiple index screening and classification are directly displayed, which is convenient for communication and management.

[0196] (5) can realize the automatic inspection of the core network device, including "the total number of interfaces, the number of abnormal interfaces, the abnormal interface identification ID, the interface ID of the CRC error code exceeding the first threshold value, the number of CRC error codes, the interface ID of the link usage rate exceeding the second threshold value, the interface ID of the interface optical module optical decay value not in the predetermined range, the interface ID of the link protocol state exception, the interface ID of the IS-IS neighbor state exception", etc. The network inspection and alarm can be completed in a few seconds, and the problems of low inspection efficiency, complex inspection results and long fault positioning time in the current core network device operation and inspection work are solved.

[0197] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, another division mode can be used. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0198] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various storage program codes.

[0199] It should be noted that the above device provided by the embodiments of the present application can realize all the method steps realized by the above method embodiments, and can achieve the same technical effects. Here, the same parts and beneficial effects in the method embodiments will not be described in detail.

[0200] The embodiments of the present application also provide an electronic device, as shown in the figure, the electronic device includes a memory 720, a transceiver 710, a processor 700; Figure 7

[0201] The memory 720 is used to store a computer program;

[0202] ​The transceiver 710 is configured to receive and send data under the control of the processor 700;

[0203] The processor 700 is used to read the computer program in the memory 720 and execute the network device management method described in the first aspect.

[0204] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by processor 700 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 710 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 when performing operations.

[0205] The processor 700 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 700 may also adopt a multi-core architecture.

[0206] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0207] An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method for managing the network device described in the first aspect above is implemented.

[0208] The computer readable storage medium can be any available medium or data storage that can be accessed by a processor including both volatile and nonvolatile media, removable and non-removable media, computer readable storage media, and computer readable transmission media. By way of example, and not limitation, computer readable media can comprise the following: magnetic storage media, such as custom (e.g., floppy disks), hard disks, magnetic tapes, and magnetic-based optical disks (e.g., Magneto-Optical (MO) disks); optical storage media, such as optical disks, including Compact Disk Read Only Memory (CD-ROM), Digital Versatile Disk (DVD), Blu-Ray Disk (BD), and holographic light disks; and semiconductor storage media, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory, and solid state drives (SSDs). Other computer readable media that can store data include the whole of or parts of machine, human, or computer generated data signals, computer generated data signals embodied in carrier waves, transitory signals, electromagnetic signals, or inductions signals (e.g., a data signal in which data is carried by a carrier wave, a transitory signal, an electromagnetic signal, or an induction signal).

[0209] Those skilled in the art will appreciate that embodiments of the present application can be readily used as a method, a system, or a computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, magnetic disks, optical storage media, and the like) embodying computer readable program code.

[0210] The computer readable program code can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the computer readable program code which execute on the computer, other programmable data processing apparatus, or other device implement the functions specified in the flowchart block or blocks. Figure 1 The flowchart and / or block diagram in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to the present application. In this regard, each block in the flowchart and / or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable Figure 1 The means for performing the function specified by one or more of the flowchart or block

[0211] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in a flowchart Figure 1 of flows or multiple flows and / or blocks Figure 1 of blocks or multiple blocks.

[0212] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the function specified in a flowchart Figure 1 of flows or multiple flows and / or blocks Figure 1 of blocks or multiple blocks.

[0213] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A management method of a network device, characterized by, The method comprises: obtaining intermediate system to intermediate system (IS-IS) topology information of an i-th core device in a target network area, wherein the IS-IS topology information of the i-th core device comprises neighbor relationship information of the i-th core device and each first network device, the first network device comprising a network device in the target network area except the i-th core device, i being each integer in 1 to N, N representing the number of core devices in the target network area; determining a network device having a direct physical neighbor relationship with the i-th core device according to the neighbor relationship information of the i-th core device and each first network device; determining a logical topology graph between network devices in the target network area according to the network device having a direct physical neighbor relationship with the N core devices; wherein the neighbor relationship information of the i-th core device and the j-th first network device comprises a first identifier corresponding to a k-th path, a second identifier corresponding to the k-th path, and a target interface corresponding to the k-th path; the k-th path is a path with the i-th core device as a starting point device and the j-th first network device as a terminal device, k being an integer from 1 to L, L representing the number of paths between the i-th core device and the j-th first network device; the first identifier represents an identifier of the terminal device of the k-th path; the second identifier represents an identifier of a next-hop device of the starting point device on the k-th path; the target interface represents an interface of the starting point device connected to the device represented by the second identifier; j is each integer in 1 to M, M representing the number of first network devices.

2. The method of claim 1, wherein, The determining of the network device having a direct physical neighbor relationship with the i-th core device according to the neighbor relationship information of the i-th core device and each first network device comprises: in the case that the first identifier and the second identifier are the same, determining that the network device having a direct physical neighbor relationship with the i-th core device through the target interface comprises the j-th first network device; in the case that the first identifier and the second identifier are different, determining that the network device having an indirect physical neighbor relationship with the i-th core device through the target interface comprises the j-th first network device.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: obtaining target information of each network device in the target network area; annotating the target information in the logical topology graph; wherein the target information comprises at least one of the following: device identifier, IS-IS neighbor protocol state, interface logical number, link usage rate, link protocol state, interface cyclic redundancy check (CRC) error code, and interface optical module optical attenuation value.

4. The method of claim 3, wherein, The method further comprises: generating an inspection report according to the target information; wherein the inspection report comprises at least one of the following: The total number of interfaces, the number of abnormal interfaces, the abnormal interface identification ID, the interface ID whose CRC error exceeds the first threshold, the number of CRC errors, the interface ID whose link usage rate exceeds the second threshold, the interface ID whose interface optical module optical attenuation value is not in a predetermined range, the interface ID whose link protocol state is abnormal, and the interface ID whose IS-IS neighbor state is abnormal.

5. The method of claim 4, wherein, The method further includes: pushing the inspection report to a predetermined communication address.

6. The method of claim 4, wherein, The method further includes: prompting the interface indicated as abnormal in the inspection report in the logical topology graph.

7. The method according to claim 1 or 2, characterized in that, The method further includes: obtaining the IS-IS topology information of the ith core device in the target network area through a collection instruction recognizable by the network device in the target network area.

8. A management apparatus of a network device, characterized by comprising: The apparatus includes: a data collection module configured to obtain the IS-IS topology information of the ith core device in the target network area, wherein the IS-IS topology information of the ith core device includes the neighbor relationship information between the ith core device and each first network device, the first network devices include the network devices in the target network area except the ith core device, i is an integer from 1 to N, and N represents the number of core devices in the target network area; an IS-IS network logical topology mapping module configured to: determine the network devices having a direct physical neighbor relationship with the ith core device according to the neighbor relationship information between the ith core device and each first network device; determine the logical topology graph of the network devices in the target network area according to the network devices having a direct physical neighbor relationship with the N core devices; wherein the neighbor relationship information between the ith core device and the jth first network device includes a first identifier corresponding to the kth path, a second identifier corresponding to the kth path, and a target interface corresponding to the kth path; the kth path is a path with the ith core device as a starting point device and the jth first network device as a terminal device, k is an integer from 1 to L, and L represents the number of paths between the ith core device and the jth first network device; the first identifier represents the identifier of the terminal device of the kth path; the second identifier represents the identifier of the next-hop device of the starting point device on the kth path; the target interface represents the interface of the starting point device connected to the device represented by the second identifier; j is an integer from 1 to M, and M represents the number of first network devices.

9. An electronic device, comprising: The apparatus includes a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read the computer program in the memory and execute the management method of the network device according to any one of claims 1 to 7.

10. A readable storage medium, characterized by, The readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the management method of the network device according to any one of claims 1 to 7.

Images