This page describes the Software Defined Internet Exchange Point - Layer 3 application (SDX-L3 or sdxl3 sdx-l3 in ONOS nomenclature). SDX-L3 is an application that extends the existing SDN-IP application of ONOS in order to support software defined Internet Exchange Points (IXP), i.e. an infrastructure where various participating Service Providers (SP) can exchange traffic between their Autonomous Systems (AS).

...

SDX-L3 is implemented as the ONOS's sdxl3 sdx-l3 or org.onosproject.sdxl3sdx-l3 application. SDX-L3 integrates the SDX-related features to the existing SDN-IP functionality thus the sdnip application should be deactivated in order to activate sdxl3 sdx-l3. Additionally, since SDX-L3 implements a different proxy-ARP handling than the one implemented in the proxy-ARP application, proxyarp should be deactivated as well.

...

onos> app activate org.onosproject.sdxl3sdx-l3

SDX-L3 configuration should be placed in the network-cfg.json file in the config directory and it will be read in automatically at startup as in the SDN-IP case. The application uses a configuration identical to SDN-IP (using as subject the "org.onosproject.router" application) along with additional configuration details that are specific for SDX-L3 and are optional. The new subject is the "org.onosproject.sdxl3sdx-l3" application and the configuration details are explained below in this page. 

...

This association is supported by the sdxl3 sdx-l3 application and is introduced either by appropriate configuration in network-cfg.json file or by the command line handlers provided by the sdxl3 sdx-l3 application during ONOS run-time. Apart from the associated connection point and interface, the user is able to assign an optional name to each BGP peer.

...

"apps" : {

"org.onosproject.sdxl3sdx-l3": {
  "participants": {
    "bgpPeers": [
      {
        "name": "AS1-Router1",
        "ip": "10.0.1.1",
        "connectPoint": "of:00000000000000a1/1",
        "intfName": "AS1-conn1"
  }]}}}

...

• Internal BGP speakers should support route server functionality (this is not related with ONOS itself).
• The feature for the association of peers with interfaces should be supported.
• Proxy-ARP functionality handles (and not reject) ARP requests between configured border routers of SPs, i.e. external BGP peers.
• Since sdxl3 sdx-l3 implements its own proxy-ARP handling, when activating sdxl3 sdx-l3 application, the ONOS proxyarp application should be deactivated.

...

Code

Currently the code for sdxl3 sdx-l3 application can be found in the ONOS sample application repository: https://gerrit.onosproject.org/onos-app-samples. 

...