CHAPTER ONE
INTRODUCTION
1.1 Background of the Study
In recent years the Internet has been transformed from a special purpose network to a ubiquitous platform for a wide range of everyday communication services. The demands on Internet reliability and availability have increased accordingly. A disruption of a link in central parts of a network has the potential to affect hundreds of thousands of phone conversations or Transfer Control Protocol (TCP) connections, with obvious adverse effects. The ability to recover from failures has always been a central design goal in the Internet. Internet Protocol (IP) networks are intrinsically robust, since Interior Gateway Protocol (IGP) routing protocols like Open Shortest Path First (OSPF) are designed to update the forwarding information based on the changed topology after a failure. This re-convergence assumes full distribution of the new link state to all routers in the network domain. When the new state information is distributed, each router individually calculates new valid routing tables (Pondugala, & Nanaji, 2015).
This network-wide IP re-convergence is a time consuming process, and a link or node failure is typically followed by a period of routing instability. During this period, packets may be dropped due to invalid routes. This phenomenon has been studied in both IGP and Border Gateway Protocol (BGP) context, and has an ad-verse effect on real-time applications. Events leading to a re-convergence have been shown to occur frequently. Much effort has been devoted to optimizing the different steps of the convergence of IP routing, detection of non-functional nodes, dissemination of information and shortest path calculation, but the convergence time is still too large for applications with real time demands. A key problem is that since most network failures are short lived, too rapid triggering of the re-convergence process can cause rout Appling and increased network instability. The IGP convergence process is slow because it is reactive and global. It reacts to a failure after it has happened, and it involves all the routers in the domain. In this paper new scheme will be unveiled for handling link and node failures in IP networks (Pondugala, et al., 2015).
Multiple Routing Configurations MRC is a proactive and local, the main idea of MRC is to use the network graph and the associated link weights to produce a small set of backup for network configurations. The link weights in these backup configurations are manipulated so that for each link and node failure, and regardless of whether it is a link or node failure, the node that detects the failure can safely forward the incoming packets to-wards the destination on an alternate link. MRC assumes that the network uses shortest path routing and destination based hop-by-hop forwarding. The shifting of traffic to links bypassing the failure can lead to congestion and packet loss in parts of the network. This limits the time that the proactive recovery scheme can be used to forward traffic before the global. Routing protocol is informed about the failure, and hence reduces the chance that a transient failure can be handled without a full global routing re-convergence. Ideally, a proactive recovery scheme should not only guarantee connectivity after a failure, but also do so in a manner that does not cause an unacceptable load distribution. This requirement has been noted as being one of the principal challenges for pre-calculated IP recovery schemes (Gowtham, & Nagavarapu, 2019).
With MRC, the link weights are set individually in each backup configuration. This gives great flexibility With respect to how the recovered traffic is routed. The backup conjurations used after a failure is selected based on the failure instance, and choose link weights in the backup configurations that are well suited for only a subset of failure instances.
- Statement of the Problems
Existing system is the Existing work on load distribution in connectionless IGP networks has either focused on the failure free case or on finding link weights that work well both in the normal case and when the routing protocol has converged after a single link failure Many of the approaches listed provide elegant and efficient solutions to fast network recovery, however MRC and Not-via tunneling seems to be the only two covering all evaluated requirements. However, MRC offers the same functionality with a simpler and more intuitive approach, and leaves more room for optimization with respect to load balancing.
IP re-convergence is a time taking process, and a node or link failure is usually followed by a period of routing instability. During this period of time, the packets may be dropped due to invalid routes. Much effort has been laid down to optimize the different steps of the convergence of IP routing, detection, dissemination of information and shortest path calculation, but still the convergence time is too large for applications with real time demands. A basic problem is that since most network failures are short lived, too rapid generation of the re-convergence process can cause route flapping and increased network instability. The IGP convergence process is slow because it is global and reactive. It reacts to a failure after it has occurred, and it involves all the routers in the network domain.
- Aim and Objectives of the Study
The objective of this study is to design and implement an IP recovery using multiple routing configuration system. As the Internet takes an increasingly central in our communication infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. But to assure fast recovery from links and nodes with no failure in IP networks, multiple routing configurations will be used.
Some of the objectives include the following:
- To enable user have reliable confident over IP networks.
- To assure fast recovery from, links and nodes failure in IP network.
- To retain scalability, backup path length, and load distribution after a failure.
- Increasing the use of internet for application with stringent performance requirements.
- To avoid instability and overload.
- To reduce recovery times and packet loss.
1.4 Significance of the Study
New scheme will be unveiled for handling node and link failures in IP networks. Multiple Routing Configurations is a local and proactive protection method that allows recovery in the range of milliseconds MRC allows packet forwarding to carry on pre-configured alternative next-hops immediately after the recognition of the failure. Using MRC as a first line of defense against network failures, the normal IP convergence process can be delayed. This process is then instigated only on the consequence of non-transient failures. Since no global re-routing is done, fast failure detection mechanisms like fast hellos or hardware alerts can be used to start MRC
Without compromising network stability. MRC guarantees recovery from any single node or link failure, which constitutes a large majority of the failures experienced in the network. MRC makes no guess regarding the root cause of the failure, e.g., whether the packet forwarding IP interrupted due to a failed link or a failed router. The main initiative of MRC is to use the network graph and the associated link weights to generate a small set of back-up network configurations. MRC believes that the network uses shortest path routing and destination based hop-by-hop forwarding. This gives great flexibility about how the recovered traffic is routed.
The back-up routing configuration used after the occurrence of the failure is selected based on the failure instance, and select link weights in the backup configurations that are compatible for only a subset of failure instances.
1.5 Scope of the Study
This supplementary specification applies to the IP recovery using multiple routing configuration, which will be developed using all the necessary materials within our reach to ensure a successful project result. This specification defines the non-functional requirements of the system; such as Reliability, Usability, Performance, and Supportability, as well as functional requirements that are common across a number of used cases. (The functional requirements are defined in the used cases specifications).
1.6 Limitations of Study
Some of the constraints that may have in one-way or another affected the outcome of this work include:
- Lack of adequate fund to finance the project: this was one of the limitation to this work because much money is needed to carry out a detailed research work which is not easily borne by every student.
- The limited knowledge of ASP.net and Visual Basic programming was great challenge to this project. However, more research was made to complete this project successfully.
- Functionality: The server manager can be able to monitor and recover redundant IP addresses and protect the loss of addresses from the address table. If there is any redundant IP address the engineer will be notified immediately.
- Security: Protect IP losses and redundant routes.
1.7 Definition of Terms
Administrator: is a person who manages the operation of the system or the server.
Analyst: This is a person or professional who studies the problem encountered by a system and creates means of solving them by introducing a better system.
Automation: Automation is the use of various control systems for operating equipment or applications with minimal or reduced human intervention.
Code: It is a written guideline that helps to determine whether a specific action is ethical or unethical.
Computer: Computer is an electronic device operating the control of instructions stored in its memory that can accept data (input) manipulate the data according to a specified rules (processing) produces result output and stores the result for future use.
Configuration: Is the process of arranging and implementing different settings in a computerized device to enable good functionality and performance.
Connection: Is an established communication channel between two or more devices over a network for the process of sending and receiving packets over the network.
Convergence: It is the state of set of routers that have the same topological information about the internetwork in which they operate. Client: A system that is capable of obtaining information, resources and applications from a server.
Data processing: is defined as the entire process of converting or manipulating data into definite meaningful information (Adigwe, & Okoye, 2015).
Data: It is the facts collected for decision making they are facts that are kept to be processed to get more information.
Database Management System (DBMS): it is software which controls the flow of data and checks and checks on how data are stored.
Database: is an organized /unique collection of related files. It is a collection of schemas, tables, queries, reports, views and other object.
Design: is the art or process of designing how something will look, work.
Documentation: material that provides official information or evidence that serves as record; written specifications and information that describes the product.
Information: is a processed data that can be read and understand.
Input: A set of data sent to the computer processing.
Internet Protocol: IP is the principal communication protocol in the internet protocol suite for relaying datagram across network boundaries.
IP Address: Is a numerical label assigned to each device connected to a computer network that uses the internet protocol for communication. IP address is a unique identifier of a device over a network.
Management Information System (MIS): Information system that generates accurate timely and organized information so that manager and other user can make decision, solve problem supervise activities and track progress.
Management: it is the function that coordinates the efforts of people to accomplish goals and objectives by using available resources efficiently and effectively. It includes planning, organizing, staffing, leading or directing, and controlling an organization or a system to accomplish a goal.
Media Access Control Address (MAC Address): MAC Address of a computer is a unique identifier assigned to network interfaces for communications at the data link layer of a network segment.
Multiple Routing Configurations: MRC is a proactive and local protection mechanism that allows fast recovery of IP addresses.
Network Recovery: Is the process of recovering and resorting normal working operations on a computer network.
Port Number: Is a way to identify a specific process to which an internet or other network message is to be forwarded when it arrives at a server.
Router: It is a networking device that forwards data packets between computer networks. Routers perform the traffic directing functions on the internet.
Routing Table: It’s a set of rules, often viewed in table format that is used to determine where packets traveling over an IP network will be directed.
Security: This helps to prevent unauthorized users from illegally accessing certain data within the database, it protects your data/ files.
Server: Is a computer program or a device that provides information, resources applications and functionality for other programs or devices called clients.
Software: These are set of logically related instructions given to the computer to perform some specific task.
Switch: Is a networking device that receives and forwards data packets to an appropriate part of the network.
System: A system is a set of interacting or interdependent components forming an integrated whole. Every system is delineated by its spatial and temporal boundaries, surrounded and influenced by its environment, described by its structure and purpose and expressed in its functioning.
DISCLAIMER: All project works, files and documents posted on this website, eProjectTopics.com are the property/copyright of their respective owners. They are for research reference/guidance purposes only and some of the works may be crowd-sourced. Please don’t submit someone’s work as your own to avoid plagiarism and its consequences. Use it as a reference/citation/guidance purpose only and not copy the work word for word (verbatim). The paper should be used as a guide or framework for your own paper. The contents of this paper should be able to help you in generating new ideas and thoughts for your own study. eProjectTopics.com is a repository of research works where works are uploaded for research guidance. Our aim of providing this work is to help you eradicate the stress of going from one school library to another in search of research materials. This is a legal service because all tertiary institutions permit their students to read previous works, projects, books, articles, journals or papers while developing their own works. This is where the need for literature review comes in. “What a good artist understands is that nothing comes from nowhere. The paid subscription on eProjectTopics.com is a means by which the website is maintained to support Open Education. If you see your work posted here by any means, and you want it to be removed/credited, please contact us with the web address link to the work. We will reply to and honour every request. Please notice it may take up to 24 – 48 hours to process your request.
