Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
In addition to the network configuration described above, there is a separate configuration file for the SDN-IP software component. Currently there is one configurable parameter, the port that SDN-IP listens for incoming BGP connections on. If you wish to configure this parameter, place this file at KARAF_ROOT/etc/org.onosproject.sdniprouting.bgp.SdnIpBgpSessionManager.cfg. Note that by default ONOS listens on TCP port number 2000 for incoming BGP connections, which is not the default BGP port number 179.
| Code Block |
|---|
bgpPort=2000 |
ONOS-1.1 0 (Avocet) note: In ONOS-1.1 0 the above configuration should be placed in file KARAF_ROOT/etc/org.onosproject.routingsdnip.bgpSdnIp.BgpSessionManager.cfg.
BGP speakers
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.
...
Once ONOS is running, SDN-IP has a couple of additional application dependencies that it relies on to ensure ARP requests are resolved properly.
onos-app-configisorg.onosproject.configis used to read in theaddresses.jsonconfiguration fileonos-app-proxyarpisorg.onosproject.proxyarpis the proxy ARP module application 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_FEATURESAPPS variable in your cell file, or by loading them manually:
| Code Block |
|---|
onos> feature:install onos-app-app activate org.onosproject.config onos> app feature:install onos-app-activate org.onosproject.proxyarp |
Once these dependencies are satisfied, the SDN-IP application can be installedactivated:
| Code Block |
|---|
onos> app feature:install onos-app-activate org.onosproject.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.
...
Check SDN-IP is installed:
| Code Block |
|---|
onos> feature:listapps -s | grep sdnip onos-app-sdnip* | 1.0.04 org.onosproject.sdnip | x | onos-11.3.0.0 | SNAPSHOT SDN-IP peering application |
The little x * in the 3rd 1st column means SDN-IP is installedactivated. If it's not there, try install activate it again.
Check whether the external routers can resolve ARP properly. If they can't resolve ARP, then look in the addresses.json file and check that the address configuration is correct.
...