Recovery modeling in MPLS networks

Transmission of QoS based traffic over packet switched network typically requires resource reservation or differentiated treatment to guarantee an acceptable level of performance. But it is also essential to bound the disruption caused by failure of nodes or links for a real time traffic to a limit that is acceptable by the application. In this paper, a simulation platform models the impact of the MPLS recovery/protection schemes on the QoS traffic parameters including disruption time and number of out of order packets arriving at the destination. The simulation considers measures to alleviate drawbacks caused by recovery process

Real-time bandwidth encapsulation for IP/MPLS Protection Switching

Bandwidth reservation and bandwidth allocation are needed to guarantee the protection of voice traffic during network failure. Since voice calls have a time constraint of 50 ms within which the traffic must be recovered, a real-time bandwidth management scheme is required. Such bandwidth allocation scheme that prioritizes voice traffic will ensure that the voice traffic is guaranteed the necessary bandwidth during the network failure. Additionally, a mechanism is also required to provide the bandwidth to voice traffic when the reserved bandwidth is insufficient to accommodate voice traffic. This mechanism must be able to utilise the working bandwidth or bandwidth reserved for lower priority applications and allocate it to the voice traffic when a network failure occurs

SPIDER: Fault Resilient SDN Pipeline with Recovery Delay Guarantees

When dealing with node or link failures in Software Defined Networking (SDN), the network capability to establish an alternative path depends on controller reachability and on the round trip times (RTTs) between controller and involved switches. Moreover, current SDN data plane abstractions for failure detection (e.g. OpenFlow "Fast-failover") do not allow programmers to tweak switches' detection mechanism, thus leaving SDN operators still relying on proprietary management interfaces (when available) to achieve guaranteed detection and recovery delays. We propose SPIDER, an OpenFlow-like pipeline design that provides i) a detection mechanism based on switches' periodic link probing and ii) fast reroute of traffic flows even in case of distant failures, regardless of controller availability. SPIDER can be implemented using stateful data plane abstractions such as OpenState or Open vSwitch, and it offers guaranteed short (i.e. ms) failure detection and recovery delays, with a configurable trade off between overhead and failover responsiveness. We present here the SPIDER pipeline design, behavioral model, and analysis on flow tables' memory impact. We also implemented and experimentally validated SPIDER using OpenState (an OpenFlow 1.3 extension for stateful packet processing), showing numerical results on its performance in terms of recovery latency and packet losses.Comment: 8 page

Comparison Analysis Of Recovery Mechanism At Mpls Network

Multi-protocol Label Switching (MPLS) has become an attractive technology of choice for Internet backbone service providers.  MPLS features the ability to perform traffic engineering and provides support for Quality of Service traffic provisioning. To deliver reliable service, MPLS requires a set of procedures to provide protection for the traffic carried on Label Switched Paths (LSP). In this case Lable Switched Routers (LSRS) supports recovery mechanism when failure happened in the network.This paper studied about performance from usage of different techniques that can be used to reroute traffic faster then  the current IP rerouting methods in the case of a failure in a network. Local rerouting, fast reroute one to one backs up, Haskin, PSL oriented path protection and 1+1 path protection recovery mechanism was compared by given of aggregate traffic which has self-similarity character. Packet drop, rejection probability, recovery time, service disruption time and pre-reserved resources backup will be made as comparator parameter with various bitrate and different position of link failure. Packet loss, rejection probability, recovery time and service disruption time at five recovery mechanisms influenced by position of link failure to ingress. 1+1 path protection mechanism has least packet drop, but costliest way to do recovery in the case of usage resources, as traffic is sent simultaneously in two paths which disjoint. Fast reroute one to one backup is quickest way to operate protection switching recovery after 1+1 path protection mechanism. Keywords: MPLS, recovery, rerouting, self-similar traffic, protection switchingDOI:http://dx.doi.org/10.11591/ijece.v1i2.8

Logical topology design for IP rerouting: ASONs versus static OTNs

IP-based backbone networks are gradually moving to a network model consisting of high-speed routers that are flexibly interconnected by a mesh of light paths set up by an optical transport network that consists of wavelength division multiplexing (WDM) links and optical cross-connects. In such a model, the generalized MPLS protocol suite could provide the IP centric control plane component that will be used to deliver rapid and dynamic circuit provisioning of end-to-end optical light paths between the routers. This is called an automatic switched optical (transport) network (ASON). An ASON enables reconfiguration of the logical IP topology by setting up and tearing down light paths. This allows to up- or downgrade link capacities during a router failure to the capacities needed by the new routing of the affected traffic. Such survivability against (single) IP router failures is cost-effective, as capacity to the IP layer can be provided flexibly when necessary. We present and investigate a logical topology optimization problem that minimizes the total amount or cost of the needed resources (interfaces, wavelengths, WDM line-systems, amplifiers, etc.) in both the IP and the optical layer. A novel optimization aspect in this problem is the possibility, as a result of the ASON, to reuse the physical resources (like interface cards and WDM line-systems) over the different network states (the failure-free and all the router failure scenarios). We devised a simple optimization strategy to investigate the cost of the ASON approach and compare it with other schemes that survive single router failures

Segment Routing: a Comprehensive Survey of Research Activities, Standardization Efforts and Implementation Results

Fixed and mobile telecom operators, enterprise network operators and cloud providers strive to face the challenging demands coming from the evolution of IP networks (e.g. huge bandwidth requirements, integration of billions of devices and millions of services in the cloud). Proposed in the early 2010s, Segment Routing (SR) architecture helps face these challenging demands, and it is currently being adopted and deployed. SR architecture is based on the concept of source routing and has interesting scalability properties, as it dramatically reduces the amount of state information to be configured in the core nodes to support complex services. SR architecture was first implemented with the MPLS dataplane and then, quite recently, with the IPv6 dataplane (SRv6). IPv6 SR architecture (SRv6) has been extended from the simple steering of packets across nodes to a general network programming approach, making it very suitable for use cases such as Service Function Chaining and Network Function Virtualization. In this paper we present a tutorial and a comprehensive survey on SR technology, analyzing standardization efforts, patents, research activities and implementation results. We start with an introduction on the motivations for Segment Routing and an overview of its evolution and standardization. Then, we provide a tutorial on Segment Routing technology, with a focus on the novel SRv6 solution. We discuss the standardization efforts and the patents providing details on the most important documents and mentioning other ongoing activities. We then thoroughly analyze research activities according to a taxonomy. We have identified 8 main categories during our analysis of the current state of play: Monitoring, Traffic Engineering, Failure Recovery, Centrally Controlled Architectures, Path Encoding, Network Programming, Performance Evaluation and Miscellaneous...Comment: SUBMITTED TO IEEE COMMUNICATIONS SURVEYS & TUTORIAL

Multiclass data plane recovery using different recovery schemes in SDN: a simulation analysis

To provide dependable services SDN networks need to be resilient to link or switching node failures. This entails, when faults occur, ensuring differentiated types of recovery, according to carried traffic, to routing paths. However, the choice of the recovery scheme best suited to each traffic class is not direct, nor is obvious the impact of the combination of various recovery schemes, according to traffic classes. We explore the usage of different recovery schemes for traffic with distinct requirements Simulation analysis confirms that using different recovery schemes for distinct types of traffic does create differentiated effects in terms of traffic carried and bandwidth usage.info:eu-repo/semantics/publishedVersio