1 / 13

IMPLEMENTATION OF VIRTUAL AGGREGATION USING QUAGGA

IMPLEMENTATION OF VIRTUAL AGGREGATION USING QUAGGA. Summer Internship, 2009 project done by Dushyant Arora under the guidance of Dr. Paul Francis At. VIRTUAL AGGREGATION. Continuously growing address space

tassos
Download Presentation

IMPLEMENTATION OF VIRTUAL AGGREGATION USING QUAGGA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMPLEMENTATION OF VIRTUAL AGGREGATION USING QUAGGA Summer Internship, 2009 project done by Dushyant Arora under the guidance of Dr. Paul Francis At

  2. VIRTUAL AGGREGATION • Continuously growing address space • Rapid Growth of Default Free Routing Table (DFRT). • Size of FIB (Forwarding Information Base): issue of concern. • Virtual Aggregation • Address space is partitioned into virtual prefixes. • Larger than any aggregatable prefix in use today. • Full RIB on all routers • Populate the Routing Information Base (RIB) as normal. • Changes required in the router operation are relatively minor.

  3. Today: All routers have routes to all destinations DestNext Hop 20.5/16 1.1.1.1 36.3/16 2.1.1.1 . . . .

  4. Virtual Aggregation(VA): Routers have routes to only part of the address space Virtual Prefixes DestNext Hop 20.5/16 1.1.1.1 . . . . DestNext Hop 188.3/16 2.1.1.1 . . . .

  5. “Aggregation Point” routers for the red Virtual Prefix Virtual Prefixes VA can be deployed autonomously by a single ISP. Neighbouring ISPs can run BGP without VA.

  6. Paths through the ISP have two components: 1: Ingress router tunnels packets to the appropriate APR(Aggregation Point Router). 2: The virtual prefixes are aggregated at the APR. 3: APR tunnels packets to remote ASBR (Autonomous System Border Router) through Egress Router.

  7. When advertising NLRI reachable through 2.2.2.2, local ASBR would advertise a BGP NEXT_HOP of 10.1.1.1 instead of 2.2.2.2. Packets received at the tunnel endpoint 10.1.1.1 would be forwarded to 2.2.2.2 after detunneling. Create virtual interfaces for the new next-hops. These new virtual interfaces are advertised via OSPF to all routers within the AS.

  8. Quagga Quagga is an open source routing software based on the Zebra router. Supports RIP, OSPF and BGP protocols. Composed of several daemons, one per routing protocol. Each daemon has its own configuration file and terminal. IMPLEMENTATION

  9. The following commands were installed inside Quagga source code for implementing VA - 1) enable popular prefix 2) read vp list 3) apr id A.B.C.D 4) apr vp A.B.C.D/M 5) enable virtual aggregation 6) change next-hop A.B.C.D A.B.C.D 7) remove vp A.B.C.D/M 8) remove popular prefix A.B.C.D/M 9) show vplist 10) show popular prefix 11) show sub prefix 12) show tunnel summary 13) show apr summary VP List - VA routers must be able to distinguish VP's from sub-prefixes. List of VPs known as VP-list is statically configured into all VA routers. Popular Prefix - These prefixes can be directly installed in the FIBs. Stored in a list statically configured into the VA Routers. Routers are configured so that they do not advertise VPs to remote ASBR. We can add/remove VP's and PP's while the router is running. Tunnel reutilization & garbage collection has also been implemented. IMPLEMENTATION

  10. CONFIGURATION TESTBED Odin Cluster

  11. Questions Prepared By Dushyant Arora

More Related