Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

bgp-routes [-j|--json] [s|--summary]

Shows best routes received from all BGP peers. Note this is not the final set of routes that gets pushed to the data plane, because these routes first go through the BGP decision process, including BGP specific information.

routes [-j|--json] [s|--summary]

Shows the routing table of SDN-IP. The routes shown here are the result of running the BGP decision process all received routesThis should be mostly the same as the BGP routes, but may include routes from other sources.

Troubleshooting

A full running SDN-IP system has a lot of pieces that need to be correct before anything will work. When setting up a system for the first time or when things go wrong, it's best to go step by step to check each piece is in place.

...

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.

Check the BGP peering sessions are established with the internal BGP speakers. If the peering sessions are not established, it may be that the sdnip.json configuration is wrong. If it seems to be correct, check the configuration of the BGP peers.

Check the configuration files are in the correct directory.

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

Code Block
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:

Code Block
onos> routes

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

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.

Code Block
onos> intents -s

Once intents are installed, there should be transit connectivity through the SDN network. 

Questions? Comments? Problems?

Please let us know via the onos-deploy mailing list. Details about ONOS mailing lists can be found here: ONOS Mailing Lists

We really welcome your help to ensure the code and documentation are clear and informative, so let us know if you have and issues.