SIGCOMM2006/INM 1 Policy-based BGP Control Architecture for Autonomous Routing Management Osamu Akashi * , Kensuke Fukuda, Toshio Hirotsu, Toshiharu Sugawara NTT Network Innovation Labs.* National Institute of informatics Toyohashi University of Technology NTT Communication Science Labs.
21
Embed
SIGCOMM2006/INM1 Policy-based BGP Control Architecture for Autonomous Routing Management Osamu Akashi *, Kensuke Fukuda, Toshio Hirotsu, Toshiharu Sugawara.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SIGCOMM2006/INM 1
Policy-based BGP Control Architecture for Autonomous Routing Management
BP: Prefix : local_pref: next_hop: ID: flag : a.b.c.0: 1000 : x.x.x.1 : x : : 500 : y.y.y.1 : y> : : 2000 : z.z.z.1 : z
iBGP connection
WD:C
WD:C
AD: the best path
WD:
SIGCOMM2006/INM 12
VR Architecture (#2)
agent
VR Policydescription
Route
r yR
oute
r xR
oute
r z
BP: Prefix : local_pref: next_hop: ID: flag : a.b.c.0: 1000 : x.x.x.1 : x : : 500 : y.y.y.1 : y> : : 2000 : z.z.z.1 : z
> : a.b.c.0: 3000 : y.y.y.1
iBGP connection
AD: current BP with the lowest l_p(=10)
WD:C
WD:C
AD: created entry
WD:
WD:C
AD: (again)
SIGCOMM2006/INM 13
Ex1) Change of the Best Paths
ASOSPF area
AISLE agent
Traffic receiver
External-BGP connection
Internal-BGP connection
Traffic generator
Conventional BGP router
(quagga)
VR
Advertising BGP full-routes
Changes of the best paths
by VR / AISLE
SIGCOMM2006/INM 14
Times for Changing the BGP Best Paths
SIGCOMM2006/INM 15
VR
(repeat)feedback
(repeat)
Ex2) Simple Load Balancing Per Peer AS for Outgoing Packets
AS
AS x agent
AS
Status information that are only acquired after actual observation:- BGP peers- Load per peers- Number of best paths per peer
Insert new entries whose next_hopare changed to a less loaded AS.
BGPentry
Border router:Adopt a new entry as the best path and traffic is partially moved.
observation
SIGCOMM2006/INM 16
Ex2) Control of Outgoing Packets (#1)
ASOSPF area
AISLE agent
Traffic receiver
External-BGP connection
Internal-BGP connection
Traffic generator
Conventional BGP router
(quagga)
VR
Advertising 256 * 3 of IP-prefix (/24)
SIGCOMM2006/INM 17
Traffic monitoringinterfaces
ASOSPF area
AISLE agent
Traffic receiver
External-BGP connection
Internal-BGP connection
Traffic generator
Conventional BGP router
(quagga)
VR
Ex2) Control of Outgoing Packets (#2)
Sending traffic to received IP-prefixes (256 * 3)
( = 768 streams)
Traffic controlby VR / AISLE
SIGCOMM2006/INM 18
ASOSPF area
AISLE agent
Traffic receiver
External-BGP connection
Internal-BGP connection
Traffic generator
Conventional BGP router
(quagga)
VRVR
AISLE agent
Ex3) Control of Incoming Packets (#1)
Advertising 256 * 3 of IP-prefix (/24)
SIGCOMM2006/INM 19
ASOSPF area
AISLE agent
Traffic receiver
External-BGP connection
Internal-BGP connection
Traffic generator
Conventional BGP router
(quagga)
VRVR
AISLE agent
Ex3) Control of Incoming Packets (#2)
Sending traffic to received IP-prefixes (256 * 3)
( = 768 streams)
Traffic monitoringinterfaces
Sending preference
Traffic controlby VR / AISLE
SIGCOMM2006/INM 20
Future Work
Experiments of various cooperative scenarios at the inter-agent level Deployed targets Realistic topologies Using actual BGP update messages at
different observation points Routing flapping problems
Verification of system stability Redundant backup (like route reflectors)
Modification and extension of policy description
SIGCOMM2006/INM 21
Conclusion
AISLE/VR: intra- and inter-AS flexible policy-based routing control architecture Implemented only by ACL/CLOS on PCs Controls conventional routes by standard