27-03-2010, 02:42 PM
sir i want complete coding for the project "multiple routing configuration for fast ip network recovery".
|
multiple routing configuration for fast ip network recovery
|
sir i want complete coding for the project "multiple routing configuration for fast ip network recovery".
31-03-2010, 06:22 PM
Multiple Routing Configurations for Fast IP Network Recovery
the slow convergence of
routing protocols after a network failure becomes a growing
problem. a new recovery scheme called Multiple
Routing Configurations (MRC) is presented in this article To assure fast recovery from page link and node failures in
IP networks. MRC is strictly connectionless, and
assumes only destination based hop-by-hop forwarding and it is
based on keeping additional routing information in the routers,
and allows packet forwarding to continue on an alternative
output page link immediately after the detection of a failure.
INTRODUCTION:
IP networks are intrinsically
robust, since IGP routing protocols like OSPF are designed
to update the forwarding information based on the changed
topology after a failure. IP networks are intrinsically
robust, since IGP routing protocols like OSPF are designed
to update the forwarding information based on the changed
topology after a failure. Much effort has been devoted to optimizing the different
steps of the convergence of IP routing like detection, dissemination
of information and shortest path calculation.
The Multiple Routing Configurations (MRC) is a
proactive and local protection mechanism that allows recovery
in the range of milliseconds.. MRC allows packet forwarding
to continue over pre-configured alternative next-hops immediately
after the detection of the failure.The main idea of MRC is to use the network graph and
the associated page link weights to produce
a set of backup
network configurations.
MRC OVERVIEW:
MRC is based on building a small set of backup routing
configurations, that are used to route recovered traffic on
alternate paths after a failure. These differ
from the normal routing configuration in that page link weights
are set so as to avoid routing traffic in certain parts of the
network. The MRC approach is threefold. a set of
backup configurations is created so that every network component is
excluded from packet forwarding in one configuration. a standard routing algorithm like OSPF
is used to calculate configuration specific shortest paths and
create forwarding tables in each router, for each configuration. Finally, a forwarding process that takes advantage of the backup
configurations to provide fast recovery from a component
failure.
For full details, refer this pdf:
the slow convergence of
routing protocols after a network failure becomes a growing
problem. a new recovery scheme called Multiple
Routing Configurations (MRC) is presented in this article To assure fast recovery from page link and node failures in
IP networks. MRC is strictly connectionless, and
assumes only destination based hop-by-hop forwarding and it is
based on keeping additional routing information in the routers,
and allows packet forwarding to continue on an alternative
output page link immediately after the detection of a failure.
INTRODUCTION:
IP networks are intrinsically
robust, since IGP routing protocols like OSPF are designed
to update the forwarding information based on the changed
topology after a failure. IP networks are intrinsically
robust, since IGP routing protocols like OSPF are designed
to update the forwarding information based on the changed
topology after a failure. Much effort has been devoted to optimizing the different
steps of the convergence of IP routing like detection, dissemination
of information and shortest path calculation.
The Multiple Routing Configurations (MRC) is a
proactive and local protection mechanism that allows recovery
in the range of milliseconds.. MRC allows packet forwarding
to continue over pre-configured alternative next-hops immediately
after the detection of the failure.The main idea of MRC is to use the network graph and
the associated page link weights to produce
a set of backup
network configurations.
MRC OVERVIEW:
MRC is based on building a small set of backup routing
configurations, that are used to route recovered traffic on
alternate paths after a failure. These differ
from the normal routing configuration in that page link weights
are set so as to avoid routing traffic in certain parts of the
network. The MRC approach is threefold. a set of
backup configurations is created so that every network component is
excluded from packet forwarding in one configuration. a standard routing algorithm like OSPF
is used to calculate configuration specific shortest paths and
create forwarding tables in each router, for each configuration. Finally, a forwarding process that takes advantage of the backup
configurations to provide fast recovery from a component
failure.
For full details, refer this pdf:
01-07-2010, 11:40 PM
Please send me Architecture diagram / block diagram /sementic diagram for fast ip network routing using Multiple routing configuration.
Please send Sementic diagram for fast ip network recovery using multiple routing configuration
Please send Sementic diagram for fast ip network recovery using multiple routing configuration
02-07-2010, 06:17 PM
Multiple Routing Configurations for Fast
IP Network Recovery
Abstract:
As the Internet takes an increasingly central role in our communications infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. To assure fast recovery from page link and node failures in IP networks, we present a new recovery scheme called Multiple Routing Configurations (MRC). We also show how an estimate of the traffic demands in the network can be used to improve the distribution of the recovered traffic, and thus reduce the chances of congestion when MRC is used.
Algorithm / Technique used:
Multiple Routing Configurations.
Algorithm Description:
Multiple Routing Configurations (MRC) is a proactive and local protection mechanism that allows recovery in the range of milliseconds. MRC allows packet forwarding to continue over preconfigured alternative next-hops immediately after the detection of the failure. Using MRC as a first line of defense against network failures, the normal IP convergence process can be put on hold. This process is then initiated only as a consequence of non-transient failures. Since no global re-routing is performed, fast failure detection mechanisms like fast hellos or hardware alerts can be used to trigger MRC without compromising network stability. MRC guarantees recovery from any single page link or node failure, which constitutes a large majority of the failures experienced in a network. MRC makes no assumptions with respect to the root cause of failure, e.g., whether the packet forwarding is disrupted due to a failed page link or a failed router.
Proposed System:
Our proposed scheme guarantees recovery in all single failure scenarios, using a single mechanism to handle both page link and node failures, and without knowing the root cause of the failure. MRC is strictly connectionless, and assumes only destination based hop-by-hop forwarding. MRC is based on keeping additional routing information in the routers, and allows packet forwarding to continue on an alternative output page link immediately after the detection of a failure. It can be implemented with only minor changes to existing solutions. In this paper we present MRC, and analyze its performance with respect to scalability, backup path lengths, and load distribution after a failure.
Hardware Requirements
¢ SYSTEM : Pentium IV 2.4 GHz
¢ HARD DISK : 40 GB
¢ FLOPPY DRIVE : 1.44 MB
¢ MONITOR : 15 VGA colour
¢ MOUSE : Logitech.
¢ RAM : 256 MB
¢ KEYBOARD : 110 keys enhanced.
Software Requirements
¢ Operating system :- Windows XP Professional
¢ Front End :- Java Technology
IP Network Recovery
Abstract:
As the Internet takes an increasingly central role in our communications infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. To assure fast recovery from page link and node failures in IP networks, we present a new recovery scheme called Multiple Routing Configurations (MRC). We also show how an estimate of the traffic demands in the network can be used to improve the distribution of the recovered traffic, and thus reduce the chances of congestion when MRC is used.
Algorithm / Technique used:
Multiple Routing Configurations.
Algorithm Description:
Multiple Routing Configurations (MRC) is a proactive and local protection mechanism that allows recovery in the range of milliseconds. MRC allows packet forwarding to continue over preconfigured alternative next-hops immediately after the detection of the failure. Using MRC as a first line of defense against network failures, the normal IP convergence process can be put on hold. This process is then initiated only as a consequence of non-transient failures. Since no global re-routing is performed, fast failure detection mechanisms like fast hellos or hardware alerts can be used to trigger MRC without compromising network stability. MRC guarantees recovery from any single page link or node failure, which constitutes a large majority of the failures experienced in a network. MRC makes no assumptions with respect to the root cause of failure, e.g., whether the packet forwarding is disrupted due to a failed page link or a failed router.
Proposed System:
Our proposed scheme guarantees recovery in all single failure scenarios, using a single mechanism to handle both page link and node failures, and without knowing the root cause of the failure. MRC is strictly connectionless, and assumes only destination based hop-by-hop forwarding. MRC is based on keeping additional routing information in the routers, and allows packet forwarding to continue on an alternative output page link immediately after the detection of a failure. It can be implemented with only minor changes to existing solutions. In this paper we present MRC, and analyze its performance with respect to scalability, backup path lengths, and load distribution after a failure.
Hardware Requirements
¢ SYSTEM : Pentium IV 2.4 GHz
¢ HARD DISK : 40 GB
¢ FLOPPY DRIVE : 1.44 MB
¢ MONITOR : 15 VGA colour
¢ MOUSE : Logitech.
¢ RAM : 256 MB
¢ KEYBOARD : 110 keys enhanced.
Software Requirements
¢ Operating system :- Windows XP Professional
¢ Front End :- Java Technology
03-07-2010, 10:05 AM
I have complete coding for multiple routing configuration for fast ip network recovery.
contact me by mail id is s.f.shahith[at]gmail.com.
There is no special charges or fee for coding.
contact me by mail id is s.f.shahith[at]gmail.com.
There is no special charges or fee for coding.
11-07-2010, 03:19 PM
Need coding,block diagram for multiple routing configurations for fast ip network recovery....
11-07-2010, 03:47 PM
hai, i need the complete project report on multiple routing configurations on fast ip network recovery...
21-07-2010, 03:23 PM
Hai sir,
I want to do project on "Multiple routing configuration for fast IP network recovery".Give me the information and coding regarding this topic.
I want to do project on "Multiple routing configuration for fast IP network recovery".Give me the information and coding regarding this topic.
15-11-2010, 01:42 PM
hi
go through the following threads for more information.
http://studentbank.in/report-multiple-ro...k-recovery
http://studentbank.in/report-need-help-i...k-recovery
http://studentbank.in/report-fast-ip-net...7#pid27467
go through the following threads for more information.
http://studentbank.in/report-multiple-ro...k-recovery
http://studentbank.in/report-need-help-i...k-recovery
http://studentbank.in/report-fast-ip-net...7#pid27467
15-11-2010, 03:16 PM
hello, sir can you provide me the documnetation of this paper
19-11-2010, 10:24 AM
hi
there are pdf are available. go through the threads mention above and please download.
there are pdf are available. go through the threads mention above and please download.
19-11-2010, 08:53 PM
As the Internet takes an increasingly central role in our communications infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. To assure fast recovery from page link and node failures in IP networks, we present a new recovery scheme called Multiple Routing Configurations (MRC).
20-11-2010, 11:01 PM
Hi,
Actually i'm getting the backup configurations. but i'm not able to Simulate the network.
So,I need help in simulating the project with JSIM Software or which ever is good.It's a bit urgent.
And also if anyone could help me with the complete Technical Report I will be very thankfull.
Actually i'm getting the backup configurations. but i'm not able to Simulate the network.
So,I need help in simulating the project with JSIM Software or which ever is good.It's a bit urgent.
And also if anyone could help me with the complete Technical Report I will be very thankfull.
24-11-2010, 01:11 PM
Hi,
i"m attaching the code now.
This will create a set of Backup configurations.
but please help me with the Simulation and Documentation.
i"m attaching the code now.
This will create a set of Backup configurations.
but please help me with the Simulation and Documentation.
24-11-2010, 02:03 PM
11-04-2011, 10:00 AM
[attachment=11974]
ABSTRACT
Title: Multiple Routing Configuration
As the Internet takes an increasingly central role in our communications infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. To assure fast recovery from page link and node failures in IP networks, we present a new recovery scheme called Multiple Routing Configurations (MRC). Our proposed scheme guarantees recovery in all single failure scenarios, using a single mechanism to handle both page link and node failures, and without knowing the root cause of the failure. MRC is strictly connectionless, and assumes only destination based hop-by-hop forwarding. MRC is based on keeping additional routing information in the routers, and allows packet forwarding to continue on an alternative output page link immediately after the detection of a failure. It can be implemented with only minor changes to existing solutions. In this paper we present MRC, and analyze its performance with respect to scalability, backup path lengths, and load distribution after a failure. We also show how an estimate of the traffic demands in the network can be used to improve the distribution of the recovered traffic, and thus reduce the chances of congestion when MRC is used.
1. INTRODUCTION
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 page link in central parts of a network has the potential to affect hundreds of thousands of phone conversations or TCP connections, with obvious adverse effects.
The ability to recover from failures has always been a central design goal in the Internet [1]. IP networks are intrinsically robust, since IGP routing protocols like 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 page link state to all routers in the network domain. When the new state information is distributed, each router individually calculates new valid routing tables.
This network-wide IP re-convergence is a time consuming process, and a page 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 [2] and BGP context [3], and has an adverse effect on real-time applications [4]. Events leading to a re-convergence have been shown to occur frequently [5].
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 we present a new scheme for handling page link and node failures in IP networks. Multiple outing Configurations (MRC) is a proactive and local protection mechanism that allows recovery in the range of milliseconds. MRC allows packet forwarding to continue over preconfigured alternative next-hops immediately after the detection of the failure. Using MRC as a first line of defense against network failures, the normal IP convergence process can be put on hold. This process is then initiated only as a consequence of non-transient failures. Since no global re-routing is performed, fast failure detection mechanisms like fast hellos or hardware alerts can be used to trigger MRC without compromising network stability [8]. MRC guarantees recovery from any single
link or node failure, which constitutes a large majority of the failures experienced in a network [7]. MRC makes no assumptions with respect to the root cause of failure, e.g., whether the packet forwarding is disrupted due to a failed page link or a failed router.
HARDWARE AND SOFTWARE SPECIFICATIONS
HARDWARE SPECIFICATION
The hardware used for the development of the project is:
Processor : Pentium Dual core
Ram : 1 GB
Monitor : 15” Color
Hard Disk : 80 GB
SOFTWARE REQUIREMENTS
The software used for the development of the project is:
Operating system : Windows family
Environment : Java
1.2. ORGANIZATION PROFILE
SOFTWARE SOLUTIONS
EdwareUK Pvt Ltd is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organization’s current IT assets. Their work with large global corporations and new products or services and to implement prudent business and technology strategies in today’s environment.
EdwareUK Pvt LTD ’S RANGE OF EXPERTISE INCLUDES:
• Software Development Services
• Engineering Services
• Systems Integration
• Customer Relationship Management
• Product Development
• Electronic Commerce
• Consulting
• IT Outsourcing
We apply technology with innovation and responsibility to achieve two broad objectives:
• Effectively address the business issues our customers face today.
• Generate new opportunities that will help them stay ahead in the future.
THIS APPROACH RESTS ON:
• A strategy where we architect, integrate and manage technology services and solutions - we call it AIM for success.
• A robust offshore development methodology and reduced demand on customer resources.
• A focus on the use of reusable frameworks to provide cost and times benefits.
They combine the best people, processes and technology to achieve excellent results - consistency. We offer customers the advantages of:
SPEED:
They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule.
ABSTRACT
Title: Multiple Routing Configuration
As the Internet takes an increasingly central role in our communications infrastructure, the slow convergence of routing protocols after a network failure becomes a growing problem. To assure fast recovery from page link and node failures in IP networks, we present a new recovery scheme called Multiple Routing Configurations (MRC). Our proposed scheme guarantees recovery in all single failure scenarios, using a single mechanism to handle both page link and node failures, and without knowing the root cause of the failure. MRC is strictly connectionless, and assumes only destination based hop-by-hop forwarding. MRC is based on keeping additional routing information in the routers, and allows packet forwarding to continue on an alternative output page link immediately after the detection of a failure. It can be implemented with only minor changes to existing solutions. In this paper we present MRC, and analyze its performance with respect to scalability, backup path lengths, and load distribution after a failure. We also show how an estimate of the traffic demands in the network can be used to improve the distribution of the recovered traffic, and thus reduce the chances of congestion when MRC is used.
1. INTRODUCTION
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 page link in central parts of a network has the potential to affect hundreds of thousands of phone conversations or TCP connections, with obvious adverse effects.
The ability to recover from failures has always been a central design goal in the Internet [1]. IP networks are intrinsically robust, since IGP routing protocols like 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 page link state to all routers in the network domain. When the new state information is distributed, each router individually calculates new valid routing tables.
This network-wide IP re-convergence is a time consuming process, and a page 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 [2] and BGP context [3], and has an adverse effect on real-time applications [4]. Events leading to a re-convergence have been shown to occur frequently [5].
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 we present a new scheme for handling page link and node failures in IP networks. Multiple outing Configurations (MRC) is a proactive and local protection mechanism that allows recovery in the range of milliseconds. MRC allows packet forwarding to continue over preconfigured alternative next-hops immediately after the detection of the failure. Using MRC as a first line of defense against network failures, the normal IP convergence process can be put on hold. This process is then initiated only as a consequence of non-transient failures. Since no global re-routing is performed, fast failure detection mechanisms like fast hellos or hardware alerts can be used to trigger MRC without compromising network stability [8]. MRC guarantees recovery from any single
link or node failure, which constitutes a large majority of the failures experienced in a network [7]. MRC makes no assumptions with respect to the root cause of failure, e.g., whether the packet forwarding is disrupted due to a failed page link or a failed router.
HARDWARE AND SOFTWARE SPECIFICATIONS
HARDWARE SPECIFICATION
The hardware used for the development of the project is:
Processor : Pentium Dual core
Ram : 1 GB
Monitor : 15” Color
Hard Disk : 80 GB
SOFTWARE REQUIREMENTS
The software used for the development of the project is:
Operating system : Windows family
Environment : Java
1.2. ORGANIZATION PROFILE
SOFTWARE SOLUTIONS
EdwareUK Pvt Ltd is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organization’s current IT assets. Their work with large global corporations and new products or services and to implement prudent business and technology strategies in today’s environment.
EdwareUK Pvt LTD ’S RANGE OF EXPERTISE INCLUDES:
• Software Development Services
• Engineering Services
• Systems Integration
• Customer Relationship Management
• Product Development
• Electronic Commerce
• Consulting
• IT Outsourcing
We apply technology with innovation and responsibility to achieve two broad objectives:
• Effectively address the business issues our customers face today.
• Generate new opportunities that will help them stay ahead in the future.
THIS APPROACH RESTS ON:
• A strategy where we architect, integrate and manage technology services and solutions - we call it AIM for success.
• A robust offshore development methodology and reduced demand on customer resources.
• A focus on the use of reusable frameworks to provide cost and times benefits.
They combine the best people, processes and technology to achieve excellent results - consistency. We offer customers the advantages of:
SPEED:
They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule.
14-04-2011, 06:00 PM
hi every body
i got the code actually but there is a little bit problem in execution of that code so i need its execution video file so that i can clearly understand how to execute the code plzzzzzzzzz help me
i got the code actually but there is a little bit problem in execution of that code so i need its execution video file so that i can clearly understand how to execute the code plzzzzzzzzz help me
14-04-2011, 07:04 PM
hi
you can refer these pages to get the details on multiple routing configuration for fast ip network recovery
Reference: http://studentbank.in/report-multiple-ro...z1JVIE3mww
http://studentbank.in/report-multiple-ro...ery?page=4
seminarprojectsattachment.php?aid=9646
you can refer these pages to get the details on multiple routing configuration for fast ip network recovery
Reference: http://studentbank.in/report-multiple-ro...z1JVIE3mww
http://studentbank.in/report-multiple-ro...ery?page=4
seminarprojectsattachment.php?aid=9646
03-08-2011, 06:51 PM
sir ,i need the complete coding of multiple routing configuration for fast ip network recovery
04-08-2011, 10:07 AM
To get more information about the topic " multiple routing configuration for fast ip network recovery
" please refer the page link below
http://studentbank.in/report-multiple-ro...ery?page=4
seminarprojectsattachment.php?aid=9646
24-01-2012, 12:59 PM
please send me example for multiple routing configurations for fast ip network recovery[/size][/font]
20-12-2012, 10:05 AM
Sir,
I m raj. I m doing M.E Computer networks.my project is based on Pim and Pim-Dm protocol.Can anyone know about Pim and Pim-Dm protocol means please guide me...please send any documents about Pim-Dm. My mail id s rajkumar4037[at]gmail.com
I m raj. I m doing M.E Computer networks.my project is based on Pim and Pim-Dm protocol.Can anyone know about Pim and Pim-Dm protocol means please guide me...please send any documents about Pim-Dm. My mail id s rajkumar4037[at]gmail.com
20-12-2012, 10:27 AM
to get information about the topic "multiple routing configuration for fast ip network recovery" related topic refer the page link bellow
http://studentbank.in/report-multiple-ro...k-recovery
http://studentbank.in/report-multiple-ro...k-recovery
13-02-2013, 11:52 AM
plz send complete code and sementic diagram for fast ip recovery using MRC project
send to chandrakanth.cse[at]gmail.com
send to chandrakanth.cse[at]gmail.com
26-04-2013, 12:27 PM
pleasesend data flow diagram for fast ip network using multiple routing configuration
|
« Next Oldest | Next Newest »
|
