...

Each BGP speaker potentially has multiple peering sessions to different external networks. It is possible for these peering sessions to be on different IP subnets, which means each BGP speaker can potentially have multiple IP addresses it is peering on. These addresses must be configured in the sdnip.json file, but they also need to be configured on the interfaces of the BGP speaker, so that it can receive packets sent to it on those addresses.

Running SDN-IP on ONOS

The first step is to get an ONOS system up and running, and you can read more about how to do this here <LINK>

Once ONOS is running, SDN-IP has a couple of additional dependencies that it relies on to ensure ARP requests are resolved properly. 

• onos-app-config is used to read in the addresses.json configuration file
• onos-app-proxyarp is the proxy ARP module that responds to ARP requests on behalf of hosts and external routers.

It's usually best to ensure these are loaded before starting SDN-IP, either by adding them to the ONOS_FEATURES, or by loading them manually:

onos> feature:install onos-app-config
onos> feature:install onos-app-proxyarp

Once these dependencies are satisfied, the SDN-IP application can be installed:

onos> feature:install onos-app-sdnip

At this point, SDN-IP will start up, read its configuration files and install intents in the network to establish connectivity for the BGP peering sessions. Then it will begin to receive routes, which are installed into the network using MultiPointToSinglePoint intents.

SDN-IP CLI

SDN-IP includes CLI commands that allow a user to monitor the state of the system. Each command is detailed below.

onos> bgp-neibors