presentation id - nanog archive › meetings › nanog26 › presentations › john.pdf© 2001,...

10
1 © 2001, Cisco Systems, Inc. All rights reserved. Presentation_ID

Upload: others

Post on 05-Jul-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

111© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Page 2: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

2© 2001, Cisco Systems, Inc. All rights reserved.

Session NumberPresentation_ID

BGP Route OscillationElimination

John Scudder

([email protected])

Page 3: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

333© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Major Factors for Route Oscillation

• Dependency of IBGP updates

Sometimes circular dependency

• Partial information by RR or confederation

Withdraws (over reduction) amplifies the issue

• Partial order (due to MED) in route selection

Route selection overly sensitive to route information

Seems to play less role than perceived

Not much can be done with the current protocol anddeployed base

Page 4: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

444© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Observations

• Full-mesh IBGP does not oscillate

Because enough information is available

• Need more information to eliminate oscillation

• RR (or confed) may hide many clients behind oneRR

Thus RR needs to be able to advertise multiple routeswithout implicit withdrawal

Trick is to announce enough extra routes whileconstraining complexity (operational, resource) to beless than IBGP

Page 5: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

555© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Proposal: Advertise Multiple Paths

• Extension to allow advertisement ofmultiple paths

Changes implicit withdrawal behavior

• Advertise (at most) one group-best foreach neighbor AS from cluster or sub-AS

Only when tie-breaker occurs below MED

Other refinements could be pursued as well

Page 6: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

666© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Benefits

• No constraints on topology

No new meshing requirements

No constraints on IGP metrics

• Eliminates oscillation — doesn’t just reduce it

Any complete solution requires multipath

• Other potential applicationsMultipath BGP that’s not a hack

Route server

Page 7: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

777© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Drawbacks

• More network state than best-external

RR < best-external < multipath < flat IBGP

• Complexity to implement

Update generation, scalability issues, etc.

• Deployment/transition

Page 8: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

888© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Open Questions

• Effects on convergence

More data transmitted suggests slower

More backup paths available suggests faster

My intuition: Faster

Page 9: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

999© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID

Documents

• BGP Persistent Route OscillationCondition (RFC 3345)

• BGP Persistent Route Oscillation Solution(draft-walton-bgp-route-oscillation-stop-00)

• Advertisement of Multiple Paths in BGP(draft-walton-bgp-add-paths-00)

Page 10: Presentation ID - NANOG Archive › meetings › nanog26 › presentations › john.pdf© 2001, Cisco Systems, Inc. All rights reserved. 2 Session Number Presentation_ID BGP Route

101010© 2001, Cisco Systems, Inc. All rights reserved.Presentation_ID