...

There are two parts to the configuration of the vRouter application. vRouter is effectively turning an OpenFlow switch into a router. This means we need to configure 'interfaces' on the switch, just as you'd do for a regular router. Of course, seeing as it is an OpenFlow switch, the switch itself has no knowledge of this interface configuration, but rather it is a logical configuration the the vRouter application uses to do its job of controlling the switch as though it was a router.

Check out the Network Configuration Service for information on how to upload configuration to ONOS.

The interface configuration in ONOS looks like this:

...

Note that you do not have to configure an interface on the port that is connected to Quagga - this configuration is only for ports that are connected to other routers. .

The other piece of configuration is for the vRouter to identify the switch that will be used for the dataplane, as well as the connection point of the Quagga instance. That looks like this:

{
    "apps" : {
        "org.onosproject.router" : {
            "router" : {
                "controlPlaneConnectPoint" : "of:00000000000000b1/5",
                "ospfEnabled" : "true"
            }
        }
    }
}

Once these two configuration sections have been uploaded to ONOS, the vRouter application should be ready to run.

Running the application

Log in to your ONOS cluster and start the vRouter application.

...

This will start the vRouter application and open the port listening for incoming FPI connections from Quagga. Quagga should be configured to connect to ONOS at the correct ip:port.

If Quagga has sent routes to ONOS, they should be visible using the routes command in ONOS:

onos> routes

Mininet-based development environment

Coming soon.