WO2019079961A1 - Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé - Google Patents

Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé

Info

Publication number
WO2019079961A1
WO2019079961A1 PCT/CN2017/107448 CN2017107448W WO2019079961A1 WO 2019079961 A1 WO2019079961 A1 WO 2019079961A1 CN 2017107448 W CN2017107448 W CN 2017107448W WO 2019079961 A1 WO2019079961 A1 WO 2019079961A1
Authority
WO
WIPO (PCT)
Prior art keywords
log
interface
identifies
shared risk
determining
Prior art date
Application number
PCT/CN2017/107448
Other languages
English (en)
Chinese (zh)
Inventor
张耀坤
孙春霞
张大冬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/107448 priority Critical patent/WO2019079961A1/fr
Priority to CN201780009064.XA priority patent/CN109964450B/zh
Publication of WO2019079961A1 publication Critical patent/WO2019079961A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/087—Jitter

Definitions

  • 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).
  • SRLG Shared Risk Link Group
  • 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.
  • 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)
  • CR-LDP Consultation-based Routing Label Distribution Protocol
  • FRR Fast Reroute
  • the shared risk link is not used as the primary and backup paths.
  • 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.
  • 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.
  • an embodiment of the present application provides a method for determining a shared risk link group, which may include:
  • 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;
  • 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 first log set 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.
  • IP network protocol
  • 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.
  • the log filtering rule includes at least one of the following:
  • 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.
  • determining that the first log and the second log meet predetermined conditions include:
  • 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
  • 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
  • the second log is generated.
  • the interval of generation time is less than the fourth threshold
  • the first log identifies that the first interface is OAM down
  • the second log identifies that the second interface is OAM down
  • the interval between the generation time of the first log and the second log is less than The fifth threshold.
  • the second log set includes a network device identifier, a log generation interface, a log generation time, and a 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.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • the log filtering rule includes at least one of the following:
  • the processing unit when it is determined that the first log and the second log meet a preset condition, is specifically configured to:
  • 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
  • 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
  • the second log is generated.
  • the interval of generation time is less than the fourth threshold
  • the first log identifies that the first interface is OAM down
  • the second log identifies that the second interface is OAM down
  • the interval between the generation time of the first log and the second log is less than The fifth threshold.
  • the second log set includes a network device identifier, a log generation interface, a log generation time, and a log occurrence event.
  • the processing unit is further configured to:
  • 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 indication of the user equipment.
  • an apparatus for determining a shared risk link group which may include:
  • processors 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.
  • 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:
  • 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
  • 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.
  • an inter-process communication (IPC) control channel is established between the main control board and the interface board.
  • IPC inter-process communication
  • 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.
  • 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
  • FIG. 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.
  • 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.
  • SDN Software Defined Network
  • 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.
  • control layer may include a controller
  • 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.
  • 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.
  • SNC SDN controller
  • CPU Central Processing Unit
  • FIG. 2 is a schematic flowchart of a method for determining an SRLG according to an embodiment of the present disclosure
  • log data of a specified network device or all networks in the network in a preset time period may be acquired.
  • the preset time period may be one year or one month, and is not limited in any embodiment of the present application.
  • 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.
  • 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.
  • the log filtering rule includes at least one of the following:
  • 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:
  • Link performance monitoring Monitors various performances of the link, including measurement of packet loss, delay, and jitter, and statistics on various types of traffic.
  • the link is detected by sending a detection packet, and the network administrator is notified when the link fails.
  • Loop test The link fault is detected by the loopback of non-Ethernet OAM packets.
  • 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.
  • 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.
  • 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.
  • 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.
  • the SRLG can be obtained from the log mining of each interface included in the log collection.
  • determining that the first log and the second log meet the preset conditions include:
  • 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
  • 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
  • the second log is generated.
  • the interval of generation time is less than the fourth threshold
  • the first log identifies that the first interface is OAM down
  • the second log identifies that the second interface is OAM down
  • the interval between the generation time of the first log and the second log is less than The fifth threshold.
  • the link corresponding to the two interfaces can be regarded as a possible shared risk link group and recorded in the SRLG set.
  • 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.
  • the pseudo code of the preset condition may include the following parts:
  • the preset condition 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.
  • 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.
  • FIG. 3 is a schematic flowchart of another method for determining an SRLG according to an embodiment of the present disclosure.
  • steps S301-S303 are the same as steps S201-S203, and details are not described herein again.
  • the method further includes:
  • the processing method of the second log set including the logs of the two interfaces is provided.
  • the processing method is similar to the foregoing, and details are not described herein again.
  • the shared risk link groups that meet the preset conditions can be sequentially filtered out to generate a set of SRLGs.
  • a shared risk link group relationship table may be generated according to the comparison with the preset conditions.
  • the shared risk link group relationship table includes identifiers of two links that fail simultaneously and frequency of simultaneous failures.
  • 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.
  • 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
  • SRLG relational table As shown in the following table, a possible form of SRLG relational table is given:
  • FIG. 4 is a schematic flowchart of still another method for determining an SRLG according to an embodiment of the present disclosure.
  • steps S401-S406 are the same as steps S301-S306 in the embodiment shown in FIG. The details are not described herein again.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • the log filtering rule includes at least one of the following:
  • the processing unit 200 is specifically configured to:
  • 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
  • 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
  • the second log is generated.
  • the interval of generation time is less than the fourth threshold
  • the first log identifies that the first interface is OAM down
  • the second log identifies that the second interface is OAM down
  • the interval between the generation time of the first log and the second log is less than The fifth threshold.
  • the second log set includes a network device identifier, a log generation interface, a log generation time, and a log occurrence event.
  • processing unit 200 is further configured to:
  • processing unit 200 is further configured to:
  • 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.
  • FIG. 6 is a schematic diagram of another apparatus for determining an SRLG according to an embodiment of the present disclosure.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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 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.
  • 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.
  • 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.
  • the bus may also include a power bus, a control bus, and a status signal bus.
  • the various buses are labeled as buses in the figure.
  • 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.
  • the embodiment of the present application further provides a system including the foregoing device and one or more network devices.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • 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.
  • 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.
  • the computer program product includes one or more computer instructions.
  • 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)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Les modes de réalisation de la présente invention concernent un procédé et un dispositif de détermination d'un groupe de liaisons à risque partagé, le procédé comprenant les étapes consistant à : acquérir un premier ensemble de journaux d'un ou plusieurs dispositifs de réseau, le premier ensemble de journaux comprenant un journal généré en raison du redémarrage du ou des dispositifs de réseau ou de la défaillance d'une carte d'interface du ou des dispositifs de réseau; filtrer des journaux dans le premier ensemble de journaux conformément à une règle de filtrage de journal de façon à obtenir un second ensemble de journaux; et acquérir, à partir du second ensemble de journaux, un premier journal généré par une première interface et un second journal généré par une seconde interface, et déterminer qu'une première liaison correspondant à la première interface et une seconde liaison correspondant à la seconde interface appartiennent à un même groupe de liaisons à risque partagé lorsqu'il est déterminé que le premier journal et le second journal satisfont une condition prédéfinie. En utilisant les modes de réalisation de la présente invention, un groupe de liaisons à risque partagé peut être déterminé de manière pratique et précise, réduisant ainsi les risques de transmission de service.
PCT/CN2017/107448 2017-10-24 2017-10-24 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé WO2019079961A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/107448 WO2019079961A1 (fr) 2017-10-24 2017-10-24 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé
CN201780009064.XA CN109964450B (zh) 2017-10-24 2017-10-24 一种确定共享风险链路组的方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/107448 WO2019079961A1 (fr) 2017-10-24 2017-10-24 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé

Publications (1)

Publication Number Publication Date
WO2019079961A1 true WO2019079961A1 (fr) 2019-05-02

Family

ID=66246174

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107448 WO2019079961A1 (fr) 2017-10-24 2017-10-24 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé

Country Status (2)

Country Link
CN (1) CN109964450B (fr)
WO (1) WO2019079961A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021143524A1 (fr) * 2020-01-15 2021-07-22 华为技术有限公司 Procédé de détection de défaut et appareil associé
CN113691395A (zh) * 2021-08-04 2021-11-23 曙光信息产业(北京)有限公司 网络运维方法、装置、计算机设备和存储介质
CN117074915A (zh) * 2023-08-23 2023-11-17 扬州万方科技股份有限公司 基于特征关键字监测技术的板卡软硬重启测试系统及方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113821491A (zh) * 2021-02-22 2021-12-21 京东科技控股股份有限公司 用于生成网络设备日志模板的方法、装置、服务器和介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1879356A (zh) * 2003-11-21 2006-12-13 思科技术公司 基于共享风险链路群组信息确定网络路由选择信息的方法和装置
WO2008058574A1 (fr) * 2006-11-16 2008-05-22 Telefonaktiebolaget Lm Ericsson (Publ) Fourniture de trajets de communication alternatifs dans un réseau de communication
CN102868563A (zh) * 2012-09-30 2013-01-09 华信邮电咨询设计研究院有限公司 共享风险链路组跨层映射管理方法
WO2016095710A1 (fr) * 2014-12-15 2016-06-23 中兴通讯股份有限公司 Procédé et dispositif pour régler un srlg

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7701848B2 (en) * 2003-07-11 2010-04-20 Chunming Qiao Efficient trap avoidance and shared protection method in survivable networks with shared risk link groups and a survivable network
CN105991188B (zh) * 2015-02-16 2019-09-10 阿里巴巴集团控股有限公司 一种检测共享风险链路组的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1879356A (zh) * 2003-11-21 2006-12-13 思科技术公司 基于共享风险链路群组信息确定网络路由选择信息的方法和装置
WO2008058574A1 (fr) * 2006-11-16 2008-05-22 Telefonaktiebolaget Lm Ericsson (Publ) Fourniture de trajets de communication alternatifs dans un réseau de communication
CN102868563A (zh) * 2012-09-30 2013-01-09 华信邮电咨询设计研究院有限公司 共享风险链路组跨层映射管理方法
WO2016095710A1 (fr) * 2014-12-15 2016-06-23 中兴通讯股份有限公司 Procédé et dispositif pour régler un srlg

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021143524A1 (fr) * 2020-01-15 2021-07-22 华为技术有限公司 Procédé de détection de défaut et appareil associé
CN113691395A (zh) * 2021-08-04 2021-11-23 曙光信息产业(北京)有限公司 网络运维方法、装置、计算机设备和存储介质
CN117074915A (zh) * 2023-08-23 2023-11-17 扬州万方科技股份有限公司 基于特征关键字监测技术的板卡软硬重启测试系统及方法
CN117074915B (zh) * 2023-08-23 2024-05-17 扬州万方科技股份有限公司 基于特征关键字监测技术的板卡软硬重启测试方法

Also Published As

Publication number Publication date
CN109964450A (zh) 2019-07-02
CN109964450B (zh) 2020-06-26

Similar Documents

Publication Publication Date Title
US10917322B2 (en) Network traffic tracking using encapsulation protocol
US10103851B2 (en) Network link monitoring and testing
CN104798341B (zh) 在电子网络上表征服务水平
WO2019079961A1 (fr) Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé
WO2015090098A1 (fr) Procédé et appareil permettant de réaliser un repérage de pannes
CN108632099B (zh) 一种链路聚合的故障检测方法及装置
WO2021018309A1 (fr) Procédé, dispositif et système de détermination d'un chemin de transmission de message et support de stockage informatique
CN112737800B (zh) 服务节点故障定位方法、调用链生成方法及服务器
CN113542008A (zh) 一种网络的oam方法及装置
CN109960634A (zh) 一种应用程序监控方法、装置及系统
CN108449228A (zh) 报文处理方法及网络设备
EP3232620B1 (fr) Procédé et dispositif d'analyse de pannes par centre de données
CN103023815B (zh) 聚合链路负载分担方法及装置
US9280426B2 (en) System and method for server redundancy
CN108599978B (zh) 一种云监控方法和装置
WO2012106914A1 (fr) Procédé de diagnostic de défaillance de tunnel dynamique, dispositif et système
CN107005440B (zh) 一种链路故障定位的方法、装置及系统
CN116248479A (zh) 网络路径探测方法、装置、设备及存储介质
CN101431435A (zh) 一种基于面向连接的业务配置与管理方法
Gao et al. Xshot: Light-weight link failure localization using crossed probing cycles in SDN
CN113766363A (zh) 故障监控方法、装置及计算设备
WO2024051258A1 (fr) Procédé, appareil et système de traitement d'événement
WO2024041213A1 (fr) Procédé, appareil et système de communication, et support de stockage
US20240171498A1 (en) Detecting in-transit inband telemetry packet drops
CN104796276B (zh) 一种链路切换方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17929610

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17929610

Country of ref document: EP

Kind code of ref document: A1