wiki

SEBA: SDN Enabled Broadband Access

Revisão de 11h11min de 25 de abril de 2019 por Lclaudio (discussão | contribs) (→Technical Details)

Phase I - Study


Title

  • SEBA - SDN Enabled Broadband Access


Objective

  • SDN-Enabled Broadband Access (SEBA) is an Exemplar Platform being built by the ONF and CORD community.


Concepts


  • SEBA is a lightweight platform based on a variant of R-CORD. It supports a multitude of virtualized access technologies at the edge of the carrier network, including PON, G.Fast, and eventually DOCSIS and more. SEBA supports both residential access and wireless backhaul and is optimized such that traffic can run ‘fastpath’ straight through to the backbone without requiring VNF processing on a server.
  • Is integrated with Kubernetes, prepared for use in high speed and operationalized with FCAPS and OSS Integration.
  • This project intends to anticipate a big trend that is to bring the features of SDN to access broadband.


Features


  • Integration with:
    • VOLTHA (Virtual OLT Hardware Abstraction): An open source project to create a hardware abstraction for broadband access equipment. It supports the principle of multi-vendor, disaggregated, “any broadband access as a service” for the Central Office. VOLTHA currently provides a common, vendor agnostic, GPON control and management system, for a set of white-box and vendor-specific PON hardware devices. With the upcoming introduction of access Technology Profiles, VOLTHA will support other access technologies like EPON, NG-PON2 and G.Fast as well. On its northbound interface, VOLTHA abstracts the PON network to appear as a programmable Ethernet switch to an SDN controller. On its southbound side, VOLTHA communicates with PON hardware devices using vendor-specific protocols through OLT and ONU adapters.
    • ONOS: The only SDN controller platform that supports the transition from legacy “brown field” networks to SDN “green field” networks. This enables exciting new capabilities, and disruptive deployment and operational cost points for network operators. ONOS is the only open source controller providing:
      • Scalability
      • High performance
      • Resiliency
      • Legacy device support
      • Next-generation device support
    • TRELLIS: Is the leading open-source SDN based, multi-purpose L2/L3 spine-leaf switching fabric for data-center (DC) networking. Leveraging the ONOS Controller, Trellis creates a non-blocking fabric for data centers using white box switching hardware and open source software. Unlike traditional networking approaches, the fabric itself does not run a control protocol (such as BGP, OSPF or RSTP). Instead, all the intelligence is moved into applications running on the clustered ONOS controller. In this way the fabric switches can be simplified, the entire fabric can be optimized by leveraging a holistic view of all activity, and new features and functionality can be deployed without upgrading the switches.


Oriented Study


Write here, the study plane and the references.


Phase II - Teaching


Content

  • GPON - GigaBit Passive Optical Networks
  • SDN - Software Defined Networking


Presentation


Metodology


Describe the metodologies.


Phase III - Example of Business Case


Benefits to the owner



Benefits to the user


Drivers



Business Models

Business Case

    Descrever um exemplo de negócio que permita avaliar a solução comercialmente


Lei do Bem


  • Projeto possui algum elemento tecnologicamente novo ou inovador?
Elemento tecnologicamente novo ou inovador pode ser entendimento como o avanço tecnológico pretendido pelo projeto, ou a hipótese que está sendo testada


  • Projeto possui barreira ou desafio tecnológico superável?
Barreira ou desafio tecnológico superável pode ser entendido como aquilo que dificulta o atingimento do avanço tecnológico pretendido, ou dificulta a comprovação da hipótese


  • Projeto utiliza metodologia/método para superação da barreira ou desafio tecnológico?
Metodologia/método para superação da barreira ou desafio tecnológico pode ser entendido como aqueles atividades que foram realizadas para superação da barreira ou do desafio tecnológico existente no projeto


  • Projeto é desenvolvido em parceira com alguma instituição acadêmica, ICT ou startup?
Se sim, o desenvolvimento tecnológico é executado por associado ou por alguma empresa terceira? qual o nome da empresa? 
Anexar cópia do contrato


Phase IV - Prototype oriented to the business


Scope


To install, configure, learn and to aplly techniques to implement the SEBA platform


Product Backlog


Describe the requisites


Tests Worksheet

  • Based on AT&T:
    • With ONUs in the `whitelist` (with couple ONUs in the list)
      • API to push ONU whitelist?
      • With a matching ONU in the whitelist and validate that the ONU is shown as `enabled`
      • With a discovered ONU that is not contained in the whitelist or the slot/pon-port information is incorrect for the ONU device.
      • A discovered ONU which has been disabled, can be re-enabled by addition to whitelist
      • An enabled ONU can be disabled by removal from whitelist
      • If an ONU is added to the whitelist (and has service), then removed, then added back its service recovers
    • Pre-provisioning of a subscriber into NEM
      • SubscriberID, S-Tag & C-Tag, NASportId, circuitId, subscriber description
      • Without discovered ONU
      • With discovered but invalid ONU
      • With valid ONU
      • With 2 ONUs on the same OLT with different S-Tag
    • RG authentication after the ONU gets into enabled state
      • Send EAPOL message from the subscriber
      • RG authentication fails if subscriber has not been provisioned
      • RG authentication passes if subscriber has been provisioned
      • RG continues to attempt authentication
    • Agg switch and NEM-AGG triggers
      • Crossconnect-service can add BNG mapping to S-VLAN [Low]
      • Crossconnect-service can add BNG mapping to ‘any’ vlan
      • After subscriber is provisioned
      • After multiple-subscribers on same OLT are provisioned with same S-VLAN, there is only 1 cross-connect in AGG switch
      • That after multiple-subscribers on same OLT are provisioned with different S-VLAN, there are multiple cross-connects in AGG switch
      • After multiple-subscribers on different OLTs are provisioned with different S-VLAN, there are corresponding cross-connects in AGG switch
      • After a subscriber is removed, the crossconnect exists if there are other subscribers with the same S-VLAN
      • After all the subscribers with the same S-VLAN are removed, then the cross-connect is also removed
      • Special crossconnects can be created - eg vlan 409
    • DHCP:
      • DHCP fails if RG has not been authenticated
      • DHCP succeeds if RG has been authenticated
    • Dataplane Failure Scenarios (needs to be fleshed out)
      • Reboot RG, ONU, OLT and Fabric Switch (Leaf attached to OLT)
      • Bring down UNI port and back up (unplug ONU LAN port and plug it back), equivalent to disconnect RG from ONU and reconnect it
      • Bring down ONU fiber and back up (unplug ONU fiber and plug it back)
      • Bring down PON port and back up (unplug PON fiber and plug it back)
      • Bring down NNI port and back up (unplug uplink cable and plug it back)
    • Control plane failure scenarios
      • VOLTHA, ONOS and NEM reboots
    • Alarm generations?
    • Verification steps in existing testcases for `onos-fabric` `onos-voltha` whenever configurations are pushed into XOS. - LOW
    • More test scenarios for subscriber `status` changes
    • Soak and Stability Tests
      • Provision subscribers and leave the POD to run for couple weeks(atleast two weeks to start with) and perform tests to validate the stability of the containers.
      • Soak test

PoC


  • Configuring SiaB:
    • The default configuration of SiaB incorporates an emulated OLT/ONU provided by Ponsim and an emulated AGG switch provided by Mininet.
    • Mininet is also configured with a host that stands in as the BNG and runs a DHCP server.
    • The Ponsim setup installs a single OLT, ONU, and RG.
    • The RG is able to authenticate itself via 802.1x, run dhclient to get an IP address from the DHCP server in Mininet, and finally ping the BNG


  • Interface SiaB:
    • Subscriber authentication
    • Show Workflow driver service instances
      • Authentication sate
      • Backend Status
      • Dhcp state
      • ONU state
    • Run DHCP cliente


  • Results:
    • SiaB is a real SEBA pod with virtual hardware
    • Good on-rampo for the community
      • About half the questions os Slack are in contect os SiaB
      • SiaB is doubling SEBAś popularitu
    • Comunity contributions to SiaB
      • USe real openflow switch + server instedad of mininet
      • supoprt for multimpes ONUs / RGs




Schedule


Historic



Researchers

  • Ana Paula Fernandes
  • Aymen Ghannouchi
  • Bruno Rodrigues Rabelo Resende
  • Luiz Cláudio Theodoro
  • Raoni Exaltação Masson
  • Willian Santos Silva


Disponível em “http://3.143.69.156/wiki/index.php?title=SEBA:_SDN_Enabled_Broadband_Access&oldid=67284”