12-03-2011, 04:09 PM
[attachment=10112]
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).. 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.
Existing System
Existing work on load distribution in connectionless IGP networks
has either focused on the failure free case or on finding page link weights that work well both in the normal case and when the routing protocol has converged after a single page 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, we argue that MRC offers the same functionality
with a simpler and more intuitive approach, and leaves
More room for optimization with respect to load balancing.
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
System Requirements
Hardware:
PROCESSOR : PENTIUM IV 2.6 GHz
RAM : 512 MB
MONITOR : 15”
HARD DISK : 20 GB
CDDRIVE : 52X
KEYBOARD : STANDARD 102 KEYS
MOUSE : 3 BUTTONS
Software:
FRONT END : JAVA, SWING
TOOLS USED : JFRAME BUILDER
OPERATING SYSTEM: WINDOWS XP
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).. 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.
Existing System
Existing work on load distribution in connectionless IGP networks
has either focused on the failure free case or on finding page link weights that work well both in the normal case and when the routing protocol has converged after a single page 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, we argue that MRC offers the same functionality
with a simpler and more intuitive approach, and leaves
More room for optimization with respect to load balancing.
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
System Requirements
Hardware:
PROCESSOR : PENTIUM IV 2.6 GHz
RAM : 512 MB
MONITOR : 15”
HARD DISK : 20 GB
CDDRIVE : 52X
KEYBOARD : STANDARD 102 KEYS
MOUSE : 3 BUTTONS
Software:
FRONT END : JAVA, SWING
TOOLS USED : JFRAME BUILDER
OPERATING SYSTEM: WINDOWS XP
