ACM Home Page
Please provide us with feedback. Feedback
Avoiding instability during graceful shutdown of multiple OSPF routers
Full text PdfPdf (677 KB)
Source IEEE/ACM Transactions on Networking (TON) archive
Volume 14 ,  Issue 3  (June 2006) table of contents
Pages: 532 - 542  
Year of Publication: 2006
ISSN:1063-6692
Authors
Aman Shaikh  AT&T Labs (Research), Florham Park, NJ
Rohit Dube  UTStarcom Inc., Alameda, CA
Anujan Varma  University of California, Santa Cruz, CA
Publisher
IEEE Press  Piscataway, NJ, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 70,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: 10.1109/TNET.2006.876152

ABSTRACT

Many recent router architectures decouple the routing engine from the forwarding engine, allowing packet forwarding to continue even when the routing process is not active. This opens up the possibility of using the forwarding capability of a router even when its routing process is brought down for software upgrade or maintenance, thus avoiding the route flaps that normally occur when the routing process goes down. Unfortunately, current routing protocols, such as BGP, OSPF and IS-IS do not support such operation. In an earlier paper [1], we described an enhancement to OSPF, called the IBB (I'll Be Back) capability, that enables a router to continue forwarding packets while its routing process is inactive.When the OSPF process in an IBB-capable router is inactive, it cannot adapt its forwarding table to reflect changes in network topology. This can lead to routing loops and/or black holes. In this paper, we focus on the loop problem and provide a detailed analysis of how and when loops are formed and propose solutions to prevent them. We develop two necessary conditions for the formation of routing loops in the general case when multiple routers are inactive. These conditions can easily be checked by the neighbors of the inactive routers. Simulations on several network topologies showed that checking the two conditions together signaled a loop in most cases only when a loop actually existed.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
[1] A. Shaikh, R. Dube, and A. Varma, "Avoiding instability during graceful shutdown of OSPF," in Proc. IEEE INFOCOM, 2002, vol. 1, pp. 883-892.
 
2
[2] North American Network Operators Group (NANOG) mailing list archives. [Online]. Available: http://www.nanog.org
 
3
 
4
[4] J. T. Moy, "OSPF Version 2," RFC2328, Apr. 1998.
 
5
 
6
 
7
[7] S. Sangli, Y. Rekhter, R. Fernando, J. Scudder, and E. Chen, Graceful Restart Mechanism for BGP Work in progress, Internet Draft, Jul. 2003.
 
8
9
10
 
11
[11] Rocketfuel: An ISP Topology Mapping Engine [Online]. Available: http://www.cs.washington.edu/research/networking/rocketfuel
 
12

Collaborative Colleagues:
Aman Shaikh: colleagues
Rohit Dube: colleagues
Anujan Varma: colleagues