Atrium Field Trial

nareshblu edited this page Nov 23, 2016 · 14 revisions

Atrium Field Trial

Customer: SIFY

Start: Q1 2017

Location: SIFY, India

Duration of the field trial: 6 months

What will be validated: Functional and scale requirements for the Open Flow based internet gateway at the Tier-1 POP

Who can participate: Vendors who have products/solutions (switches, controllers that meet core field trial requirements) Field trial requirements will be validated based on a published acceptance test plan

Deployment Topology

topology_1

Deployment Overview

  • Each Tier-1 POP has 1 internet gateway router and 1 route reflector providing internet connectivity to several internet provider edge routers connected on a MPLS backbone

  • Each Internet Gateway has to peer with Upto 20 transit peers using eBGP

    • 1 route reflector using iBGP

    • 1 MPLS neighbors using LDP

  • Full internet feed and default route (IPv4 + IPv6) is received from transit partners

  • Internet routes are reflected to all Internet edge routers through Route Reflectors

  • Route reflectors handle control plane traffic only. Best path routing decision is done by RR using traditional BGP algorithm

  • The Internet Gateway and Provider Edge has to hold full RIB and FIB

Functional Requirement

  • Support for IPv4 and IPv6 routes

  • i-BGP and e-BGP

  • support GTSM and MD5 authentication

  • BGP route policies / route filtering BGP flow spec (optional)

  • Route dampening (optional)

  • Support for 4 Byte ASN

  • Support for LDP processing (Phase 2 requirement)

Scale Requirement

  • Handle control plane traffic for peering with 20 routers each of which advertise 30K routes on an average from each transit peer (Phase 1 requirement)

  • The gateway must also be able to handle conditions where a few transit peers might be advertising up-to 450K routes (Phase 1 requirement)

  • The control plane must have the ability to process up-to 300 LDP tags (Phase 2 requirement)

Scale Requirement

Protocol RIB FIB
IPv4 IP Routes 600k 600k
IPv6 IP Routes 30k 30k

Atrium Field Trial Test Plan

No Test-Title Methodology Phase Result [PASS/FAIL] Remark
Functional
1 Support for IPv4 Configure and connect the network controller (ODL/ONOS) and Quagga,with DUT. Initiate the emulated router with IPv4 address. Verify,if the BGP connection comes up between emulated router and Control Plane Quagga instance. 1 MANDATORY
2 Support for IPv6 Configure and connect the network controller (ODL/ONOS) and Quagga,with DUT. Initiate the emulated router with IPv6 address. Verify,if the BGP connection comes up between emulated router and Control Plane Quagga instance. 1 MANDATORY
3 BGP Peering (E-BGP) Configure and connect the network controller (ODL/ONOS) and Quagga with,DUT. Initiate emulated router from Traffic Generator with required configuration. Verify,if the E-BGP connection comes up between emulated router and Control Plane Quagga instance. 1 MANDATORY
4 BGP Peering (I-BGP) Configure and connect the network controller (ODL/ONOS), Route Reflector and Quagga with DUT. Verify,if the I-BGP connection comes up between Route Reflector and Control Plane Quagga instance. 1 MANDATORY
5 GTSM and MD5 authentication Configure and connect the network controller (ODL/ONOS)and Quagga,with DUT. Configure the emulated router with GTSM and MD5,autehntication. Enable MD5 and GTSM in Quagga as well for every,neighbour. Initiate the emulated router. Verify if the connection is authenticated. 1 MANDATORY
6 BGP Flowspec Configure and connect the network controller (ODL/ONOS) and Quagga,with DUT. Initiate the emulated router with required configuration.,Define BGP Flowspec policies to drop packets from a particular source if,its sending rate is more than 500 bps. Verify if packets from such a,sender are unable to reach the router. 1 OPTIONAL
7 Route Dampening Configure and connect the network controller (ODL/ONOS) and Quagga,with DUT. Initiate the emulated router with required configuration.,Define Half-life time sufficiently enough to be able to change routes in,emulated router. Keep a low Suppress Limit which is easily achievable,(between 1-20000 points, where each penalty is for 1000 points). Verify,if penalties are working correctly when you change route in emulated,router and when penalty reaches Suppress Limit, the route is suppressed. 1 OPTIONAL
8 Support for 4 byte ASN Configure and connect the network controller (ODL/ONOS) and Quagga,with DUT. Configure the emulated router with 4 byte ASN. Enable 4-byte,ASN support on Quagga. Initiate the emulated router. Verify if the connection is established. 1 MANDATORY
9 Route Learning Establish topology as per the deployment topology. Send 10 IPv4,routes from emulated router. Verify that the routes are learnt by,Control Plane Quagga instance ,Route Reflector and Provider Edge router.,Ensure forwarding flow entry are installed in DUT which corresponds to,learnt routes.Repeat the procedure with IPv6 prefix. 1 MANDATORY
10 Route Deletion Establish,topology as per the deployment topology. Add routes as per methodology,in test-case 3. Delete 10 IPv4 routes from emulated router. Verify that,the routes are removed by Control Plane Quagga instance ,Route Reflector,and Provider Edge router. Ensure forwarding flow entry are removed from,DUT which corresponds to removed routes.Repeat the procedure with IPv6 prefix. 1 MANDATORY
11 Tear Down Establish topology as per the deployment topology. Add routes as per,methodology in test-case 3. Stop all the emulated routers. Verify that,all the E-BGP connections in Control Plane Quagga instance are,terminated. Ensure all the forwarding entries are removed from DUT. 1 MANDATORY
Scale
12 Flow Consistency Addition Establish topology as per the deployment topology. Send 10k IPv4,routes from emulated router with 2k routes per 5 seconds. Verify that,10k routes are learnt by Control Plane Quagga instance ,Route Reflector,and Provider Edge router. Ensure forwarding flow entry are installed in,DUT. 1 MANDATORY
13 Max Flow Entries Establish topology as per the deployment topology. Send 600k IPv4,routes from 1 emulated router with 2k routes per 5 seconds. Verify that,600k routes are learnt by Control Plane Quagga instance ,Route Reflector,and Provider Edge router. Ensure forwarding flow entry are installed in,DUT. Take note of the time to install the flow rules in DUT. 1 MANDATORY
14 Max Flow Entries Route Reflector Establish topology as per the deployment topology. Send 600k IPv4,routes from 20 emulated router (30k route advertisements each) with 2k,routes per 5 seconds. Verify that 600k routes are learnt by Control,Plane Quagga instance ,Route Reflector and Provider Edge router. Ensure,forwarding flow entry are installed in DUT. Take note of the time to,install the flow rules in DUT. 1 MANDATORY
15 Max Flow Entries with overlapping routes Establish topology as per the deployment topology. Send 600k IPv4,routes from all emulated router with 2k routes per 5 seconds with 30%,overlapping routes. Verify that forwarding flow entries are installed in,DUT. Take note of the time to install the flow rules in DUT. 1 MANDATORY
16 Max Flow Entries Route Reflector with overlapping routes Establish topology as per the deployment topology. Send 600k IPv4,routes from all emulated router with 2k routes per 5 seconds with 30%,overlapping routes. Verify that 600k routes are learnt by Route,Reflector and Provider Edge router. 1 MANDATORY
Solution Tests
17 Provider Edge learns route from Route Reflector Establish topology as per the deployment topology. Send IPv4,routes from all emulated router with 2k routes per 5 seconds. Verify,that all the routes are learnt by Provider Edge router. 1 MANDATORY
18 Customer traffic from PEs use the correct internet peers to connect to the internet Establish topology as per the deployment topology. Send IPv4,routes from all emulated router with 2k routes per 5 seconds. Verify,that all the routes are learnt by Provider Edge router. When trying to,ping from PE on one of the routes learned from any AS, verify if the,packet follows correct path. 1 MANDATORY
19 Traffic rerouting when peering routers fail Establish topology as per the deployment topology. Add routes as,per methodology in test-case 3. Stop few emulated routers. Verify that,all the traffic is rerouted using available peering routers. 1 MANDATORY

Field Trial Participation Requirement

Ensure that your switch supports flow objectives driver for the ONOS/ODL controllers. If your product does not support flow objectives driver, plan to develop and contribute to the controller/Atrium distribution. Send your products for Phase 1 and Phase 2 validation in the lab environment (All the field trial requirements are currently validated at CNLabs, Bangalore).

Each phase will have a test report summary and findings will be presented in the Atrium project meetings Participate in the Atrium discussions; contribute to development / bug fixes / enhancement of the code. If you have an open source solution that supports control planes other than ONOS/ODL with Quagga that you would like to make part of the field trial, present your inputs in the Atrium discussion forum for inclusion on the roadmap.

Website/bugs/project status: https://github.com/onfsdn/atrium-docs/wiki

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.