This has relevance to setting up multiple levels of route reflectors, IGP metric redistribution into BGP, and certain confederation configurations. The problem tends to occur when connecting POPs to a core.
> >A new Request for Comments is now available in online RFC libraries. > > > RFC 3345 > > Title: Border Gateway Protocol (BGP) Persistent Route > Oscillation Condition > Author(s): D. McPherson, V. Gill, D. Walton, A. Retana > Status: Informational > Date: August 2002 > Mailbox: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED] > Pages: 19 > Characters: 38137 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-idr-route-oscillation-01.txt > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc3345.txt > > >In particular configurations, the BGP scaling mechanisms defined in >"BGP Route Reflection - An Alternative to Full Mesh IBGP" and >"Autonomous System Confederations for BGP" will introduce persistent >BGP route oscillation. This document discusses the two types of >persistent route oscillation that have been identified, describes >when these conditions will occur, and provides some network design >guidelines to avoid introducing such occurrences. > >This document is a product of the Inter-Domain Routing Working Group >of the IETF. > >This memo provides information for the Internet community. It does >not specify an Internet standard of any kind. Distribution of this >memo is unlimited. > >This announcement is sent to the IETF list and the RFC-DIST list. >Requests to be added to or deleted from the IETF distribution list >should be sent to [EMAIL PROTECTED] Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to [EMAIL PROTECTED] > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to [EMAIL PROTECTED] with the message body >help: ways_to_get_rfcs. For example: > > To: [EMAIL PROTECTED] > Subject: getting rfcs > > help: ways_to_get_rfcs > >Requests for special distribution should be addressed to either the >author of the RFC in question, or to [EMAIL PROTECTED] Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC >Authors, for further information. > > >Joyce K. Reynolds and Sandy Ginoza >USC/Information Sciences Institute > >... > >Below is the data which will enable a MIME compliant Mail Reader >implementation to automatically retrieve the ASCII version >of the RFCs. > > >[The following attachment must be fetched by mail. Command-click the >URL below and send the resulting message to get the attachment.] > >[The following attachment must be fetched by ftp. Command-click the >URL below to ask your ftp client to fetch it.] > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=50492&t=50492 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
