...

Are all the BGP sessions between the external routers and the BGP speakers up? To be either checked from the external routers or from the BGP speakers

Are the BGP sessions between the BGP speakers and SDN-IP up? To be checked from on the BGP speakers or from SDN-IP (below)

onos> bgp-neighbors

Has SDN-IP received the routes?

onos> intents -s
onos> intentsroutes

Once you see routes in SDN-IP it's time to check if these get transformed into intents. Each route should correspond to a If you don't see any multi-point-to-single-point intent

Next, check that the internal BGP speakers are peering with ONOS correctly:

onos> bgp-neighbors

You should see a list of internal BGP speakers. If not, check that the connectivity is OK and the BGP configuration in the BGP speaker is correct.

Then, check if ONOS receives the expected routes:

onos> routes

If the routes are not received, check if the internal BGP speaker has received the routes and advertised them to ONOS.

In addition, you could use the following command to see BGP-specific information about the received routes:

onos> bgp-routes

Once the routes are received, ONOS will start to install MultiPointToSinglePoint intents for each route. You can check this is correct by looking at the number of MultiPointToSinglePoint intents in the intent summary. It should be the same as the number of routes, and all intents should move to the INSTALLED state before long.

onos> intents -s

...

onos> intents -s
onos> intents

Likely if intents are wrong, your SDN-IP configuration is wrong.

If intents have been installed all correctly but still things don't work, last thing is to check if corresponding flows got installed correctly. The following commands can help you to see what's going on.

Is there any flow in pending add (meaning that ONOS / the switch are not able to add)?

onos> flows
onos> flows pending_add

Questions? Comments? Problems?

...