Pre-provisioning of local protection for handling dual-failures in OpenFlow-based networks

Thorat, Pankaj; Jeon, Seil; Raza, Syed M.; Choo, Hyunseung

doi:10.23919/cnsm.2017.8256050

Cited by 7 publications

(7 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The below figure shows the whole process of restoration approach. • Missing all matrix [70] Protection approach: Single Link and node failure recovery…”

Section: ) Restoration Approachmentioning

confidence: 99%

“…The researcher [71] and proposed the protection-based Figure 14: proactive approach approach heuristic algorithms, namely Forward Local Rerouting (FLR) and Backward Local Rerouting (BLR), to compute backup paths to improve TCAM and bandwidth usage efficiency in terms of single link failure, but not multiple link and node failure. The researcher [70] addressed this issue by developing a fault-tolerant forwarding table design (FFTD). It reduces the requirement for alternate path flow storage by up to 80 percent.It's also solved the carrier grid network scalability and congestion problems through multiple path restoration.…”

Section: ) Restoration Approachmentioning

confidence: 99%

See 1 more Smart Citation

Data plane failure and its recovery techniques in SDN: A systematic literature review

Khan¹,

Salleh²,

Koubâa³

et al. 2023

Preprint

View full text Add to dashboard Cite

Software-defined networking (SDN) plays a vital role in enterprise-networking and wide area networking. While it also has an emerging role in other wireless technologies such as 5G and IoT (Internet of Things), The growing number of strict SLA applications on the internet requires the network to be more scalable and fault tolerant. There is a need for research to evaluate the current state of the art of solutions in SDN and their emerging roles in other technologies. This study used a systematic literature review methodology to conduct this research. AS part of the survey, we reviewed 188 papers from 2010- 2021 and got 70 papers more relevant for our work. We only covered papers written in English. This research tries to help network engineers, administrators, and academic researchers in the domain of networking, find a better fault-tolerant solution for data plane in SDN.

show abstract

“…The below figure shows the whole process of restoration approach. • Missing all matrix [70] Protection approach: Single Link and node failure recovery…”

Section: ) Restoration Approachmentioning

confidence: 99%

Section: ) Restoration Approachmentioning

confidence: 99%

Data plane failure and its recovery techniques in SDN: A systematic literature review

Khan¹,

Salleh²,

Koubâa³

et al. 2023

Preprint

View full text Add to dashboard Cite

show abstract

“…However, in a large-scale network, the overhead would be non-trivial [9]. Another solution [148][148] considered the switch Flowtable storage constraints into account to devise a recovery scheme. A Fault-Tolerant Forwarding Table Design (FFTD) was introduced to group the flows using group entries and aggregates the flows using a tagging mechanism for rapid recovery from the dual failures.…”

Section: B Local and Path Restoration Approachesmentioning

confidence: 99%

“…In this way, FFTD satisfies the GCN's 50 ms recovery requirement thereby reducing the backup path flow storage requirement. However, neither [142] nor [148] considered post-recovery congestion after the localized recovery. In yet another solution to reduce the consumption of a backup resource, a shared ring was proposed [149].…”

Section: B Local and Path Restoration Approachesmentioning

confidence: 99%

Dynamic Routing and Failure Recovery Approaches for Efficient Resource Utilization in OpenFlow-SDN: A Survey

et al. 2022

View full text Add to dashboard Cite

Software Defined Networks (SDN) is a new network paradigm that emerged to offer better network management through the separation of network control logic and data forwarding element. This separation speed up network innovation without the need to rely on the vendor-proprietary interface for network element configuration to forward packets. However, SDN is flow driven network, for each arrived flow, a feasible path is computed to forward the flow to its destination. Afterward, the SDN control logic process the corresponding routing and instruct the set of data forwarding elements to install them on their Flowtable to guide the routing process. Unfortunately, the network changes more frequently in dynamic large-scale networks and the Flowtable is a constraint with limited space. These challenges require the SDN controller to compute paths more often which may also need a large number of flow routing rules placement. In addition, the frequency of communication link failures increases lately. The successful deployment of SDN heavily depends on how it satisfies the reliability requirement with uninterrupted services. Several studies were conducted to compute the optimal path for data forward to meet their Quality of Service demand. Other studies focus on reducing the frequency of link failure. Some studies were conducted to manage the constraint Flowtable resources. This survey focuses on Routing rules placement, unoptimized routing, link, and switch load balancing, failure detection, and recovery. The paper extensively discusses each issue and analyzes the weakness of the current solutions. Finally, it highlights potential challenges that need future research attention.

show abstract

“…However, these programming languages still lack certain features. For example, there are several alternatives, like the work, to cope with link and node failures. Each of these approaches can perform differently in different scenarios.…”

Section: Future Research Directionsmentioning

confidence: 99%

Solutions for adopting software defined network in practice

Shah

Giaccone

Rawat

et al. 2019

Int J Communication

View full text Add to dashboard Cite

Software defined networking (SDN) has emerged as a new network paradigm, which decouples both control and management planes from data plane by implementing control and management at a (logically) centralized node, i.e., the controller. The data plane communicates with controller by using an open programming interface (like Openflow protocol 1 ). The reference SDN architecture is given in Figure 1 and explained as follows.Data plane: The data plane consists of standard switching devices, acting as routers, switches, and access points depending on the how they are programmed. A forwarding table is available in each switching device. When a data packet arrives at the switching device, the latter looks up its forwarding table whether an entry exists for the corresponding flow. If yes, then the data packet is forwarded/dropped as per action specified in the entry. Otherwise, the switching device buffers the data packet and sends a message to the controller to ask for instructions on how to process the packet. The controller sends back a forwarding rule to install in the forwarding table, which programs the action that the switching device must apply for the buffered data packet, and eventually for the future packets belonging to the same flow.Control plane: The controller acts as the "network brain" and is responsible for computing the forwarding behavior for the data packets based on the network topology, the network requirements (e.g., specified throughout access control list (ACL) policies), and the configuration of other network management functions (e.g., load balancing). The controller computes the forwarding decision and installs the corresponding rules in the forwarding tables present in the switching devices.Management plane: The management plane specifies the network applications (like load balancing, firewall, and monitoring) developed by the network operator.Plane interfaces: These planes in SDN interact with each other through standardized interfaces. The basic interfaces are (a) the southbound interface, used for communication between data plane and control plane, and (b) the northbound interface, used for communication between control plane and management plane.The SDN architecture has several advantages over the traditional networks. First, it centralizes the control in the SDN controller allowing a single and coherent view of the network state, simplifying the development of complex network applications and enabling the network administrator to push specific policies across the entire network. Second, the SDN architecture allows to evolve the control plane without changing the switching devices, since their actual behavior is programmed at the controller and can be reprogrammed at wish. Third, in traditional networks, the network administrator has to utilize management systems and/or manually define and implement security policies (e.g., ACL) at several switching devices. Instead, in SDN, security and/or traffic engineering policies can be defined just at the controller, and these will be forced in th...

show abstract

Pre-provisioning of local protection for handling dual-failures in OpenFlow-based networks

Cited by 7 publications

References 15 publications

Data plane failure and its recovery techniques in SDN: A systematic literature review

Data plane failure and its recovery techniques in SDN: A systematic literature review

Dynamic Routing and Failure Recovery Approaches for Efficient Resource Utilization in OpenFlow-SDN: A Survey

Solutions for adopting software defined network in practice

Contact Info

Product

Resources

About