EP4635152A1 - Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux noeuds - Google Patents

Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux noeuds

Info

Publication number
EP4635152A1
EP4635152A1 EP23844607.4A EP23844607A EP4635152A1 EP 4635152 A1 EP4635152 A1 EP 4635152A1 EP 23844607 A EP23844607 A EP 23844607A EP 4635152 A1 EP4635152 A1 EP 4635152A1
Authority
EP
European Patent Office
Prior art keywords
probe
path
node
repair
frr
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP23844607.4A
Other languages
German (de)
English (en)
Inventor
Jaganbabu Rajamanickam
Madhan Sankaranarayanan
Nagendra Kumar Nainar
Rakesh Gandhi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
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
Priority claimed from US18/504,840 external-priority patent/US12184534B2/en
Application filed by Cisco Technology Inc filed Critical Cisco Technology Inc
Publication of EP4635152A1 publication Critical patent/EP4635152A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/10—Active monitoring, e.g. heartbeat, ping or trace-route

Definitions

  • the present technology relates to the field of network communication and routing technologies, specifically addressing traffic engineering and segment routing. More particularly, the proposed technology encompasses methods for enhancing network reliability and efficiency by incorporating end-to-end monitoring mechanisms for the dynamic discover ⁇ and utilization of repair paths between nodes in a network.
  • Routing including Traffic engineering and Segment Routing provides an innovative approach to proactively monitor networks and route data packets more efficiently. It leverages advanced monitoring techniques, such as Multi-hop BFD. Seamless BFD (SBFD), Multi-Hop Performance Measurement (PM), Path MTU discovery, and path-tracing (PT) to closely track the performance metrics and status of network paths. This real-time analysis facilitates the timely detection of anomalies, faults, or degradation in the network. Routing including Traffic Engineering and Segment Routing are also capable of monitoring multiple repair paths and different types of repair paths over complex networks that span across multiple administrative domains.
  • SBFD Seamless BFD
  • PM Multi-Hop Performance Measurement
  • PT path-tracing
  • PLR Point of Local Repair
  • FIG. 1 illustrates an example of a high-level network architecture in accordance with an embodiment
  • FIG. 2 illustrates an example communication network including one or more autonomous systems (ASes) according to some aspects of the present technology-;
  • ASes autonomous systems
  • FIG. 3 illustrates an example circuit diagram depicting Segment Routing (SR) between a source node and a destination node that includes a backup circuit according to some aspects of the present technology
  • FIG. 4 illustrates an example communication diagram between a source node and a destination node implementing SR path assurance/path tracing that tests all ECMP paths between two endpoints, according to some aspects of the present technology
  • FIG. 5A-5B illustrates an example message flow between a source node and destination node in a continuous mode according to some aspects of the present technology
  • FIG. 6A-6B illustrates an example communication diagram between a source node and destination node in a targeted mode according to some aspects of the present technology
  • FIG. 7 illustrates an example MPLS Network Action (MNA) header for FRR path traversing and discovery in continuous mode according to some aspects of the present technology
  • FIG. 8 illustrates an example in-stack-data (ISD) MNA header for FRR path traversing and discovering in the targeted mode according to some aspects of the present technology
  • FIG. 9A illustrates an example Post-Stack Data (PSD) MNA header for FRR path traversing and discovery in continuous mode for post-stack data (PSD) according to some aspects of the present technology
  • FIG. 9B illustrates an example PSD MNA header for FRR path traversing and discovery' in targeted mode according to some aspects of the present technology
  • FIG. 10 illustrates an example ISD MNA header 1000 for FRR path traversing in continuous and targeted modes , according to some aspects of the present technology
  • FIG. 1 1 A illustrates an example ISD and PSD MNA header for FRR path traversing and discovering in continuous mode, according to some aspects of the present technology 7 ;
  • FIG. 11B illustrates an example ISD and PSD MNA header for FRR path traversing and discovering in targeted mode, according to some aspects of the present technology
  • FIG. 12A illustrates an example IPv6 extension header for continuous mode according to some aspects of the present technology 7 ;
  • FIG. 12B illustrates an example IPv6 extension header for targeted mode according to some aspects of the present technology 7 ;
  • FIG. 13 illustrates an example process for monitoring an FRR path between a source node and a destination node in a network according to some aspects of the present technology
  • FIG. 14 illustrates an example of a computing system according to some aspects of the present technology.
  • references to “one embodiment'’ or “an embodiment’' means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure.
  • the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
  • various features are described which can be exhibited by some embodiments and not by others.
  • repair paths offer a substantial enhancement to fault recovery and redundancy, enabling swift detection of link or node outages and seamless transitions to alternative routes to maintain uninterrupted data transmission. Moreover, this proactive approach minimizes downtime by preemptively redirecting traffic before failures impact user experience, thereby mitigating service interruptions and ensuring heightened uptime.
  • Identifying specific transition points further refines traffic management, allowing for precision in rerouting to optimize load distribution and alleviate congestion.
  • the recognition of transition points betw een primary and repair paths augments path diversity, fortifying the network against common-cause failures that might otherwise compromise both routes.
  • transition points transcends administrative boundaries, facilitating seamless communication and coordination across disparate network segments.
  • automating the discovery of repair paths and pinpointing transition points manual intervention is minimized, simplilying network management and reducing the risk of human errors.
  • Repair path discovery and the identification of transition points collectively reinforce network resilience, responsiveness, and security, ushering in a new era of fault-tolerant, high-performance network communication.
  • a method for monitoring a Fast Re-Route (FRR) path between a source node (Node-S) and a destination node (Node-E) in a network includes generating a discovery-probe at the source node (Node-S) to detect at least one node with an FRR indicator along the FRR path that includes a plurality of next available nodes, where the discovery' probe is forwarded to the plurality of next available nodes to initiate a repair path discovery along the FRR path.
  • FRR Fast Re-Route
  • the method also includes upon the discovery probe reaching a first node with the FRR indicator, generating a primary' probe configured to detect a primary' path includes a first set of nodes to forward the primary probe towards the destination node, and a repair probe configured to detect a repair path includes a second set of nodes to forward the repair probe towards the destination node.
  • the method also includes in response to receiving the pnmary probe via the primary path and the repair probe via the repair path at the destination node, sending the primary' probe and the repair probe back to the source node to monitor the FRR path between the source node and the destination node.
  • the method may further include identifying a second node along the FRR path that includes a second repair path, wherein the second node does not include the FRR indicator, and forwarding the discovery probe to the next available node, wherein the discovery' probe bypasses the second repair path.
  • the method may further include identifying a second node along the primary path that includes a second FRR indicator, wherein the second node is configured to generate a duplicate primary’ probe to detect the primary path includes a third set of nodes to forward the duplicate primary probe towards the destination node, and generate a duplicate repair probe to detect a repair path includes a fourth set of nodes to forward the repair probe towards the destination node.
  • the discovery probe comprises a hop count value, wherein the hop count value indicates a specific node along the FRR path to start discovery of the repair path.
  • the monitored FRR path sent to the source node indicates a node value representative of a total number of nodes in the primary path, and a hop count value indicated where the repair node is generated.
  • the discovery probe, the primary probe, and the repair probe are encapsulated within data packets that include a header indicating their respective roles and functions within an FRR path monitoring.
  • the method may further include triggering an FRR switchover process based on network conditions and performance metrics, wherein in response to the FRR switchover being triggered, the second probe is configured to generate a repair FRR Switchover Probe and send it along the repair path instead of the repair probe, to expedite the monitoring of the repair path and ensure network resiliency during FRR switchover events.
  • a network device includes one or more memories having computer-readable instructions stored therein.
  • the network device also includes one or more processors configured to execute the computer-readable instructions to generate a discovery probe at a source node (Node-S) to detect at least one node with a Fast Re-Route (FRR) indicator along an FRR path that includes a plurality of next available nodes, wherein the discover ⁇ 7 probe is forwarded to the plurality of next available nodes to initiate a repair path discover ⁇ 7 along the FRR path; upon the discovery probe reach a first node with the FRR indicator, generate a primary probe configured to detect a primary path includes a first set of nodes to forward the primary probe towards a destination node, and a repair probe configured to detect a repair path includes a second set of nodes to forward the repair probe towards the destination node; and, in response to receiving the primary probe via the primary path and the repair probe via the repair path at the destination node, send the primary probe and the repair probe back to the source node to
  • one or more non-transitory computer-readable storage media includes computer-readable instructions, which when executed by one or more processors of a network device, cause the network device to generate a discovery probe at a source node (Node-S) to detect at least one node with a Fast Re-Route (FRR) indicator along an FRR path that includes a plurality of next available nodes, wherein the discovery 7 probe is forwarded to the plurality of next available nodes to initiate a repair path discovery along the FRR path; upon the discovery probe reach a first node with the FRR indicator, generate a primary probe configured to detect a primary path includes a first set of nodes to forward the primary probe towards a destination node, and a repair probe configured to detect a repair path includes a second set of nodes to forward the repair probe towards the destination node; and, in response to receiving the primary probe via the primary path and the repair probe via the repair path at the destination node, send the primary probe and the repair probe back to the source node to monitor
  • Node-S source
  • the following description is directed to certain implementations for the purposes of describing innovative aspects of this disclosure.
  • RF radio frequency
  • IEEE 802.11 the Institute of Electrical and Electronics Engineers
  • the IEEE 802.15 the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G or 5G (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), among others.
  • SIIG Bluetooth Special Interest Group
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • the described implementations can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) MIMO.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • SU single-user
  • MIMO multiple-input multiple-output
  • MU multi-user
  • the described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an internet of things (I
  • the present disclosure provides a holistic approach that not only monitors the entirety of the network path but also ensures coherence between primary' and repair paths, effectively mitigating packet loss during switchover events from primary path to repair path, for example, due to a failure event.
  • Techniques described herein elevate the dependability, fault tolerance, and flexibility of data packet transmission within contemporary networking environments.
  • the disclosed technology provides a solution to overcome these challenges by enabling the traversal and discovery’ of Fast Re-Route (FRR) primary and repair paths between a source and destination node using MPLS Network Action Sub-Stack (MNAS) /IPv6 extension headers.
  • FRR Fast Re-Route
  • MNAS MPLS Network Action Sub-Stack
  • IPv6 extension headers MPLS Network Action Sub-Stack
  • the present disclosure facilitates Operations, Administration, and Maintenance (0AM) processes such as Ping, Traceroute. iOAM, DEX, Bidirectional Forwarding Detection (BFD), Performance Measurement (PM) (TWAMP, OWAMP and STAMP), Path Tracing (PT), and more, allowing for the execution of additional functionalities.
  • Various routing and control-plane protocols including OSPF, ISIS, BGP, LDP, RSVP, etc. packets benefit from ability to traverse FRR and primary and repair paths. Techniques presented herein operate in two distinct modes, namely a "continuous mode” and “targeted mode
  • FIG. 1 illustrates an example of a network architecture 100 for implementing aspects of the present technology.
  • An example of an implementation of the network architecture 100 is the Cisco® SD-WAN architecture.
  • Cisco® SD-WAN architecture Cisco® SD-WAN architecture.
  • FIG. 1 illustrates an example of a network architecture 100 for implementing aspects of the present technology.
  • An example of an implementation of the network architecture 100 is the Cisco® SD-WAN architecture.
  • Cisco® SD-WAN architecture Cisco® SD-WAN architecture
  • the network architecture 100 can comprise an orchestration plane 102, a management plane 106, a control plane 112, and a data plane 116.
  • the orchestration plane 102 can assist in the automatic on-boarding of edge network devices 118 (e.g., switches, routers, etc.) in an overlay network.
  • the orchestration plane 102 can include one or more physical or virtual network orchestrator appliances 104.
  • the network orchestrator appliances network orchestrator appliance 104 can perform the initial authentication of the edge network devices 118 and orchestrate connectivity between devices of the control plane 112 and the data plane 116.
  • the network orchestrator appliances 104 can also enable communication of devices located behind Network Address Translation (NAT).
  • NAT Network Address Translation
  • physical or virtual Cisco® SD-WAN vBond appliances can operate as the network orchestrator appliances 104.
  • the management plane 106 can be responsible for central configuration and monitoring of a network.
  • the management plane 106 can include one or more physical or virtual network management appliances 110.
  • the network management appliances 1 10 can provide centralized management of the network via a graphical user interface to enable a user to monitor, configure, and maintain the edge network devices 118 and links (e.g., internet transport network 128, MPLS network 130, 4G/Mobile network 132) in an underlay and overlay network.
  • the network management appliances 110 can support multi-tenancy and enable centralized management of logically isolated networks associated with different entities (e g., enterprises, divisions within enterprises, groups within divisions, etc.). Alternatively, or in addition, the network management appliances 110 can be a dedicated network management system for a single entity.
  • the control plane 112 can build and maintain a network topology and make decisions on where traffic flows.
  • the control plane 1 12 can include one or more physical or virtual network control appliances 114.
  • the network control appliances 114 can establish secure connections to each edge network device 118 and distribute route and policy information via a control plane 112 protocol (e.g., Overlay Management Protocol (OMP) (discussed in further detail below).
  • OMP Overlay Management Protocol
  • the network control appliances 114 can operate as route reflectors.
  • the network control appliances 114 can also orchestrate secure connectivity in the data plane 116 between and among the edge network devices 118. For example, in some embodiments, the network control appliances 114 can distribute crypto key information among the edge network devices 118.
  • IPSec Internet Protocol Security
  • TLS Transport Layer Security
  • SSH Secure Shell
  • IKE Internet Key Exchange
  • physical or virtual Cisco® SD-WAN vSmart controllers can operate as the network control appliances 114.
  • the data plane 116 can be responsible for forwarding packets based on decisions from the control plane 112.
  • the data plane 116 can include the edge network devices 118, which can be physical or virtual edge network devices.
  • the edge network devices 118 can operate at the edges various network environments of an organization, such as in one or more data centers 126. campus networks 124, branch office networks 122, home office networks 120, and so forth, or in the cloud (e.g., Infrastructure as a Service (laaS), Platform as a Sendee (PaaS), SaaS, and other cloud service provider networks).
  • laaS Infrastructure as a Service
  • PaaS Platform as a Sendee
  • SaaS SaaS
  • the edge network devices 118 can provide secure data plane 116 connectivity' among sites over one or more WAN transports, such as via one or more Internet transport networks 128 (e.g., Digital Subscriber Line (DSL), cable, etc.), MPLS networks 130 (or other private packet- switched network (e.g., Metro Ethernet, Frame Relay, Asynchronous Transfer Mode (ATM), etc.), mobile networks 132 (e.g., 3G, 4G/LTE, 5G, etc.), or other WAN technology' (e.g., Synchronous Optical Networking (SONET), Synchronous Digital Hierarchy (SDH), Dense Wavelength Division Multiplexing (DWDM), or other fiber-optic technology'; leased lines (e.g., Tl/El, T3/E3, etc.); Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), or other private circuit-switched network; small aperture terminal (VS AT) or other satellite network; etc.).
  • Internet transport networks 128 e.g., Digital Subscribe
  • the edge network devices 118 can be responsible for traffic forwarding, security, encryption, quality of service (QoS), and routing (e.g., BGP. OSPF, etc.), among other tasks.
  • QoS quality of service
  • routing e.g., BGP. OSPF, etc.
  • physical or virtual Cisco® SD-WAN vEdge routers can operate as the edge network devices 118.
  • FIG. 2 illustrates an example communication network 200 including one or more autonomous systems (ASes) according to some aspects of the present technology.
  • ASes autonomous systems
  • a computer network 200 is a geographically distributed collection of nodes interconnected by communication links 202 and segments for transporting data between end nodes, such as personal computers and workstations, or other network devices, such as sensors, etc.
  • end nodes such as personal computers and workstations, or other network devices, such as sensors, etc.
  • LANs local area networks
  • WANs wide area networks
  • LANs typically connect the nodes over dedicated private communications links located in the same general physical location, such as a building or campus.
  • WANs typically connect geographically dispersed nodes over long-distance communications links.
  • the Internet is an example of a WAN that connects disparate networks throughout the world, providing global communication between nodes on various networks.
  • TCP/IP Transmission Control Protocol/Intemet Protocol
  • a protocol consists of a set of rules defining how the nodes interact with each other.
  • An Autonomous System is a network or group of networks under common administration and with common routing policies.
  • a typical example of an AS is a network administered and maintained by an Internet Service Provider (ISP).
  • Customer networks such as universities or corporations, connect to the ISP, and the ISP routes the network traffic originating from the customer networks to network destinations that may be in the same ISP or may be reachable only through other ISPs.
  • Border Gateway Protocol is an Exterior Gateway Protocol (EGP) that is used to exchange routing information among network elements (e.g., routers) in the same or different ASes.
  • a computer host that executes a BGP process is typically referred to as a BGP host or a BGP network device.
  • BGP host or a BGP network device.
  • BGP peers To exchange BGP routing information, two BGP hosts, or peers, first establish a transport protocol connection with one another. Initially, the BGP peers exchange messages to open a BGP session, and, after the BGP session is open, the BGP peers exchange their entire routing information. Thereafter, only updates or changes to the routing information are exchanged, or advertised, between the BGP peers. The exchanged routing information is maintained by the BGP peers during the existence of the BGP session.
  • the networks within an AS are typically coupled together by conventional “intradomain” routers configured to execute intradomain routing protocols, and are generally subject to a common authority.
  • a sendee provider e.g., an ISP
  • an AS, area, or level is generally referred to as a “domain.”
  • FIG. 2 is a schematic block diagram of an example computer network 200 illustratively comprising network devices 214 interconnected by various methods of communication.
  • the links 202 may be any suitable combination of wired links and shared media (e.g., wireless links, Internet Exchange Points, etc.) where certain network devices 214, such as, e.g., routers, computers, etc., may be in communication with other network devices 214. e.g., based on distance, signal strength, current operational status, location, etc.
  • network devices 214, links, etc. may be used in the computer network, and that the view shown herein is for simplicity.
  • Data packets may be exchanged among the network devices 214 of the computer network 200 using predefined network communication protocols such as certain known wired protocols, as well as wireless protocols or other shared-media protocols where appropriate.
  • the computer netw ork 200 includes a set of autonomous systems (AS) 204, 206, 208, 210 and 212.
  • the computer netw ork 200 may be positioned in any suitable netw ork environment or communications architecture that operates to manage or otherwise direct information using any appropriate routing protocol or data management standard.
  • computer network 200 may be provided in conjunction with a border gateway protocol (BGP).
  • BGP border gateway protocol
  • an AS may be a collection of connected Internet Protocol (IP) routing network devices 214 under the control of one or more network operators that presents a common, clearly defined routing policy to a network (e g., the Internet).
  • IP Internet Protocol
  • an AS comprises network devices 114 that are established on the edge of the system, and that serve as the system's ingress and egress points for network traffic.
  • the network devices 214 may be considered edge network devices, border routers, or core network devices within the respective AS. These network devices typically, but not always, are routers or any other element of network infrastructure suitable for switching or forwarding data packets according to a routing protocol or switching protocol.
  • the network devices 214 located within an AS may alternatively be referred to as “forwarding network devices’’ or “intermediate network devices.”
  • the ASes 204, 206, 208, 210 and 212 are shown with a limited number of network devices 214.
  • an AS normally comprises numerous routers, switches, and other elements.
  • Each AS 204, 206, 208, 210 and 212 may be associated with an Internet Sendee provider (ISP). Even though there may be multiple ASes supported by a single ISP, the Internet only sees the routing policy of the ISP. That ISP must have an officially registered Autonomous System Number (ASN). As such, a unique ASN is allocated to each AS for use in BGP routing. ASNs are important primarily because they uniquely identify each network on the Internet.
  • ISP Internet Sendee provider
  • the network devices 214 within the ASes may exchange routing information to various network destinations.
  • BGP is conventionally used to exchange routing and reachability information among network devices 214 within a single AS or betw een different ASes.
  • BGPv4 As defined in Request for Comments (RFC) 1771 of the Internet Engineering Task Force (IETF).
  • RRC Request for Comments
  • IETF Internet Engineering Task Force
  • Various embodiments may implement other versions of BGP, however, and the use of BGPv4 is not required.
  • the BGP logic of a router is used by the data collectors to collect BGP AS path information, e.g., the “AS PATH” attribute, as described further below; from BGP tables of border routers of an AS, to construct paths to prefixes.
  • BGP hosts network devices 214
  • BGP peers To exchange BGP routing information, two BGP hosts (network devices 214), or peers, first establish a transport protocol connection with one another. Initially, the BGP peers exchange messages to open a BGP session, and, after the BGP session is open, the BGP peers exchange their entire routing information. Thereafter, in certain embodiments, only updates or changes to the routing information, e.g., the “BGP UPDATE” attribute, are exchanged, or advertised, between the BGP peers. The exchanged routing information is maintained by the BGP peers during the existence of the BGP session.
  • the BGP routing information may include the complete route to each network destination, e.g., “destination network device,” that is reachable from a BGP host.
  • a route, or path comprises an address destination, which is usually represented by an address prefix (also referred to as prefix), and information that describe the path to the address destination.
  • the address prefix may be expressed as a combination of a network address and a mask that indicates how many bits of the address are used to identify the network portion of the address.
  • IPv4 Internet Protocol version 4
  • the address prefix can be expressed as “9.2.0.2/16'’.
  • the ‘716” indicates that the first 16 bits are used to identify the unique network leaving the remaining bits in the address to identify the specific hosts within this network.
  • a path joining a plurality of ASes, e.g., links 202, may be referred to as an “AS_PATH.”
  • the AS_PATH attribute indicates the list of ASes that must be traversed to reach the address destination.
  • the AS 204 may store an AS PATH attribute of “204, 206, 208, 210 and 212” where the address destination is the AS 204 (or a particular IP address within AS 212).
  • the AS_PATH attribute indicates that the path to the address destination AS 212 from AS 208 passes through ASes 204, 206 and 210, in that order.
  • all network devices 214 in the respective ASes 204, 206, 208, 210 and 212 be configured according to BGP, in areal-world implementation, it may be unlikely that each network device communicates using BGP.
  • the disclosed embodiments are applicable to scenarios where all network devices 214 in the computer network 100 are configured according to BGP, as well as scenarios where only a subset of the network devices 214 is configured as such.
  • the disclosed embodiments are applicable to either case, as described in further detail below.
  • BGPSEC a security extension to the BGP has been developed, referred to as BGPSEC, which provides improved security for BGP routing.
  • BGP does not include mechanisms that allow an AS to verify the legitimacy and authenticity of BGP route advertisements.
  • the Resource Public Key Infrastructure (RPKI) provides a first step towards addressing the validation of BGP routing data.
  • BGPSEC extends the RPKI by adding an additional type of certificate, referred to as a BGPSEC router certificate, that binds an AS number to a public signature verification key, the corresponding private key of which is held by one or more BGP speakers within this AS. Private keys corresponding to public keys in such certificates can then be used within BGPSEC to enable BGP speakers to sign on behalf of their AS.
  • BGPSEC BGPSEC
  • AS Path security is to use signatures to protect the AS Path attribute of BGP update messages so that a BGP speaker can assess the validity of the AS Path in update messages that it receives.
  • AS Path security is not limited to BGPSEC; certain embodiments may, additionally or alternatively, be applicable to other suitable protocols, including, for example, SoBGP, S-BGP, and PGPBGP, to name just a few.
  • FIG. 3 illustrates an example circuit diagram depicting a segment routing (SR) between a source node and a destination node that includes a backup circuit according to some aspects of the present technology.
  • Example circuit diagram 300 depicts a SR between a source node 302 and a destination node 324.
  • Circuit diagram 300 can include primary circuit 304 and a backup circuit 306 (repair circuit 306), according to some aspects of the present technology.
  • the repair circuit 306 is designed to protect the primary circuit 304 from the head-end perspective as an end-to-end solution since the head-end knows how to send probes to the protected path from its control plane.
  • configuration of circuit diagram 300 can be used to enable hveness-detection through the implementation of probe-based schemes, in addition to performance delay and loss monitoring on end-to-end primary' and backup paths as part of path protection.
  • This approach allows for fast detection of network faults and efficient repair by tracing the repair paths from the headend.
  • Segment Routing for Repair network operators can maintain reliable and highly resilient networks with minimal disruption to users and reduced operational costs.
  • this approach also allows for the detection of faults across different administrative domains.
  • the source node 302 as the head-end in the depiction of FIG. 3, is configured as the starting node of the FRR path.
  • primary circuit 304 and repair circuit 306 can be created using multiple segment routing (SR) adjacency segment identifiers (SIDs) associated with multiple adjacencies from a network node, to reach destination node 324.
  • Repair circuit 306 may be created to protect primary’ circuit 304 from detected network failures at source node 302.
  • repair circuit 306 is not utilized to reach the destination node 324, and data packets are instead transmitted along primary circuit 304 to node 308.
  • Node 308 can perform a detection to identify if a failure has occurred. If a failure has not occurred, node 308 can transmit data packets to the next available node, (e.g., node 310), followed by node 312.
  • node 308 can re-route the data packets to a backup route in accordance with an interior gateway protocol (IGP) FRR intended to provide fast and efficient protection against link or node failures.
  • the backup route can include transmitting the data packets between node 316. and node 318, to be received by node 310 on primary circuit 304.
  • Node 310 can subsequently transmit the data packets to node 312.
  • Node 312 can transmit data packets along primary’ circuit 304 to node 314 and then to destination node 324, as long as no node failure occurs on primary circuits 304 after node 312.
  • the data packets can be rerouted along an alternate IGP FRR path as a backup.
  • the backup route can include transmitting data packets from node 312 to node 320 and then to node 322, which will ultimately be received by node 314 along primary' circuit 304.
  • node 314 Upon node 314 receiving the data packets, node 314 can transmit the data packets to destination node 324.
  • segment-routing traffic engineering can further be implemented where repair paths exist betyveen two endpoints that are not visible to the head-end. Instead, the repair path exists on midpoint nodes. Furthermore, the repair paths could be located in different administrative domains, of which the head-end is not aware.
  • the current technology involves encoding forwarding states within packets, allowing the data plane to react to those states and foryvard packets through the primary or repair path, regardless of the FRR state. This feature enables seamlessly operations across various domains and controlplane technologies.
  • SR-Path Assurance/Path Tracing can monitor the primary data plane paths.
  • Path Tracing includes tracing the packet path betyveen source and destination nodes by recording interface identifiers along the path, as well as by recording timestamps and interface load on each hop for per-hop delay and packet loss calculations. For instance, in the case of Equal Cost Multi-Path (ECMP) routing, different ECMP paths can be tested by encoding different entropy -labels (for MPLS and Segment-Routing MPLS (SR-MPLS)) and flow-labels (for IPv6 and SRv6) in the packet. Path tracing will now be described along the repair paths, with reference to FIG. 4.
  • ECMP Equal Cost Multi-Path
  • FIG. 4 illustrates an example communication diagram between a source node and a destination node implementing SR-path assurance/path tracing that tests all ECMP paths betyveen two endpoints, according to some aspects of the present technology.
  • PLR point of local repair
  • source node 302 can send probe traffic to node 404.
  • the probe traffic can be forced to take repair FRR path 422 through node 414, node 416, to be routed to node 406.
  • the probe traffic is forced to take repair FRR path 422 using SR- Path Assurance or Path Tracing.
  • the probe traffic can identify a node failure on primary FRR path 424 including nodes 408 and 410.
  • the probe traffic can also determine that repair FRR path 422, which includes nodes 418, 420, and 410, is also experiencing a node failure due to the node failure at node 408. Therefore, the probe traffic can send this information back to source node 402, indicating that destination node 412 is inaccessible due to the node failure at node 408 on both primary FRR path 424 and repair FRR path 422.
  • the information carried by the probe traffic allows for liveness detection on the repair paths between two endpoints from source node 402, thus greatly enhancing network reliability.
  • source node 402 can take appropriate corrective action with the provided information. This enables network operators to identify faults and restore service while minimizing disruptions quickly.
  • an MPLS sub-stack and/or IPv6 extension headers may be utilized, which can assist in determining the next hop for a data packet, as well as provide routing information to reach a destination node.
  • FIG. 5A-5B illustrates an example message flow between a source node and destination node in a continuous mode according to some aspects of the present technology.
  • Example message flow 500 can be between source node 502 and destination node 512 in a continuous mode, according to some aspects of the present technology.
  • a discovery probe packet with a hop-by-hop scope option is sent from source node 502 to destination node 512 to discover all FRR nodes on the path.
  • the packet may be duplicated at the first FRR node, with one sent through the primary path, via a primary probe, and another through the repair path, via a repair probe.
  • the discovery' probe packet can follow an FRR path until an FRR switchover indication is detected.
  • An FRR switchover can indicate a process of switching or diverting network traffic from the primary' FRR path to the repair FRR path when a network failure or fault is detected or performance metric is violated.
  • the FRR switchover can further indicate an action that can take place when a network event triggers the use of the repair FRR path to maintain netw ork continuity and reduce service disruption. Accordingly, if an FRR switchover is triggered in any node, the primary probe may be dropped. Whenever the primary probe hits an FRR node, the primary probe can duplicate a repair probe packet and forward the same to the repair FRR path, while the primary’ probe continues on the primary FRR path. The repair probe can then flow through the regular data path from that point and does not overlap with any other repair path.
  • FIG. 5A-5B two FRR paths are shown in communication between source node 502 and destination node 512 (primary FRR path 522 through nodes 504, 506. 508, 510) and a repair path formed of first repair path 524 (through nodes 504, 514, 516, and back to node 506) and second repair path 526 (through nodes 508, 518, 520, and back to node 510).
  • a discovery probe 528 is generated with an MPLS Network Action (MNA) header that includes a ‘'Start-DIS” set to zero ("0") and “FRR-Node-Count” set to zero in the MNA flag.
  • MNA MPLS Network Action
  • the "Start-DIS" in the discovery probe allows the source node 502 to start the repair FRR path discovery from a specific node on the path based on the hop count. If set to zero, this indicates that discovery should begin from source node 302. whereas if it is set to a nonzero value, it starts when Start-DIS > TTL. This helps network operators quickly locate and repair faults in their networks. Additionally, the MNA flag field can be used to monitor their network performance and make informed decisions about maintenance and upgrades in the long run.
  • This discovery probe 528 may then be forwarded to node 504.
  • the discovery probe detects that FRR capability is available. This results in generation of two probes - a primary' probe 530 and a repair probe 532.
  • primary' probe 530 may be generated with "FRR-Node-Count” set to " 1", and is sent along primary' FRR path 522 towards node 506.
  • a repair probe 532 is generated with "FRR-Node-Count” set to the cunent TTL value, after being decremented. Repair probe 532 is then sent along first repair path 524.
  • the FRR-Node-Count field in discovery probe 528 keeps track of the number of FRR nodes detected on the path for the Primary -Probe, and from where the repair probe and the FRR switchover probe was generated based on hop count.
  • Node 504 which has the FRR capability, lacks information about the status of other nodes on the first repair path 524, such as node 514, node 516, and node 506.
  • Node 506 forwards primary probe 530 and repair probe 532 to node 508.
  • Repair probe 532 is forwarded by node 508 to node 510 as a regular data packet.
  • the FRR node count increases in the primary probe 530 received from node 504 when it reaches node 506.
  • node 508 creates a second primary' probe 538 and a second repair probe 540. These probes are transmitted along primary' FRR path 522 and second repair path 526, respectively.
  • node 510 modifies the FRR node count field in second primary probe 538 by incrementing the count field followed by forwarding the updated packet as Final primary' probe 542 to destination node 512.
  • Second repair probe 540 upon being received by node 518 along second repair path 526 is modified (the current TTL value in second repair probe 540 is decremented), and forwarded to node 520 and then to node 510. Node 510 then sends repair probe 532, Final primary probe 542, and second repair probe 540 as regular data packets to destination node 512.
  • the MNA option originally possessing a hop-by-hop discovery configuration is changed to an end-to-end discovery configuration and the three probes (i.e., repair probe 532, second repair probe 540, and Final primary probe 542) are sent back to the source node 502.
  • FIG. 6A-6B illustrates an example communication diagram between a source node and destination node in a targeted mode, according to some aspects of the present technology.
  • the described example process includes sending a discovery-probe packet with a hop-by- hop discovery' configuration from a source node to a destination node to traverse and discover the first occurrence of a node with FRR capability.
  • a single discovery probe packet is sent from a source towards the destination with the Start-DIS field set with the hop from where it needs to start the discovery for the first occurrence of the FRR node.
  • the discoveryprobe When the discoveryprobe hits the first FRR node based on “Start-DIS”, it sends two probes, namely a primary probe towards the primary path and a repair probe towards the repair path.
  • the primary-probe packet flows through the primary’ path, if the FRR syvitchover is triggered in any of the node, then the primary-probe is dropped.
  • the primary probe also carries the hop count at the node based on the TTL value in the packet.
  • the repair probe carries the hop count at the node based on the TTL value in the packet and flows through the regular data path from that point.
  • a single discover ⁇ ’ probe packet yvith a hop-by-hop discovery configuration is sent from source node 602 to destination node 612 for tracing a specific FRR repair path. Similar to FIG. 5A-5B, there are two FRR paths betyveen source node 602 and destination node 612. The first path is primary FRR path 624 between source node 602 and destination node 612 through nodes 604, 606, 608. and 610. The other path is a repair path comprising of a first repair FRR paths 626 (through nodes 604, 614, 616, and 606) and second repair FRR path 628 (through nodes 608, 618, 620 and 610).
  • the source node 602 generates a discovery probe 622 that includes an MPLS MNA header where the TTL is set as “64”, “Start-DIS” as “63”, “FRR-Node-Count” as “0” and "Repair-Path- TTL” as "1".
  • the Repair-Path-TTL is decremented by 1 after passing through each intermediate node along primary FRR path 624. This packet is then forwarded to node 604. To ensure effective tracing of the repair path by source node 602, the source node initiates the "Repair-Path-TTL" value at " 1" and increase it by " 1" for each subsequent probe.
  • discovery probes 622 reaches node 604.
  • node 606 since there is no FRR, node 606 also forwards discovery' probe 622 to node 608 after decrementing the TTL value to 62.
  • the MPLS packet's TTL value is again decremented by 1 to “61” and is now less than Start-DIS “63” value. Therefore, at node 608, two new probes are generated (primary probe 630 and repair probe 632).
  • primary probe 630 is generated with FRR-Node-Count set to “1” and the value in the “Repair-Path-TTL” being replaced with the current TTL value “61” (after decrementing). Primary probe 630 is then forwarded to node 610.
  • repair probe 632 is generated with FRR-Node-Count set to the current TTL value “61” (after decrementing) and the outer packet’s TTL with the value in the Repair- Path-TTL field "64". Repair probe 632 is then forwarded to node 618, then to node 620, and finally to node 610 as regular data packet.
  • Node 610 then forwards primary probe 630 and repair probe 632 received from nodes 608 and 620, respectively, to destination node 612. Thereafter, destination node 612 may modify the MNA option in the received primary' probe 630 and repair probe 632 to “End-To-End” option and send the modified primary probe 630 and repair probe 623 back to source node 602.
  • FIG. 7 illustrates an example MPLS MNA header for FRR path traversing and discovery in continuous mode, according to some aspects of the present technology 7 .
  • the MPLS MNA header 700 can be a header of discovery probe 528 of FIG. 5A and can include an MPLS label 702.
  • the MPLS label 702 can include a short, fixed-length value (e.g.. 20 bits), that is assigned to the packet at source node 502.
  • the MPLS label 702 in some examples can represent a forwarding equivalence class (FEC), which is a group of packets that should be treated in the same w ay within the network.
  • the MPLS MNA header 700 further includes a merge node announcement (MNA) label 704.
  • MNA merge node announcement
  • the MNA label 704 is a label assigned to an alternate path by a merge node identified as being FRR capable.
  • the MNA label is used to guide the packets through the alternate path to reach their destination without traversing the failed portion of the network.
  • the MPLS MNA header 700 further includes a first network access identifier (NAI) opcode 706.
  • NAI opcode is a field or code within a network protocol message that specifies the type or format of the Network Access Identifier being transmitted. As shown in MPLS MNA header 700, the first NAI Opcode 706 is set to 3.
  • the MPLS MNA header 700 further includes a second NAI Opcode 708 that is assigned by for FRR path traversing and discovering.
  • the second NAI Opcode 708 includes a “Start-DIS” that allows the source node to start the repair FRR path discovery after a specific node on the path based on the hop count. For example, if the Start-DIS is set to “0”, the first FRR discover ⁇ ' starts from the source node. If the Start-DIS is non-zero, the first FRR discovery’ start when the Start- DIS > TTL.
  • the second NAI Opcode 708 includes a FRR node count that tallies FRR nodes in the path, and a probe state (PS) indicator with a two-bit indication.
  • PS probe state
  • the probe when the PS indicator is set as 00(D), the probe is in a discovery' state. On the other hand, when it is set as 01 (P), the probe is in a primary state traversing the primary FRR path. If the FRR is triggered, the probe is dropped. If the PS indicator is 10(R). the probe is in a repair state traversing the primary FRR path. Lastly, if the PS indicator shows 1 1(RF), the probe is in a repair-FRR-switchover state traversing the primary' FRR path.
  • FIG. 8 illustrates an example ISD MNA header for FRR path traversing and discovering in the targeted mode according to some aspects of the present technology 7 .
  • the MPLS MNA header 800 can be a header of discovery' probe 622 and may include different components (fields) as discussed above with reference to MPLS MNA header 700 of FIG. 7.
  • the MPLS MNA header 800 can include an additional repair path TTL 802 used to trace the route of the repair path.
  • the repair path TTL 802 is a specific value that indicates the maximum number of hops or network segments that a packet can traverse along the repair path.
  • the repair path TTL is included in the MNA header to ensure that packets follow the correct alternate path while avoiding looping or excessive traversal.
  • a single reserved bit can be used in the repair path TTL 802 field to differentiate between the functionality’ of each mode.
  • the In-Stack Data (ISD) MNA header discussed in FIG. 8. can be used as a Post-Stack Data (PSD) MNA header instead in a continuous mode.
  • PSD Post-Stack Data
  • FIG. 9A illustrates an example PSD MNA header for FRR path traversing and discovery in continuous mode, according to some aspects of the present technology.
  • the PSD MNA header can be a header in discovery probe 528 and may include a PSD MNA field 902.
  • the PSD MNA field 902 can include a PS-MNA-Opcode (PS-MNA-OP), a Start-DIS as a TTL value, and an FRR- Node-Count.
  • PS-MNA-OP field can indicate and specify the type or format of the PSD MNA being transmitted, to provide interpretation information or how to interpret and process the PSD MNA.
  • the Start-DIS is a hop count value that allows the source node to start the repair FRR path discovery from a specific node on the path based on the hop count.
  • the FRR node count in the case of the primary probe, records the number of FRR nodes in the path. In the case of a repair probe, it records the hop count from where this probe is generated.
  • FIG. 9B illustrates an example PSD MNA header for FRR path traversing and discover ⁇ ' in targeted mode, according to some aspects of the present technology.
  • PSD MNA field 902 can be a header of discovery probe 622.
  • the PSD MNA header 900 can also include a repair path TTL 904 field.
  • the repair path TTL 904 field is a specific value that is assigned to packets when they are directed along an alternate or repair path during network recovery’, such as in MPLS Fast Re-Route (FRR).
  • This repair path TTL 904 field represents the maximum number of network segments, or hops, that the packet is allowed to traverse along the repair path.
  • FIG. 10 illustrates an example ISD MNA header for FRR path traversing in continuous and targeted modes , according to some aspects of the present technology.
  • ISD MNA header 1000 can be a header in discovery probe 528 and/or discovery probe 622.
  • the ISD MNA header 1000 can utilize the PS value of the second NAI Opcode 1002 field to identify traversal paths during a network failure.
  • the PS value can exclude Start-DIS and FRR-Node-Count, enabling probes to navigate repair paths without gaining further knowledge.
  • FIG. 11 A illustrates an example ISD and PSD MNA header for FRR path traversing and discovery in continuous mode, according to some aspects of the present technology.
  • 1100 can be a header in discovery' probe 528.
  • the PS MNA OP 1102 field includes the Start-DIS, and FRR node count.
  • the PS could be encoded in the ISD MNA. Accordingly, the “Start- DIS” and “FRR-Node-Count can be encoded in the PSD MNA in the continuous mode.
  • FIG. 1 IB illustrates an example ISD and PSD MNA headers 1106 for FRR path traversing and discovery in targeted mode, according to some aspects of the present technology'.
  • ISD and PSD MNA header 1106 can be a header in discovery probe 622.
  • the PS can also be encoded in the ISD MNA and the “Start-DIS” and “FRR-Node-Count” could be encoded in the PSD (Post-Stack Data) MNA in targeted mode. Additionally, the Repair Path TTL 1104 value can be indicated as reserved.
  • This indication of “reserved’” for the Repair Path TTL 1104 provides the ability to precisely define and govern the maximum number of hops or network segments that packets are allowed to traverse when utilizing the alternate repair path. Such meticulous control is imperative to ensure that packets follow the intended path without the risk of excessive traversal or looping.
  • IPv6 data packets are often be utilized to cany' routing and delivery information.
  • the IPv6 data packets possess an IPv6 header that is a fixed-length header of 40 bytes in length, which simplifies packet processing and enhances routing efficiency.
  • IPv6 data packets can further include extension headers (e.g., IPv6 Hop-By-Hop and Destination options), which are additional headers that provide various functionalities such as fragmentation, security, mobility, and routing information.
  • FIG. 12A illustrates an example IPv6 extension header for FRR path traversing in continuous mode, according to some aspects of the present technology.
  • the IPv6 extension header 1200 can be the header in discovery probe 528.
  • the IPv6 extension header 1200 can include instructions that indicate an order that the fields in the IPv6 header are to be executed.
  • the IPv6 extension header 1200 can include a next header field, a length of the extension header, an option type field, and a specified length.
  • IPv6 extension 1202 fields are allocated to carry Start-DIS, FRR-Node-Count, and PS information.
  • the probe's entropy label for MPLS and flow-label for IPv6 can be varied in another embodiment.
  • FIG. 12B illustrates an example IPv6 extension header for targeted mode according to some aspects of the present technology.
  • IPv6 extension header 1206 can be a header in discovery probe 622.
  • the new IPv6 extension 1202 is allocated to carry "Start-DIS", "FRR-Node-Count", and "Probe-State” information.
  • an additional copy of the primary probe can be created in its final form. Accordingly, one copy can be sent according to the instructions provided, while the other can be updated with the TTL. This will allow the source node to detect any failures in the backup probe response and use the targeted mode to isolate the problem.
  • FIG. 13 illustrates an example process for monitoring a FRR path betw een a source node and a destination node in anetwork, according to some aspects of the present technology.
  • example process 1300 depicts a particular sequence of operations, the sequence may be altered without departing from the scope of the present disclosure. For example, some of the operations depicted may be performed in parallel or in a different sequence that does not materially affect the function of the process 1300. In other examples, different components of an example device or system that implements the process 1300 may perform functions at substantially the same time or in a specific sequence.
  • the process 1300 generates a discover ⁇ ' probe from the source node. This probe is used to detect at least one node that has an FRR indicator along the FRR path.
  • the FRR path includes multiple next available nodes.
  • the discover ⁇ ' probe reaches the first node that has the FRR indicator, it is forwarded to the remaining next available nodes for repair path discovery' along the FRR path.
  • the source node 502 illustrated in FIG. 5A may generate a discovery probe to detect at least one node comprising an FRR indicator along the FRR path that includes a plurality of next available nodes.
  • a discover ⁇ ' probe is forwarded to a plurality of next available nodes to initiate a repair path discover ⁇ ' along the FRR path.
  • the discover ⁇ ' probe comprises a hop count value. Accordingly, in a targeted mode as illustrated in FIG. 6B. the hop count value can indicate a specific node along the primary’ FRR path 624 to start the discovery of the second repair FRR path 628 in accordance w ith the specified hop count value.
  • the process 1300 includes identifying an FRR indicator at a first node upon the discovery’ probe reaching a first node comprising the FRR indicator.
  • the discovery probe including the Discovery probe 528 in FIG. 5A can be received by node 504, possessing FRR capability.
  • the discover ⁇ ’ probe identifies node 504 as a merge node with FRR capability , indicated by the FRR indicator, allow ing it to divert data traffic to a repair FRR path.
  • the discovery probe can continue along the primary FRR path and detect a second node, with FRR capability that includes the ability to divert data traffic to a second repair FRR path during a netw ork failure.
  • the discovery' probe can be received by node 508, in FIG. 5B, possessing FRR capability.
  • Node 508 can indicate via a second FRR indicator that there is a first repair FRR first repair path 524 that data traffic can be routed to upon the detection of a network failure.
  • the process 1300 can further include generating a duplicate repair probe to detect a repair path comprising a fourth set of nodes to for-ward the repair probe towards the destination node.
  • node 508 illustrated in FIG. 5B may generate a duplicate repair probe from the repair probe generated at node 504, to detect a repair path comprising another set of nodes to forward the repair probe toward the destination node.
  • process 1300 includes generating a primary probe configured to detect a primary path comprising a first set of nodes to forward the primary probe toward the destination node.
  • node 504 can generate a primary probe configured to detect a primary FRR path comprising a first set of primary 7 nodes to forward the primary probe toward the destination node.
  • the process 1300 can further include generating a repair probe configured to detect a repair path comprising a second set of nodes to forward the repair probe toward the destination node.
  • node 504 can generate a repair probe (e.g., repair probe 532 or repair probe 632) configured to detect a repair FRR path comprising a first set of repair nodes to forward the primary probe toward the destination node.
  • process 1300 includes sending the primary probe and the repair probe back to the source node to monitor the FRR path between the source node and the destination node, in response to receiving the primary probe via the primary path and the repair probe via the repair path at the destination node.
  • the destination node 512 illustrated in FIG. 5B may send the primary probe and the repair probe received from node 510 back to the source node 502 to monitor the FRR path, including the primary FRR path 522, and first repair path 524/ second repair path 526 between the source node 502 and the destination node 512.
  • the monitored FRR path sent to the source node indicates a node value representative of the total number of nodes in the primary path.
  • the discovery probe, the primary probe, and the repair probe are encapsulated within data packets that include a specific header indicating their respective roles and functions within FRR path monitoring.
  • FIG. 14 illustrates an example of a computing system according to some aspects of the present technology.
  • Example computing system 1400 can be any of the network devices and components described above with reference to FIGs. 1-13 including, but not limited to, source node 502/602, destination node 512/612, any intermediary' nodes in FIGs. 5 and 6, etc.
  • FIG. 14 shows an example of computing system 1400, which can be for example any computing device making up a system network, or any component thereof in which the components of the system are in communication with each other using connection 1402.
  • Connection 1402 can be a physical connection via a bus, or a direct connection into processor 1404, such as in a chipset architecture.
  • Connection 1402 can also be a virtual connection, networked connection, or logical connection.
  • computing system 1400 is a distributed system in which the functions described in this disclosure can be distributed within a datacenter, multiple data centers, a peer network, etc.
  • one or more of the described system components represents many such components each performing some or all of the function for which the component is described.
  • the components can be physical or virtual devices.
  • Example computing system 1400 includes at least one processing unit (central processing unit (CPU) or processor) 1404 and connection 1402 that couples various system components including system memory 1408, read-only memory (ROM) 1410. and random-access memory’ (RAM) 1412 to processor 1404.
  • Computing system 1400 can include a cache of high-speed memory 1408 connected directly with, in close proximity to, or integrated as part of processor 1404.
  • Processor 1404 can include any general-purpose processor and a hardware service or software sendee, such as services 1416, 1418, and 1420 stored in storage device 1414, configured to control processor 1404 as well as a special -purpose processor where software instructions are incorporated into the actual processor design.
  • Processor 1404 may essentially be a completely self- contained computing system, containing multiple cores or processors, a bus. memory controller, cache, etc.
  • a multi-core processor may be symmetric or asymmetric.
  • computing system 1400 includes an input device 1426, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc.
  • Computing system 1400 can also include output device 1422, which can be one or more of a number of output mechanisms known to those of skill in the art.
  • output device 1422 can be one or more of a number of output mechanisms known to those of skill in the art.
  • multimodal systems can enable a user to provide multiple types of input/output to communicate with computing system 1400.
  • Computing system 1400 can include communication interface 1424, which can generally govern and manage the user input and system output.
  • Storage device 1414 can be a non-volatile memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs), read-only memory (ROM), and/or some combination of these devices.
  • a computer such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs), read-only memory (ROM), and/or some combination of these devices.
  • the storage device 1414 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 1404, it causes the system to perform a function.
  • a hardware sendee that performs a particular function can include the software component stored in a computer-readable medium in connection with the hardware components, such as processor 1404, connection 1402, output device 1422, etc., to carryout the function.
  • a method for monitoring a Fast Re-Route (FRR) path between a source node (Node-S) and a destination node (Node-E) in a network includes generating a discovery-probe at the source node (Node-S) to detect at least one node with an FRR indicator along the FRR path that includes a plurality of next available nodes.
  • the method also includes upon the discovery- probe reaching a first node with the FRR indicator, generating a primary- probe configured to detect a primary- path and a repair probe configured to detect a repair path.
  • the method also includes in response to receiving the primary probe via the primary path and the repair probe via the repair path at the destination node, sending the primary- probe and the repair probe back to the source node to monitor the FRR path between the source node and the destination node.
  • the present technology may be presented as including individual functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
  • a service can be software that resides in the memory- of a client device and/or one or more servers of a content management system and performs one or more functions when a processor executes the software associated with the sen-ice.
  • a service is a program or a collection of programs that carry out a specific function.
  • a service can be considered a server.
  • the memory- can be a non-transitory computer-readable medium.
  • the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like.
  • non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
  • Methods according to the above-described examples can be implemented using computerexecutable instructions that are stored or otherwise available from computer-readable media.
  • Such instructions can comprise, for example, instructions and data that cause or otherwise configure a general -purpose computer, special-purpose computer, or special-purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network.
  • the computer-executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code.
  • Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, solid-state memory devices, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
  • Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include servers, laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein can also be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
  • the instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
  • a method for monitoring a fast re-route (FRR) path between a source node (node- s) and a destination node (node-e) in a network comprising the steps of: generating a discoveryprobe at the source node (node-s) to detect at least one node comprising an FRR indicator along the FRR path that includes a plurality of next available nodes, wherein the discovery probe is forwarded to the plurality of next available nodes to initiate a repair path discovery along the FRR path; upon the discovery probe reaching a first node with the FRR indicator, generating: a primary probe configured to detect a primary’ path comprising a first set of nodes to forward the primary’ probe towards the destination node; and a repair probe configured to detect a repair path comprising a second set of nodes to forward the repair probe towards the destination node; and in response to receiving the primary’ probe via the primary’ path and the repair probe via the repair path at the destination node, sending the primary
  • Clause 2 The method of clause 1, further comprising: identifying a second node along the FRR path that includes a second repair path, wherein the second node does not include the FRR indicator; and forwarding the discovery probe to the next available node, wherein the discovery probe bypasses the second repair path.
  • Clause 3 The method of clause 1 or 2, further comprising: identifying a second node along the primary path that includes a second FRR indicator, wherein the second node is configured to: generate a duplicate primary probe to detect the primary path comprising a third set of nodes to forward the duplicate primary probe towards the destination node; and generate a duplicate repair probe to detect a repair path comprising a fourth set of nodes to forward the repair probe towards the destination node.
  • Clause 4 The method of any of clauses 1 to 3, wherein the discovery probe comprises a hop count value, wherein the hop count value indicates a specific node along the FRR path to start discovery of the repair path.
  • Clause 5 The method of any of clauses 1 to 4, wherein the monitored FRR path sent to the source node indicates a node value representative of a total number of nodes in the primary’ path, and a hop count value indicated where the repair node is generated.
  • Clause 6 The method of any of clauses 1 to 5, wherein the discovery' probe, the primary probe, and the repair probe are encapsulated within data packets that include a specific header indicating their respective roles and functions within the FRR path monitoring process.
  • Clause 7. The method of any of clauses 1 to 6, further comprising: triggering an FRR switchover process based on network conditions and performance metrics, wherein in response to the FRR switchover being triggered, the second probe is configured to generate a repair FRR Switchover Probe and send it along the repair path instead of the repair probe, to expedite the monitoring of the repair path and ensure network resiliency during FRR switchover events..
  • a network device comprising: one or more memories having computer-readable instructions stored therein; and one or more processors configured to execute the computer- readable instructions to: generate a discovery-probe at the source node (node-s) to detect at least one node comprising an FRR indicator along the FRR path that includes a plurality of next available nodes, wherein the discover ⁇ ' probe is forwarded to the plurality of next available nodes to initiate a repair path discovery' along the FRR path; upon the discovery' probe reach a first node with the FRR indicator, generating: a primary probe configured to detect a primary’ path comprising a first set of nodes to forward the primary probe towards the destination node; and a repair probe configured to detect a repair path comprising a second set of nodes to forward the repair probe towards the destination node; and in response to receiving the primary' probe via the primary path and the repair probe via the repair path at the destination node, send the primary' probe and the repair probe back to the source node to monitor the F
  • Clause 9 The network device of clause 8, further comprising: identifying a second node along the FRR path that includes a second repair path, wherein the second node does not include the FRR indicator; and forwarding the discovery probe to the next available node, wherein the discovery' probe bypasses the second repair path.
  • Clause 10 The network device of clause 8 or 9. further comprising: identifying a second node along the primary path that includes a second FRR indicator, wherein the second node is configured to: generate a duplicate primary' probe to detect the primary path comprising a third set of nodes to forward the duplicate primary' probe towards the destination node; and generate a duplicate repair probe to detect a repair path comprising a fourth set of nodes to forward the repair probe towards the destination node.
  • Clause 11 The network device of any of clauses 8 to 10, wherein the discovery' probe comprises a hop count value, w herein the hop count value indicates a specific node along the FRR path to start discovery of the repair path.
  • Clause 12 The network device of any of clauses 8 to 11. wherein the monitored FRR path sent to the source node indicates a node value representative of a total number of nodes in the primary’ path, and a hop count value indicated where the repair node is generated.
  • Clause 13 The network device of any of clauses 8 to 12, wherein the discovery probe, the primary’ probe, and the repair probe are encapsulated within data packets that include a specific header indicating their respective roles and functions within the FRR path monitoring process.
  • Clause 14 The network device of any of clauses 8 to 13. further comprising: triggering an FRR switchover process based on network conditions and performance metrics, wherein in response to the FRR switchover being triggered, the second probe is configured to generate a repair FRR Switchover Probe and send it along the repair path instead of the repair probe, to expedite the monitoring of the repair path and ensure network resiliency during FRR switchover events.
  • One or more non-transitory computer-readable storage media comprising computer-readable instructions, which when executed by one or more processors of a network appliance, cause the network appliance to: generate a discovery-probe at the source node (node-s) to detect at least one node comprising an FRR indicator along the FRR path that includes a plurality of next available nodes, wherein the discovery probe is forwarded to the plurality of next available nodes to initiate a repair path discovery along the FRR path; upon the discovery’ probe reach a first node with the FRR indicator, generating: a primary probe configured to detect a primary path comprising a first set of nodes to forward the primary probe towards the destination node; and a repair probe configured to detect a repair path comprising a second set of nodes to forward the repair probe towards the destination node; and in response to receiving the primary' probe via the primary path and the repair probe via the repair path at the destination node, send the primary' probe and the repair probe back to the source node to monitor the
  • Clause 16 The one or more non-transitory computer-readable storage media of clause 15, wherein the one or more processors are further configured to: identifying a second node along the FRR path that includes a second repair path, wherein the second node does not include the FRR indicator; and forwarding the discovery probe to the next available node, wherein the discovery probe bypasses the second repair path.
  • Clause 17 The one or more non-transitory computer-readable storage media of clause 15 or 1 , wherein the one or more processors are further configured to: generate a duplicate primary probe to detect the primary' path comprising a third set of nodes to forward the duplicate primary' probe towards the destination node; and generate a duplicate repair probe to detect a repair path comprising a fourth set of nodes to forward the repair probe towards the destination node.
  • Clause 18 The one or more non-transitory computer-readable storage media of any of clauses 15 to 17, wherein the discovery’ probe comprises a hop count value, wherein the hop count value indicates a specific node along the FRR path to start discovery of the repair path.
  • Clause 19 The one or more non-transitory computer-readable storage media of any of clauses 15 to 18, wherein the monitored FRR path sent to the source node indicates a node value representative of a total number of nodes in the primary path, and a hop count value indicated where the repair node is generated.
  • Clause 20 The one or more non-transitory computer-readable storage media of any of clauses 15 to 19, wherein the discovery probe, the primary probe, and the repair probe are encapsulated within data packets that include a specific header indicating their respective roles and functions within the FRR path monitoring process.

Landscapes

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

Abstract

Selon un aspect, un procédé de surveillance d'un chemin de reroutage rapide (FRR) entre un nœud source (nœud S) et un nœud de destination (nœud E) dans un réseau comprend les étapes consistant à : générer une sonde de découverte au niveau du nœud source (nœud S) de façon à détecter au moins un nœud contenant un indicateur de FRR le long du chemin de FRR qui compte une pluralité de prochains nœuds disponibles ; lorsque la sonde de découverte atteint un premier nœud contenant l'indicateur de FRR, générer une sonde primaire configurée pour détecter un chemin primaire et une sonde de réparation configurée pour détecter un chemin de réparation ; et en réponse à la réception de la sonde primaire par l'intermédiaire du chemin primaire et de la sonde de réparation par l'intermédiaire du chemin de réparation au niveau du nœud de destination, renvoyer la sonde primaire et la sonde de réparation au nœud source de façon à surveiller le chemin de FRR entre le nœud source et le nœud de destination.
EP23844607.4A 2022-12-14 2023-12-13 Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux noeuds Pending EP4635152A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
IN202221072144 2022-12-14
IN202341055817 2023-08-21
US18/504,840 US12184534B2 (en) 2022-12-14 2023-11-08 Monitoring primary and local repair paths on all hops between two nodes
PCT/US2023/083817 WO2024129850A1 (fr) 2022-12-14 2023-12-13 Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux nœuds

Publications (1)

Publication Number Publication Date
EP4635152A1 true EP4635152A1 (fr) 2025-10-22

Family

ID=89715876

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23844607.4A Pending EP4635152A1 (fr) 2022-12-14 2023-12-13 Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux noeuds

Country Status (2)

Country Link
EP (1) EP4635152A1 (fr)
WO (1) WO2024129850A1 (fr)

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11516122B2 (en) * 2021-04-20 2022-11-29 Ciena Corporation Validating active and inactive paths in a multiprotocol label switching (MPLS) network

Also Published As

Publication number Publication date
WO2024129850A1 (fr) 2024-06-20

Similar Documents

Publication Publication Date Title
US10771434B1 (en) Route signaling driven service management
US10999125B1 (en) Inter-application communication via signal-routes
EP3605968B1 (fr) Modèle de redondance de passerelle d'applications dynamiques n:1
US12184534B2 (en) Monitoring primary and local repair paths on all hops between two nodes
US10819833B2 (en) Dynamic re-route in a redundant system of a packet network
US9742657B2 (en) Method and system for resynchronization of forwarding states in a network forwarding device
US9641430B2 (en) Verifying data plane paths based on a validated secure control plane
US20240129223A1 (en) Systems and methods for data plane validation of multiple paths in a network
US9608858B2 (en) Reliable multipath forwarding for encapsulation protocols
US20070180105A1 (en) Technique for distinguishing between link and node failure using bidirectional forwarding detection (BFD)
EP3750073B1 (fr) Procédé de migration sans coupure d'authentification de session vers un homologue d'authentification diameter différent à état
US12244509B2 (en) PIM proxy over EVPN fabric
EP4554177A1 (fr) Suivi de chemin appliqué à des matrices de protocole internet version 6 (ipv6)
WO2024129850A1 (fr) Surveillance d'un chemin primaire et d'un chemin de réparation local sur tous les sauts entre deux nœuds
US12418472B2 (en) End-to-end dynamic multicast-only fast re-route (MoFRR)
US12476893B2 (en) Point-to-multipoint service assurance using performance measurement
US20250247336A1 (en) Routing improvement to reduce impact of out-of-resource condition
US20250141788A1 (en) Redundant multicast for dynamic connectivity
Garg Label Distribution Protocol & Loop Free Alternative
WO2017149364A1 (fr) Réacheminement de trafic coordonné dans un système avec redondance inter-châssis
Le Implementation of GlobalProtect and Data Centre Interconnect
Rao Traffic management between two locations across multiprotocol label switching backbone cloud with enhanced network security
Press Building Resilient IP Networks

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250626

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR