WO2019079961A1

WO2019079961A1 - Method and device for determining shared risk link group

Info

Publication number: WO2019079961A1
Application number: PCT/CN2017/107448
Authority: WO
Inventors: 张耀坤; 孙春霞; 张大冬
Original assignee: 华为技术有限公司
Priority date: 2017-10-24
Filing date: 2017-10-24
Publication date: 2019-05-02
Also published as: CN109964450B; CN109964450A

Abstract

Disclosed in the embodiments of the present application are a method and device for determining a shared risk link group, the method comprising: acquiring a first log set of one or more network devices, the first log set comprising a log generated due to the restart of the network device(s) or the failure of an interface board of the network device(s); filtering logs in the first log set according to a log filtering rule so as to obtain a second log set; and acquiring from the second log set a first log generated by a first interface and a second log generated by a second interface, and determining that a first link corresponding to the first interface and a second link corresponding to the second interface belong to a same shared risk link group when determining that the first log and the second log meet a preset condition. By employing the embodiments of the present application, a shared risk link group may be conveniently and accurately determined, thereby reducing the risks of service transmission.

Description

Method and device for determining shared risk link group

Technical field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for determining a Shared Risk Link Group (SRLG).

Background technique

Some of the independent physical interfaces/links in the router network have the same risk of failure. When one physical interface/link fails, the physical interface/link with the same risk of failure will also be down. For example, some links pass the same optical transmission, and when a transmission failure occurs, these links are simultaneously down. These links can be referred to as shared risk links. If there are shared risk links on the two critical paths in the network (such as the active and standby paths used for link protection), after the same transmission, when the transmission failure occurs, the service protection at the router level will be completely invalid, resulting in comprehensive services. Interrupted.

In the prior art, the router industry has the concept and function of sharing a risk link group, and can manually set which links belong to the same SRLG, and have the same fault risk. Traffic mirroring (Traffic Engineering, TE) selects paths for hot backup, based on the CR-LDP (Consultation-based Routing Label Distribution Protocol (CR-LSP) or Fast Reroute (FRR) The Bypass tunnel is used as a tabu calculation. The shared risk link is not used as the primary and backup paths. However, which paths in the network belong to the same SRLG need to be recognized by humans; for various objective reasons, it is difficult to find out which links have the same risk regardless of whether the network server or the customer is provided. Therefore, although the SRLG function is currently available, it must be manually identified and manually added. It is very difficult to implement, and it is easy to cause the two links that are mutually backed up to share risks, and the risk of service transmission is high.

Summary of the invention

The technical problem to be solved by the embodiments of the present application is to provide a method and a device for determining a shared risk link group, so as to realize convenient and accurate determination of a shared risk link group and reduce service transmission risk.

In a first aspect, an embodiment of the present application provides a method for determining a shared risk link group, which may include:

Obtaining a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device restart or is not caused by an interface board failure of the network device;

Filtering the logs in the first log set according to the log filtering rule to obtain a second log set;

Obtaining a first log and a second log from the second log set, where the first log is a log generated by the first interface, and the second log is a log generated by the second interface, where When the first log and the second log meet the preset condition, the first link corresponding to the first interface and the second link corresponding to the second interface belong to the same shared risk link group.

By obtaining the first log set of one or more network devices in the network, the first log set can be filtered according to the log filtering rule by using the log analysis method at the network protocol (IP) level to obtain the network device. The log of the corresponding fault of the interface forms a second log set; thereby realizing the automatic identification of the transport layer The information, and then determining the shared risk link group in the second log set according to whether the preset condition is met, can save the customer from identifying a large amount of input of the SRLG, and can avoid the inaccuracy of human identification; and can also obtain the SRLG set according to the obtained Dynamically adjusting the service deployment, especially in the scenario where the shared risk link confirmation mechanism cannot be deployed based on IP lighting, has practical significance, and is a very useful supplement to the current SRLG function, which can significantly improve the stability and security of network service transmission.

In a possible implementation manner, the log filtering rule includes at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Filtering to obtain a log of the bidirectional forwarding detection up and/or bidirectional forwarding detection down of the physical interface; and

Filtering logs for running, managing, and maintaining OAM up and/or OAM down for physical interfaces.

Through the above various log rules, the useful information of the transport layer can be obtained, which is beneficial to narrowing the data range of the SRLG set mining and identification, and improving the effectiveness and efficiency of the information analysis.

In a possible implementation manner, determining that the first log and the second log meet predetermined conditions include:

Determining that the first log and the second log satisfy at least one of the following conditions:

The first log identifies that the status of the first interface changes to up, the second log identifies that the status of the second interface changes to up, the generation time of the first log, and the generation of the second log The interval of time is less than the first threshold;

The first log identifies that the status of the first interface changes to down, the second log identifies that the status of the second interface changes to down, the generation time of the first log, and the generation of the second log The interval of time is less than the second threshold;

The first log identifies that the first interface has an error, the second log identifies that the second interface has an error, and the interval between the first log generation time and the second log generation time is less than Third threshold

The first log identifies that the first interface is running, managing, and maintaining OAM up, the second log identifies that the second interface is OAM up, the first log is generated, and the second log is generated. The interval of generation time is less than the fourth threshold; and,

The first log identifies that the first interface is OAM down, the second log identifies that the second interface is OAM down, and the interval between the generation time of the first log and the second log is less than The fifth threshold.

By determining the SRLG through the above conditions, it is possible to accurately confirm the link with the shared risk, provide a reference for the customer or directly send it to the network device as a reference for path selection.

In a possible implementation manner, the second log set includes a network device identifier, a log generation interface, a log generation time, and a log occurrence event.

By carrying the network device identifier and the log generation interface, the log generation time, and the log occurrence event, the determining device can accurately know the location and type of the fault, thereby obtaining an accurate SRLG analysis and recognition result.

In a possible implementation manner, the method further includes:

Acquiring a third log from the second log set, where the third log is a log generated by the third interface;

When it is determined that the first log and the third log meet the preset condition, determining that the first link corresponding to the first interface and the third link corresponding to the third interface belong to the same shared risk link group;

When it is determined that the second log and the third log meet the preset condition, determining that the second link corresponding to the second interface and the third link corresponding to the third interface belong to the same shared risk link group.

When there are three or more interfaces, two methods may be performed according to preset conditions in a manner similar to the first aspect. The sharing risk between the interfaces is determined, so that a collection of SRLGs can be obtained, which is convenient for users and network devices to circumvent.

In a possible implementation manner, the method further includes:

The determined shared risk link group is reported to the user equipment for alarming.

The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device according to the indication of the user equipment.

In a second aspect, an embodiment of the present application provides an apparatus for determining a shared risk link group, which may include:

a transceiver unit, configured to acquire a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device or is not caused by an interface board failure of the network device;

a processing unit, configured to filter the logs in the first log set according to the log filtering rule to obtain a second log set, and obtain the first log and the second log from the second log set, where the first log is a log generated by the first interface, where the second log is a log generated by the second interface, and when it is determined that the first log and the second log meet a preset condition, determining that the first interface corresponds to The second link corresponding to the first link and the second interface belong to the same shared risk link group.

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

In a possible implementation manner, when it is determined that the first log and the second log meet a preset condition, the processing unit is specifically configured to:

In a possible implementation manner, the processing unit is further configured to:

When it is determined that the first log and the third log meet the preset condition, determining that the first link corresponding to the first interface and the third link corresponding to the third interface belong to the same shared risk link Group

In a third aspect, an embodiment of the present application provides an apparatus for determining a shared risk link group, which may include:

a processor, a memory, and a bus, wherein the processor and the memory are connected by a bus, wherein the memory is configured to store a set of program codes, the processor is configured to invoke program code stored in the memory, and execute the embodiment of the present application The steps of any of the implementations of the first aspect or the first aspect.

In a fourth aspect, an embodiment of the present application provides an apparatus for determining a shared risk link group, where the apparatus includes: a main control board and an interface board. The main control board includes: a first processor and a second memory. The interface board includes: a second processor, a second memory, and an interface card. The main control board is coupled to the interface board. The first memory can be used to store program code, and the first processor is configured to call the program code in the first memory to perform the following operations:

Obtaining a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device restarting or not being caused by an interface board failure of the network device; and the first log is generated according to a log filtering rule The log in the set is filtered to obtain a second log set, and the first log and the second log are obtained from the second log set, where the first log is a log generated by the first interface, and the second log is Determining, by the log generated by the second interface, the first link corresponding to the first interface and the second link corresponding to the second interface, when determining that the first log and the second log meet a preset condition Roads belong to the same shared risk link group.

The second memory can be used to store program code, and the second processor is configured to call the program code in the second memory to perform the following operations:

The trigger interface card sends a log acquisition message to one or more network devices to trigger the network device to return a log that is not caused by the network device restart or the interface board failure of the network device.

In a possible implementation manner, an inter-process communication (IPC) control channel is established between the main control board and the interface board.

In a fifth aspect, an embodiment of the present application provides a computer readable storage medium having instructions stored therein that, when run on a computer, implement any of the above first aspect or the first aspect The method in the possible implementation.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings to be used in the embodiments of the present application or the background art will be described below.

FIG. 1 is a schematic structural diagram of a system for determining an SRLG in an SDN network according to an embodiment of the present application;

2 is a schematic flowchart of a method for determining an SRLG according to an embodiment of the present disclosure;

FIG. 3 is a schematic flowchart of another method for determining an SRLG according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart of still another method for determining an SRLG according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of an apparatus for determining an SRLG according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of another apparatus for determining an SRLG according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of another apparatus for determining an SRLG according to an embodiment of the present application.

Detailed ways

The embodiments of the present application are described below in conjunction with the accompanying drawings in the embodiments of the present application.

The terms "comprising" and "having", and any variations thereof, are intended to cover a non-exclusive inclusion in the specification and claims of the application. For example, a process, method, system, product, or device that comprises a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or alternatively Other steps or units inherent to these processes, methods, products or equipment.

Referring to FIG. 1 , FIG. 1 is a schematic diagram of a system architecture for determining an SRLG in a Software Defined Network (SDN) according to an embodiment of the present application; the architecture of the SDN network including the SDN may be divided into top-down technologies. Five parts: application layer, northbound interface, control layer, southbound interface, and network device layer.

Application layer: including a variety of different services and applications, the application layer through the programming interface provided by the control layer to program the underlying devices, develop a variety of business applications, and achieve a variety of business innovation.

Northbound interface: connects the interface between the application layer and the control layer, so that various SDN applications can easily call the underlying network resources.

Control layer: It is the core of the entire SDN network. It centrally manages all the devices in the network and regards the entire network as a unified resource pool. It allocates resources flexibly and dynamically according to different needs of users and the global network topology. For the lower layer, communication with the network device layer is performed through a standard protocol; for the upper layer, the application layer is provided with control capability for network resources through an open interface.

Southbound interface: Connects the interface between the control layer and the network device to implement control over network device status and data traffic forwarding.

Network device layer: The hardware device layer, which contains all the physical devices in the network that make up the entire IT infrastructure, such as switches, routers, and so on. The network device layer is mainly responsible for data processing, forwarding, and the like.

In the embodiment of the present application, the control layer may include a controller, and the network device layer may include, but is not limited to, a network device such as a router, and may include, for example, a switch, a gateway device, and the like, in addition to the router shown in FIG. Other network devices such as security devices. Each router can be interconnected to form a router network topology that contains multiple paths.

It should be noted that the apparatus for determining the SRLG in the present application may be implemented by an SDN controller (SNC) or other back-end server in the SDN network; and in the ordinary router network, it may be processed by the main control center of each router. The Central Processing Unit (CPU) processes and is coordinated by different routers.

The method for determining the SRLG in the present application will be described in detail below with reference to FIGS. 2 to 3.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a method for determining an SRLG according to an embodiment of the present disclosure;

S201. Acquire a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device restart or is not caused by an interface board fault of the network device;

Optionally, log data of a specified network device or all networks in the network in a preset time period may be acquired. E.g, The preset time period may be one year or one month, and is not limited in any embodiment of the present application.

Optionally, when the first log set is obtained, in order to reduce the amount of data analyzed, the log of the network device restart may be excluded, such as the log of the physical interface up and/or down caused by the human operation shutdown; and the interface of the network device may also be excluded. A log such as a physical interface up and/or down caused by a board failure.

S202. Filter the logs in the first log set according to the log filtering rule to obtain a second log set.

S203: Obtain a first log and a second log from the second log set, where the first log is a log generated by the first interface, and the second log is a log generated by the second interface, where When it is determined that the first log and the second log meet the preset condition, the first link corresponding to the first interface and the second link corresponding to the second interface belong to the same shared risk link group.

Optionally, the log filtering rule includes at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Filtering to obtain a log of the bidirectional forwarding (BFD) detection of the physical interface and/or the bidirectional forwarding detection down; and

Filters the logs of the Operation, Administration, and Maintenance (OAM) up and/or OAM down of the physical interface.

BFD is a two-way forwarding detection mechanism that provides millisecond-level detection and fast detection of links. BFD can communicate with the upper-layer routing protocol to achieve fast convergence and ensure service continuity.

Ethernet OAM is a tool for monitoring network faults. It is mainly used to solve the link problems common in the last mile of Ethernet access. Users can monitor the link status between the two devices by enabling Ethernet OAM on two point-to-point devices.

Ethernet OAM can effectively improve the management and maintenance capabilities of Ethernet and ensure the stable operation of the network. Its main functions include:

1. Link performance monitoring: Monitors various performances of the link, including measurement of packet loss, delay, and jitter, and statistics on various types of traffic.

2. Fault detection and alarm: The link is detected by sending a detection packet, and the network administrator is notified when the link fails.

3. Loop test: The link fault is detected by the loopback of non-Ethernet OAM packets.

Optionally, if the various logs related to the network device are obtained in step S201, the log that excludes the restart of the network device may be excluded during the log filtering in step S202, such as the physical interface up and/or caused by the human operation shutdown. Down log; and can also exclude logs such as physical interface up and / or down caused by network board interface failure.

It should be noted that the above log filtering rules may be arbitrarily selected for use, or two or more combinations may be arbitrarily selected or used in combination. After filtering by the log filtering rule, you can obtain logs of related devices that are up and/or down with the physical interface, and then mine from it to get the SRLG.

Optionally, for ease of viewing and mining, the logs in the second log collection can be sorted by time. The second log set may include, but is not limited to, a network device identifier, a log generation interface, a log generation time, and a log occurrence event.

As shown in the following table, a possible form of the second log collection is given:

For example, the data in sequence number 1 indicates that the network device, that is, the router R14, is at 2017-06-15 17:51:30, and a CRC fault occurs on one interface GigabitEthernet0/8/7 on the device, and an error occurs. If a similar failure occurs on another interface at the same time, the two interfaces may be at risk.

After the second log set is obtained, the SRLG can be obtained from the log mining of each interface included in the log collection.

Optionally, taking the first log and the second log included in the second log set as an example, determining that the first log and the second log meet the preset conditions include:

The above various preset conditions can be selected for one use or used together.

It should be noted that, except that the two interfaces have the same fault condition at the same time, the link corresponding to the two interfaces can be regarded as a possible shared risk link group and recorded in the SRLG set. When different fault conditions occur at the same time, you can also consider the links corresponding to the two interfaces as possible shared risk link groups and record them to the SRLG. In the collection, especially when there are many times when different faults occur at the same time, the links corresponding to the two interfaces can be regarded as possible shared risk link groups.

It should be noted that the “simultaneous” described in the embodiments of the present application is not the same time in the strict sense. Due to factors such as the transmission time of the line, there may be very fine time difference between the two physical interfaces/links. Therefore, in the present application, "simultaneously" includes both the strict same time, and also includes two very close times at a small time difference such as 500 milliseconds or 1 second. The first threshold to the fifth threshold in the embodiment of the present application may be a smaller time difference or infinitely close to 0. The specific values of the five thresholds may be the same or different, and are not limited in any embodiment of the present application.

Optionally, the pseudo code of the preset condition may include the following parts:

That is, when the above-mentioned preset condition occurs, it returns true, and the first link, that is, the link A and the second link, that is, the link B, are regarded as possible shared risk link groups, and are recorded in the set of SRLG; If the default situation occurs, that is, if the conditions in the above preset conditions are not met, then false is returned, and link A and link B are regarded as non-shared risk link groups, and need not be recorded in the set of SRLG.

By obtaining the first log collection of one or more network devices in the network, you can filter the first log collection based on the log filtering rules by using the log analysis method at the IP level to obtain the log of the corresponding fault of the network device interface. The second log collection; thereby realizing the automatic identification of the useful information of the transport layer, and then determining the shared risk link group in the second log set according to whether the preset condition is met, thereby eliminating the large amount of investment of the customer to identify the SRLG, and avoiding artificial The inaccuracy of the identification; at the same time, the service deployment can be dynamically adjusted according to the obtained SRLG set, especially in the point where the shared risk link confirmation mechanism cannot be deployed based on the IP light addition, which has practical significance and is very useful supplement to the current SRLG function. It can significantly improve the stability and security of network service transmission.

Referring to FIG. 3, FIG. 3 is a schematic flowchart of another method for determining an SRLG according to an embodiment of the present disclosure. In this embodiment, steps S301-S303 are the same as steps S201-S203, and details are not described herein again. After step S303, the method further includes:

S304. Acquire a third log from the second log set, where the third log is a log generated by the third interface.

S305. When it is determined that the first log and the third log meet the preset condition, determine that the first link corresponding to the first interface and the third link corresponding to the third interface belong to the same sharing risk. Link group.

S306. When it is determined that the second log and the third log meet the preset condition, determine that the second interface corresponds to The second link and the third link corresponding to the third interface belong to the same shared risk link group.

The processing method of the second log set including the logs of the two interfaces is provided. When the fourth log is still present, the processing method is similar to the foregoing, and details are not described herein again. Through the comparison of the logs of the two interfaces and the preset conditions, the shared risk link groups that meet the preset conditions can be sequentially filtered out to generate a set of SRLGs.

Optionally, during the screening process, a shared risk link group relationship table may be generated according to the comparison with the preset conditions.

Then, according to the information in the shared risk link group relationship table, a set of shared risk link groups is output.

The shared risk link group relationship table includes identifiers of two links that fail simultaneously and frequency of simultaneous failures.

Specifically, the process of outputting the SRLG according to the second log set may include:

Input: the second log collection;

The detection time threshold time1: for example, 500 milliseconds or 1 second, it is considered that the two physical interfaces are up/down at the same time, and the risk may be shared.

Output: Shared Risk Link SRLG Collection

Step 1: Traverse the second log set and output the SRLG relationship table.

Step 2: Traverse the SRLG relational table and output all collections of SRLG

As shown in the following table, a possible form of SRLG relational table is given:

An example of a shared risk link group in the set of output SRLGs is as follows:

{R16.GigabitEthernet0/8/1, R11.GigabitEthernet1/1/0, R1.GigabitEthernet12/0/1}; indicates that the links corresponding to the above three interfaces are at risk.

Or it can be expressed as follows: {R3.GigabitEthernet0/3/0, R9.GigabitEthernet9/0/11}; indicates that the links corresponding to the above two interfaces have a common risk.

Referring to FIG. 4, FIG. 4 is a schematic flowchart of still another method for determining an SRLG according to an embodiment of the present disclosure. In this embodiment, steps S401-S406 are the same as steps S301-S306 in the embodiment shown in FIG. The details are not described herein again. After step S406, the method further includes:

S407. Report the shared risk link group to the user and perform an alarm.

S408. The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device after the user confirms.

That is, after the physical link of the possible co-risk transmission is determined by the method in the foregoing embodiment, it can be added to the SRLG set, which can be used for the customer to confirm the decision, or automatically send the SRLG set to the network device. Eliminate the process of customer identification.

Referring to FIG. 5, it is a schematic diagram of a device for determining an SRLG according to an embodiment of the present disclosure;

The transceiver unit 100 is configured to acquire a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device or is not caused by an interface board failure of the network device;

The processing unit 200 is configured to filter the logs in the first log set according to the log filtering rule to obtain a second log set, and obtain the first log and the second log from the second log set, where the first The log is a log generated by the first interface, and the second log is a log generated by the second interface. When it is determined that the first log and the second log meet a preset condition, determining that the first interface corresponds to The first link and the second link corresponding to the second interface belong to the same shared risk link group.

Optionally, the log filtering rule includes at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Optionally, when it is determined that the first log and the second log meet the preset condition, the processing unit 200 is specifically configured to:

Optionally, the second log set includes a network device identifier, a log generation interface, a log generation time, and a log occurrence event.

Optionally, the processing unit 200 is further configured to:

Reporting the identified shared risk link group to the user for alarms;

The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device after the user confirms.

Please refer to FIG. 6 , which is a schematic diagram of another apparatus for determining an SRLG according to an embodiment of the present disclosure. As shown in FIG. 6 , the apparatus may include a processor 110 , a memory 120 , and a bus 130 . The processor 110 and the memory 120 are connected by a bus 130 for storing instructions for executing the instructions stored by the memory 120 to implement the steps in the method corresponding to Figures 2 to 4 above.

Further, the device may further include an input port 140 and an output port 150. The processor 110, the memory 120, the input port 140 and the output port 150 can be connected by a bus 130.

The processor 110 is configured to execute instructions stored in the memory 120 to control the input port 140 to receive signals, and control the output port 150 to send signals to complete the steps performed by the controller in the above method. The input port 140 and the output port 150 may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as input and output ports. The memory 120 may be integrated in the processor 110 or may be provided separately from the processor 110.

As an implementation manner, the functions of the input port 140 and the output port 150 can be implemented by a dedicated chip through a transceiver circuit or a transceiver. The processor 110 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general purpose chip.

As another implementation manner, a device provided by an embodiment of the present application may be implemented by using a general-purpose computer. The program code for the functions of the processor 110, the input port 140 and the output port 150 is stored in a memory, and the general purpose processor implements the functions of the processor 110, the input port 140 and the output port 150 by executing code in the memory.

For the concepts, explanations, detailed descriptions and other steps related to the technical solutions provided by the embodiments of the present application, refer to the descriptions of the foregoing methods or other embodiments, and no further details are provided herein.

Those skilled in the art will appreciate that FIG. 6 shows only one memory and processor for ease of illustration. In an actual controller, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like.

Referring to FIG. 7, an embodiment of the present application provides an apparatus 210 for determining an SRLG. The device 210 includes a main control board 220 and an interface board 230. The main control board 220 includes a processor 221 and a memory 222. The interface board 230 includes a processor 231, a memory 232, and an interface card 233. The main control board 220 and the interface board 230 are coupled.

The memory 222 can be used to store the program code of the main control board 210, and the processor 221 is used to call the program code in the memory 222 to perform the following operations:

The memory 232 can be used to store program code of the interface board 230, and the processor 231 is used to call the program code in the memory 232 to perform the following operations:

The trigger interface card 233 sends a log acquisition message to one or more network devices to trigger the network device to return a log that is not caused by the network device restarting or the interface board failure of the network device.

In a possible implementation manner, an inter-process communication protocol IPC control channel is established between the main control board 220 and the interface board 230.

The device 210 can be an SDN controller, a router, or other background server. The device 210 can implement the functions of the device for determining the SRLG in the foregoing method embodiments. For the specific implementation steps, refer to the foregoing method embodiments, and details are not described herein.

It should be understood that, in the embodiment of the present application, the processor may be a central processing unit ("CPU"), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration. Circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.

In addition to the data bus, the bus may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the various buses are labeled as buses in the figure.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

According to the method provided by the embodiment of the present application, the embodiment of the present application further provides a system including the foregoing device and one or more network devices.

It is also to be understood that the first, second, third, fourth, and various reference numerals are in the

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that in various embodiments of the present application, the size of the sequence numbers of the above processes does not imply an order of execution. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. achieve. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may 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 a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A method for determining a shared risk link group, comprising:

Obtaining a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device restart or is not caused by an interface board failure of the network device;

Filtering the logs in the first log set according to the log filtering rule to obtain a second log set;

Obtaining a first log and a second log from the second log set, where the first log is a log generated by the first interface, and the second log is a log generated by the second interface, where When the first log and the second log meet the preset condition, the first link corresponding to the first interface and the second link corresponding to the second interface belong to the same shared risk link group.
The method according to claim 1, wherein the log filtering rule comprises at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Filtering to obtain a log of the bidirectional forwarding detection up and/or bidirectional forwarding detection down of the physical interface; and

Filtering logs for running, managing, and maintaining OAM up and/or OAM down for physical interfaces.
The method according to claim 1 or 2, wherein determining that the first log and the second log satisfy a preset condition comprises:

Determining that the first log and the second log satisfy at least one of the following conditions:

The first log identifies that the status of the first interface changes to up, the second log identifies that the status of the second interface changes to up, the generation time of the first log, and the generation of the second log The interval of time is less than the first threshold;

The first log identifies that the status of the first interface changes to down, the second log identifies that the status of the second interface changes to down, the generation time of the first log, and the generation of the second log The interval of time is less than the second threshold;

The first log identifies that the first interface has an error, the second log identifies that the second interface has an error, and the interval between the first log generation time and the second log generation time is less than Third threshold

The first log identifies that the first interface is running, managing, and maintaining OAM up, the second log identifies that the second interface is OAM up, the first log is generated, and the second log is generated. The interval of generation time is less than the fourth threshold; and,

The first log identifies that the first interface is OAM down, the second log identifies that the second interface is OAM down, and the interval between the generation time of the first log and the second log is less than The fifth threshold.
The method according to any one of claims 1 to 3, wherein the second log set comprises a network device identifier, a log generation interface, a log generation time, and a log occurrence event.
The method according to any one of claims 1 to 4, further comprising:

Acquiring a third log from the second log set, where the third log is a log generated by the third interface;

Determining the first corresponding to the first interface when determining that the first log and the third log meet the preset condition The third link corresponding to the link and the third interface belongs to the same shared risk link group;

When it is determined that the second log and the third log meet the preset condition, determining that the second link corresponding to the second interface and the third link corresponding to the third interface belong to the same shared risk link group.
The method according to any one of claims 1 to 5, further comprising:

The determined shared risk link group is reported to the user equipment for alarming.

The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device according to the indication of the user equipment.
An apparatus for determining a shared risk link group, comprising:

a transceiver unit, configured to acquire a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device or is not caused by an interface board failure of the network device;

a processing unit, configured to filter the logs in the first log set according to the log filtering rule to obtain a second log set, and obtain the first log and the second log from the second log set, where the first log is a log generated by the first interface, where the second log is a log generated by the second interface, and when it is determined that the first log and the second log meet a preset condition, determining that the first interface corresponds to The second link corresponding to the first link and the second interface belong to the same shared risk link group.
The apparatus according to claim 7, wherein the log filtering rule comprises at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Filtering to obtain a log of the bidirectional forwarding detection up and/or bidirectional forwarding detection down of the physical interface; and

Filtering logs for running, managing, and maintaining OAM up and/or OAM down for physical interfaces.
The apparatus according to claim 7 or 8, wherein when the first log and the second log are determined to meet a preset condition, the processing unit is specifically configured to:

Determining that the first log and the second log satisfy at least one of the following conditions:

The first log identifies that the status of the first interface changes to up, the second log identifies that the status of the second interface changes to up, the generation time of the first log, and the generation of the second log The interval of time is less than the first threshold;

The first log identifies that the status of the first interface changes to down, the second log identifies that the status of the second interface changes to down, the generation time of the first log, and the generation of the second log The interval of time is less than the second threshold;

The first log identifies that the first interface has an error, the second log identifies that the second interface has an error, and the interval between the first log generation time and the second log generation time is less than Third threshold

The first log identifies that the first interface is running, managing, and maintaining OAM up, the second log identifies that the second interface is OAM up, the first log is generated, and the second log is generated. The interval of generation time is less than the fourth threshold; and,

The first log identifies that the first interface is OAM down, the second log identifies that the second interface is OAM down, and the interval between the generation time of the first log and the second log is less than The fifth threshold.
The apparatus according to any one of claims 7 to 9, wherein the second log set comprises a network device identifier, a log generation interface, a log generation time, and a log occurrence event.
The device according to any one of claims 7 to 10, wherein the processing unit is further configured to:

Acquiring a third log from the second log set, where the third log is a log generated by the third interface;

When it is determined that the first log and the third log meet the preset condition, determining that the first link corresponding to the first interface and the third link corresponding to the third interface belong to the same shared risk link group;

When it is determined that the second log and the third log meet the preset condition, determining that the second link corresponding to the second interface and the third link corresponding to the third interface belong to the same shared risk link group.
The device according to any one of claims 7 to 11, wherein the processing unit is further configured to:

The determined shared risk link group is reported to the user equipment for alarming.

The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device according to the user indication.
An apparatus for determining a shared risk link group, comprising:

a processor, a memory and a bus, the processor and the memory being connected by a bus, wherein the memory is for storing a set of program code, the processor is for calling the program code stored in the memory, and performing the following operations:

Obtaining a first log set of one or more network devices, where the first log set includes a log that is not generated by the network device restart or is not caused by an interface board failure of the network device;

Filtering the logs in the first log set according to the log filtering rule to obtain a second log set;

Obtaining a first log and a second log from the second log set, where the first log is a log generated by the first interface, and the second log is a log generated by the second interface, where When the first log and the second log meet the preset condition, the first link corresponding to the first interface and the second link corresponding to the second interface belong to the same shared risk link group.
The apparatus according to claim 13, wherein the log filtering rule comprises at least one of the following:

Filtering the log that the physical interface is up and/or down.

Filtering to get a log of errors in the physical interface;

Filtering to obtain a log of the bidirectional forwarding detection up and/or bidirectional forwarding detection down of the physical interface; and

Filtering logs for running, managing, and maintaining OAM up and/or OAM down for physical interfaces.
The device according to claim 13 or 14, wherein when the first log and the second log are determined to meet a preset condition, the processor is specifically configured to:

Determining that the first log and the second log satisfy at least one of the following conditions:

The first log identifies that the status of the first interface changes to up, the second log identifies that the status of the second interface changes to up, the generation time of the first log, and the generation of the second log The interval of time is less than the first threshold;

The first log identifies that the status of the first interface changes to down, the second log identifies that the status of the second interface changes to down, the generation time of the first log, and the generation of the second log The interval of time is less than the second threshold;

The first log identifies that the first interface has an error, the second log identifies that the second interface has an error, and the interval between the first log generation time and the second log generation time is less than Third threshold

The first log identifies that the first interface is running, managing, and maintaining OAM up, the second log identifies that the second interface is OAM up, the first log is generated, and the second log is generated. The interval of generation time is less than the fourth threshold; and,

The first log identifies that the first interface is OAM down, the second log identifies that the second interface is OAM down, and the interval between the generation time of the first log and the second log is less than The fifth threshold.
The apparatus according to any one of claims 13 to 15, wherein the second log set comprises a network device identifier, a log generation interface, a log generation time, and a log occurrence event.
The device according to any one of claims 13 to 16, wherein the processor is further configured to:

Acquiring a third log from the second log set, where the third log is a log generated by the third interface;

When it is determined that the first log and the third log meet the preset condition, determining that the first link corresponding to the first interface and the third link corresponding to the third interface belong to the same shared risk link group;

When it is determined that the second log and the third log meet the preset condition, determining that the second link corresponding to the second interface and the third link corresponding to the third interface belong to the same shared risk link group.
The device according to any one of claims 13 to 17, wherein the processing unit is further configured to:

The determined shared risk link group is reported to the user equipment for alarming.

The determined shared risk link group is delivered to the network device, or the determined shared risk link group is delivered to the network device according to the user equipment indication.